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
- About the MSDP Deduplication Multi-Threaded Agent
- About MSDP fingerprinting
- Enabling 400 TB support for MSDP
- About MSDP Encryption using NetBackup Key Management Server service
- Configuring a storage server for a Media Server Deduplication Pool
- About disk pools for NetBackup deduplication
- Configuring a Media Server Deduplication Pool storage unit
- Configuring client attributes for MSDP client-side deduplication
- About MSDP encryption
- About a separate network path for MSDP duplication and replication
- About MSDP optimized duplication within the same domain
- Configuring MSDP replication to a different NetBackup domain
- About NetBackup Auto Image Replication
- Configuring a target for MSDP replication to a remote domain
- About storage lifecycle policies
- Resilient network properties
- About variable-length deduplication on NetBackup clients
- About the MSDP pd.conf configuration file
- About saving the MSDP storage server configuration
- About protecting the MSDP catalog
- About NetBackup WORM storage support for immutable and indelible data
- Running MSDP services with the non-root user
- MSDP volume group (MVG)
- About the MSDP volume group
- Configuring the MSDP volume group
- 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
- About the cloud direct
- 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 managing universal shares
- Introduction to universal shares
- Prerequisites to configure universal shares
- Managing universal shares
- Restoring data using universal shares
- Advanced features of universal shares
- Direct universal share data to object store
- Universal share accelerator for data deduplication
- Configure a universal share accelerator
- About the universal share accelerator quota
- Load backup data to a universal share with the ingest mode
- Managing universal share services
- Troubleshooting issues related to universal shares
- 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
MSDP volume group disaster recovery
You can protect the MSDP catalog of an MVG server as a regular MSDP server. You can use an MSDP catalog backup policy.
Scenario 1: MSDP catalog can be recovered
If the MSDP catalog can be recovered, you can follow the same steps to reconfigure the MSDP server with the recovered catalog.
We recommend that you protect the MSDP catalog of an MVG server as a regular MSDP server. One way is to use an MSDP catalog backup policy.
Scenario 2: MSDP catalog cannot be recovered from MVG server catalog backup
For some reason, the MSDP catalog cannot be recovered because there is no backup or the backup data cannot be used. You can rebuild the MSDP volume group configuration data and reconfigure the MVG server.
Table:
No | Step | Description |
---|---|---|
1 | Reassemble the MSDP volume group configuration. | Find out the MVG volumes that MVG server had and the physical volumes each MVG volume used. Use one of the following ways to find out the information.
|
2 | Reconfigure an MVG server. | You can configure the MSDP server with MVG option selected like an MSDP server. Using the previous host name is recommended but is not necessary. If NetBackup lost the configuration of the storage server for the MVG server, use NetBackup web UI to configure it. If NetBackup still has the configuration of the storage server for the MVG server, use nbdevconfig -setconfig command. The configuration list file has no difference with that for a regular MSDP server, except we need to enable MVG by adding: V7.5 "mvgenabled" "1" string For more information, See Configuring an MVG server using the command-line. |
3 | Add back the MVG volumes one by one. | If NetBackup still has the disk pool configured with the MVG volumes, run NetBackup command nbdevconfig -setconfig with add-virtual-volume option to add back the MVG volumes one by one, with the information collected in Step 1. See Creating an MVG volume using the command-line. In case the disk pool configuration with the MVG volumes was lost, use NetBackup web UI to recreate the corresponding disk pools and MVG volumes with the information collected in Step 1. In this case, NetBackup catalog also most likely lost the backup image records, which are associated with the MVG volumes. Thus, like recovering a regular MSDP server for the physical volumes, NetBackup image 2-phase import is also needed after the MVG server and MVG volumes are reconfigured. |
4 | (Optional) Adjust the client and policy assignment table. | The client and policy assignment table is rebuilt in the step 3. If a client and policy combination were taken by multiple MSDP servers before disaster, the information can be rebuilt but the primary one may be different than the one before the disaster. Run the following MSDP commands to check and adjust the primary MSDP server of a client and policy combination if required.: cacontrol --cluster get-cp-assignment <dsid-of-mvg-volume> [<client> [<policy>]] cacontrol --cluster set-cp-assignment <dsid-of-mvg-volume> <client> <policy> <msdp-server> The MSDP server which has more data for the client and policy is usually set as the primary one. |