Proxmox snapshots: create, schedule, roll back and manage
A Proxmox snapshot captures a VM or container at a point in time so you can roll back in seconds. Here's how snapshots work, how they differ from backups, how to automate and retain them, and how to manage snapshots across every host from one panel.
How Proxmox snapshots work
A snapshot freezes the state of a guest, its disk, and optionally its RAM, at a moment
in time. Because it records only what changes afterwards, a snapshot is near-instant to
take and lets you return the guest to that exact state later. For QEMU/KVM VMs you can
include the running memory state (vmstate); LXC containers snapshot their
filesystem.
Snapshots depend on the storage backend, ZFS, LVM-thin and qcow2 support them; plain
LVM and directory raw disks do not. They live on the same storage as the
guest, so a snapshot is a fast rollback point, not a backup.
Proxmox snapshot vs backup
Different tools for different jobs, use both.
| Aspect | Snapshot | Backup (vzdump / PBS) |
|---|---|---|
| Speed | Near-instant | Full copy — takes time |
| Where it's stored | Same storage as the guest | Separate storage / PBS |
| Survives disk/host loss | No | Yes |
| Best for | Quick rollback before a change/upgrade | Disaster recovery, retention, off-site |
| Includes RAM state | Optional (QEMU vmstate) | No (unless suspend/stop mode) |
Take a snapshot before a risky change so you can undo it instantly; run scheduled backups to a separate datastore for real recovery and retention. Snapshots complement backups, they don't replace them.
Scheduled and automatic snapshots
Proxmox VE schedules backups natively, but it has no built-in scheduler for
snapshots. Teams usually automate snapshots one of two ways: a cron
job on the node calling qm snapshot / pct snapshot, or a script
that drives the API on a timer, taking a rolling snapshot (for example hourly or nightly)
and pruning old ones.
NexoVirt exposes snapshot create, roll back and delete through its REST API and panel, so you can script automatic snapshots across every host from one place, or trigger them from your own tooling, without logging into each node.
Rolling back a snapshot
Rollback reverts the guest to the snapshot's state. For a VM without a saved RAM
state the guest should be stopped first; with vmstate it can resume
live. Rollback is destructive to changes made after the snapshot, so it pairs
best with "snapshot before you change something".
Retention and cleanup
Proxmox does not auto-prune snapshots, they accumulate and each one keeps its deltas on storage, so leaving many around eats disk. Keep a small rolling set (for example the last few) and delete the rest on a schedule via cron or the API.
Manage Proxmox snapshots from one panel
Create, roll back and delete snapshots for every VM and container across all your hosts.
One snapshot view
See and manage snapshots for any guest on any host, no per-node logins.
REST API for automation
Create, roll back and delete snapshots over a clean token-authenticated API, so scheduled and automatic snapshots are a short script.
Snapshots + backups
Pair fast snapshots with scheduled Proxmox Backup Server jobs, both managed alongside your guests.
Frequently asked questions
Proxmox guide
Snapshots for every guest, one panel
NexoVirt manages snapshots across all your Proxmox hosts from the panel and a REST API. Community Edition is free (up to 2 nodes).