Creative ways to optimize for cloud: offsite backups edition
Backblaze, like many providers, charges not only for storage, but also for API usage. In my case that meant that I was spending more on API usage than I was on storage (3-4x).
I spent some time debugging the issue and determined that it was #wal-g, the software I use for streaming #postgres backups that was causing the issue, running 20K+ ListObjects calls per day.
So I configured postgres to backup to a bucket on my local #S3 server (#Minio), and then configured Minio to sync that bucket to #backblaze. That incurs exactly zero charged API calls, and the problem is solved.
What I thought was the problem (#kopia, which I use for filesystem backups) is actually quite efficient wrt/charged API calls.