we had exchange archive to the primary storage policy which was hyperscale x 1.5 , and an aux copy to windows with local disk , the jobs in the primary copy is cleared .
hyperscale x primary → first aux copy
now as part of the hardware refresh we introduced new windows server and copied from second copy
first aux copy → second copy
but we are seeing a diffrence in the media size , 0 tb diffrence
first copy
second copy
When deduplication is performed on the Primary, hash comparisons for blocks of job can independently verify which blocks already exist and which need to be created in DDB.
However, during an Aux Copy, multiple jobs are being copied simultaneously across various streams. We don’t deduplicate between streams running concurrently, as they are processed at the same time.
This is a significant reason why the sizes won’t match. While subsequent streams will deduplicate against what has already been written, they won’t deduplicate against other concurrent streams.
Because of this reason, we may see such a discrepancy.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
