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
Restoring the MSDP catalog from a shadow copy
NetBackup automatically restores the necessary parts of the MSDP catalog if corruption is detected. However, you can restore the MSDP catalog from a shadow copy manually, although in normal circumstances it is not necessary. Veritas recommends that you contact your Veritas Support representative before you restore all or part of the MSDP catalog from a shadow copy.
The procedure that you use depends on the restore scenario, as follows:
Restore the entire MSDP catalog from a shadow copy |
In this scenario, you want to restore the entire catalog from one of the shadow copies. See “To restore the entire MSDP catalog from a shadow copy”. |
Restore a specific MSDP database file |
The MSDP catalog is composed of multiple small database files. Those files are organized in the file system by the client name and policy name, as follows: UNIX: /database_path/databases/catalogshadow/2/ClientName/PolicyName Windows: database_path\databases\catalogshadow\2\ClientName\PolicyName You can restore the database files for a client and a policy combination. The restore of a specific client's and policy's database files is always from the most recent shadow copy. See “To restore a specific MSDP database file from a shadow copy”. |
To restore the entire MSDP catalog from a shadow copy
- If any MSDP jobs are active, either cancel them or wait until they complete.
- Disable all policies and storage lifecycle policies that back up to the Media Server Deduplication Pool.
On the MSDP storage server, run the following command, depending on host type:
UNIX: /usr/openv/pdde/pdcr/bin/cacontrol --catalog recover all
Windows: install_path\Veritas\pdde\cacontrol --catalog recover all
- Enable all policies and storage lifecycle policies that back up to the Media Server Deduplication Pool.
- Restart the jobs that were canceled before the recovery.
To restore a specific MSDP database file from a shadow copy
- If any MSDP jobs are active for the client and the backup policy combination, either cancel them or wait until they complete.
- Disable the policies and storage lifecycle policies for the client and the backup policy combination that back up to the Media Server Deduplication Pool.
- Change to the shadow directory for the client and policy from which you want to recover that database file. That directory contains the database files from which to recover. The following are the pathname formats:
UNIX: /database_path/databases/catalogshadow/2/ClientName/PolicyName
Windows: database_path\databases\catalogshadow\2\ClientName\PolicyName
Run the following command, depending on host type:
UNIX: /usr/openv/pdde/pdcr/bin/cacontrol --catalog recover 2 "/ClientName/PolicyName"
Windows: install_path\Veritas\pdde\cacontrol --catalog recover 2 "\ClientName\PolicyName"
- Enable all policies and storage lifecycle policies that back up to the Media Server Deduplication Pool.
- If you canceled jobs before you recovered the database files, restart them.
More Information