> For the complete documentation index, see [llms.txt](https://docs.zmanda.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zmanda.com/guides/protected-items/proxmox.md).

# Proxmox

## Proxmox VE <a href="#proxmox-ve" id="proxmox-ve"></a>

*This feature requires Zmanda Pro 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, Zmanda takes a snapshot of the VM, then streams all necessary files into the Chunking engine, optionally using Changed Block Tracking (CBT) for improved performance. Zmanda then frees the VM snapshot on the host. The machine running Zmanda Backup does not require any temporary disk space.

### General Access Beta[​](https://docs.cometbackup.com/latest/protected-items/proxmox#general-access-beta) <a href="#general-access-beta" id="general-access-beta"></a>

Zmanda’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*

### Performance[​](https://docs.cometbackup.com/latest/protected-items/proxmox#performance) <a href="#performance" id="performance"></a>

Disk data is streamed from Proxmox to Zmanda. This means a large amount of traffic takes place over the internal network. For the best performance, Zmanda 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 Zmanda 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[​](https://docs.cometbackup.com/latest/protected-items/proxmox#requirements) <a href="#requirements" id="requirements"></a>

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

### Backup[​](https://docs.cometbackup.com/latest/protected-items/proxmox#backup) <a href="#backup" id="backup"></a>

#### Protected Item Configuration (Zmanda Backup desktop app)[​](https://docs.cometbackup.com/latest/protected-items/proxmox#protected-item-configuration-comet-backup-desktop-app) <a href="#protected-item-configuration-zmanda-backup-desktop-app" id="protected-item-configuration-zmanda-backup-desktop-app"></a>

1. Select Proxmox on the Protected Item list.\
   ![](/files/V5nuJewFjtuvtQUf1mLZ)
2. Populate Proxmox cluster credentials.\
   ![](/files/s1ru3V3kDJRrMnJtiNCw)
3. Run `Test Connection` to check the connectivity of the client to the host.\
   ![](/files/Iloio1YytVqZUx4yxCdb)
4. Use the picker to select which Virtual Machines from the Proxmox cluster to protect. Zmanda can protect all virtual machines and containers in a cluster, a single node of a cluster or individual virtual machines and disks.\
   ![](/files/L84j4y0VTagRhYc2kH2W)
5. Select the isolation method to use for selected containers.\
   ![](/files/2xkXUQ6dORuk2qgyBvsr)
6. Select the backup type - either Changed Block Tracking (default) or full backup. A full backup will back up all data on a disk whereas Changed Block Tracking will only back up blocks on disk which have changed since the last backup.\
   ![](/files/3KNoa6mktIq2sZwUOtAi)

#### Isolation[​](https://docs.cometbackup.com/latest/protected-items/proxmox#isolation) <a href="#isolation" id="isolation"></a>

When creating a backup, isolation mode determines how the container is handled during the backup process to ensure that the data captured is consistent and not being modified while the backup runs. You can choose between different levels of isolation depending on your storage type and tolerance for downtime.\
Note: these options currently only apply to containers.

**Default (Snapshot)**[**​**](https://docs.cometbackup.com/latest/protected-items/proxmox#default-snapshot)

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

**Stop**[**​**](https://docs.cometbackup.com/latest/protected-items/proxmox#stop)

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

**Suspended**[**​**](https://docs.cometbackup.com/latest/protected-items/proxmox#suspended)

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

### Restore[​](https://docs.cometbackup.com/latest/protected-items/proxmox#restore) <a href="#restore" id="restore"></a>

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[​](https://docs.cometbackup.com/latest/protected-items/proxmox#restore-directly-to-proxmox) <a href="#restore-directly-to-proxmox" id="restore-directly-to-proxmox"></a>

Select Storage Vault, and then Protected Item to restore from

1. Select Storage Vault, and then Protected Item to restore from\
   ![](/files/AWvgF5i9OeJWLnNOuW8S)
2. Select Restore to Proxmox

   ![](/files/BXw5Drg3GMLsOsoeRqXU)
3. Select the Virtual Machines to restore

   ![](/files/LiIJ2SkFdfPt0UWVw5bw)
4. Enter the credentials of the Proxmox cluster you would like the VM to be restored to.\
   ![](/files/96Zw1eIul3MwRvhzot8M)
5. Once the destination credentials have been configured, you can live browse the destination node and storage that the VM will be restored to.\
   ![](/files/ISyEnMYZALKy2uuqz62s)
6. Click restore to restore the selected VM(s) to the configured destination.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.zmanda.com/guides/protected-items/proxmox.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
