Ransomware attackers specifically target and attempt to destroy backup systems to increase the probability of payment. Hardening your system is critical. Please ensure you have reviewed your platform security using the Security Hardening Checklist
Cohesity

COHESITY Documentation

Explore our documentation to get started, discover products & new features, access troubleshooting guides, register sources, platforms support.

Products
Data Security Alliance
Visit Cohesity.com
Demos
Support
Blogs
Developers
Partner Portals
Cohesity Community
© 2026 Cohesity, Inc. All Rights Reserved.
Terms of Use|
Privacy Policy|
Legal|
  1. Home
  2. Veritas NetBackup™ Deduplication Guide
  3. MSDP cloud support
  4. About backward compatibility support
Veritas NetBackup™ Deduplication Guide

About backward compatibility support

If an Auto Image Replication (A.I.R) source storage server has NetBackup 8.2 or earlier, the target disk volume cannot be a cloud LSU.

To replicate image from an earlier version of an MSDP server to the cloud LSU of target MSDP server, you need a user name with the cloud LSU name when you add the A.I.R target. The format of the user name with the target cloud LSU is:

<username>?LSU=<target cloud LSU>

For example, there is a target storage server and user name of the server is userA and there is a cloud LSU s3cloud1 in the target storage server. To replicate image from an old storage server to the cloud LSU of the target server, you can use the following user name while adding the A.I.R target:

userA?LSU=s3cloud1

You must also create an import SLP to local volume of target storage server in the target master server. Then select the imported SLP while creating the target A.I.R SLP on the source side. When A.I.R runs, the import job in target side shows the policy name as SLP_No_Target_SLP in the Activity Monitor, but the data is sent to cloud.

If the NetBackup client version is 8.2 or earlier, the client direct backup from the old client to cloud LSU of one storage server might fail. During the backup if mtstrmd is used on the client side, the job fails with a media write error. To disable mtstrmd at the client side, open the configuration file pd.conf on the client and change the following:

MTSTRM_BACKUP_ENABLED = 1 to MTSTRM_BACKUP_ENABLED = 0.

The pd.conf file is located in the following directories:

  • UNIX

    /usr/openv/lib/ost-plugins/

  • Windows

    install_path\Veritas\NetBackup\bin\ost-plugins

When doing a client direct backup with a cloud LSU and an old client, the client does only client-side deduplication.

To use cloud LSU, the load balance server of the storage server must not be an earlier version (NetBackup 8.2 or earlier). If there are new and old load balancers, new load balance server is selected automatically to make sure that the job can be done successfully. When you are restoring a backup image on cloud LSU and you select the media server explicitly, the media server selected must not be an earlier version of NetBackup.

Feedback

Was this page helpful?
Previous

Configuring AIR to use cloud LSU

Next

About the configuration items in cloud.json, contentrouter.cfg and spa.cfg

Feedback

Was this page helpful?