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
- About MSDP stream handlers
- 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 NetBackup 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
- About NetBackup WORM storage support for immutable and indelible data
- 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
- MSDP cloud support
- About MSDP cloud support
- 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
- Trouble shooting multi-domain issues
- Appendix A. Migrating to MSDP storage
About the tool updates for cloud support
DCSCAN:
Dcscan downloads data container from the cloud. The default download path is <STORAGE>/tmp/DSID_#dsid
, where #dsid is dependent on the cloud LSU DSID value. Different cloud storage providers have different DSID values. You do not need to know the DSID value, dcscan gets the DSID value automatically. The default download path can be modified in the contentrouter.cfg file using the DCSCANDownloadTmpPath field.
While using the dcscan tool to look at cloud data, -a option is disabled, because it downloads all data containers from cloud, it is an expensive operation. The -fixdo option is disabled as well, because dcscan only downloads data container from the cloud. Others operations are same as the local LSU.
SEEDUTIL:
Seedutil can be used for seeding a backup for a better deduplication rate. It creates links in the <destination client name> directory to all the backup files found in the path <client name>/<policy name> that have <backup ID> in their names. The user needs to know which DSID value the cloud LSU has used. That DSID value needs to be given to the seedutil, to let seedutil know which cloud LSU will seed a client. If you do a seeding for a local LSU, the default DSID is 2, you do not need to give the DSID value. Seedutil cannot seed across different DSIDs.
For example,/usr/openv/pdde/pdag/bin/seedutil -seed -sclient <source_client_name> -spolicy <source_policy_name> -dclient <destination_client_name> -dsid <dsid_value>.
CRCONTROL:
Using crcontrol - clouddsstat option to show cloud LSU datastore usage. DSID value needs to be given. As cloud storage has unlimited space, the size is hard-coded to 8 PB.
For example:
# /user/openv/pdde/pdcr/bin/crcontrol --clouddsstat <dsid_value> ************ Data Store statistics ************ Data storage Raw Size Used Avail Use% 8.0P 8.0P 80.9G 8.0P 0% Number of containers : 3275 Average container size : 26524635 bytes (25.30MB) Space allocated for containers : 86868179808 bytes (80.90GB) Reserved space : 0 bytes (0.00B) Reserved space percentage : 0.0%
CRSTATS:
Using crstats -cloud -dsid option to show the cloud LSU statistics. DSID value needs to be given. As cloud storage has unlimited space, the size is hard-coded to 8 PB.
For example:
#/usr/openv/pdde/pdcr/bin/crstats --cloud-dsid <dsid_value> Storage Pool Raw Size=9007199254740992Bytes Storage Pool Reserved Space=0Bytes Storage Pool Required Space=0Bytes Storage Pool Size=9007199254740992Bytes Storage Pool Used Space=86868179808Bytes Storage Pool Available Space=9007112386561184Bytes Catalog Logical Size=402826059439Bytes Catalog files Count=3726 Space Allocated For Containers=86868179808Bytes Deduplication Ratio=4.6
PDDECFG:
Using pddecfg to list all the cloud LSUs.
For example:
/usr/openv/pdde/pdcr/bin/pddecfg -a listcloudlsu dsid, lsuname, storageId, CachePath 3, S3Volume, amazon_1/cloud-bucket1/sub1, /msdp/data/ds_3 4, S3Volume2, amazon_1/cloud-bucket1/sub2, /msdp/data/ds_4