[normie3000]

Having run litestream in prod for 2+ years, I share all of these concerns.

> It seems like the thing getting backed up shouldn’t have the privilege of deleting backups in case it gets compromised.

For backups, I added a nightly cron job which exports my SQLite db to a write-only S3 bucket.

[superq]

If that will fit your RPO, why not only do that? Saves a lot of complexity (and risk).

[normie3000]

It doesn't fit my RPO.

What's the additional risk?

[superq]

Complexity == risk.

> It seems like the thing getting backed up shouldn’t have the privilege of deleting backups in case it gets compromised.

(agreed)

> For backups, I added a nightly cron job which > exports my SQLite db to a write-only S3 bucket.

Why not only do this and use an s3 sync instead? You can safely backup SQLite databases while they're being written to, so no need to export (dump) them; just copy the files themselves.

This might mean that your entire backup/restore strategy is just to copy some files. If so, that's ideal.

(Of course, s3 sync does require reading as well as writing, so perhaps just increase your cron job to run more often so it fits within your RPO)

[normie3000]

I'm starting to buy it.

> You can safely backup SQLite databases while they're being written to

Is this true with WAL enabled?