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 Key Management Server 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
- Running MSDP services with the non-root user
- 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 bucket-level immutable storage support for Google Cloud Storage
- About object-level immutable storage support for Google Cloud Storage
- About AWS IAM Role Anywhere support
- About Azure service principal support
- About NetBackup support for AWS Snowball Edge
- 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
- Disaster recovery in S3 interface for MSDP
- 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
- Configuring and using universal shares
- Configuring universal share user authentication
- Using the ingest mode
- Enabling a universal share with object store
- Configure a universal share accelerator
- About the universal share accelerator quota
- Configuring isolated recovery environment (IRE)
- Configuring an isolated recovery environment using the web UI
- Configuring an isolated recovery environment using the command line
- Using the NetBackup Deduplication Shell
- Managing users from the deduplication shell
- About the external MSDP catalog backup
- 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 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 Auto Image Replication (A.I.R.)
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 (A.I.R.).
Table: Supported A.I.R. models
Model | Description |
---|---|
One-to-one model | A single production datacenter can back up to a disaster recovery site. |
One-to-many model | A single production datacenter can back up to multiple disaster recovery sites. |
Many-to-one model | Remote offices in multiple domains can back up to a storage device in a single domain. |
Many-to-many model | Remote datacenters in multiple domains can back up multiple disaster recovery sites. |
NetBackup supports the following storage types for A.I.R.:
Media Server Deduplication Pool (MSDP)
An OpenStorage disk appliance that supports replication
NetBackup uses storage lifecycle policies (SLP) in the source domain and the target domain to manage A.I.R. operations. The following table is a process overview of A.I.R., generally describing the events in the originating and target domains.
Table: Process overview of A.I.R.
Event | Domain in which an event occurs | Event description |
---|---|---|
1 | The originating primary server (Domain 1) | Clients are backed up according to a backup policy that indicates a storage lifecycle policy as the policy storage selection. After the backup, images are replicated from the original domain to the target domain. |
2 | The target primary server (Domain 2) | The storage server in the target domain recognizes that a replication event has occurred. It notifies the NetBackup primary server in the target domain. |
3 | The target primary server (Domain 2) | NetBackup imports the image immediately, based on an SLP that contains an import operation. |
4 | The target primary server (Domain 2) | After the image is imported into the target domain, NetBackup continues to manage the copies in that domain. |
Figure: Typical A.I.R. setup is a typical A.I.R. setup that shows an image that is replicated from one source domain to one target domain.
NetBackup provides the ability to establish a trust relationship between replication domains. A trust relationship is optional for an MSDP as the target storage.
The following items describe how a trust relationship affects A.I.R.:
No trust relationship - NetBackup replicates to all defined target storage servers. You cannot select a specific host or hosts as a target.
Trust relationship - You can select a subset of your trusted domains as a target for replication. NetBackup only replicates to the specified domains rather than to all configured replication targets. This type of A.I.R. is known as targeted A.I.R.
To set up a primary server for A.I.R.
- Open the web UI.
- At the top right, click Settings > Global security.
- Select the Trusted primary servers tab.
- Click Add.
- Enter the remote primary server name.
- On the Validate CA tab, click Next to confirm the entry.
- On the Verify CA fingerprint tab, review and click Next.
- On the Select authentication method tab, select one of the following:
Select Specify authentication token of the trusted primary server and enter the token in the token field.
Select Specify credentials of the trusted primary server and enter the username and password.
- Repeat these steps in the target domain. Use the source primary server name as the primary server name in the Validate Certificate Authority field.
- Configure storage server at both source domain and target domain.
The image is replicated from one storage server in the source domain to one storage server in the target domain. The image is needed to configure the MSDP at the source domain and the target domain.
Use the NetBackup web UI to configure the MSDP storage server, disk pool, and storage unit.
MSDP supports secure communications between two media servers from two different NetBackup domains. The secure communication is set up when you run A.I.R.. The two media servers must use the same CA to do the certificate security check. The source MSDP server uses the Certificate Authority (CA) of the target NetBackup domain and the certificate that the target NetBackup domain authorized. You must manually deploy CA and the certificate on the source MSDP server before using A.I.R.
To configure the NetBackup CA and a NetBackup host ID-based certificate
- On the source MSDP storage server, run the following command to get the NetBackup CA from the target NetBackup primary server:
Windows:
install_path\NetBackup\bin \nbcertcmd -getCACertificate -server target_primary_server
UNIX:
/usr/openv/netbackup/bin /nbcertcmd -getCACertificate -server target_primary_server
- On the source MSDP storage server, run the following command to get the certificate generated by target NetBackup primary server:
Windows:
install_path\NetBackup\bin \nbcertcmd -getCertificate -server target_primary_server -token token_string
UNIX:
/usr/openv/netbackup/bin /nbcertcmd -getCertificate -server target_primary_server -token token_string
Images are replicated from source domain MSDP storage server to target domain MSDP storage server. The target MSDP server is the replication target of the source MSDP server. Set up the replication target at the source domain.
To set up the replication target
- On the primary server of the source domain, open the NetBackup Administration Console, select Media and Device Management > Credentials > Storage Servers.
- Double-click on the source domain MSDP server.
- In the Replication tab, click on Add. Fill in the required information.
The Target storage server name is the host name of the MSDP storage server in the target domain. The username and password are the credentials that are used to configure the MSDP server in the target domain.
To run a target A.I.R., you need to create an SLP at both the source domain and the target domain. Follow the procedures in Table: To configure an SLP.
Table: To configure an SLP
At target domain: |
|
At source domain: |
|
Create a backup policy to perform a backup and run the SLP. | At the source domain, create a backup and use the SLP as the policy storage. Run the backup and after the backup runs, the replication job at the source domain runs. After a short period of time, the import job at the target domain runs. The target domain manages the replicated image at the target storage server. |