MSDP job details

In the Activity monitor, the job details show the details of a deduplication job. The details depend on whether the job is media server deduplication or client-side deduplication job.

Media server deduplication job details

For media server deduplication, the Details 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%

Client-side deduplication job details

For client-side deduplication jobs, the Details 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 True Image Restore 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 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%)

Field descriptions

Table: MSDP activity field descriptions describes the deduplication activity fields.

Table: MSDP activity field descriptions

Field	Description
`Dedup space saving`	The percentage of space that is saved by data deduplication (data is not written again).
`Compression space saving`	The percentage of space that is saved because the deduplication engine compressed some data before writing it to storage.
`cache hits`	The percentage of data segments in the backup that is represented in the local fingerprint cache. The deduplication plug-in did not have to query the database about those segments If the `pd.conf` file FP_CACHE_LOCAL parameter is set to 0 on the storage, the `cache hits` output is not included for the jobs that run on the storage server. See MSDP pd.conf file parameters.
`CR sent`	The amount of data that is sent from the deduplication plug-in to the component that stores the data. In NetBackup, the NetBackup Deduplication Engine stores the data. If the storage server deduplicates the data, it does not travel over the network. The deduplicated data travels over the network when the deduplication plug-in runs on a computer other than the storage server, as follows: On a NetBackup client that deduplicates its own data (client-side deduplication). On a fingerprinting media server that deduplicates the data. The deduplication plug-in on the fingerprinting server sends the data to the storage server, which writes it to a Media Server Deduplication Pool.
`CR sent over FC`	The amount of data that is sent from the deduplication plug-in over Fibre Channel to the component that stores the data. In NetBackup, the NetBackup Deduplication Engine stores the data.
`dedup`	The percentage of data that was stored already. That data is not stored again.
`multi-threaded stream used`	Indicates that the Deduplication Multi-Threaded Agent processed the backup.
`PDDO stats`	Indicates that the job details are for storage on the following destinations: Media Server Deduplication Pool
`rebased`	The percentage of segments that were rebased (that is, defragmented) during the backup. Those segments had poor data locality. NetBackup reports backup job completion only after backup rebasing is completed. See About MSDP storage rebasing.
`scanned`	The amount of data that the deduplication plug-in scanned.
`Using OpenStorage client direct to restore...`	Indicates that the restore travels over the client-direct data path and does not use NetBackup media server components to process the data.
`encrypted`	Indicates if the new transferred data being written to the deduplication pool is encrypted or not.

Descriptions of the job details that are not related to deduplication are in a different topic.

More Information

About the MSDP Deduplication Multi-Threaded Agent

MSDP job details

Feedback

Feedback