cancel
Showing results for 
Search instead for 
Did you mean: 

Need clarification on job details detailed status regarding client side dedupe

Environment:  netbackup appliance (master/media), 2.6.0.3, client is physical box running windows server 2012 standard.  This is a file share, which is configured as a synthetic backup.

Where my confusion lies, is in the reporting on the daily incremental-- 

04/29/2015 01:17:19 - Info crhnbu01 (pid=3673) StorageServer=PureDiskNETBACKUP01; Report=PDDO Stats (multi-threaded stream used) for (NETBACKUP01): scanned: 177340597 KB, CR sent: 727843 KB, CR sent over FC: 0 KB, dedup: 99.6%, cache disabled
04/29/2015 01:17:19 - Info bpbrm (pid=3398) validating image for client crhsfiles1.nterprise.crhs.net
04/29/2015 01:17:41 - Info bpbkar (pid=5560) done. status: 0: the requested operation was successfully completed
04/29/2015 01:17:41 - end writing; write time: 2:13:48
the requested operation was successfully completed  (0)

Current kilobytes written is shown as 177092457, whereas the CR sent is 727843 KB, so which is actually being transmitted over the network?

Second, the client is configured for client side dedupe, and per the dedupe guide should display two deduplication rates where I only have one dedupe rate.  What am I missing?

1 Solution

Accepted Solutions
Accepted Solution!

Client-side dedup job should

Client-side dedup job should have 2 lines like this:

08/18/2014 14:23:19 - Info s1a (pid=9319) StorageServer=PureDisk:s1a; Report=PDDO Stats for (s1a): scanned: 15709014 KB, CR sent: 553810 KB, CR sent over FC: 0 KB, dedup: 96.5%, cache hits: 167158 (95.0%)
08/18/2014 14:23:31 - Info s1a (pid=9319) Using the media server to write NBU data for backup w8v_1408326813 to s1a
08/18/2014 14:23:37 - Info bptm (pid=9319) EXITING with status 0 <----------
08/18/2014 14:23:37 - Info s1a (pid=9319) StorageServer=PureDisk:s1a; Report=PDDO Stats for (s1a): scanned: 1 KB, CR sent: 0 KB, CR sent over FC: 0 KB, dedup: 100.0%, cache disabled
08/18/2014 14:25:27 - Info bpbkar (pid=3568) bpbkar waited 79 times for empty buffer, delayed 912 times.
08/18/2014 14:25:30 - Info bpbrm (pid=9264) validating image for client w8v
08/18/2014 14:26:14 - Info bpbkar (pid=3568) done. status: 0: the requested operation was successfully completed

So the first "CR sent" = 553810KB is the client data, second "CR sent" = 0KB is the metadata.

But if you're talking about synthetic backup job, it's a different story.. synthetic backup does not involve operation in the client, it basically consolidate existing full and incremental backups to bundle into one single backup, so you will have only 1 "CR sent".

 

View solution in original post

2 Replies

Policy type is MS-Windows,

Policy type is MS-Windows, the client attribute on the master/media server is set to "Always use client-side deduplication".

Accepted Solution!

Client-side dedup job should

Client-side dedup job should have 2 lines like this:

08/18/2014 14:23:19 - Info s1a (pid=9319) StorageServer=PureDisk:s1a; Report=PDDO Stats for (s1a): scanned: 15709014 KB, CR sent: 553810 KB, CR sent over FC: 0 KB, dedup: 96.5%, cache hits: 167158 (95.0%)
08/18/2014 14:23:31 - Info s1a (pid=9319) Using the media server to write NBU data for backup w8v_1408326813 to s1a
08/18/2014 14:23:37 - Info bptm (pid=9319) EXITING with status 0 <----------
08/18/2014 14:23:37 - Info s1a (pid=9319) StorageServer=PureDisk:s1a; Report=PDDO Stats for (s1a): scanned: 1 KB, CR sent: 0 KB, CR sent over FC: 0 KB, dedup: 100.0%, cache disabled
08/18/2014 14:25:27 - Info bpbkar (pid=3568) bpbkar waited 79 times for empty buffer, delayed 912 times.
08/18/2014 14:25:30 - Info bpbrm (pid=9264) validating image for client w8v
08/18/2014 14:26:14 - Info bpbkar (pid=3568) done. status: 0: the requested operation was successfully completed

So the first "CR sent" = 553810KB is the client data, second "CR sent" = 0KB is the metadata.

But if you're talking about synthetic backup job, it's a different story.. synthetic backup does not involve operation in the client, it basically consolidate existing full and incremental backups to bundle into one single backup, so you will have only 1 "CR sent".

 

View solution in original post