Node backups
Back up every server on a node in one go.
Open Admin > Nodes, click a node, then open its Node backups.
Use this before you do something to the whole machine, such as moving it, changing its disks or taking it down for maintenance.
Taking one
- Click New node backup.
- Type a name, or leave it blank to use the date and time.
- Leave Incremental off for a complete copy, or turn it on for a smaller one that shares data with each server's earlier backups.
- Click Start a backup.
Every server on the node goes into one batch. A backup runs in the background, so nothing has to come down first.
What gets left out
Some servers cannot be included, and the batch says which.
- A server that is installing.
- A server in the middle of a move.
- A server already at its own backup limit.
Those appear under Skipped on the batch, with the reason. Read that list before you rely on the batch being complete.
Reading the history
History lists the batches you have taken, each with a state.
| State | Meaning |
|---|---|
| Pending | Queued, not started. |
| In progress | Running now. |
| Completed | Every server in the batch was backed up. |
| Completed with errors | The batch finished, and at least one server in it did not. |
| Failed | The batch did not finish. |
| Cancelled | You stopped it. |
Completed with errors is the one to open. Click the batch to see which servers succeeded, which failed, and which were skipped.
Cancel a batch that is still running from the same page.
Restoring
A node backup is a batch of ordinary server backups, so restore them one server at a time from that server's own Backups tab.
WARNING
There is no single button that puts a whole node back. Restoring is per server, and each restore replaces the files on that server.
Next steps
- Backup storage to choose where these go
- Server management to restore one server
- Server migration to move a server to another node
