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
- 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
- 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 CloudCatalyst
- Using NetBackup CloudCatalyst to upload deduplicated data to the cloud
- Configuring a CloudCatalyst storage server for deduplication to the cloud
- 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
- Troubleshooting
- About unified logging
- About legacy logging
- Troubleshooting MSDP installation issues
- Troubleshooting MSDP configuration issues
- Troubleshooting MSDP operational issues
- Troubleshooting CloudCatalyst issues
- CloudCatalyst logs
- Problems encountered while using the Cloud Storage Server Configuration Wizard
- Disk pool problems
- Problems during cloud storage server configuration
- CloudCatalyst troubleshooting tools
- Appendix A. Migrating to MSDP storage
About trusted master servers for Auto Image Replication
NetBackup provides the ability to establish a trust relationship between replication domains. A trust relationship is optional. The following items describe how a trust relationship affects Auto Image Replication:
With Targeted A.I.R., when establishing trust between the source and the remote target server, you need to establish trust in both the domains.
In the source master server, add the target master server as a trusted server.
In the target master server, add the source master server as a trusted server.
The following diagram illustrates the different tasks for adding trusted master servers.
Table: Tasks to establish a trust relationship between master servers for Targeted A.I.R.
Step | Task | Procedure |
---|---|---|
Step 1 | Administrators of both the source and target master servers must obtain each other's CA certificate fingerprint and authorization tokens or the user credentials. This activity must be performed offline. Note: Veritas recommends using an authentication token to connect to the remote master server. An authentication token provides restricted access and allows secure communication between both the hosts. The use of user credentials (user name and password) may present a possible security breach. | To obtain the authorization tokens, use the bpnbat command to login and nbcertcmd to get the authorization tokens. To obtain the SHA1 fingerprint of root certificate, use the nbcertcmd -displayCACertDetail command. To perform this task, see the NetBackup Commands Reference Guide. Note: When you run the commands, keep the target as the remote server. |
Step 2 | Establish trust between the source and the target domains.
| To perform this task in the Veritas Administration Console, see the following topic: See Adding a trusted master server. To perform this task using the nbseccmd, see the NetBackup Commands Reference Guide. |
Step 3 | After you have added the source and target trusted servers, they have each other's host ID-based certificates. The certificates are used during each communication. Master Server A has a certificate issued by Master Server B and vice versa. Before communication can occur, Master Server A presents the certificate issued by Master Server B and vice versa. The communication between the source and target master servers is now secured. | To understand the use of host ID-based certificates, see the Veritas Security and Encryption Guide. |
Step 4 | Create an import storage lifecycle policy in the target domain. | |
Step 5 | Create a replication storage lifecycle policy in the source domain using the specific target master server and storage lifecycle policy. The backups that are generated in one NetBackup domain can be replicated to storage in one or more target NetBackup domains. | |
Step 6 | The backups that are generated in one NetBackup domain can be replicated to storage in one or more target NetBackup domains. This process is referred to as Auto Image Replication. |
If your source and target trusted servers use different NetBackup versions, consider the following.
Note:
When you upgrade both the source and the target master server to version 8.1 or later, you need to update the trust relationship. Run the following command:
nbseccmd -setuptrustedmaster -update
See the NetBackup Commands Reference Guide.
Table: Trust setup methods for different NetBackup versions
Source server version | Target server version | Trust setup method |
---|---|---|
8.1 and later | 8.1 and later | Add a trusted master server using authorization token. Complete action on both the servers. |
8.1 and later | 8.0 or earlier | On the source server, add the target as the trusted master server using the remote (target) server's credentials. |
8.0 or earlier | 8.1 and later | On the source server, add the target as the trusted master server using the remote (target) server's credentials. |