Wasabi Data Deletion Charges
We are using Wasabi for our cloud storage, where we pay $5.99 per TB per month. Yet we are ending up paying a lot more, because Wasabi charges us for data that is deleted prior to being stored for 90 days. We are actually being charged *more* (almost twice as much) for data that we are deleting than for data that we are saving. Does anyone have any advice or best practice tips for data retention on our MSP360 cloud backups when using Wasabi? We backup mainly Windows computers, and with mainly image based backup plans. Should we try to avoid the deletion fee by running full backups monthly instead of weekly or bi-weekly? Or would it give us any net cost benefit to retain our data for 90 days before deletion? Any advice would be welcome.
Please send me the direct message with your current retention policy settings for I could review them and recommend how to tweak them to avoid the Wasabi deletion fee.
You can work with Ivan offline for help on tweaking the retention. But I want to mention a few things as you look to review your retention and backup scheduling knowing about Wasabi's minimum retention requirements.
Early deletion fees are billed no differently than the data you keep stored. Meaning, the costs will be the same. As an example, if you have 5 TB of data and 10 TB of deleted data billed at an average of 45 days for early deletion, then you have parity with what Wasabi would bill for 10 TB of data stored.
You can, of course, tweak the retention settings to keep more data available (say 60 versus 30 days). Since you're paying for the storage anyway, you might as well try and keep more data available for restores.
Ultimately, your retention should be driven from business restore point objectives. If that number is less than the Wasabi minimum retention, then you may have early deletion fees as a result.
There are a couple things you can do to minimize storage requirements:
Do not keep data longer than 90 days if you do not need backups older than 90 days
For image based backups, run the backups less frequently,but make sure they sync up with retention needs. A example of something not to do is run a full backup every 180 days and set retention to 90 days because you'll need to back up 360 days before the first 180 days can be removed from storage. A better use case would be to run full backups every 30 days and keep 60 days in storage. That way, when you hit 90 days, the first 30 can safely be removed from storage, you're eliminating most, if not all, early deletion fees, and you have 60 days to restore. You could run the full backups more frequently, but if you find the full size is much larger than its associated incrementals, you'll end up with more storage use, but the ability to remove backups more quickly (say, every 14 days).
But work with the team offline to tweak your settings.
Or you could send the backups to Backblaze, which has no minimum retention period and costs only $5.00 per TB per month. While we keep our data file backups for 90 days, we run new Image/VHDx backups to the cloud each month and only keep one copy in the Cloud.
Yes Backblaze does charge $0.01 cent per GB for downloads (vs Wasabi's free downloads), but we only do large restores a few times a year - a 200GB Image download costs a whopping $2.00.
Sign in or register to add a comment.
Add a Comment
Welcome to MSP360 (CloudBerry) Forum!
MSP360 Managed Backup
Microsoft SQL Server
Microsoft SQL Server
MSP360 Remote Desktop
Problem deleting data to reclaim Amazon S3 / Glacier space
feature request: support seeding hybrid backup using azure data box disk service or similar
Feature Request: Remote deploy backup to new endpoint (endpoint recovery and data migration)
Unable to copy the data between s3 compatible storage to AWS snowball
Terms of Service
Useful Hints and Tips
Created with PlushForums
© 2020 MSP360 (CloudBerry) Forum