how Delete from disk option mechanism works w.r.t S3 compatible storage

[manoj98]

Performed Delete from Disk operation manually on capacity tier backups and though the job got successful, i have noticed some actual data objects under archive directory are being left over in the S3 compatible bucket .

i have the below questions to understand how the Delete form DIsk operation mechanism works w.r.t S3 compatible repository

1. in veeam logs where can we find if any delete requests are being sent to those left over objects from veeam end ?
2. is if Veeam maintains a list of items it has pushed and uses that internal list to generate deletes when user perform 'Delete from disk' manually, or, does it perform s3 listings and delete based off the the s3 listing results?

[Mildur]

Hello Manoj,

During the offload session, we run a cleanup process to remove outdated objects.
The backup server is aware of which object IDs can be deleted.

I strongly recommend contacting our customer support team for any troubleshooting related to object storage repositories. Having the logs or a list of unused objects won't be beneficial for you, as we do not support manipulating objects directly on the bucket.

Please also be aware, that with immutable buckets, we keep objects longer than expected.

Code: Select all

Actual object retention = job retention policy + immutability period + block generation period

Best,
Fabian