Backups and schedules

Backups

A server’s Backups tab:

Create backup: packs the server’s files into a tar.gz on the node. Paths can be left out, e.g. logs/**. Symbolic links are skipped.
Download: streamed from the node through the panel, so the node needs no open port.
Upload: a tar.gz (e.g. one downloaded earlier, or from another server) becomes a backup to restore. It is checked when complete; it counts against the limit. Files keep their permissions. A new server can also start from a backup (Servers).
Restore: stops the server if it runs, then puts the files back. Optionally, files that aren’t in the backup are deleted, so the folder looks exactly like the backup.
Lock: a locked backup can’t be deleted, and schedules never replace it.
Limit: each server keeps at most 3 backups by default. Owners and admins change it in the tab; 0 turns backups off. Backups count against the node’s disk.

Deleting a server deletes its backups. Backups stay on the node; copies to S3 or a NAS are planned.

A server’s Schedules tab runs tasks at set times, given as a cron expression in a time zone, with presets such as “every day at 04:00”.

Tasks: a console command, a power action, a backup, or a Steam update. They run in order, and each one can wait first (up to an hour).
Failures: the run stops at a failed task, unless the task says to go on.
Only while running: skips the run when the server is off, so a server someone stopped on purpose isn’t started again.
Backups: at the limit, a scheduled backup replaces the oldest unlocked one.
Run now starts it at once.

People can only schedule what they may do themselves: a schedule with a restart needs power.restart, and so on.

#	Task	Wait first
1	Command `say Restart in 60 seconds`	—
2	Power: restart	60 s

Every day at 04:00, only while running.