Scheduled backups
Set it per site, then decide whether it should also run while the app is closed.
Setting a schedule
On a site's Overview, the Automatic backups module:
- Run — every day, every week, or off.
- At — the hour, in your computer's local time.
- Keep — the newest 3, 7, 14 or 30; older scheduled backups are removed after each run.
Scheduled backups are always Full. The sentence under the module says exactly what will happen and when it last ran; the Auto badge in the site list marks sites that have one.
While the app is open
The app checks every fifteen minutes whether a site is due, and runs it. A schedule for 03:00 runs at the first check after 03:00 — the app compares with the last run, not the clock, so a computer that was asleep at 03:00 backs up when it wakes rather than skipping the day.
While the app is closed
Preferences → Also run when the app is closed. Turning it on registers a small background job with your operating system that runs the same check every fifteen minutes and exits:
| macOS | a LaunchAgent in ~/Library/LaunchAgents |
|---|---|
| Windows | a Task Scheduler task, for your user |
| Linux | a systemd user timer in ~/.config/systemd/user |
All three run as you, so your SSH keys work; all three survive a restart; all three run a check that was missed during sleep once the machine wakes. Turning the switch off removes the job completely. The status line under the switch says whether it is installed and running.
Two at once
If the app is open and the background job fires at the same moment, only one of them runs a given site: they take a lock and re-check what the other just did.
Failures
A scheduled backup that fails raises a system notification and a red day on the site's timeline; a successful one is silent, so the notification means something. Every run, either way, is in History.