Proxmox snapshots & backups: rollback and PBS

Proxmox VE gives you two distinct mechanisms for protecting a guest before or after a change: snapshots and backups. They look similar on the surface, both let you recover a previous state, but they solve different problems, live in different places, and carry different trade-offs. Getting the distinction right matters before you set up a protection strategy for production workloads. This post walks through both, covers scheduled backup jobs, Proxmox Backup Server integration, and explains how NexoVirt ties all of it together from a single panel.

Snapshots vs Backups: Different Problems

A Proxmox snapshot is an instant rollback point stored alongside the guest on the same storage. For QEMU VMs on a storage that supports copy-on-write (ZFS, Ceph, LVM-thin, qcow2 on directory storage), the snapshot is essentially free to create: Proxmox freezes the disk state and records the VM configuration and optional RAM contents. For LXC containers it stores the filesystem tree. The key characteristic is locality: the snapshot lives on the same host, on the same storage volume. If that storage fails, the snapshot goes with it.

A backup (vzdump) is a portable archive: a compressed, self-contained file that can be copied off-host, stored on a NAS, shipped to a Proxmox Backup Server, or downloaded. It survives a storage failure on the source node. Restoring from a backup re-creates the guest from scratch; restoring from a snapshot is a near-instant rollback that does not move any data.

When to use which:

• Before a risky change (kernel upgrade, config edit, application migration): take a snapshot. If it goes wrong, you are back in seconds. Delete the snapshot once you are confident the change is stable.
• Regular protection against hardware failure or data loss: run scheduled vzdump backups to off-host storage or PBS. Snapshots do not protect against a failed disk.
• Both, for important workloads: a snapshot for fast rollback during a maintenance window, plus a nightly backup job for durable off-host copies.

Proxmox Snapshots: Create, List, Rollback, Delete

Proxmox snapshots are managed per-guest in the Proxmox web UI under the Snapshots tab, or via the native API at POST /nodes/{node}/qemu/{vmid}/snapshot. Each snapshot has a name and an optional description. For a VM, you can optionally include the RAM state (the running memory contents), which lets you restore a guest to exactly the running condition it was in, useful if you are snapshotting a live application. Including RAM makes the snapshot take a few seconds longer and uses more storage; without it the guest must boot from a clean disk state on rollback.

A typical snapshot workflow before a Proxmox upgrade or a guest OS update:

• Create a snapshot with a descriptive name: pre-upgrade-2026-06-25.
• Apply the upgrade or change.
• Verify the guest is working correctly.
• Delete the snapshot to reclaim the copy-on-write space.

If the change breaks something, rollback via POST /nodes/{node}/qemu/{vmid}/snapshot/{snapname}/rollback. For LXC the path is the same, substituting lxc for qemu. The rollback stops the guest, restores the disk and configuration, and starts it again. For RAM snapshots it also restores the memory state.

NexoVirt exposes snapshot management per-guest directly from the panel: create a named snapshot, view the snapshot list with timestamps and descriptions, roll back with a confirmation step, and delete snapshots you no longer need, without opening the Proxmox web UI or running API calls by hand.

vzdump Backups: Back Up Now, Restore, Delete

vzdump is Proxmox's built-in backup tool. It produces a compressed archive of the guest: disk images, configuration, and (for LXC) the filesystem, stored as a .vma.zst, .vma.gz, or .tar.zst file depending on guest type and compression setting. The archive is self-contained and can be restored to the same host or a different one.

The important options at a high level:

• Mode. Snapshot mode (default for most storage types) freezes the disk momentarily using a storage snapshot internally, minimising downtime. Suspend mode pauses the VM during the backup. Stop mode shuts the guest down, takes the backup, and restarts it, the slowest but most consistent option for guests that cannot use storage snapshots.
• Compression. Zstandard (zstd) is the default since Proxmox 6.2 and is fast with good ratios. gzip is slower but widely compatible; lzo is fastest with lower compression. For large disks, zstd is the practical choice.
• Storage target. vzdump writes to a storage defined in the Proxmox datacenter that has the backup content type enabled. This can be a local directory, a NAS (NFS or CIFS), or a Proxmox Backup Server datastore, each with different retention behaviour.

Restoring from a backup re-creates the guest: it gets a new (or the same) VMID, its disks are written from the archive, and its configuration is applied. The guest does not need to exist to restore; you can restore to a completely clean node.

NexoVirt provides on-demand backup and restore per guest: trigger a backup from the panel, browse the backup list for a guest, restore from a selected backup, or delete old backups to free storage space, all without navigating the datacenter storage views in the Proxmox UI.

Scheduled Backup Jobs

One-off backups are useful, but real protection requires regular, unattended jobs. Proxmox datacenter-level backup jobs let you define a schedule, a target storage, a set of guests (or all guests on the cluster), retention rules (how many backups to keep), and notification settings. The scheduler is cron-based; common configurations are nightly at 02:00, or staggered across nodes to avoid simultaneous I/O on shared storage.

Retention is configured per job: keep the last N daily, N weekly, and N monthly copies. Proxmox evaluates and prunes automatically after each run. Without explicit retention settings, backups accumulate until the target storage fills up, something worth configuring before you rely on a backup job.

NexoVirt exposes scheduled backup jobs from the panel. You can create and manage datacenter-level jobs: set the schedule, target storage, guest selection, and retention, without logging into the Proxmox UI separately. For multi-host setups, jobs across all connected hosts are visible and manageable from one place.

Proxmox Backup Server: Deduplicated, Incremental, Off-Host Backups

Proxmox Backup Server (PBS) is a dedicated backup appliance that runs alongside your Proxmox VE hosts. It adds two capabilities that plain vzdump to directory storage does not provide: deduplication and incremental backups. After the first full backup of a guest, subsequent backups only transfer the changed blocks, for a running VM that is mostly unchanged between nightly jobs, the incremental transfer can be a fraction of the full size. PBS stores backups in a content-addressed datastore, so duplicate blocks across guests are stored once.

Connecting a PBS to a Proxmox VE node is a datacenter storage operation: you add a PBS datastore as a storage target (type pbs) with the PBS server address, datastore name, fingerprint, and credentials. Once added, it appears in the backup job target list like any other storage, and vzdump routes the backup directly to PBS over its native protocol.

The PBS web UI provides a separate view of stored backups with garbage-collection stats, verification jobs (which re-read and checksum backup chunks to detect corruption), and tape-out targets for long-term archiving. From the Proxmox VE side, you restore from PBS the same way as any other backup: select the archive and restore. The difference is that PBS restores only the blocks that have changed since the last restore, which can be significantly faster for large disks.

For any setup where storage efficiency and off-host durability matter, whether that is a separate physical PBS appliance, a PBS instance on a NAS VM, or a remote PBS over a WireGuard tunnel, PBS is the recommended backup target for production Proxmox VE environments.

How NexoVirt Ties It Together

Managing snapshots, on-demand backups, scheduled jobs, and PBS connections across multiple Proxmox hosts from separate Proxmox web UIs becomes unwieldy as the number of hosts grows. NexoVirt brings all of this into one panel, scoped per guest.

From a guest's detail page in NexoVirt you can take a snapshot before a risky change, roll back if something goes wrong, and delete the snapshot once you are done. The same page gives you on-demand backup to any datacenter storage, including a configured PBS datastore, and lets you browse, restore from, or delete existing backups. Scheduled backup jobs are managed at the datacenter level across all connected hosts, visible and editable in a single view without switching between Proxmox instances.

The rest of the NexoVirt feature set: cloud-init OS templates, IPAM & static IP assignment, NAT & port-forwarding, Plans with traffic limits and expiry enforcement, RBAC with a customer portal, TOTP 2FA, rule-based alerting with Discord & Google Chat webhook delivery, and a clean REST API, is covered on the features page.

NexoVirt is available now. Community Edition is free (up to 2 nodes). If you manage multiple Proxmox hosts and want a unified panel for snapshots, backups, and the rest of the guest lifecycle, you can get started free and try it against your own infrastructure.