One QPKG backs up Proxmox VE VMs and LXC containers, VMware ESXi / vCenter, Microsoft Hyper-V and Nutanix AHV. No agents on any host, guest or container: SpesBac drives each platform's native API to snapshot and export, and lands the backups directly in a NAS shared folder. A built-in Proxmox Backup Server adds incremental backup and deduplication, giving mixed virtualization estates a single, controllable backup hub where data never leaves the premises.
Ransomware, accidental deletion, failed upgrades and hardware faults all end the same way: you need a backup that restores. SpesBac lets an existing or new QNAP NAS act as both the backup target and the backup scheduler, with no separate Windows backup server to build.
Organizations running VMware alongside Proxmox, Hyper-V alongside Nutanix, or VMs alongside LXC containers, manage schedules, retention and run history from one console instead of buying a backup product per platform.
While moving from VMware to Proxmox VE, Hyper-V or Nutanix AHV, old and new platforms share the same backup workflow, so protection never lapses mid-migration.
Sites without a dedicated backup engineer or spare server get backup storage and job execution in a single QNAP NAS, managed from a web browser.
Backups land only in shared folders on the customer's own NAS and never pass through a public cloud. Ideal for regulated industries and for MSPs delivering managed backup on standardized hardware.
Connect, schedule, run, retain, review and restore: every step of VM and container backup lives in one NAS package.
Each platform is backed up with its native mechanism: vzdump for PVE VMs and LXC containers, snapshot plus datastore HTTP streaming for VMware, Export-VM over WinRM for Hyper-V, and the Prism Central v4 API for Nutanix. Nothing is installed inside the VMs or containers.
The QPKG ships a second container running Proxmox Backup Server. It provisions its datastore and admin password on first start and includes a PVE setup wizard, PVE VMs read only changed blocks via dirty bitmap, LXC containers upload only chunks PBS does not already hold, and both are deduplicated server-side.
Each job runs on a cron expression and keeps the newest N backups per VM. PVE uses vzdump prune-backups directly, for other platforms SpesBac prunes old timestamped backup folders automatically.
PVE restores through the API to a new VMID, detecting VMs and LXC containers automatically (next free ID suggested, NFS and PBS snapshots supported). Hyper-V restores with Import-VM -Copy -GenerateNewId and optional rename. VMware and Nutanix come with in-console restore instructions.
Every run keeps a full log and records transfer size. Each job lists its existing backup files, which can be deleted in place. The dashboard shows upcoming jobs and recent results at a glance.
Platform credentials are stored with Fernet encryption and the admin password with PBKDF2-SHA256. On startup the backup root must sit on a data volume, so backups can never silently fill the NAS system partition.
SpesBac runs as containers on Container Station. The QPKG itself is a thin shell that loads the images and starts or stops the service, so upgrades and removal are clean and nothing extra is left in the NAS system layer.
type / job / VM / timestamp in a dedicated backup shared folder on the NAS, ready for a second layer of protection with QNAP snapshots, HBS offsite replication or WORM.Admin login · Hosts & credentials · Backup jobs · Run history
vzdump (VMs & LXC) · Snapshot + datastore download · WinRM Export-VM · Prism v4 Recovery Point
<type>/<job>/<vm>/<timestamp> · PBS incremental datastore · Automatic retention
In-console restore for PVE / Hyper-V · Extend to 3-2-1 with native QNAP tools
Every platform is backed up through its official management interface: no host modification and no injected drivers. Preparation is limited to an account and a storage target.
| Platform | Restore | Prerequisites |
|---|---|---|
| Proxmox VE VMs & LXC containers | In-console restore to a new VMID, VMs and LXC containers auto-detected | A PVE storage pointing to the NAS, API token or password |
| VMware ESXi / vCenter | Guided manual restore steps in the console | Account with snapshot and datastore browse privileges |
| Microsoft Hyper-V | Import-VM -Copy -GenerateNewId with optional new name | WinRM enabled on the host, NAS share granted to the Hyper-V host |
| Nutanix AHV | Upload the .raw as an Image in Prism, then create the VM | Prism Central pc.2024.3 or later, account with VM, Recovery Point and Image privileges |
Six tabs cover day-to-day operations: Dashboard, Hosts, Backup Jobs, PBS Incremental, Run History and Settings. The mockup below is illustrative, values are for demonstration only.
| Job | Type | Schedule | Keep | Last Result | Transferred |
|---|---|---|---|---|---|
| PVE-Production | Proxmox VE (PBS) | 0 2 * * * | 14 | Success | 3.2 GB |
| VMware-ERP | VMware | 30 1 * * 6 | 4 | Success | 186 GB |
| HyperV-AD | Hyper-V | 0 3 * * * | 7 | Success | 42 GB |
| AHV-Web | Nutanix AHV | 0 4 * * 0 | 4 | Scheduled | - |
One QNAP NAS can be your backup hub, log archive and packet evidence store at the same time.
VM and container backup makes systems recoverable, SpesLog makes events traceable. Together they restore service after an incident while preserving a complete audit trail.
In a ransomware incident, packet evidence from SpesCap pinpoints when the intrusion began, and SpesBac restores from a clean backup taken before it.
Pre-installed on SPES-designed custom enterprise QNAP NAS, with storage pool planning, platform connections and first-backup verification completed by senior engineers.
Our architecture consultants are ready to help with virtualization inventory, backup strategy, NAS sizing and on-site PoC evaluation.