Backing up and restoring Proxmox VMs (backup, restore, deduplication)
How does Proxmox VE back up virtual machines?
The admin guide says Proxmox VE backups are always full backups with the guest’s configuration and all its data. You start them in the web interface or with vzdump.
A backup storage has to be defined first: either a Proxmox Backup Server, which stores backups as de-duplicated chunks and metadata, or a file-level storage with regular files. The guide recommends a Proxmox Backup Server on a dedicated host and calls an NFS server a good alternative.
How do I schedule regular backups?
Create a job under Datacenter → Backup. The schedule format is very similar to systemd calendar events, and “Repeat missed” runs a job the host slept through. By hand, this example from the guide backs up guest 777:
vzdump 777 --dumpdir /mnt/backup --mode snapshot
Which backup mode should I choose?
For VMs the guide knows three modes, and snapshot is the default:
- snapshot: the shortest downtime, at the cost of a small inconsistency risk. Blocks are copied while the VM runs. With the guest agent running, Proxmox VE briefly freezes the file system.
- stop: the highest consistency, at the cost of a short downtime. The VM is shut down in an orderly way and returns to full operation once the backup has started.
- suspend: kept for compatibility only. The guide recommends
snapshot, because suspending does not necessarily improve consistency.
How long does Proxmox VE keep backups?
The prune-backups option sets which backups stay, with keep-last, keep-daily, keep-weekly, keep-monthly and keep-yearly. An example from the guide:
vzdump 777 --prune-backups keep-last=3,keep-daily=13,keep-yearly=9
How do I restore a VM from a backup?
You can restore a backup in the web interface or with two command-line tools: qmrestore for VMs and pct restore for containers. The examples from the guide:
qmrestore /mnt/backup/vzdump-qemu-888.vma 601
pct restore 600 /mnt/backup/vzdump-lxc-777.tar
Can the VM run while it is still being restored?
For VMs stored on a Proxmox Backup Server, yes: with the --live-restore option of qmrestore or the checkbox in the interface. The VM starts at once and the data follows in the background, the chunks it is using first.
The guide names two caveats. The VM reads more slowly until the data has loaded, and if the live restore fails, the VM is left in an undefined state, and data written meanwhile is most likely lost.
Can I restore single files?
Yes, but only for backups on a Proxmox Backup Server. The “File Restore” button in the Backups tab of the storage opens a file browser on the backup. For VMs, the guide says not all data may be accessible, for example with unsupported guest file systems.
What does Proxmox Backup Server add?
Proxmox Backup Server (PBS) backs up virtual machines, containers and physical hosts. Its documentation lists:
- Incremental and de-duplicated: backups are sent to the server incrementally and de-duplicated there. Each backup still references all data and is therefore a full backup.
- Verification: SHA-256 checksums protect integrity. Verify jobs check the backups on a schedule, and all backups should be re-verified at least monthly.
- Remote sync: data can be synchronised efficiently to another site, and only new data is transferred.
For setup, see Installing and setting up Proxmox Backup Server; for licence and cost, Is Proxmox Backup Server free?.
How does the deduplication work?
PBS stores data as chunks identified by their SHA-256 checksum. Several snapshots can reference the same chunks. For VMs the chunks are all the same size, typically 4 MiB. With “dirty bitmaps”, Proxmox VE remembers which blocks changed and uploads only those.
A deleted snapshot does not free its space at once, because other backups may reference the same chunks. A garbage collection run removes what no snapshot needs any more.
How do I keep a second copy at another site?
Use a remote and a sync job. A remote is another Proxmox Backup Server, and a sync job matches its datastore against a local one. The guide creates the remote first and then the job:
proxmox-backup-manager remote create pbs2 --host pbs2.mydomain.example --userid sync@pam --password 'SECRET' --fingerprint 64:d3:ff:3a:50:38:53:5a:9b:f7:50:...:ab:fe
proxmox-backup-manager sync-job create pbs2-local --remote pbs2 --remote-store local --store local --schedule 'Wed 02:30'
This is a pull job, running on the server that is to receive the copy. Jobs in push direction need at least PBS 2.2 on the target, and the documentation advises a dedicated remote with a dedicated user for each of them.
How do I protect the copy from ransomware?
With remove-vanished, a sync job also deletes backups that have disappeared at the source. As protection against ransomware, the documentation says to leave it off, so that an attacker who has taken over the source cannot cause deletions on the target hosts. That is the pull case, like the job above.
For push jobs, the manual advises a remote user with limited permissions on the target. Separate from that is Remote.DatastorePrune: the user of the sync job needs this right on the sending server, only to remove vanished snapshots and groups on the target.
The 3-2-1 rule, off-site targets and cloud storage are covered in Proxmox Backup Server: cloud and off-site.
How do I back up a host or a file system with proxmox-backup-client?
The command-line client also backs up machines that Proxmox VE does not manage. The FAQ says it works on most modern Linux systems. The documentation’s example uploads the root directory as a file archive:
proxmox-backup-client backup root.pxar:/ --repository backup-server:store1
The client does not include mounted volumes automatically and reports “skip mount point”. Add them with --include-dev, for example --include-dev /boot/efi. To restore, list the snapshots and restore an archive. For single files there is an interactive shell, catalog shell.
The commands below give no --repository. The variable PBS_REPOSITORY selects the same repository as the option; the manual sets it like this:
export PBS_REPOSITORY=backup-server:store1
proxmox-backup-client snapshot list
proxmox-backup-client restore host/elsa/2019-12-03T09:35:01Z root.pxar /target/path/
What about the Proxmox host itself?
vzdump backs up guests, meaning VMs and containers. For the host, the documentation gives two starting points. The client command above also backs up physical hosts.
The configuration under /etc/pve lives in a database, /var/lib/pve-cluster/config.db. With serious problems, the guide says it can help to copy that file to a new Proxmox VE host: stop the pve-cluster service, replace the file, adapt /etc/hostname and /etc/hosts, reboot. The guest data does not come along.
Nexilon, a certified Proxmox Silver Partner, plans, installs and looks after Proxmox environments, takes over operations on request and offers a managed offsite PBS in its own data centres.
Sources
- Proxmox VE Administration Guide: Backup and Restore, retrieved on 12 November 2026
- Proxmox VE Administration Guide: Proxmox Cluster File System (pmxcfs), retrieved on 12 November 2026
- Proxmox Backup Documentation: Introduction, retrieved on 12 November 2026
- Proxmox Backup Documentation: Backup Client Usage, retrieved on 12 November 2026
- Proxmox Backup Documentation: Managing Remotes & Sync, retrieved on 12 November 2026
- Proxmox Backup Documentation: Maintenance Tasks, retrieved on 12 November 2026
- Proxmox Backup Documentation: Technical Overview, retrieved on 12 November 2026
- Proxmox Backup Documentation: Backup Storage, retrieved on 12 November 2026
- Proxmox Backup Documentation: FAQ, retrieved on 12 November 2026