VMware vSphere
Restore a complete VM or selected files from supported backups. Instant VM Restore lets you start a VMware VM from a backup snapshot.
Catalogic DPX ยท Virtual machine backup
VMware, Hyper-V and Proxmox backup
Protect VMware, Microsoft Hyper-V and Proxmox VE virtual machines with Catalogic DPX. Manage backup and restore in one platform, without deploying a backup agent inside each protected guest.
For teams running a mixed VM estate or adding another hypervisor. Explore your platform below, then review the deployment and recovery details.
Backup for the hypervisors you run
Choose your platform to see the backup and recovery options that fit your environment.
Microsoft Hyper-V
Protect VMs through a host backup agent. Restore a complete VM, or retrieve selected files from supported backups on vStor.
Proxmox VE
Back up QEMU virtual machines to vStor without a guest backup agent. Restore VMs to their original or an alternate Proxmox node.
VMware backup with file and instant restore options
Use VMware VADP through a DPX proxy to back up supported VMs to vStor or NetApp storage. After the base backup, VMware Changed Block Tracking identifies the blocks to transfer.
- Restore a complete VM to its original or an alternate ESXi host.
- Retrieve selected files from supported VM filesystems when the backup is stored on vStor.
- Start a VMware VM from a backup snapshot with Instant VM Restore, then use Rapid Return to Production to move it to permanent storage.
- Create application-consistent backups with the file system and application quiesce option enabled. VMware Tools must be installed in the source VM.
Hyper-V backup through a host agent
Install the DPX Hyper-V Backup Agent on the host to handle snapshot processing and communication with backup storage. Protected guests do not need a DPX backup agent. Backup and restore use the DPX web interface.
- Protect supported Hyper-V hosts and clusters, with discovery of new and modified VMs.
- Restore a complete VM to a selected Hyper-V host.
- Download selected files from supported VM backups on vStor.
- Review VM configuration versions before deployment. The documented agentless workflow requires version 8.0 or later.
Proxmox VE backup for QEMU virtual machines
DPX reads VM data through the Proxmox API and a host plugin, storing recovery points on vStor. Backup and restore are managed in the DPX web interface.
- Protect QEMU VMs across multiple Proxmox clusters in one backup job. LXC containers are outside this workflow.
- Transfer changed blocks after the base backup while valid change tracking is available.
- Account for disk format when planning backup windows. RAW and VMDK disks lose change tracking after a power-off or restart; QCOW2 tracking persists.
- Restore VMs to the original or an alternate node and storage. DPX creates new VMs rather than overwriting existing machines.
Choose a restore workflow for the incident
Start with the affected workload and the result you need. The available workflow depends on the source platform and backup repository.
Recover missing files
Use agentless file restore for supported VMware and Hyper-V backups on vStor. Check filesystem eligibility before relying on this path.
Rebuild a complete VM
Restore a full VM from a retained recovery point in the supported VMware, Hyper-V or Proxmox workflow. Plan the destination host and storage before an incident.
Start a VMware VM from backup
Use Instant VM Restore when you need to start a VMware VM from its backup snapshot. Returning it to permanent storage through RRP requires Storage vMotion and the appropriate license.
Deployment and recovery details
Agentless means no DPX backup agent inside each protected guest VM. The components outside the guest, and the available restore workflows, depend on the hypervisor.
| Deployment or recovery task | VMware vSphere | Microsoft Hyper-V | Proxmox VE |
|---|---|---|---|
| Backup components | DPX virtualization proxy using VMware VADP | DPX Hyper-V Backup Agent on the host | Proxmox API and DPX plugin on the host |
| Full VM restore | Original or alternate ESXi host | Selected Hyper-V host | Original or alternate Proxmox node and storage |
| Selected file restore | Supported filesystems on vStor | Supported filesystems on vStor | Outside the documented agentless file-restore workflow |
| Instant VM Restore | Start a VM from a backup snapshot | Full VM restore workflow | Proxmox Restore workflow |
| DPX Archive to cloud or tape | Supported; cloud archival requires a vStor source | Not supported for agentless Hyper-V backups | Not supported for Proxmox backups |
Scope: current DPX 4.16 documentation. Check supported hypervisor versions before deployment.
File restore requires vStor and excludes ReFS, Btrfs and LVM-managed volumes. Individual browser file downloads are limited to 2 GB. Review file-restore requirements.
VMware Rapid Return to Production uses Storage vMotion and requires appropriate vSphere licensing. Review migration requirements.
How agentless backup connects to your hosts
VMware backups read through DPX proxy servers. Hyper-V uses a host backup agent, and Proxmox uses its API with a DPX host plugin. These components replace per-guest backup agents for the supported agentless VM workflows.
Plan protected copies and longer retention
Protect retained snapshots
vStor deletion locks protect retained snapshots against modification and deletion. MFA is required to configure locks; fixed protection remains in place until its retention period expires.
GuardMode Scan checks supported mounted filesystems for ransomware indicators. Review scan results and test recovery when choosing a recovery point.
Match archival to the source platform
DPX Archive supports agentless VMware backups and block backups. Agentless Hyper-V and Proxmox backups are outside this archive workflow. VMware cloud archival requires the source repository to be vStor.
Discuss the backup type and retention requirements together before selecting cloud or tape archival. See long-term retention and archival for the available workflows.
Questions to resolve before deployment
Does agentless backup cover every application recovery task?
VM-level protection and granular application recovery have different requirements. For example, restoring an individual SQL Server table uses application-aware agent-based protection. The VMware application-consistency guide explains when the DPX Client is needed inside a VM.
Which versions and guest configurations are supported?
Use the DPX compatibility matrix and the platform-specific backup guide to check your hosts and guests. Review VM configuration versions for Hyper-V, and disk formats and QEMU coverage for Proxmox before planning the backup job.
Can one Proxmox restore job recover several VMs?
Yes. A restore job can include VMs from different Proxmox backup jobs. DPX restores them one at a time in the order you choose. Recovery points must still be active. See the Proxmox restore guide.
What should we verify in a recovery test?
Test the restore workflow you expect to use, including the destination host and storage. For file restore, confirm filesystem eligibility and the vStor requirement. For VMware RRP, confirm Storage vMotion licensing. Include application checks before accepting the recovered workload.
Plan a hypervisor backup demo
Bring your hypervisor versions, VM count and backup-storage plan. We will review the relevant backup and restore workflows against your recovery objectives.
Resources for hypervisor evaluation
Review Proxmox coverage and the DPX 4.16 release details before planning a deployment.
Catalogic DPX for Proxmox VE
Review the Proxmox backup offering alongside the setup and restore documentation.
DPX 4.16 Release Overview
Read the release overview for the changes introduced with DPX 4.16.
See DPX with your hypervisor requirements
Share your VM estate and recovery objectives. We will walk through the backup components, storage requirements and restore workflows relevant to your environment.
Request a hypervisor backup demo