Hello.
So we are testing Wasabi and were thinking the cloud storage with Wasabi would be a great deal (and it is for the most part). But with the billing for 90 days even for deleted files I can see where this could be unexpected costs if you have weekly or bi weekly fulls. I view the cloud as emergency storage in the event of massive failure so I will only have 7 restore points in the cloud with a weekly full perhaps. And assuming the weekly full is 500gb even though it is deleted weekly for the next full I will end up paying for 6tb of storage (12 weeks of 500gb fulls) when I am actually only using 500gb. Obviously this is not good and it does not seem like there is an option to change this on the Wasabi front.

Soo. What would be the best practice in this scenario to optimize cloud storage using CB and Wasabi when you really only want 7 restore points in the cloud?

Also how do synthetic fulls work here? My assumption would be that since the file name is not changed or deleted this will not hold true? I suspect it holds true for the incrementals that are merged during the synthetic full process but those would be small.

Is the assumption with Wasabi that people will need longer than 90 days of cloud storage and thus this will not be much of an issue? As I said we will be keeping all the long term storage on our local device (hopefully via the coming GFS method) and the cloud will only have 7 days.

I guess I was looking for the gotcha with Wasabi. I am hoping this is not it.

Thanks