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 Cloud Catalyst
- Using NetBackup Cloud Catalyst to upload deduplicated data to the cloud
- Configuring a Cloud Catalyst 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 Cloud Catalyst issues
- Cloud Catalyst logs
- Problems encountered while using the Cloud Storage Server Configuration Wizard
- Disk pool problems
- Problems during cloud storage server configuration
- Cloud Catalyst troubleshooting tools
- Appendix A. Migrating to MSDP storage
Optimized duplication is used to copy data from an MSDP storage server to a Cloud Catalyst storage server (preferred use case)
This is the preferred Cloud Catalyst use case. In this scenario, the NetBackup environment contains two media servers: one is an MSDP storage server and one is a Cloud Catalyst storage server.
First, client data is backed up to the MSDP storage server, which is used for short-term data retention. In subsequent backups, the data is deduplicated. (See Figure: Flow of data from an MSDP storage server to a Cloud Catalyst storage server.)
A storage lifecycle policy then copies the data to a Cloud Catalyst storage server using optimized duplication. Data is uploaded from the Cloud Catalyst local cache to the cloud when an MSDP container file is full. This occurs soon after the backup or duplication job begins, but not immediately.
The cloud storage is used for long-term data retention. Deduplication makes it possible for subsequent jobs to transfer substantially less data to the cloud, depending on the deduplication rate.
This use case is preferred to backing up directly to a Cloud Catalyst storage server. (See Backups go directly to a Cloud Catalyst storage server.)
See Configuring a Cloud Catalyst storage server for deduplication to the cloud.