We run the backup in a loop; but eventually the backups get too big (there’s no way to remove a backup point and GC the segments it uses that nothing else uses). So we do a full backup weekly, and while the full backup is running (because it takes a few hours) the incremental backup is also running (so we don’t have gaps).

Ahh, that's a really good point, and one I hadn't thought too much about as our backups are currently tiny. Thanks.

What’s your ideal retention policy? 1day, 7days, 30days etc?

Heh, thinking about retention policy when dealing with an immutable database feels odd. I think that 2-4 weeks of high-frequency incremental backups should cover us. With longer term backups that we keep for as long as possible. I could look at running multiple backups at different frequencies of incremental backup? eg. 1 backup on loop that is reset every month, and then another that only runs every week that we archive and reset yearly, etc.