Skip to main content

Proxmox VE

Using this Protected Item type will not incur a per-guest charge while the beta program is ongoing.

This feature requires Comet Backup 25.6.8 or later.

This Protected Item backs up Proxmox virtual machines by connecting directly to a Proxmox VE cluster.

For each virtual machine selected for backup, Comet takes a snapshot of the VM, then streams all necessary files into the Chunking engine, optionally using Changed Block Tracking (CBT) for improved performance. Comet then frees the VM snapshot on the host. The machine running Comet Backup does not require any temporary disk space.

General Access Beta

Comet's Proxmox Protected Item is currently in General Access Beta.

Please note:

  • As this Protected Item is currently in beta, there is a risk of bugs or unintended behavior
  • Check this link for known beta limitations

Performance

Disk data is streamed from Promox to Comet. This means a large amount of traffic takes place over the internal network. For the best performance, Comet Backup should be installed as a VM on the same Proxmox VE cluster and/or specific host that it is backing up.

You can choose how many VMs Comet backs up at a time. Backing up multiple VMs at a time may increase performance.

Changed Block Tracking can be used to read only blocks that have changed since the last successful backup. Additionally, unallocated disk areas are skipped (Standard and CBT) to further improve the backup performance.

Requirements

  • Desktop Client
    • Running on the same network as the target Proxmox Cluster
  • Proxmox Cluster
    • Proxmox VE 8.x

Backup

Protected Item Configuration (Comet Backup desktop app)

  1. Select Proxmox on the Protected Item list.

  2. Populate Proxmox cluster credentials.

  3. Run Test Connection to check the connectivity of the client to the host.

  4. Use the pick to select which Virtual Machines from the Proxmox cluster to protect. Comet can protect all Virtual Machines in a cluster, a single node f a cluster or individual virtual machines.

  5. Select the back up method to use for all selected virtual machine. See consistency for more details on the possible modes.

Consistency

The following options are available to achieve point-in-time consistency when backing up the virtual machine:

Default (Snapshot)

Take a temporary snapshot of the virtual machine. The virtual machine is not interrupted. This is the fastest and best option, however, it requires the virtual machine disks to be on a storage device that supports snapshots.

Stop

Stop the virtual machine during the backup job and restart it after the backup job completes. This is disruptive but it can work when the virtual machine is on a storage device that does not support snapshots.

Suspended

Suspend the virtual machine during the backup job and resume it after the backup job completes. This is disruptive but it can work when the virtual machine is on a storage device that does not support snapshots.

Restore

With a Proxmox Protected Item, you are able to restore the data in a number of ways. The key ones being:

  • Direct restore to Proxmox
  • Direct restore to Hyper-V
  • Direct restore to VMware
  • Granular Restore (pick individual files / folders from the guests vm to restore)
  • Restore disk image files as *.img format

Restore Directly to Proxmox

  1. Select Storage Vault, and then Protected Item to restore from

  2. Select Restore to Proxmox

  3. Select the Virtual Machines to restore

  4. Enter the credentials of the Proxmox cluster you would like the VM to be restored to.

  5. Once the destination credentials have been configured, you can live browse the destination node and storage that the VM will be restored to.

  6. Click restore to restore the selected VM(s) to the configured destination.