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
MSDP encryption behavior and compatibilities
MSDP supports multiple encryption algorithms. Therefore, it manages both the Blowfish and the AES encrypted data to ensure data compatibility.
For restore operations, MSDP recognizes the Blowfish data and the AES data to be able to restore the old backup images.
The following tables describe the encryption behavior for backup, duplication, and replication operations when the encryption is in progress.
Table: Encryption behavior for a backup operation to a NetBackup 8.0 storage server
Type of client | Data encryption format |
---|---|
Client with NetBackup 8.0, including the Client Direct deduplication |
AES |
Client with NetBackup version earlier than 8.0, excluding Client Direct deduplication |
AES |
Client with NetBackup version earlier than 8.0, using the Client Direct deduplication |
AES (using inline data conversion) |
Load balancing server with NetBackup version 8.0 |
AES |
Load balancing server with NetBackup version earlier than 8.0 |
AES (using inline data conversion) |
Table: Encryption behavior for optimized duplication and Auto Image Replication operations to a NetBackup 8.0 target server
Type of source storage | Data encryption format for the duplication or the replication data that is encrypted with AES | Data encryption format for the duplication or the replication data that is encrypted with Blowfish |
---|---|---|
Source server with NetBackup 8.0 |
AES |
AES (using inline data conversion) |
Source server with NetBackup version earlier than 8.0 |
Not applicable |
AES (using inline data conversion) |
Note:
Inline data conversion takes place simultaneously while the backup, duplication, or replication operations are in progress.