Frequently Asked Questions
What’s the difference between the Proxmox module and QEMU module?
Bacula offers two distinct modules for Proxmox environments. The Proxmox module supports Full-level backups for both KVM virtual machines and LXC containers, creating VMA archives for VMs and TAR archives for containers. The QEMU module specifically targets QEMU virtual machines with both Full and Incremental backup capabilities, though it doesn’t support LXC containers. Choose the Proxmox module for comprehensive coverage or the QEMU module for incremental backup capabilities of virtual machines.
How does VMID management work during restore operations?
Bacula automatically handles VMID conflicts during restore operations through intelligent allocation strategies. When restoring to a Proxmox hypervisor, if the original VMID is available, the VM restores with its original identifier. If the VMID is already in use, Bacula assigns a new VMID either sequentially (next available) or randomly within a range of the maximum existing VMID +1 to +11. This approach prevents resource conflicts during concurrent restore operations while maintaining system stability.
Can I exclude specific VM disks from backup operations?
Yes, you can exclude individual virtual machine disks from Proxmox image backups directly through the Proxmox Console VM Disk Settings interface. This feature allows selective backup of critical disks while excluding temporary storage, swap disks, or other non-essential virtual storage devices, optimizing backup efficiency and reducing storage requirements without requiring complex configuration changes.
What backup modes are available for different VM states?
Bacula supports three backup modes for Proxmox VMs: snapshot mode (default) creates live backups using Proxmox snapshots with minimal downtime, suspend mode temporarily pauses VMs during backup for consistency then resumes operation, and stop mode completely shuts down VMs before backup and restarts them afterward. All modes work with VMs in any power state (running or stopped), and the hypervisor automatically manages snapshot creation and cleanup.
How does cluster support handle VM migration between nodes?
Bacula’s cluster support automatically adapts to VM migration between cluster nodes through the scan_proxmox_cluster tool. When VMs move between nodes, the tool updates job client directives to point to the current hosting node, ensuring backup operations continue seamlessly. If a VM is no longer detected on any node, the corresponding job resource is disabled or removed from configuration, maintaining clean and accurate backup policies across dynamic cluster environments.