Backup & Recovery (Proxmox VE)
StackConsole CMP provides integrated virtual machine backup and recovery for Proxmox VE, supporting both local Proxmox datastores and enterprise Proxmox Backup Server (PBS) integration.
To configure backup storages or API user credentials in the provider setup, see Connecting CMP to Proxmox and the Proxmox VE Capabilities & Explorer.
1. Supported Backup Targets
CMP supports two distinct backup destination models:
| Destination Model | Storage Target | CMP Support Status | Characteristics & Production Notes |
|---|---|---|---|
| Local Proxmox Datastore | Standard Proxmox storage (backup content type) | Supported | Standard vzdump archives stored on local host/cluster storage. Suitable for quick operational restores; does not provide external disaster recovery. |
| Proxmox Backup Server (PBS) | Dedicated PBS Datastore | Supported | Enterprise-grade deduplicated, incremental, encrypted chunk-based backups. Highly recommended for multi-node and commercial production environments. |
2. Dedicated Backup Storage & Selection Algorithm
CMP decouples VM root disk storage from backup target storage:
- Configuring Dedicated Backup Storage:
- Cloud providers can define dedicated backup storages under Settings → Orchestrator → Provider Setup → Step 4 (Storage Setting) or directly in Proxmox cluster configuration.
- Multiple Backup Storages Supported:
- Providers can configure multiple backup targets across different nodes or storage pools.
- Automated Storage Selection:
- When multiple backup storages are configured, CMP applies its built-in storage selection algorithm to evaluate target storage capacity, health, and load, automatically placing the backup archive on the best available storage target.
3. Proxmox Backup Server (PBS) Requirements & Permissions
When integrating Proxmox Backup Server with CMP:
The Proxmox API user configured in CMP must be granted the appropriate permissions across the Proxmox cluster and the PBS storage realm.
PVEDatastoreAdminon/storage(or the specific PBS storage identifier).PVEVMAdminon/vms(required to invoke backup jobs and manage snapshots).
If permissions are missing or restricted, backup job initiation will fail with an authorization error from the Proxmox API (403 Permission check failed).
4. Operational Capabilities & Workflows
4.1 On-Demand Backup Creation
- Customers and administrators can trigger on-demand backups from the CMP VM management view.
- The backup mode (snapshot, suspend, or stop) defaults to live snapshot mode to prevent guest downtime.
4.2 VM Scheduler Backups
- CMP supports automated scheduled backups configured by administrators or customers.
- Schedules define backup frequency (daily, weekly), execution time, and backup retention counts.
4.3 VM Restore Workflow
- Restores can be initiated directly from the backup archives list in CMP.
- Important: Restoring a VM overwrites the existing virtual machine disk state. The VM must be in a stopped state during the restoration process.
4.4 Backup Deletion
- Older or obsolete backup archives can be purged directly through CMP, automatically freeing allocated storage space on local datastores or PBS chunk pools.
5. VM Snapshot vs. VM Backup
It is critical to distinguish between snapshots and backups:
| Dimension | VM Snapshot | VM Backup |
|---|---|---|
| Mechanism | QEMU point-in-time state / delta file | Independent archive file or deduplicated chunk repository |
| Location | Resides on the same datastore pool as the VM disk | Resides on a dedicated backup datastore or external PBS instance |
| Use Case | Short-term rollback before software updates or testing | Disaster recovery, long-term retention, and hardware failure protection |
| Billing | Configured via VM Snapshot packages (per-GB hourly) | Governed via storage quotas and backup plan packages |
Related Documentation
- Proxmox VE Capabilities & Explorer — full matrix of supported backup, restore, and PBS capabilities
- Connecting CMP to Proxmox
- Node Selection Algorithm
- Proxmox Requirements Checklist