S3 offload concerns

[efd121]

I have a situation with my offloads to a S3 appliance that are taking too long and I’m wondering how the following situation is managed by Veeam.
I see a task in the offload job that shows its offloading a VM for the first time that is from June 29th. The slowness I’m experiencing doesn’t allow this task to run to completion before its interrupted. I understand that Veeam will pick up where it left off the next time this VM gets an opportunity to offload.

My questions is what happens when that backup has expired and been removed from the performance tier? Does Veeam now delete all the blocks offloaded from that backup right away or do the offloaded blocks stick around for the immutable retention?

I have a handful of very large VMs that only have 7 days of retention on the performance tier, and I’m concerned this could result in large amounts of partial backups consuming space on the S3 appliance.
Dave

[david.domask]

Hi David,

Veeam is aware of which blocks are required still on the S3 Repository and tracks which blocks are immutable and which are ready to be cleared as they're no longer required. Veeam will handle ensuring that no longer needed data is cleared (assuming the immutability period on the data is passed), so no action is really needed -- the data will be managed and tidied up as necessary.

Thanks!

[efd121]

Thanks, so to confirm if I have a VM that has offloaded 50% of a backup those blocks are marked immutable at that time vs when that VM has finally been fully offloaded?
Assuming the above is true its somewhat good news. It would mean in my case that when the offloads get fully caught up, I will likely have a significant amount of partial offloads that will be removed after their immutability expires.