A backup is a copy of every disk of a server, taken while it runs and stored away from its node, together with a small manifest (server, hostname, sizes, addresses at the time, checksums). The node does all the work: it copies the disks, uploads them to the destination and deletes old ones. The panel only decides what runs when, and never holds a connection to the destination itself.
Backups are off by default. You turn them on under Backups › Overview once at least one destination has passed a check. While they are off nothing is scheduled and Back up now is hidden; backups already taken stay listed and restorable.
The Backups section of the sidebar has five pages: Overview (on/off, protection status, running and failed backups, pauses), Restore, History, Destinations and Schedules. Each server also has a Backups tab with its own backups, Back up now, restore and its schedule.
- Destinations: SFTP and Hetzner Storage Box, S3-compatible, Proxmox Backup Server, NFS, a directory on each node; encryption and speed limits
- Schedules and retention: the default schedule, plans and servers with their own, how many are kept, pauses
- Incremental backups: chains of a full backup and incrementals
- Immutable backups (S3 Object Lock)
- Restoring backups: in place, to a new server, by customers, verify, and staff roles for backup work
The panel's own database and keys are backed up separately: see Backing up the panel. Snapshots kept beside the disk on the node are not backups: see Snapshots.
- Backup destinationsAdd SFTP, S3-compatible, Proxmox Backup Server, NFS or local backup destinations, check them, encrypt them and choose where each server's backups go.
- Schedules and retentionSet when servers are backed up and how many backups each keeps, per panel, plan, server or customer, and pause scheduled backups with a reason.
- Incremental backupsSend only what changed since the last backup: chains of one full backup and up to 30 incrementals, which servers can take them, and how chains are kept and deleted.
- Immutable backups (S3 Object Lock) BetaLock every backup on an S3 bucket with Object Lock, so a stolen key or ransomware on the panel cannot delete or change it before its retention ends.
- Restoring backupsRestore a backup onto its own server or as a new server, verify backups, let customers restore within limits, and give staff a backup role.