Agent sprawl
Agentless backup through vCenter removes the need for software in every VM.
VMware Backup
VMware vSphere Backup and Recovery with Catalogic DPX
Protect VMware vSphere VMs with Catalogic DPX agentless backup, vCenter tag-based policies, encrypted VM support, flexible recovery, 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.
- Agentless VMware backup managed through vCenter
- VADP with Changed Block Tracking for efficient incremental backup
- Policy-driven VM selection using vCenter tags, with auto-discovery of new VMs
- Backup and recovery of VMs with encrypted virtual disks
- Instant and full recovery for VMs, VMDKs, and individual files
- Application-consistent backup for supported Windows workloads
- vStor backup storage with immutability, replication, and archive
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. Each challenge below links to the section that covers how DPX handles it.
Recovery time pressure
Instant and full restore options for files, disks, and whole VMs.
Large VM estates
Tag-based policies and auto-discovery keep hundreds of VMs in scope.
Application consistency
When VSS quiescing is enough, and when a database needs agent-based protection.
Storage and network impact
Choosing between SAN, HotAdd, and LAN/NBD transport, and sizing the proxies.
Ransomware recovery
Immutable backup storage, verified recovery points, and offsite copies.
Choose the right VMware backup method for each workload
DPX provides two ways to protect a VMware workload. Agentless VMware backup covers image-level protection through vCenter and needs no software inside the VM. DPX Block Data Protection runs the DPX Client inside the VM and fits workloads that need granular recovery, direct storage access, or an application-specific restore workflow.
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. VMware quiescing delivers application consistency for those supported applications, while database workloads that need object-level recovery are better served by agent-based protection. Many estates run both methods under the same DPX environment. See SQL Server backup and Oracle backup for application-specific detail.
| Requirement | Recommended DPX method |
|---|---|
| Image-level protection across many VMs | Agentless VMware backup through vCenter with proxy-based snapshot processing |
| Crash-consistent VM backup | Agentless VMware backup |
| Application-consistent backup of VSS-aware Windows applications | Agentless VMware backup with file system and application quiescing enabled |
| Granular recovery of SQL Server, Exchange, or Oracle objects | DPX Block Data Protection with the DPX Client installed inside the VM |
| Direct-attached or iSCSI volumes inside the VM | DPX Block Data Protection |
| Database-heavy VMware estate | Both methods, using agentless backup for the VM image and Block Data Protection for application recovery |
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
Common DPX deployment patterns for VMware
Size the VMware backup architecture to the estate. These patterns show how proxy count, transport choice, backup storage, and job design usually change as a VMware environment grows.
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.
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.
Keep protection aligned with vCenter tags
DPX can automatically include virtual machines in protection policies based on VMware vCenter tags, helping backup coverage follow workload classification and lifecycle changes. Administrators can select one or more tags, and VMs with any selected tag enter the backup scope automatically. New or changed VMs are discovered and protected without editing each job by hand.
Protect encrypted virtual machines
DPX supports backup and recovery of VMware VMs with encrypted virtual disks. A restored VM does not retain the original VMware encryption policy automatically, so administrators must reapply the appropriate policy and use a configured KMS when the restored VM must remain encrypted.
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. Replication alone leaves a gap here, because encrypted or corrupted source data can reach the replica.
- 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
Find your environment below. For exact versions, datastore types, transport modes, and restore options, see the DPX Compatibility Guide for agentless VMware backup.
| In your environment | What to expect from DPX |
|---|---|
| vSphere 8.0.x, 7.0.3, or 6.7 | Agentless backup and restore are supported. Check the compatibility guide for restore modes on the older releases. |
| vCenter | Required. DPX discovers and manages VMware backup jobs through vCenter. |
| ESXi hosts | Nothing to install. DPX reaches your hosts through vCenter. |
| VMware Tools | Needed for quiescing and application-consistent backup. |
| vSAN | Supported. SAN transport is unavailable on vSAN, so jobs use another transport such as HotAdd or LAN/NBD. |
| VVol datastores | Supported for agentless backup to vStor or NetApp storage. |
| More than one vCenter | Supported. Use one backup job per vCenter rather than a single job spanning several. |
| VMware Cloud | Talk to us about your deployment before you plan around it. |
Resources for VMware backup with DPX
Datasheets, release details, and customer results for teams evaluating or operating DPX in a VMware environment. The agentless VMware backup documentation covers proxy deployment, job configuration, restore workflows, and vStor setup.
Catalogic DPX Datasheet
Platform overview covering agentless VMware backup, instant VM restore, ransomware detection, and immutable vStor storage.
DPX 4.16 Release Overview
Current release details, including VMware vTPM support, vStor audit logging, and expanded disaster recovery.
Southern Utah University Case Study
How a heavily virtualized campus replaced a struggling backup system with Catalogic DPX and Quantum storage.
Latest VMware backup articles
Guidance from the Catalogic blog on VMware backup design, recovery objectives, and protecting vSphere virtual machines.
DPX
DPX 4.15: Modern NDMP Backup Management, VMware Tags, and Enterprise Encryption
DPX 4.15 delivers NDMP management in the web UI, VMware tag-based backup scoping, KMIP key management in vStor, and client-side cloud archive encryption. Here's what changed and why it matters.
DPX
GuardMode
Ransomware
Understanding GuardMode: Enhanced Ransomware Protection for Backups in 2025
Learn how GuardMode provides advanced Ransomware Protection for Backups. Detect threats before they corrupt your data and recover only affected files.
Catalogic
DPX
DPX vPlus
DPX vStor
Critical Insights into November 2024 VMware Licensing Changes: What IT Leaders Must Know
Discover how the November 2024 VMware licensing changes could impact your IT strategy, renewals, and budget planning. Prepare for informed decision-making.
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.
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.
What can DPX restore from a VMware backup?
DPX supports file restore from a VM backup snapshot, Instant and Full VMDK Restore for a selected virtual disk, and Instant and Full VM Restore for a complete virtual machine. Instant restores make data available quickly by mapping a snapshot, while full restores transfer data to the target datastore.
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.
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