Proxmox Backups and Restore

What This Article Covers

• How backups work in Proxmox VE.
• The difference between snapshots and backups.
• Which storage targets are appropriate.
• How to set up backup jobs.
• How restore and disaster recovery work.
• Common pitfalls and best practices.

Introduction: Proxmox Backups and Restore

Backups are essential for any self-hosting setup. Proxmox VE includes built-in backup and restore functions for VMs and LXC containers. They protect against data loss, failed updates, ransomware, and accidental deletion. Automating backups and testing them regularly means you can recover quickly when trouble strikes.

This article shows how to set up, manage, and restore backups in Proxmox. It’s aimed at homelab operators and small teams who want to protect their virtual machines and containers.

Key Terms

• Snapshot: A point-in-time copy of a running or stopped container.
• Backup: A complete backup transferred to an external location.
• Retention: Rules determining how long backups are kept.
• Storage: The destination for backups, such as local disk, NFS, or Proxmox Backup Server.
• LVM-Thin: Storage format that enables efficient snapshots and backups.
• ZFS: A filesystem with built-in snapshots.
• vzdump: Command-line tool for backups in Proxmox.
• Disaster Recovery: Recovery after an outage.

Snapshots vs. Backups

Snapshots

• Created quickly.
• Remain on the same storage.
• Useful before updates or testing.
• No protection if storage fails.
• Deleted along with the guest when no longer needed.

Backups

• Written to a separate location.
• Can be transferred to different hardware.
• Protect against storage or host failure.
• Take longer than snapshots.
• Must be tested regularly.

Storage Targets for Backups

Available options in Proxmox:

• Local storage: Fast, but no protection if the host fails.
• NFS or CIFS: Network storage.
• Proxmox Backup Server: Specialized backup solution.
• USB or external hard drive: For small setups.
• Cloud storage via mount: For example S3 via rclone or s3fs.

Best practice: store backups in at least two different locations, with at least one outside your server.

Backing Up via the GUI

1. Select a datacenter or individual node.
2. Click Backup.
3. Select a VM or container.
4. Choose storage and mode.
5. Set retention.
6. Start the backup.

Backing Up via Command Line

vzdump 100 --storage backup-nfs --mode snapshot --compress zstd

Parameters:

• 100: ID of the VM or LXC.
• --storage backup-nfs: Target storage.
• --mode snapshot: Snapshot-based, guest keeps running.
• --compress zstd: Compression.

Backup Modes

• Snapshot: Guest continues running during backup.
• Suspend: Guest pauses briefly, consistent backup with minimal downtime.
• Stop: Guest is stopped, consistent backup, causes downtime.

For production systems, Snapshot is usually the right choice.

Automated Backup Jobs

Under Backup in the Datacenter section, you can create scheduled jobs. Recommended settings:

• Daily: Critical VMs and containers.
• Weekly: Less critical systems.
• Monthly: Archive backups.
• Retention: At least 7 days of daily backups, 4 weeks of weekly backups, 12 months of monthly backups.

Restoring a VM or LXC

Backups are restored via the GUI or using qmrestore and pct restore:

# Restore VM
qmrestore /var/lib/vz/dump/vzdump-qemu-100-2026_09_07.vma.zst 100

# Restore LXC
pct restore 100 /var/lib/vz/dump/vzdump-lxc-100-2026_09_07.tar.zst

During restore, you can assign a new ID if the original is still in use.

Individual Files from a Backup

For LXC backups, you can extract the .tar.zst file and pull out individual files. VM backups in .vma format must be restored to a VM first to access files.

Proxmox Backup Server

Proxmox Backup Server is a separate appliance for backups:

• Deduplication.
• Incremental backups.
• Checksums and integrity checks.
• User-friendly management.

Worth deploying in larger environments.

The 3-2-1 Rule

A proven backup strategy:

• 3 copies of your data.
• 2 different media.
• 1 copy off-site.

Following this rule protects you against most failure scenarios.

Common Pitfalls

• Never testing backups: Untested backups may not work when you need them.
• Insufficient space: Backups grow quickly, especially with daily jobs.
• Forgotten retention: Backups consume storage indefinitely without cleanup rules.
• Snapshots only: Snapshots are not backups and are lost if storage fails.
• Unencrypted external backups: Sensitive data should be encrypted.
• No restore plan: Lacking a clear procedure for emergencies.

Further Reading and Resources

• BotServ.de Proxmox Basics
• BotServ.de Proxmox Ollama
• BotServ.de OpenClaw on Proxmox
• BotServ.de Backup in General

FAQ: Proxmox Backups

How often should I create backups? Daily for critical systems, weekly for less important ones.

Are snapshots the same as backups? No. Snapshots stay on the same storage and do not protect you if storage fails.

Can I encrypt backups? Yes, Proxmox supports encrypted backups using a passphrase or key.

How much storage do backups need? Typically somewhat less than the sum of your VM disk sizes, depending on compression.

Can I move backups to another Proxmox instance? Yes, backups can be copied to compatible storage and restored there.

Sources and Further Reading

• Proxmox VE Backup Documentation: https://pve.proxmox.com/wiki/Backup_and_Restore
• Proxmox Backup Server: https://pbs.proxmox.com/
• 3-2-1 Backup Rule: https://www.veeam.com/blog/321-backup-rule.html

Summary: Proxmox Backups and Restore

Proxmox VE provides powerful backup and restore capabilities for VMs and LXC containers. The key is distinguishing snapshots from backups, choosing an appropriate storage target, automating backup jobs with sensible retention, and testing restores regularly. Following the 3-2-1 rule and encrypting backups protects you from most failure scenarios. Backups are not overhead but the foundation of a reliable self-hosting setup.