Schedules and retention

Set when servers are backed up and how many backups each keeps, per panel, plan, server or customer, and pause scheduled backups with a reason.

Every server follows one backup schedule: its own, its customer's choice, its plan's, or the panel's default. A schedule says how often and at what time backups are taken and how many are kept. All times are UTC.

Turn backups on#

  1. Add a destination and check it (Backup destinations); the first one is the default.
  2. Set the default schedule under Backups › Schedules (below).
  3. Go to Backups › Overview and press Turn on.

While backups are off, nothing is scheduled and Back up now is hidden. Existing backups stay listed and restorable.

The default schedule#

Go to Backups › Schedules › Change the default schedule. The fields:

Field Meaning
How often Daily, Every other day, Weekdays (Monday to Friday), Weekly, Monthly
On / On day The weekday for Weekly; the day of the month (1 to 28) for Monthly
At (UTC) The time backups start, for example 02:00
Backups kept How many of the newest backups each server keeps (1 to 100), manual ones included
Delete older than (days) Optional maximum age. The newest backup is never deleted for its age
Incremental backups per full backup 0 (the default) makes every backup full; see Incremental backups

Start within (hours) (4 by default, 1 to 23) applies to every schedule: from the scheduled time, backups start one per node at a time for that many hours. Servers whose last good backup is oldest go first, servers never backed up before all others. A backup that has not started when the window ends is marked failed with the reason ("the host was busy…"); the server's next backup is made at its own time.

The page also shows the destination scheduled backups go to, how the last scheduled run went, and which plans and servers follow a schedule of their own.

Plans, servers and customers#

A server's schedule is the first of these that applies:

  1. The server's own, set by an administrator with Schedule on the server's Backups tab.
  2. Its customer's choice (below), when the plan allows one.
  3. Its plan's: Customers › Hosting plans, the plan, section Backups and snapshots, Backups: "The panel's default schedule", "No scheduled backups" or "Their own schedule" with the fields above. Plans are linked, not copied: changing a plan's schedule changes it for every server on it at once.
  4. The panel's default.

Schedules customers choose#

When a server's plan (or the panel's default, for a server without a plan) takes scheduled backups, its owner can choose a schedule on the server's Backups tab: daily, every other day, weekdays or weekly, a time, and how many to keep, at most what the plan keeps. They can also choose "As its plan" or "No scheduled backups". The create form offers the same choice under "Back up this server". While an administrator has set the server's own schedule, the customer's choice is not followed and the tab says "Set by your provider".

Retention#

After each successful backup, the server's oldest completed backups beyond Backups kept are deleted from the destination, and so are backups older than Delete older than (days). An hourly job applies the age rule to every server, retries deletes that failed, deletes failed backups after 7 days and deletes the backups of deleted servers 7 days after the server was deleted.

Retention never deletes:

  • the server's newest completed backup for its age;
  • anything of a server whose schedule takes no backups (its backups stay until someone deletes them);
  • a backup being restored or verified;
  • a backup kept with Keep… (below);
  • anything on a read-only destination;
  • a backup still locked by S3 Object Lock (it is deleted once the lock ends).

With incremental backups, chains are deleted whole, so more backups than Backups kept may be stored for a while.

Keeping a backup longer#

On a backup card of the server's Backups tab, Keep… keeps one backup until a date or forever. Administrators may choose any date or Forever; resellers a date up to 365 days ahead. A kept backup is not deleted by retention, maximum age or a deleted server's clean-up, does not count toward Backups kept, and cannot be deleted by the customer. Each card says when the backup goes ("Kept while it is one of the newest 7", "Expires in 2 days", "Kept until 3 Dec 2026", "Kept forever").

Reseller limits#

A reseller's pool can limit Kept backups (Customers › Users, the reseller): all backups of the reseller's and its customers' servers together. A new backup at the limit is refused, unless the server already keeps as many as its schedule says (the new one replaces its oldest).

Manual backups#

Back up now on the server's Backups tab is available to whoever manages the server while backups are on and the server's destination is ready, the server runs or is stopped, and it is not suspended or in rescue. A manual backup counts toward the number kept. If the node is already taking or restoring a backup, it waits ("Waiting for its turn") and starts next, before scheduled ones. A server has at most one manual backup waiting.

The node holds the server while its disks are copied; during that time power actions and other tasks wait, and the page says "Taking a backup". The upload afterwards does not hold the server.

Pausing scheduled backups#

Pause scheduled backups, with a reason, for maintenance or an incident:

Scope Where
The whole panel Backups › Overview › Pause scheduled backups
One destination Pause schedules on its row under Backups › Destinations
One node Pause scheduled backups on the node's Maintenance tab

While paused, no scheduled backup is made or started in that scope; one that was waiting is marked missed when its window ends, with the pause's reason. Backups already running finish. Back up now, restores, deletes and retention go on. Resuming within a backup window makes that window's backups at once; windows that ended while paused are not caught up, and they are listed under Backups › History. Customers see "Paused by your provider for now".

Turning backups off on the Overview is a separate, stronger switch: it stops manual backups too.

Following the runs#

  • Backups › Overview shows protected servers (a good backup within the schedule plus a grace period: 2 days for daily, 8 for weekly, 32 for monthly), backups running now with their progress, recent failures with Retry, the servers without a recent backup and the next scheduled runs.
  • Backups › History lists one row per scheduled run (one node, one scheduled time) and one per manual backup, with filters for node, state, scheduled or manual, and dates. A row opens to its servers' backups. Runs stay listed for Keep history for (days) (365 by default, set on the Overview) after their backups are gone.