Appearance

Backups and snapshots ​

This page describes creating and restoring backups and snapshots of a server.

Difference

A backup saves the server for a later restore. A snapshot additionally captures the server's current state and can serve as a starting point for further snapshots. There's no automatic schedule – both actions are triggered manually.

Creating a backup ​

  1. Open the desired server and go to the Backups section.
  2. Click Create backup.
  3. Optionally enter a note to identify the backup later.
  4. Save to create the backup.

The new backup then appears in the overview with its note, size and creation date.

Restoring a backup ​

  1. Find the desired backup in the overview.
  2. Click Restore.
  3. Confirm the prompt.

Warning

Restoring a backup replaces the server's current data with the state from the backup. Any unsaved changes made since the backup was created will be lost.

Deleting a backup ​

Click Delete on the relevant entry in the backup overview and confirm the prompt.

Creating a snapshot ​

  1. Go to the Snapshots section of the server.
  2. Click Create snapshot.
  3. Enter the following:
    • Name (required)
    • Description (optional)
    • The option Save the VM's memory and running state in the snapshot (enabled by default)
  4. Save to create the snapshot.

Rolling back to a snapshot ​

  1. Find the desired snapshot in the overview.
  2. Click Reset.
  3. Confirm the prompt.

Warning

Rolling back to a snapshot discards all changes made to the server since the snapshot was created.

Deleting a snapshot ​

Click Delete on the relevant entry in the snapshot overview and confirm the prompt.

Follow-up checks ​

After creating a backup or snapshot, check:

  • that it appears in the respective overview
  • that the note, name or description was saved correctly

After a restore or rollback, check:

  • that the server is running normally again
  • that the expected data and settings were restored

Common issues ​

Restore doesn't produce the expected result ​

Possible cause:

  • the wrong or an outdated backup or snapshot was selected

Server unreachable after a rollback ​

Possible cause:

  • the snapshot was created while the server wasn't running, or while network changes were pending