Restore a backup

Restore brings a snapshot back to a server. You restore from /backups — open the Snapshots view (the fleet-wide restore list), pick a snapshot, and choose what to bring back.

Restore a full site or DB-only

When you restore a site snapshot you choose the scope:

• Full — files and database together.
• Database only — restore just the database, leaving the site’s files untouched.
• Files only — restore just the web root.

The restore runs natively on the VPS via the agent, restoring from the restic snapshot in place.

Caution

Restoring overwrites the current data for the chosen scope. A database-only restore replaces the live database; a full restore replaces files and database.

Watch progress

Restores report realtime progress back to the dashboard as they run, so you can watch the operation complete instead of guessing. The snapshot’s status updates as the job moves through queued → running → completed (or failed, with a log snippet).

Restore a Docker stack

MZPanel can restore a whole Docker Compose stack — not just rehydrate a volume. A stack backup captures the compose definition, environment, and volumes, and takes DB-consistent logical dumps (pg_dumpall, mongodump, mariadb-dump) by running them inside the container rather than tarring a hot database volume.

Restoring a stack is a single restore point that rebuilds the stack:

1. Recreate the stack from the captured compose definition and environment.
2. Restore the non-database volumes and host bind mounts.
3. Load the logical database dumps back into the stack’s database services.

Single Docker apps follow the same recreate-from-backup model. For Docker snapshots the restore drawer is Docker-aware: it hides the site scope picker and notes that the stack or app will be recreated.

Tip

Because stack backups ride the same destinations as site backups, you can restore a stack from a local, peer, or offsite destination — see Backups.