Veeam offload to Wasbai question

[importantchicken562]

Hi,

We use the latest version of Veeam and Wasabi.

Our backup jobs are configured to copy onto local storage(performance tier), then copy those backups onto Wasabi(capacity tier) daily.

The number of restore points for each job is 30.

Initially when we signed up with Wasabi on thier 'Pay as you Go' model I was under the impression the minimum retention time was 30 days. It turns out it was 90 days. This causes our 'deletion' charges to skyrocket.

It turns out you CAN in fact have Wasabi set it to 30 days but you need to specifically request it with them.

We did request it to be changed to 30 days which has already taken effect. I also changed the restore points to 31 days(we do a daily incremental once a day).

Our 'deletion' requests continue to go up despite Wasabi making the change.

Wasabi tech support responded with this:

'Moving forward, I was looking at your buckets and notice that all of them has no versioning enabled. It means that every time you "overwrite" a file, it will deleted the current one and upload a new one, and this explains the increase in the deleted object.'

We dont use immutable backups, YET. I need to figure out this billing issue first. According to Veeam documentation, versioning does not need to be enabled for regular backups.

Anyone offer any advice? I do plan on implementing immutable backups just need to get an understanding of the 'work flow' of Veeam and how it works with Wasabi to figure out this billing issue.

Thank you

[david.domask]

Hi importantchicken562,

When you say the deletion requests continue to go up, can you be a bit more specific?

Veeam has a Checkpoint Removal Job which handles the retention for backups on Object Storage, and this will be handling retention in the background.

I'm not confident Wasabi's statement is relevant (or correct as we're not overwriting files) to the issue, but I'm also not quite understanding if you think the deletions are unexpected or too high/many?

If you suspect there's an excess of data/API calls to your provider, it would be best to open a Support case and allow Support a chance to review the behavior in the logs.

> Anyone offer any advice? I do plan on implementing immutable backups just need to get an understanding of the 'work flow' of Veeam and how it works with Wasabi to figure out this billing issue.

For the concerns over the deletions, it's best to start with support. For understanding the workflow of Veeam with Object Storage and immutability, start with the User Guide pages on Immutability and Block Generation:

https://helpcenter.veeam.com/docs/backu ... ml?ver=120
https://helpcenter.veeam.com/docs/backu ... ml?ver=120

Please pay attention to this line from the immutability page as it helps understand the model best I find:

Veeam Backup & Replication protects a backup chain and all its restore points during a certain immutability period. The immutability period is the number of days you have to respond to malicious actions.

So what this is telling is don't think about immutability per restore point, instead consider how many days you want to have to respond to some malicious action -- immutability will ensure you can roll back that many days to restore the state of the repository to before an attack for example.

[importantchicken562]

Thank you David. It turns out the issue was some of our jobs were set to restore points instead of days. I believe changing them all to days has resolved our issue.