Skip to main content

I have a query for deduplication which is enabled when creating a storage policy.
The partition path was chosen as a single partition path on a media-agent drive.

I took a Full backup of a VM and it wrote some chunks in the HCP S3 Storage.
Re-took the same backup again and it wrote more chunks in the HCP S3 Storage even though there wasn’t any change of the “VM content”.

 

How does deduplication play a role here?

 

 

 

I assume there were changes inside the VM, yes?

Thanks,
Scott
 


@Scott Moseman no changes inside the VM. Took the same backup twice.


@Jass Gill - What was the dedup saving achieved for both the Full backup jobs? 

I would recommend running four full backup jobs for the same client and then compare the results. 


Reply