Agentless Backup for VMware
Complete guide to DPX agentless VMware backup, proxy setup, and vCenter integration.
VMware Backup
VMware vSphere Backup and Recovery with Catalogic DPX
Protect VMware vSphere VMs with Catalogic DPX agentless backup, VADP, CBT, vStor, instant VM restore, VMDK restore, replication, and archive.
Agentless VMware backup for vSphere environments
DPX protects VMware virtual machines without installing backup agents inside every VM. Backups are coordinated through VMware vCenter and a Catalogic DPX virtualization proxy server. The proxy handles VMware snapshot processing, communicates with backup storage, and sends job information to the DPX Master Server.
- VMware vCenter integration
- DPX virtualization proxy servers
- VMware vStorage APIs for Data Protection (VADP)
- Changed Block Tracking for efficient incremental backup
- Auto-discovery and protection of new or changed VMs
- Instant and full VM recovery options
- VMDK-level restore
- Application-consistent backup where VM and application requirements are met
Why VMware backup needs more than VM snapshots
VMware snapshots are useful for short operational windows, but they are not a complete backup and recovery strategy. VMware environments need backup storage, retention, recovery orchestration, application consistency, and tested disaster recovery paths.
Agent sprawl
Installing and maintaining backup agents in every VM increases administrative overhead. DPX agentless VMware backup avoids this for broad VM protection.
Recovery time pressure
A full VM rebuild can take too long during an outage. DPX provides instant and full restore options so teams can choose the right recovery path for each incident.
Large VM estates
VMware environments often contain hundreds of VMs across folders, resource pools, clusters, and vCenters. DPX supports policy-level protection and VM auto-discovery.
Application consistency
Some VMs run SQL Server, Exchange, or Oracle and need consistency handling. DPX addresses when agentless quiescing is enough and when agent-based block protection is the better fit.
Storage and network impact
Backup transport matters. SAN, HotAdd, and LAN/NBD have different performance profiles. DPX supports architecture-aware VMware backup design.
Ransomware recovery
VMware backup must support clean recovery points, immutable backup storage, offsite copies, and repeatable restore workflows for ransomware incidents.
VMware backup capabilities in Catalogic DPX
DPX combines agentless VMware backup with flexible restore options and enterprise backup storage. The goal is not only to capture VM data, but to make VMware recovery practical under operational, ransomware, and disaster recovery conditions.
- Agentless VMware backup through vCenter
- DPX virtualization proxy architecture
- VADP-based protection
- Changed Block Tracking for efficient incremental backup
- Auto-discovery and protection of new or changed VMs
- Crash-consistent VM backup
- Application-consistent backup using VMware Tools and VSS-aware quiescing where applicable
- Instant VM Restore
- Full VM Restore
- Instant VMDK Restore
- Full VMDK Restore
- File restore from VM backup snapshots
- Agent-based block backup when granular application recovery is required
- vStor as a DPX primary backup destination
- Replication, archive, and long-term retention options
VMware Architecture
Use the right VMware backup transport for the environment
DPX VMware backup architecture uses a DPX Master Server, one or more virtualization proxy servers, VMware vCenter, ESXi hosts, protected VMs, and backup storage such as Catalogic vStor or NetApp. DPX does not need to be installed on vCenter, ESXi hosts, or every VM for agentless backup. Backups can use different transport paths — SAN and HotAdd are generally preferred for performance, while LAN/NBD is useful in smaller environments or where SAN or HotAdd access is unavailable.
- Deploy proxy servers close to protected VMs
- Use multiple proxies for larger environments and load balancing
- Prefer SAN or HotAdd where the environment supports it
- Use LAN/NBD where simpler deployment matters more than maximum performance
- Avoid combining VMs from multiple vCenters in one agentless backup job
- Define jobs at a container level such as resource pool or VM folder where practical
Recover a file, a VMDK, or an entire VMware VM
Different incidents require different restore paths. DPX provides explicit VMware recovery options so administrators understand how it handles operational recovery, VM failure, storage issues, and site recovery.
File Restore
Restore selected files or directories from a VM backup snapshot without treating every request as a full VM restore.
Instant VM Restore
Make a backed-up VM available quickly by mapping a snapshot to the original or alternate ESXi host or vCenter. Use this when recovery time matters more than immediately moving all data back to production storage.
Full VM Restore
Restore the complete VM by transferring data to a target datastore. Use this when the VM needs to be fully rehydrated into the VMware environment.
Instant VMDK Restore
Map a selected VMDK from backup to the original or alternate VM. Use this when the recovery target is a disk, not the entire VM.
Full VMDK Restore
Restore a selected VMDK into a VM when the disk must be permanently restored rather than temporarily mapped.
Rapid Return to Production
After instant recovery, use Rapid Return to Production to move the restored workload back to production storage where supported by the VMware licensing and storage configuration.
Use agentless VMware backup for broad VM protection
Agentless VMware backup reduces agent sprawl, simplifies protection across many VMs, integrates with vCenter, and works well for image-level VM protection across large VMware estates.
- No DPX installation required on every VM
- vCenter-based VM discovery and job management
- Proxy-based snapshot processing
- Good fit for large VMware estates
- Supports crash-consistent and application-consistent backup depending on VM configuration
Use DPX Block Data Protection for application depth
Some application workloads need deeper recovery than VM-level protection provides. For VMs running Microsoft SQL Server, Exchange Server, Oracle, or direct-attached volumes, DPX Block Data Protection provides application-aware recovery when granular restore is required.
- Application-aware protection for supported workloads
- Granular recovery where supported
- Better fit for database-heavy VMs
- Required for selected application-specific recovery scenarios
- Managed under the same DPX environment
Application-consistent protection for VMware workloads
DPX can create application-consistent VMware backups when the VM is configured for file system and application quiescing. For Windows VMs, VMware Tools can invoke Microsoft VSS to quiesce VSS-aware applications such as Active Directory, SQL Server, Exchange, and SharePoint before the VM snapshot is taken.
Application consistency through VMware quiescing is valuable, but it is not always a substitute for agent-based application protection. If the workload requires granular recovery, direct storage access, or application-specific restore workflows, use DPX Block Data Protection with the DPX Client installed inside the VM.
Use vStor as a VMware backup target
Catalogic vStor is the preferred DPX backup repository for modern VMware environments. It supports DPX block and agentless backups, can be deployed as a VMware virtual appliance, and serves as a primary backup destination for DPX recovery workflows.
- Primary backup destination for DPX
- Supports agentless VMware backups
- Supports block backup storage
- Can be deployed as a VMware virtual appliance
- Supports backup and recovery workflows from vStor
- Supports archive source use cases for block and agentless backups
Keep VMware backups recoverable after ransomware
For VMware ransomware recovery, DPX provides immutable backup storage, replicated recovery points, backup verification, offsite copies, and restore flexibility across file, disk, VM, and full-environment scenarios.
- Immutable backup storage with vStor
- Replicated backup copies for disaster recovery
- Archive to object storage or tape where required
- Recovery from alternate secondary storage
- Restore options for file, disk, VM, and full environment scenarios
VMware platform support
A compatibility overview for planning purposes. Always verify VMware version, datastore type, transport mode, restore option, and application consistency requirements in the current DPX Compatibility Guide before designing production backup policies.
| Area | DPX positioning |
|---|---|
| VMware vSphere 8.0.x | Supported for agentless VMware backup and restore where documented |
| VMware vSphere 7.0.3 | Supported for agentless VMware backup and restore where documented |
| VMware vSphere 6.7 | Supported where documented — verify in the current compatibility guide as older vSphere versions are aging out in many environments |
| VMware vCenter | Required for DPX agentless VMware backup management |
| VMware ESXi hosts | Managed through vCenter — DPX is not installed on ESXi hosts for agentless backup |
| VMware Tools | Required for VM quiescing and application-consistent backup scenarios |
| VMware vSAN | Supported — vSAN does not support SAN transport mode for VADP backup; other VADP transport modes continue to operate |
| VMware VVol datastore | Supported for agentless VMware backup to NetApp and vStor storage where documented |
| Multiple vCenters | Supported through separate backup jobs — avoid one job spanning multiple vCenters |
| VMware Cloud | Verify in the current DPX Compatibility Guide before claiming support |
Always verify VMware version, datastore type, transport mode, restore option, and application consistency requirements in the current DPX Compatibility Guide before designing production backup policies.
Common DPX deployment patterns for VMware
Small VMware environment
Use vCenter, one DPX virtualization proxy, and vStor as the backup destination. LAN/NBD may be acceptable if performance requirements are modest.
Medium VMware environment
Use multiple DPX virtualization proxies, vStor backup storage, and container-level backup jobs based on VM folders or resource pools.
Large VMware environment
Use multiple proxies, careful job separation by vCenter, SAN or HotAdd transport where possible, and replicated vStor storage for disaster recovery.
Database-heavy VMware environment
Use agentless VMware backup for general VM protection and DPX Block Data Protection for application-aware recovery of supported databases and application servers.
Ransomware recovery design
Use immutable backup storage, replicated backup points, verified snapshots, and documented instant restore workflows.
Hybrid retention design
Use fast local backup storage for operational recovery, replicated storage for disaster recovery, and archive to tape or object storage for long-term retention.
Technical resources for VMware backup with DPX
Documentation for VMware administrators planning or operating DPX agentless backup, proxy deployment, restore workflows, and vStor configuration.
Best Practices for Agentless VMware Backup
Architecture and job design best practices for DPX VMware backup in production environments.
DPX Compatibility Guide: Agentless Backup for VMware
Verify exact VMware vSphere version, transport mode, and restore support for your DPX deployment.
VMware backup FAQ
Does Catalogic DPX protect VMware vSphere?
Yes. Catalogic DPX supports VMware vSphere backup through agentless VMware backup, vCenter integration, DPX virtualization proxy servers, and VADP-based protection.
Does DPX require an agent inside every VMware VM?
No. For agentless VMware backup, DPX does not require installation inside every VM. DPX uses vCenter and one or more DPX virtualization proxy servers to process VMware backup jobs.
What VMware versions does DPX support?
The DPX Compatibility Guide lists support for VMware vSphere 8.0.x, 7.0.3, and 6.7 for agentless VMware backup and selected restore modes. Always verify support in the current DPX Compatibility Guide rather than relying on marketing pages for version-specific details.
Does DPX use VMware Changed Block Tracking?
Yes. DPX VMware backup uses VADP and Changed Block Tracking for efficient incremental backup of VMware virtual machines.
Can DPX restore an entire VMware VM?
Yes. DPX supports Instant VM Restore and Full VM Restore for agentless VMware backups. Instant VM Restore makes the VM available quickly by mapping a snapshot, while Full VM Restore transfers data to the target datastore.
Can DPX restore a VMDK?
Yes. DPX supports Instant VMDK Restore and Full VMDK Restore, allowing administrators to recover a selected virtual disk rather than the entire VM.
Can DPX restore individual files from VMware backups?
Yes. DPX supports file restore from VM backup snapshots.
Does DPX support application-consistent VMware backup?
Yes, where the VM and application meet the requirements. DPX can use VMware Tools and Microsoft VSS for VSS-aware Windows applications when file system and application quiescing is enabled. For granular application recovery, DPX Block Data Protection with the DPX Client installed inside the VM is the recommended approach.
Does DPX support VMware vSAN?
Yes, with transport-mode considerations. VMware vSAN does not support SAN transport mode for VADP backup. Other VADP transport modes continue to operate. See the current DPX Compatibility Guide for exact vSAN configuration requirements.
Should VMware Cloud be listed as supported?
Only if the current DPX Compatibility Guide confirms it. This page focuses on documented vSphere support. Contact Catalogic for current VMware Cloud support status.
Need to validate your VMware backup architecture?
Talk to Catalogic about vSphere backup, proxy placement, vStor sizing, restore workflows, and ransomware recovery planning for your VMware environment.
Protect VMware vSphere with Catalogic DPX
Use DPX to protect VMware virtual machines with agentless backup, VADP, Changed Block Tracking, vStor backup storage, instant recovery, VMDK restore, replication, and archive.
Request a Demo