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
- 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 Key Management Server 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
- Running MSDP services with the non-root user
- 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
- 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 using universal shares
- Configuring universal share user authentication
- Using the ingest mode
- Enabling a universal share with object store
- Configure a universal share accelerator
- About the universal share accelerator quota
- 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
Rebuilding the sampling cache
When MSDP is upgraded, the fingerprint lookup method does not change. If you want to use the new fingerprint lookup method predictive and sampling cache, you can configure it manually. Use the rebuild_scache script to rebuild the sampling cache during the maintenance window. It enhances the local deduplication ratio in post-upgrade environments when you enable predictive cache and sampling cache manually on local BYO, Flex, and Flex Worm environments.
The script is stored at the following location:
UNIX:
/usr/openv/pdde/pdag/scripts/rebuild_scache.sh
Windows:
install_path\Veritas\pdde\rebuild_scache.bat
You are not required to specify the log level. Logs are saved at the following location:
UNIX: /var/log/puredisk/<date and time>-rebuild-scache.log
Windows: C:\rebuild-scache.log
Consider the following recommendations when you run the script to rebuild the sampling cache.
After the upgrade, run this script immediately before running the backup tasks to rebuild the sampling cache.
Ensure that the predictive and sampling cache are enabled when the script is running.
For S3 interface for MSDP and universal share environments, rebuilding the sampling cache may affect deduplication ratios.
The script execution affects all backup jobs causing them to fail during the rebuilding process and the backup jobs are not performed.
If the backup job cannot be performed after the rebuilding process is complete, restart the MSDP.
When the script is initiated, ensure that it is successful. If it is terminated for some reason, run the script again.
If errors occur during the rebuilding process, run the script again.
To rebuild the sampling cache after an upgrade
- Enable predictive and sampling cache in
contentrouter.cfg
andspa.cfg
. - On the storage server, run the script:
UNIX:/usr/openv/pdde/pdag/scripts/rebuild_scache.sh
Windows:install_path\Program Files\Veritas\bin\rebuild_scache.bat
- Type y and press Enter to proceed. A warning about the job status is displayed.
- Type y and press Enter to initiate the process to rebuild. The script displays the rebuild state and percentage.
In the Flex worm environment, use deduplication shell to start the sampling cache rebuilding.
To rebuild the sampling cache from the deduplication shell
- Open an SSH session to the server.
- Run the following command for the initial sampling cache rebuilding.
setting rebuild-scache rebuild-sampling-cache
- See the sampling cache rebuilding status.
setting rebuild-scache rebuild-sampling-cache-status