Here's a close hypothetical, I'd like one full backup per month. I schedule a 3:00am backup every night to restart after interruptions. I can't see how to get one backup per month without scheduling every night, monitoring for success, and then changing the schedule when I finally get a full backup so as to stop further full backups til next month. Then next month, manually set the schedule to every night again, and so on.... Note: changing the schedule is also a pain as I have to co-ordinate remote to a machine 700 kms away. An option to automatically restart interrupted backups would avoid all this fiddling - just schedule a monthly full backup - done.

Anway, thanks for the help. I'll keep an eye out for changes and re-evaluate again if it looks promising.

Thanks, David, but I don't think I can make Cloudberry work for for my use case. It's not a work machine, so online hours are not predictable. I did think of your suggestion, but if the machine is left on, it would result in too many full backups and no "down time" between full backups.

It just seems like a little too much monitoring and manual involvement to keep a small number of full backups for this particular machine.

Thanks. I'm a little surprised there is not more demand for unattended restarts given the long term trend towards laptops from always on desktops, and set-n-forget always being cheaper to manage/monitor. I can't imagine looking after a fleet of laptops efficiently without have some kind automatic restart of backups.

I'm using the new backup format, which supposedly does a file-based synthetic (in-cloud copying) backup.

https://help.msp360.com/cloudberry-backup/backup/about-backups/new-backup-format/synthetic-full-backup

You seem to have missed my point, I don't want to have to intervene and restart the backup when interrupted, I want cloudberry backup to resume the interrupted backup itself.

The hypothetical scenario is a machine that is effectively unattended, is only online for a few hours at a time, and a full backup will take 100-ish hours.

At present it appears I have to manually intervene to resume the full backup.