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 MSDP mutli-domain VLAN Support
MSDP supports multi-domain NetBackup setups. In a multi-domain set-up, it is important for master servers from other domains to connect with the MSDP storage server and the master server of the NetBackup domain that contains the MSDP server. The master servers and media servers must have multiple network interfaces and host names in a multi-domain setup.
When you configure MSDP VLAN, the local NetBackup domain and the other NetBackup domain must have the NetBackup version 8.2 or later.
The following table describes the hierarchy that is used in the example:
NetBackup domain A | NetBackup domain B |
---|---|
|
|
masterA
is the master server of domain A and has two host names and IP addresses. mediaA
is the media server of domain A and has two host names and IP addresses. MSDP storage server is created on media server mediaA
.
To let domain B access the MSDP storage server on mediaA
of domain A, run the following steps:
Create an MSDP storage server on media server
mediaA
of NetBackup domain A. (NetBackup Administration Console > Media and Device Management > Configure Disk storage servers > Media Server Deduplication Pool)Run following command on
mediaA
to create a new MSDP usertestuser1
with passwordtestuser1pass
:spauser -a -u "testuser1" -p "testuser1pass"
Servers in the domain B can only access IP like 10.XX.40.*, so
masterA2
is used as the master server host name of domain A.Run following command on
mediaB
to get a CA certificate and a host certificate frommasterA
:nbcertcmd -GetCACertificate -server masterA2
nbcertcmd -GetCertificate -server masterA2 -token <token_string>
If the nbcertcmd - GetCACertificate displays the error "The server name does not match any of the host names listed in the server's certificate", refer to the following article to add more host name to master server:
Create an MSDP OpenStorage server on
mediaB
of NetBackup domain B. NetBackup Administration Console > Media and Device Management > Configure Disk storage servers > OpenStorage).The OpenStorage server name
mediaA2
is used as the host name that has the IP address 10.XX.40.*.OpenStorage server type is PureDisk, user name is
testuser1
, and password istestuser1pass
. You must enter the server type as PureDisk.
Now mediaB
of NetBackup domain B can use the MSDP storage server mediaA2
and the network IP address 10.XX.40.*
If an external CA is used in the NetBackup setup, you do not need to run the nbcertcmd - GetCACertificate and the nbcertcmd - GetCertificate commands. If NetBackup domain A and NetBackup domain B do not use the same external CA, you must synchronize the external root CA between the two NetBackup domains for MSDP communication. If the servers have multiple host names, then the Subject Alternative Name field of the external certificate must contain all the host names.