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 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
- 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 immutable object support for AWS S3 compatible platforms
- About immutable storage support for Azure blob storage
- About immutable storage support for Google Cloud Storage
- 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
- Monitoring deduplication activity
- 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
- Using the ingest mode
- Enabling a universal share with object store
- Configuring isolated recovery environment (IRE)
- Using the NetBackup Deduplication Shell
- Managing users from the deduplication shell
- 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 installation issues
- 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
MSDP job details
The NetBackup web UI > Activity monitor > Job ID shows the details of a deduplication job. The details depend on whether the job is media server deduplication or client-side deduplication job.
For media server deduplication, the Detailed Status tab shows the deduplication rate on the server that performed the deduplication. The following job details excerpt shows details for a client for which MSDP_Server.example.com deduplicated the data (the dedup field shows the deduplication rate and the compression field shows the storage space that is saved by compression):
LOG 1551428319 4 Info MSDP_Server.example.com 27726 StorageServer=PureDisk:MSDP_Server.example.com; Report=PDDO Stats (multi-threaded stream used) for (MSDP_Server.example.com): scanned: 105098346 KB, CR sent: 2095410 KB, CR sent over FC: 0 KB, dedup: 98.0%, cache hits: 337282 (41.0%), where dedup space saving:89.7%, compression space saving:8.3%
For client-side deduplication jobs, the Detailed Status tab shows two deduplication rates. The first deduplication rate is always for the client data. The second deduplication rate is for the metadata (disk image header and information (if applicable)). That information is always deduplicated on a server; typically, deduplication rates for that information are zero or very low.
Additionally, for the client-side deduplication, the first Info line now displays the dedupe and compression values separately
The following job details example excerpt shows the two rates. The 1/8/2013 11:58:09 PM entry is for the client data; the 1/8/2013 11:58:19 PM entry is for the metadata.
1/8/2013 11:54:21 PM - Info MSDP_Server.example.com(pid=2220) Using OpenStorage client direct to backup from client Client_B.example.com to MSDP_Server.example.com 1/8/2013 11:58:09 PM - Info MSDP_Server.example.com(pid=2220) StorageServer=PureDisk:MSDP_Server.example.com; Report=PDDO Stats for (MSDP_Server.example.com: scanned: 110028 KB, CR sent: 16654 KB, CR sent over FC: 0 KB, dedup: 84.9%, cache disabled, where dedup space saving:3.8%, compression space saving:81.1% 1/8/2013 11:58:09 PM - Info MSDP_Server.example.com(pid=2220) Using the media server to write NBU data for backup Client_B_1254987197.example.com to MSDP_Server.example.com 1/8/2013 11:58:19 PM - Info MSDP_Server.example.com(pid=2220) StorageServer=PureDisk:MSDP_Server.example.com; Report=PDDO Stats for (MSDP_Server.example.com: scanned: 17161 KB, CR sent: 17170 KB, dedup: 0.0%, cache hits: 0 (0.0%)
Table: MSDP activity field descriptions describes the deduplication activity fields.
Table: MSDP activity field descriptions
Descriptions of the job details that are not related to deduplication are in a different topic.
More Information