Built-in Backups - Automatic Staggering or One Site at a Time

Now that I’m setting up the built-in backups, I’m wondering if scheduling could be simpler as the number of sites grows. Daily database and weekly full backups across 20 sites could mean maintaining 40 separate tasks.

When several sites share a server, manually staggering start times also doesn’t guarantee they won’t overlap if a backup takes longer than expected.

Would either of these options be possible?

• Automatic staggering: Select sites and a backup window, then let MainWP spread their start times across it.

• Sequential processing: Select sites and a starting time, then back them up one at a time, similar in concept to Sync, with an optional delay between sites.

For sequential processing, it would be useful to choose whether the next site starts after backup creation or after the remote upload is verified and local files are cleaned up. Ideally, the limit would also cover separate tasks targeting the same server.

The goal is less manual scheduling and better control over server load and temporary storage. Is there already a recommended way to achieve this?