NetBackup™ Deduplication Guide
- Introducing the NetBackup media server deduplication option
- Quick start
- 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
- MSDP cloud support
- About MSDP cloud support
- Cloud space reclamation
- About the disaster recovery for cloud LSU
- About Image Sharing using MSDP cloud
- About MSDP cloud immutable (WORM) storage support
- About immutable object support for AWS S3
- About immutable object support for AWS S3 compatible platforms
- About immutable storage support for Azure blob storage
- About immutable storage support for Google Cloud Storage
- S3 Interface for MSDP
- Configuring S3 interface for MSDP on MSDP build-your-own (BYO) server
- Identity and Access Management (IAM) for S3 interface for MSDP
- S3 APIs for S3 interface for MSDP
- Monitoring deduplication activity
- 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
- Configuring and using universal shares
- Using the ingest mode
- Enabling a universal share with object store
- Configuring isolated recovery environment (IRE)
- Using the NetBackup Deduplication Shell
- Managing users from the deduplication shell
- Managing certificates from the deduplication shell
- Managing NetBackup services from the deduplication shell
- Monitoring and troubleshooting NetBackup services from the deduplication shell
- Managing S3 service from the deduplication shell
- Troubleshooting
- About unified logging
- About legacy logging
- Troubleshooting MSDP installation issues
- Troubleshooting MSDP configuration issues
- Troubleshooting MSDP operational issues
- Trouble shooting multi-domain issues
- Appendix A. Migrating to MSDP storage
- Appendix B. Migrating from Cloud Catalyst to MSDP direct cloud tiering
- About direct migration from Cloud Catalyst to MSDP direct cloud tiering
- Appendix C. Encryption Crawler
About MSDP mutli-domain VLAN Support
MSDP supports multi-domain NetBackup setups. In a multi-domain set-up, it is important for primary servers from other domains to connect with the MSDP storage server and the primary server of the NetBackup domain that contains the MSDP server. The primary 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 |
---|---|
|
|
primaryA
is the primary 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 web UI > Storage > Storage Configurations > Storage Servers, click and select .
Run following command on
mediaA
to create a new MSDP usertestuser1
with passwordtestuser1pass
:spauser -a -u "testuser1" -p "testuser1pass" --role admin
Servers in the domain B can only access IP like 10.XX.40.*, so
primaryA2
is used as the primary server host name of domain A.Run following command on
mediaB
to get a CA certificate and a host certificate fromprimaryA
:nbcertcmd -GetCACertificate -server primaryA2
nbcertcmd -GetCertificate -server primaryA2 -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 primary server:
Create an MSDP OpenStorage server on
mediaB
of NetBackup domain B.(NetBackup web UI > Storage > Storage Configurations > Storage Servers, click and select .
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.*
In a multi-domain NetBackup configuration, there are times when the media server in domain B must know the server certificate of the media server in domain A. For example, this setup is required when a VMware image recovery is performed from domain A to domain B.
To move mediaA2
's server certificate to mediaB
is a two-step process, and you need to be a privileged user to run the following steps:
Transfer a copy of the NGINX server certificate (
/etc/nginx/keys/spws.cert
) frommediaA2
tomediaB
.Run the following command on
mediaB
to import that certificate tomediaB
's trusted keystore.Note:
The
storepass
andkeypass
values can be found in/usr/openv/var/global/jkskey
onmediaB
.% /usr/openv/java/jre/bin/keytool -keystore /usr/openv/var/global/wsl/credentials/truststoreMSDP.bcfks -storetype BCFKS -providername BCFIPS -providerclass org.bouncycastle.jcajce.provider.BouncyCastleFipsProvider -provider org.bouncycastle.jcajce.provider.BouncyCastleFipsProvider -providerpath /usr/openv/analyticscollector/lib/bc-fips-1.0.2.3.jar -storepass 28e523bc7ddfcf91 -keypass 28e523bc7ddfcf91 -alias net126-host161.cdc.veritas.com -import -file spws.cert
Note:
Your version of the
bc-fips-X.X.X.X.jar
file can be different than the one in the previous example. Search that directory forbc-fips*
to find the right version for your NetBackup installation.When you run the -list command on
mediaB
, you should see something similar to the following example:% /usr/openv/java/jre/bin/keytool -list -keystore /usr/openv/var/global/wsl/credentials/truststoreMSDP.bcfks -storetype BCFKS -providername BCFIPS -providerclass org.bouncycastle.jcajce.provider.BouncyCastleFipsProvider -provider org.bouncycastle.jcajce.provider.BouncyCastleFipsProvider -providerpath /usr/openv/analyticscollector/lib/bc-fips-1.0.2.3.jar -storepass 28e523bc7ddfcf91 Keystore type: BCFKS Keystore provider: BCFIPS Your keystore contains 2 entries ca1, Jan 11, 2023, trustedCertEntry, Certificate fingerprint (SHA-256): 4A:52:C8:9E:B1:1F:A9:21:99:3B:AA:5A:0C:B5:C3:2F:51:(string continues) mediaA2, Jan 16, 2023, trustedCertEntry, Certificate fingerprint (SHA-256): AE:34:D1:63:B1:94:33:8C:07:5D:9A:D6:2B:CF:5B:52:D7:(string continues)
The second certificate that is listed is that of
mediaA2
.
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.