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
Analyzing the disc space consumption of the backup images
Use msdpimgutil spacereport command to analyze how much disk space is consumed by the backup images. This utility helps you identify images with unexpected deduplication rates and make a right decision on what images to expire in the event of high deduplication pool space usage.
The msdpimgutil utility is located at the following location:
UNIX:
/usr/openv/pdde/pdcr/bin/msdpimgutil
Windows:
install_path\Veritas\pdde\msdpimgutil.exe
Limitations:
The command does not support universal share dump data statistics.
When you run this command to check the data size, do not expire the backup images that you specify in the command input parameters.
Ensure that the expired storage space is reclaimed before you run this utility.
The command does not support the MSDP-Object-Store policy type data statistics.
Run the following command with the required options to analyze the disk space consumed.
msdpimgutil spacereport <[--backup_id_list <backupid list>] [--client <client name>] [--policy <policy name>] [--startdate <start date>] [--enddate <end date>]> [--copynumber <copy number>]
For example,
msdpimgutil spacereport --client sadiexxvmxx.xxx.xxx.veritas.com --policy PCloud --startdate 2023-09-02T01:23:22 --enddate 2023- 12-03T01:23:22 - copynumber 1
To analyze the disk space consumption of the backup images
- Get the size consumed by the specified backup images.
msdpimgutil spacereport --backup_id_list sadiexxvmxx.xxx.xxx.veritas.com_xxxxx02360 sadiexxvmxx.xxx.xxx.veritas.com_xxxxx02243
- Get the size consumed by all the backup images from a specified client.
msdpimgutil spacereport --client sadiexxvmxx.xxx.xxx.veritas.com
- Get the size consumed by all backup images from a specified policy or client and policy.
msdpimgutil spacereport --client sadiexxvmxx.xxx.xxx.veritas.com --policy dirPlocal2
- Get the size consumed by all the backup images between the specified start date and end date.
msdpimgutil spacereport --startdate 2023-09-02T01:23:22 --enddate 2023-12-03T01:23:22