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
- 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 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
- 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
- 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
- Appendix A. Migrating to MSDP storage
Configuring the NetBackup client-side deduplication to support multiple interfaces of MSDP
If you have network configurations like VLAN or Subnet with NetBackup client, then the MSDP server has multiple network interfaces. These interfaces are connected to different switches or VLANs. As MSDP has only one storage server, NetBackup clients cannot access the MSDP server using the storage server name. The deduplication can fail on the clients.
You can add support for up to 30 interfaces.
Run the following steps to use the cacontrol command option (Location: /usr/openv/pdde/pdcr/bin/) to configure MSDP and specify the network interfaces that the NetBackup client can use:
- Log on the MSDP server.
- Use the following command to add the alternate interfaces:
cacontrol --interface add msdp-a.server.com
You can remove an added interface using the following command:
cacontrol --interface remove msdp-a.server.com
- Use either of the following options to validate the interface configuration:
cacontrol --interface list
bpstsinfo -si -storage_server msdp-a.server.com -stype PureDisk
Location of the bpstsinfo command: /usr/openv/netbackup/bin/admincmd/
- Configure the NetBackup client-side deduplication backup policy and run the backup operation.