NetBackup™ Deduplication Guide
- Introducing the NetBackup media server deduplication option
- Quick start
- Planning your deployment
- Planning your MSDP deployment
- NetBackup naming conventions
- About MSDP deduplication nodes
- About the NetBackup deduplication destinations
- About MSDP storage capacity
- About MSDP storage and connectivity requirements
- About NetBackup media server deduplication
- About NetBackup Client Direct deduplication
- About MSDP remote office client deduplication
- About the NetBackup Deduplication Engine credentials
- About the network interface for MSDP
- About MSDP port usage
- About MSDP optimized synthetic backups
- About MSDP and SAN Client
- About MSDP optimized duplication and replication
- About MSDP performance
- About MSDP stream handlers
- MSDP deployment best practices
- Use fully qualified domain names
- About scaling MSDP
- Send initial full backups to the storage server
- Increase the number of MSDP jobs gradually
- Introduce MSDP load balancing servers gradually
- Implement MSDP client deduplication gradually
- Use MSDP compression and encryption
- About the optimal number of backup streams for MSDP
- About storage unit groups for MSDP
- About protecting the MSDP data
- Save the MSDP storage server configuration
- Plan for disk write caching
- Provisioning the storage
- Licensing deduplication
- Configuring deduplication
- Configuring MSDP server-side deduplication
- Configuring MSDP client-side deduplication
- About the MSDP Deduplication Multi-Threaded Agent
- Configuring the Deduplication Multi-Threaded Agent behavior
- Configuring deduplication plug-in interaction with the Multi-Threaded Agent
- About MSDP fingerprinting
- About the MSDP fingerprint cache
- Configuring the MSDP fingerprint cache behavior
- About seeding the MSDP fingerprint cache for remote client deduplication
- Configuring MSDP fingerprint cache seeding on the client
- Configuring MSDP fingerprint cache seeding on the storage server
- Enabling 400 TB support for MSDP
- About MSDP Encryption using NetBackup KMS service
- About MSDP Encryption using external KMS server
- Configuring a storage server for a Media Server Deduplication Pool
- About disk pools for NetBackup deduplication
- Configuring a disk pool for deduplication
- Creating the data directories for 400 TB MSDP support
- Adding volumes to a 400 TB Media Server Deduplication Pool
- Configuring a Media Server Deduplication Pool storage unit
- Configuring client attributes for MSDP client-side deduplication
- Disabling MSDP client-side deduplication for a client
- About MSDP compression
- About MSDP encryption
- MSDP compression and encryption settings matrix
- Configuring encryption for MSDP backups
- Configuring encryption for MSDP optimized duplication and replication
- About the rolling data conversion mechanism for MSDP
- Modes of rolling data conversion
- MSDP encryption behavior and compatibilities
- Configuring optimized synthetic backups for MSDP
- About a separate network path for MSDP duplication and replication
- Configuring a separate network path for MSDP duplication and replication
- About MSDP optimized duplication within the same domain
- Configuring MSDP optimized duplication within the same NetBackup domain
- About MSDP replication to a different domain
- Configuring MSDP replication to a different NetBackup domain
- About NetBackup Auto Image Replication
- About trusted primary servers for Auto Image Replication
- About the certificate to be used for adding a trusted master server
- Adding a trusted master server using a NetBackup CA-signed (host ID-based) certificate
- Adding a trusted primary server using external CA-signed certificate
- Removing a trusted primary server
- Enabling NetBackup clustered primary server inter-node authentication
- Configuring NetBackup CA and NetBackup host ID-based certificate for secure communication between the source and the target MSDP storage servers
- Configuring external CA for secure communication between the source MSDP storage server and the target MSDP storage server
- Configuring a target for MSDP replication to a remote domain
- About configuring MSDP optimized duplication and replication bandwidth
- About performance tuning of optimized duplication and replication for MSDP cloud
- About storage lifecycle policies
- About the storage lifecycle policies required for Auto Image Replication
- Creating a storage lifecycle policy
- About MSDP backup policy configuration
- Creating a backup policy
- Resilient Network properties
- Specifying resilient connections
- Adding an MSDP load balancing server
- About variable-length deduplication on NetBackup clients
- About the MSDP pd.conf configuration file
- Editing the MSDP pd.conf file
- About the MSDP contentrouter.cfg file
- About saving the MSDP storage server configuration
- Saving the MSDP storage server configuration
- Editing an MSDP storage server configuration file
- Setting the MSDP storage server configuration
- About the MSDP host configuration file
- Deleting an MSDP host configuration file
- Resetting the MSDP registry
- About protecting the MSDP catalog
- Changing the MSDP shadow catalog path
- Changing the MSDP shadow catalog schedule
- Changing the number of MSDP catalog shadow copies
- Configuring an MSDP catalog backup
- Updating an MSDP catalog backup policy
- About MSDP FIPS compliance
- Configuring the NetBackup client-side deduplication to support multiple interfaces of MSDP
- About MSDP multi-domain support
- About MSDP application user support
- About MSDP mutli-domain VLAN Support
- About NetBackup WORM storage support for immutable and indelible data
- MSDP cloud support
- About MSDP cloud support
- Create a Media Server Deduplication Pool (MSDP) storage server in the NetBackup web UI
- Creating a cloud storage unit
- Updating cloud credentials for a cloud LSU
- Updating encryption configurations for a cloud LSU
- Deleting a cloud LSU
- Backup data to cloud by using cloud LSU
- Duplicate data cloud by using cloud LSU
- Configuring AIR to use cloud LSU
- About backward compatibility support
- About the configuration items in cloud.json, contentrouter.cfg, and spa.cfg
- About the tool updates for cloud support
- About the disaster recovery for cloud LSU
- About Image Sharing using MSDP cloud
- About restore from a backup in Microsoft Azure Archive
- About MSDP cloud immutable (WORM) storage support
- Monitoring deduplication activity
- Monitoring the MSDP deduplication and compression rates
- Viewing MSDP job details
- About MSDP storage capacity and usage reporting
- About MSDP container files
- Viewing storage usage within MSDP container files
- Viewing MSDP disk reports
- About monitoring MSDP processes
- Reporting on Auto Image Replication jobs
- Managing deduplication
- Managing MSDP servers
- Viewing MSDP storage servers
- Determining the MSDP storage server state
- Viewing MSDP storage server attributes
- Setting MSDP storage server attributes
- Changing MSDP storage server properties
- Clearing MSDP storage server attributes
- About changing the MSDP storage server name or storage path
- Changing the MSDP storage server name or storage path
- Removing an MSDP load balancing server
- Deleting an MSDP storage server
- Deleting the MSDP storage server configuration
- Managing NetBackup Deduplication Engine credentials
- Managing Media Server Deduplication Pools
- Viewing Media Server Deduplication Pools
- Determining the Media Server Deduplication Pool state
- Changing OpenStorage disk pool state
- Viewing Media Server Deduplication Pool attributes
- Setting a Media Server Deduplication Pool attribute
- Changing a Media Server Deduplication Pool properties
- Clearing a Media Server Deduplication Pool attribute
- Determining the MSDP disk volume state
- Changing the MSDP disk volume state
- Inventorying a NetBackup disk pool
- Deleting a Media Server Deduplication Pool
- Deleting backup images
- About MSDP queue processing
- Processing the MSDP transaction queue manually
- About MSDP data integrity checking
- Configuring MSDP data integrity checking behavior
- About managing MSDP storage read performance
- About MSDP storage rebasing
- About the MSDP data removal process
- Resizing the MSDP storage partition
- How MSDP restores work
- Configuring MSDP restores directly to a client
- About restoring files at a remote site
- About restoring from a backup at a target master domain
- Specifying the restore server
- Managing MSDP servers
- Recovering MSDP
- Replacing MSDP hosts
- Uninstalling MSDP
- Deduplication architecture
- Configuring and using universal shares
- About Universal Shares
- Configuring and using an MSDP build-your-own (BYO) server for Universal Shares
- MSDP build-your-own (BYO) server prerequisites and hardware requirements to configure Universal Shares
- Configuring Universal Share user authentication
- Mounting a Universal Share created from the NetBackup web UI
- Creating a Protection Point for a Universal Share
- Using the ingest mode
- Changing the number of vpfsd instances
- Upgrading to NetBackup 10.0
- Troubleshooting
- About unified logging
- About legacy logging
- NetBackup MSDP log files
- Troubleshooting MSDP installation issues
- Troubleshooting MSDP configuration issues
- Troubleshooting MSDP operational issues
- Verify that the MSDP server has sufficient memory
- MSDP backup or duplication job fails
- MSDP client deduplication fails
- MSDP volume state changes to DOWN when volume is unmounted
- MSDP errors, delayed response, hangs
- Cannot delete an MSDP disk pool
- MSDP media open error (83)
- MSDP media write error (84)
- MSDP no images successfully processed (191)
- MSDP storage full conditions
- Troubleshooting MSDP catalog backup
- Storage Platform Web Service (spws) does not start
- Disk volume API or command line option does not work
- Viewing MSDP disk errors and events
- MSDP event codes and messages
- Unable to obtain the administrator password to use an AWS EC2 instance that has a Windows OS
- Trouble shooting multi-domain issues
- Appendix A. Migrating to MSDP storage
- Appendix B. Migrating from Cloud Catalyst to MSDP direct cloud tiering
- About migration from Cloud Catalyst to MSDP direct cloud tiering
- About Cloud Catalyst migration strategies
- About direct migration from Cloud Catalyst to MSDP direct cloud tiering
- About postmigration configuration and cleanup
- About the Cloud Catalyst migration -dryrun option
- About Cloud Catalyst migration cacontrol options
- Reverting back to Cloud Catalyst from a successful migration
- Reverting back to Cloud Catalyst from a failed migration
- Appendix C. Encryption Crawler
- Index
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 data center can back up to a disaster recovery site. |
One-to-many model | A single production data center 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 data centers 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 event occurs | Event description |
|---|---|---|
1 | The originating master 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 original domain to the target domain. |
2 | The target master server (Domain 2) | The storage server in the target domain recognizes that a replication event has occurred. It notifies the NetBackup master server in the target domain. |
3 | The target master server (Domain 2) | NetBackup imports the image immediately, based on an SLP that contains an import operation. |
4 | The target master 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 master server for A.I.R.
- On the master server of the source domain, open the NetBackup Administration Console, select NetBackup Management > Host Properties > Master Servers.
- Double-click on the master server. In the Master Server Properties dialog box, in the left pane, click on Servers.
- Select the Trusted Master Servers tab.
- Click Add.
- Add the name of the master server for the target domain in the Trusted Master Server field.
- Click Validate Certificate Authority.
- Use one of the following methods for authentication:
Select Specify authentication token of the trusted master server and then enter the token in the Token field.
To create a token, review the Creating authorization tokens section in the NetBackup Security and Encryption Guide
Select Specify credentials of the trusted master server and then enter a User name and Password in the fields.
- Click OK to complete the setup.
- Repeat these steps in the target domain. Use the source master server name as the master 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 Java GUI 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 target NetBackup master server:
Windows:
install_path\NetBackup\bin \nbcertcmd -getCACertificate -server target_master_serverUNIX:
/usr/openv/netbackup/bin /nbcertcmd -getCACertificate -server target_master_server
- On the source MSDP storage server, run the following command to get the certificate generated by target NetBackup master server:
Windows:
install_path\NetBackup\bin \nbcertcmd -getCertificate -server target_master_server -token token_stringUNIX:
/usr/openv/netbackup/bin /nbcertcmd -getCertificate -server target_master_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. Use the Java GUI at the source domain to setup the replication target.
To set up the replication target
- On the master 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 Replicaiton 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 User name and Password is the credential used to configure the MSDP server in target domain.
To run a target A.I.R., you need to create an SLP at both the source domain and the target domain. Use Java GUI to create an import SLP.
Follow the procedures in Table: To configure an SLP to configure the 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 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. |