proxmox

How to Set Up Automatic Proxmox Backups

Losing a virtual machine to a failed disk, a bad update, or a misconfiguration is every homelab user’s nightmare. Setting up automatic Proxmox backups ensures that even if something goes wrong, you can restore your VMs and containers quickly without losing days or weeks of work — and Proxmox makes this far easier than most people expect.

Why Automated Backups Matter

Manual backups are easy to forget, especially once a homelab grows past a handful of VMs. Automating the process removes human error from the equation entirely, running consistently on a schedule whether you remember to trigger it or not. For anyone running production-like services at home — DNS, file storage, or self-hosted apps your household actually depends on — this isn’t optional.

Setting Up a Backup Job in Proxmox

Proxmox VE includes a built-in backup scheduler accessible directly from the web interface, no extra plugins required.

  1. Log in to the Proxmox web UI.
  2. Navigate to Datacenter → Backup.
  3. Click Add to create a new backup job.
  4. Choose the Node (or select “All” to back up VMs across your entire cluster).
  5. Set the Schedule — common choices are daily, or every few hours for critical VMs.
  6. Select the Storage destination where backups will be saved (local storage, an NFS share, or a dedicated backup server).
  7. Choose the Selection Mode: “All,” a specific pool, or manually selected VMs/containers.
  8. Set the Compression type — zstd is recommended for a good balance of speed and file size.
  9. Configure Retention settings to control how many backups are kept before older ones are automatically deleted.

Choosing a Backup Mode

Proxmox offers three backup modes:

  • Snapshot – fastest option, takes a live snapshot with minimal downtime, recommended for most use cases
  • Suspend – briefly pauses the VM during backup, slightly safer for data consistency but causes momentary downtime
  • Stop – fully shuts down the VM before backing up, safest for data integrity but causes the longest downtime

For most homelab workloads, Snapshot mode offers the best balance between safety and uptime.

Sending Backups Off-Site

Storing backups only on the same physical server defeats much of their purpose — if the hardware fails entirely, local backups go down with it. Consider adding a secondary storage target such as:

  • A NAS device on your local network (via NFS or SMB)
  • An external USB drive rotated periodically
  • A cloud storage bucket using tools like rclone for off-site redundancy

Testing Your Backups

An untested backup is not a reliable backup. Periodically restore a backup to a test VM to confirm it boots correctly and the data is intact, rather than assuming the backup job succeeding means the restore will work flawlessly too.

Final Thoughts

Configuring automatic Proxmox backups takes just a few minutes through the built-in scheduler, yet it’s one of the highest-value tasks you can do for your homelab. Combined with off-site storage and occasional restore testing, this simple setup protects hours of configuration work and irreplaceable data from a single hardware failure or bad update.

Similar Posts

Leave a Reply

Your email address will not be published. Required fields are marked *