How to Design a Proxmox Backup Strategy with Comet Backup

Key Takeaways

• Decide which Proxmox VMs need to come back first, then set backup timing, storage, and retention around those systems.
• Comet Backup lets you choose exactly which VMs, containers, nodes, or disks to protect via its Proxmox Protected Item.
• Changed Block Tracking helps keep Proxmox backups smaller after the first successful run. Your storage gets a breather.
• GFS retention and admin controls keep Storage Vaults tidy, restore points useful, and “who changed this?” moments to a minimum.

A good Proxmox backup strategy starts by deciding which VMs should be restored first, how often they should be backed up, and where those backups should be stored.

With Comet Backup, you can build that plan around Proxmox VE workloads, flexible storage, and fast restore paths.

Why use Comet Backup for Proxmox VE backups?

Comet Backup gives MSPs and IT teams a direct way to manage Proxmox VE backups inside their existing backup workflow. It connects to your Proxmox VE cluster, so you can choose the VMs, containers, nodes, and disks that need protection.

Here’s where it helps most:

• Direct Proxmox VE protection: Comet Backup connects to the Proxmox VE cluster through a Proxmox Protected Item. You can pick the VMs, containers, nodes, and disks that need protection, then run those jobs through the same Comet Backup workflow you use for the rest of your environment.
• Efficient backup runs: Changed Block Tracking helps Comet Backup back up only the disk blocks that changed since the last successful job. That keeps backup runs lighter, especially on larger VMs and busy clusters.
• Greater choice between restore options: Comet Backup lets you restore Proxmox VE backups to Proxmox VE, Hyper-V, or VMware. You can back up the entire VM set or back up individual VMs based on priority, schedule, and retention needs.

How to Build a Proxmox Backup Strategy with Comet Backup

To design a robust Proxmox VE backup strategy with Comet Backup, follow these steps:

Step 1 – Prepare Your Environment.

Ensure you are running Proxmox VE 8.x or higher and that the Comet Backup Agent is installed within the same network as your target Proxmox cluster. 

Step 2 – Add Protected Item.

Open the Comet Backup desktop application, click on Protected Items, select + Add Protected Item:

Source – Alt text: Protected Items within Comet Backup Management Console

You’ll see a list of backup types you can select with Comet Backup. Choose Proxmox from the list, rename it as needed, and click next.

Step 3: Configure Cluster Credentials.

Enter your Proxmox cluster credentials, click Test Connection, and then click Next:

Source – Alt text: Proxmox Cluster Credentials Test Connection in Comet Backup

Step 4: Select VMs & Containers to Backup.

Use the built-in picker to choose whether to protect all virtual machines/containers in the cluster, a single node, or even individual virtual machines and disks:

Source – Alt text – Machine Backup Options You Can Choose From 

Step 5: Set Isolation Mode (for Containers). 

When setting up your Proxmox backup, you can choose from multiple isolation modes, which determines how the container is handled during the backup process:

Source – Alt text – Isolation Modes: Snapshot, Stop, and Suspend 

Pro tip: Default Snapshot mode is usually the best starting point when the container sits on storage that supports snapshots. Stop and Suspend are also available when you need the container handled differently during the backup job.

Step 6: Choose Backup Type.

You get the option to choose two backup types –

• Changed Block Tracking (default): Backs up only disk blocks that changed since the last successful backup; this is the default option and the better fit for most Proxmox VE backup jobs
• Full Backup: Backs up all the data on the disk

Source – Alt-text: Backup Type Options within Comet Backup Console

Once done, head over to the Schedule tab and click on the + sign to add a backup schedule:

Source – Alt text: Schedule a Backup Process 

You can configure multiple backup schedules as needed with the common schedule types being daily, weekly, monthly, and so on:

Source – Alt text: Scheduling Options Available 

Pro tip: Don’t forget to select the Storage Vault where your backups will be stored. Click Save and you’re done!

Best Practices for Designing a Proxmox Backup Strategy 

Once your Proxmox Protected Item is configured, the real win is keeping the setup clean, predictable, and easy to restore from.

Comet Backup gives you the controls, but the strategy still needs a bit of admin discipline. Here are a few backup best practices to keep in mind:

• Use GFS retention: Comet Backup’s default retention policy keeps all backups forever. That is fine for day one, but not so much for a long-term plan. To keep your Storage Vaults purposeful, use the Grandfather-Father-Son retention policy: 

• Keep all backups for the last 3 days
• One backup per day for 14 days
• One backup per month for 24 months

• Make schedules and retention rules line up: If a rule keeps Sunday backups, make sure a job runs on Sunday. 
• Keep Storage Vaults manageable: Smaller Storage Vaults can be easier to clean up and lighter to process during retention passes. 
• Plan storage around the actual backup load: If you are self-hosting storage, size it for the IOPS your concurrent Proxmox backup jobs will require. “It worked fine in testing” is not a storage plan. For cloud storage, Storage Templates can help standardise direct-to-cloud backups across users and environments.
• Protect backup settings from unwanted changes: Use policy controls to limit who can delete snapshots, edit Storage Vaults, change Protected Items, and override retention settings. Admins should be able to trust that the backup policy they set is still in effect tomorrow morning.
• Back up the Comet Backup setup too: Enable System Self-Backup for the Comet Management Console and store it in a safe off-site location. Keep your server and devices up to date on your chosen release stream. You also want to make sure your systems stay synced with internet time so schedules and logs stay accurate.

FAQs

Does Changed Block Tracking help Proxmox VE backups run faster?

Surely. After the first successful job, Comet Backup reads only the disk blocks that changed. This keeps backup windows tighter, reduces unnecessary data movement, and makes your storage shift much easier.

Where should I install the Comet Backup Agent for Proxmox VE?

Install the Comet Backup Agent as a VM on the same Proxmox cluster or host you are protecting to keep backup traffic close to the source, reduce extra network hops, and give Proxmox backup jobs a cleaner path to run.

Can Comet Backup restore one file from a Proxmox VM backup?

Comet Backup can browse image-based Proxmox VM backups and restore individual files or folders from inside the disk image. Meaning, you can recover the file someone needs without restoring the whole VM. 

How does Comet Backup protect Proxmox backup data?

Comet Backup encrypts the backup on the client before it leaves the client. By the time your Proxmox VM data reaches cloud, off-site, or provider-managed storage, it is already encrypted with AES-256-CTR.

Are Proxmox snapshots enough for backup?

Proxmox snapshots are useful for quick rollback, but they are not a full backup plan. A proper strategy needs separate storage, retention rules, and tested restores.