sreitshamer

My favorite is "Software development isn't a code production activity, it's a knowledge acquisition activity."

(Arq developer here) Haven't gotten many requests for it at all over the years. I presume it's because there are so many free options for Linux.

(Arq developer here) By default Arq tries to be unobtrusive. Edit your backup plan and slide the “CPU usage” slider all the way to the right to make it go faster.

Software development isn't a code-production activity, it's a knowledge-acquisition activity. It involves refactoring and deleting code too. I guess the AI isn't helping with that?

Is there a way to mount the sqlite tables as a filesystem?

I'm confused by this comment. Arq can store your backups in your own AWS account, using Glacier Deep Archive storage class. It's your own AWS account, so you pay exactly the Deep Archive price.

Not sure when you last looked into Glacier, but they did away with the "peak hourly request" fee which could be insane if you restored data too quickly. Pricing is much more reasonable now. You still have to wait hours to download your data, but Glacier deep archive is about $.001/GB per month for storage and about $0.29/GB to download (plus some transaction fees that aren't usually significant).

Google Cloud's Archive tier is cheapest to store at about $1.23/TB per month, but downloading is very expensive.

You could also make the Arq backups in your S3 bucket immutable, for more ransomware protection.

Console is sluggish for me, but S3 (us-east-1) seems to work fine.

There's no need to edit the backup plan. As I wrote in the reddit thread, clear the cache and do a backup. Sorry it's not more clear.

Are you maybe referring to Glacier "vaults" (the original Glacier API)? With the old Glacier Vault API you had to initiate an "inventory-retrieval" job with an SNS topic etc. It took days. Painful.

But these days you can store objects in an S3 bucket and specify the storage class as "GLACIER" for "S3 Glacier Flexible Retrieval" (or "GLACIER_IR" for S3 Glacier Immediate Retrieval or "DEEP_ARCHIVE" for S3 Glacier Deep Archive). You can use the regular S3 APIs. We haven't seen any rate limiting on this approach.

The only difference from the "online" storage classes like STANDARD, STANDARD_IA, etc is that downloading an object with GLACIER/GLACIER_IR/DEEP_ARCHIVE storage class requires first making it downloadable by calling the S3 "restore" API on it, and then waiting until it's downloadable (1-5 minutes for GLACIER_IR, 3-5 hours for GLACIER, and 5-12 hours for DEEP_ARCHIVE).