Deleted Storage behavior on Cloud Object Storage S3

[enrique.frisoli]

Hi All!

I`m testing on my lab an Office 365 backup with Veeam Backup Office 365 7.0.0.3604 to Wasabi Cloud, and I am seeing that the "deleted storage" amount increase every day, probably because we are working with Jet Databases at the end.

Somebody know how much can increase that value? Have some relation with the "total storage" used?

For example, in my lab, I am just having 8,87MB "total storage" and 76,58MB "deleted storage". My concern is about the 30 days on deleted storage that Wasabi have as policy.

Please, see the image about how "deleted storage" increase on my bucket

Thanks!!

[chris.childerhose]

Not sure why your deleted is higher than the used. Mine is the opposite for the O365 v7 backups I have running. Might want to open a support case to investigate.

[enrique.frisoli]

Ok! Thanks Chris! I will recreate a new bucket from scratch.

[chris.childerhose]

Not a problem. I will be interested if this works for you or not.

[micoolpaul]

Hi, is this an item-level retention or snapshot-level retention you’re using?
And what retention period have you got set on it?

You don’t have JetDB in object storage, that exists on your local cache only btw! So that’s not what’s causing this delta in consumed vs deleted.

[enrique.frisoli]

Hi! I created a new Object Storage Repository. (Snapshot-based retention + 3 years Retention Policy + Frequency to apply retention: Monthly), changed the Job to the new repo but I´m having same behavior. Frequency of backups are daily (2 Jobs Exhange OnLine and Sharepoint OnLine)

My Office 365 tenant is not production, just a development tenant for testing, so I don´t have to much data.

Here some pictures:





Could be possible that "deleted storage" have a minimum quantity always by design? initially first day this value was 52MB and next days it was growing arround 2 MB per day.

[Polina]

Hi Enrique,

There's no such design, and what you see doesn't look normal. Please open a support case to troubleshoot it with our engineers, and post its ID here for reference. Don't forget to attach logs and details from Wasabi to the case.

Thanks!

[enrique.frisoli]

Hi Polina! Ok, understood, case created: Case #06138853 for troubleshooting. This is just a test environment, so, it was opened with severity 4. Thanks!!