Defrag and compact caused full backup to be re-uploaded to S3

[YouGotServered]

Case 04092117

We are testing object storage in a backup job with immediate copy in v10 right now, and everything was working as expected until our monthly defrag and compact operation ran. Right after that operation, there was a repository offload to upload the incremental restore point from the job run (expected), but immediately after there was another repository offload to S3 that was about 35GB, which is roughly the size of the VBK in question.

So it looks like after the defrag and compact, Veeam re-uploaded the whole VBK. This doesn't make sense to me for two reasons:
1. There was really no new restore point to copy, only the structure of the backup file, so why did it copy the new file?
2. I thought there was source side dedupe to ensure that similar data was not re-copied up to S3 storage, is that not the case?

Anyone have any idea what is happening, or is my understanding of how this works completely wrong?

I don't want to do a defrag and compact of 10TB worth of backups and then find that Veeam is re-sending it all to S3.

Thanks!

[Gostev]

Hello! It's a known issue, see the sticky topic on the main forum. Thanks!

[YouGotServered]

Got it, thanks. I see a hotfix is in development, any further update on that?

[Gostev]

It should be released soon.

[jmmarton]

The hotfix is now available.

Joe

[Gostev]

Well - not really a hotfix, but the public cumulative patch
https://www.veeam.com/kb3127