I don’t use Google Cloud Storage, so might be wrong, but it’s sometimes seemed like more of a billing consideration based on the intended access pattern than a technical hurt. Which at least for access sounds less awful for Duplicati than archives that need lots of work and time.Īmazon S3 does have a programmatic way to unfreeze cold archives, but Duplicati doesn’t support it.
You get the same experience as our hot storage options Access and management is performed through the same consistent set of APIs used by our other Cloud Storage classes, with full integration into Object Lifecycle Management. The Archive class provides almost instantaneous (milliseconds) access to your data when needed. Somehow that just doesn’t seem right to me.What storage is that? Put your archive data on ice with new storage offering is Google Cloud Storage. Now 15 bucks isn’t a lot, but as the repo grows so will this bandwidth usage and eventually I will probably be paying multiples of that just for running backups ( besides the actual storage cost). Now here comes the fun: for the past month they charged me $13.59 for bandwidth, at 1 cent per GB that means restic downloaded well over a terabyte just for running backups. My retention is set to -keep-daily 60 and this comes out to 13.252 GiB, so that’s maybe a few 100 MB churn per day. All my backups are tagged, so I can just run restic stats -mode raw-data -tag backup_mysql to get the total size used by just these dumps. Today I only ran one backup, for mysqldump'ing a bunch of databases. My current usage for today is $0.24 (25 GB), according to their billing panel (I think it’s just 1 cent/GB). My problem lies with the Download Bandwidth they charge you for. I have about 5.5 TB of actual data so the bucket size seems about right. File Lifecycle: Keep only the last version.Some stats straight from the Backblaze panel: Maybe I just figured it wrong, but after running backups on a regular schedule my B2 costs are quite a bit higher than I expected.
0 kommentar(er)
