Hello,
This is a request for explanation that doesn't correspond to a technical issue (only for clarification).
Giving a cycle of audits being performed on our backup infrastructure I'm asked to justify a (seemingly) odd behavior happening on NetBackup: some duplication jobs from two different OST pool on the same domain seems to reach very high amount of data, below (and attached) is an example.
A single duplication job seems to be transfering over 50 TiB, but is referring to a lone full backup image (the one following the duplication job in the activity monitor), sized "only" 11 TiB.
Here's the detailed job log:
May 20, 2018 8:35:08 AM - requesting resource LCM_STU_XXXXXXXX-DR
May 20, 2018 8:35:47 AM - granted resource LCM_STU_XXXXXXXX-DR
May 20, 2018 8:35:47 AM - started process RUNCMD (pid=12848)
May 20, 2018 8:35:47 AM - ended process 0 (pid=12848)
May 20, 2018 8:35:48 AM - begin Duplicate
May 20, 2018 8:35:49 AM - requesting resource STU_XXXXXXXX-DR
May 20, 2018 8:35:49 AM - reserving resource @aaaas
May 20, 2018 8:37:16 AM - resource @aaaas reserved
May 20, 2018 8:37:16 AM - granted resource MediaID=@aaaau;DiskVolume=STU_XXXXX_DR;DiskPool=dkp_DDXXXXX_DR;Path=STU_XXXXX_DR;StorageServer=XXXXXXXX-02;MediaServer=zzzzzzzzzzzzz
May 20, 2018 8:37:16 AM - granted resource STU_XXXXXXXX-DR
May 20, 2018 8:37:17 AM - requesting resource @aaaas
May 20, 2018 8:37:17 AM - granted resource MediaID=@aaaas;DiskVolume=STU_YYYYYYY;DiskPool=dkp_DDYYYYYYY;Path=STU_YYYYYYY;StorageServer=YYYYYYYY-01;MediaServer=zzzzzzzzzzzzz
May 20, 2018 8:37:18 AM - Info Duplicate (pid=12848) Initiating optimized duplication from @aaaas to @aaaau
May 20, 2018 8:37:18 AM - Info bpduplicate (pid=12848) Suspend window close behavior is not supported for optimized duplications
May 20, 2018 8:37:18 AM - Info bpduplicate (pid=12848) window close
<... Continuing with multiple fragments ...>
May 20, 2018 5:34:39 PM - end writing; write time: 0:20:15
May 20, 2018 5:34:40 PM - begin writing
May 20, 2018 5:42:02 PM - end Duplicate; elapsed time 9:06:14
May 20, 2018 5:42:12 PM - end writing; write time: 0:07:32
the requested operation was successfully completed (0)
Have you ever seen this type of behavior? What may cause that growth giving that the duplication is not an aggregate of multiple backup images?
Many thanks
M.
