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
- About MSDP Encryption using KMS 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
- 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
- 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
- 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
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