Veritas NetBackup™ Deduplication Guide
- Introducing the NetBackup media server deduplication option
- Planning your deployment
- About MSDP storage and connectivity requirements
- About NetBackup media server deduplication
- About NetBackup Client Direct deduplication
- About MSDP remote office client deduplication
- About MSDP performance
- About MSDP stream handlers
- MSDP deployment best practices
- Provisioning the storage
- Licensing deduplication
- Configuring deduplication
- Configuring the Deduplication Multi-Threaded Agent behavior
- Configuring the MSDP fingerprint cache behavior
- Configuring MSDP fingerprint cache seeding on the storage server
- About MSDP Encryption using NetBackup KMS service
- Configuring a storage server for a Media Server Deduplication Pool
- Configuring a disk pool for deduplication
- Configuring a Media Server Deduplication Pool storage unit
- About MSDP optimized duplication within the same domain
- Configuring MSDP optimized duplication within the same NetBackup domain
- Configuring MSDP replication to a different NetBackup domain
- About NetBackup Auto Image Replication
- Configuring a target for MSDP replication to a remote domain
- Creating a storage lifecycle policy
- Resilient Network properties
- Editing the MSDP pd.conf file
- About protecting the MSDP catalog
- Configuring an MSDP catalog backup
- About NetBackup WORM storage support for immutable and indelible data
- Configuring deduplication to the cloud with NetBackup Cloud Catalyst
- Using NetBackup Cloud Catalyst to upload deduplicated data to the cloud
- Configuring a Cloud Catalyst storage server for deduplication to the cloud
- MSDP cloud support
- About MSDP cloud support
- Monitoring deduplication activity
- Viewing MSDP job details
- Managing deduplication
- Managing MSDP servers
- Managing NetBackup Deduplication Engine credentials
- Managing Media Server Deduplication Pools
- Changing a Media Server Deduplication Pool properties
- Configuring MSDP data integrity checking behavior
- About MSDP storage rebasing
- Managing MSDP servers
- Recovering MSDP
- Replacing MSDP hosts
- Uninstalling MSDP
- Deduplication architecture
- Troubleshooting
- About unified logging
- About legacy logging
- Troubleshooting MSDP installation issues
- Troubleshooting MSDP configuration issues
- Troubleshooting MSDP operational issues
- Troubleshooting Cloud Catalyst issues
- Cloud Catalyst logs
- Problems encountered while using the Cloud Storage Server Configuration Wizard
- Disk pool problems
- Problems during cloud storage server configuration
- Cloud Catalyst troubleshooting tools
- Trouble shooting multi-domain issues
- Appendix A. Migrating to MSDP storage
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.