Lucky for you, I’ve implemented this, so I have that number.
How big is each object? How many objects will I have? Who knows. 487GB is 487 * 0.00099 = $0.48213 for 30 days, right? No! See the ** after the pricing on the page?įor each object that is stored in S3 Glacier or S3 Glacier Deep Archive, Amazon S3 adds 40 KB of chargeable overhead for metadata, with 8KB charged at S3 Standard rates and 32 KB charged at S3 Glacier or S3 Deep Archive rates. Glacier Deep Archive charges $0.00099/GB/Month. $62.28 if you ever have to retrieve and download it.$0.20 additional per month if you do incremental backups once daily.Let’s break down what you pay for, using my actual usage of 487GB as an example. That’s why, when exploring using Glacier Deep Archive, I did some rough calculations on API cost plus storage cost, and then just did it. It’s usually easy to get a rough estimate of how much you’ll spend on AWS, but rarely easy to nail it down precisely. You pay for everything from storage to network traffic to API calls. In AWS, cost is one of the hardest things to factor. You can’t get your data immediately (up to 12 hours to retrieve).You pay to retrieve your data in case of emergency.You pay a little overhead for each object (file) in S3 GDA.You pay for putting the data into S3 GDA.Let’s look again, this time considering S3 GDA: Offeringĩ9c per month?!? Too good to be true? A little, yeah. In comes S3 Glacier Deep Archive (S3 GDA) to the rescue! Glacier Deep Archive is a cheaper tier of S3 that is designed for the same durability as regular S3, but at a much lower price. Let’s look at the cost for 1TB of data per month: Offeringīut wait, there’s another option. That’s over 4x as expensive as the other options! Comparatively, Amazon S3 looks ridiculously pricey at $0.023 per GB/Month. Wasabi similarly offers pricing at $0.0059 per GB/Month (minimum 1TB $5.99). Backblaze B2 offers storage for $0.005 per GB/Month. Loads of storage providers claim to be the cheapest. The strategy described below will work with other solutions too, but note that my experience is solely with Arq. One offsite is on a server that I own in another state, and the other is stored in Amazon S3.įor my backups, I use Arq Backup. I personally follow a modified strategy of 2 local and 2 offsite. Do you have one? Ideally you should be following something similar to the 3-2-1 backup strategy of having 3 copies of data: two local and one offsite.
0 kommentar(er)
