DPX Compatibility Guide
Review supported platforms, versions, and workload-level capability notes for DPX.
Proxmox VE Backup
Proxmox VE Backup and Recovery with Catalogic DPX
Protect Proxmox VE environments with Catalogic DPX agent-based backup today and new agentless Proxmox protection for VM-level recovery, vStor, archive, and ransomware resilience.
Two DPX protection models for Proxmox VE
Proxmox VE backup programs usually need more than one method. Some workloads need application-aware backup inside the guest operating system. Other workloads need VM-level protection without deploying a backup client in every VM. Catalogic is expanding DPX so teams can combine both approaches with one platform.
Proxmox adoption creates new backup requirements
Proxmox VE gives organizations an open virtualization platform, but production data protection still needs centralized policy control, retention, tested recovery workflows, ransomware resilience, and support for mixed workloads.
VMware migration pressure
Many organizations are evaluating Proxmox after VMware licensing and portfolio changes. Backup teams need a model that can protect both existing enterprise workloads and new Proxmox clusters.
Mixed workload recovery
Proxmox VMs often run Windows Server, Linux, databases, file services, and line-of-business applications. Some workloads require guest-level, application-aware backup.
VM-level operational recovery
Not every workload needs a backup client in every VM. Agentless VM-level protection can lower operational overhead for broad Proxmox backup coverage.
Container considerations
Proxmox supports LXC containers as well as VMs. Container claims should stay aligned with documented DPX support for each release.
Storage diversity
Proxmox estates use local storage, ZFS, Ceph RBD, NFS, and mixed models. Backup design must match storage architecture and restore objectives.
Ransomware recovery
Enterprise Proxmox backup strategy needs immutable storage, offsite copies, archive, clean recovery points, and tested runbooks.
DPX capabilities for Proxmox data protection
DPX is positioned as the enterprise backup and recovery layer for Proxmox environments. The message combines current agent-based protection and new agentless Proxmox development while keeping release status clear.
- Agent-based backup for supported Windows and Linux guests running on Proxmox
- File-level and block-level backup for supported guest operating systems
- Bare Metal Recovery for supported guest operating systems where applicable
- Application-aware protection for supported workloads using DPX clients
- New DPX agentless Proxmox protection for VM-level backup and restore
- Centralized policy, monitoring, and recovery management
- vStor backup storage for efficient DPX recovery workflows
- Immutable backup storage for ransomware recovery design
- Archive to object storage or tape for long-term retention
- Hybrid strategy for VMware, Hyper-V, and Proxmox estates
Available Protection ModelValidate Guest OS Support
Protect critical Proxmox workloads from inside the VM
Agent-based DPX protection is the right model when workload recovery matters more than the hypervisor wrapper. Install the DPX client in supported Windows or Linux VMs running on Proxmox and protect operating systems, file systems, volumes, and supported applications according to the DPX Compatibility Guide.
Best-fit workloads
- Microsoft Windows Server VMs
- Red Hat Enterprise Linux, Ubuntu, SUSE Linux Enterprise Server, and Oracle Linux VMs
- Application servers that need deeper recovery workflows
- Database servers where application consistency matters
- File servers requiring granular file or volume recovery
Key points
- Protect the guest OS directly.
- Use file-level or block-level backup where supported.
- Use BMR where supported by guest OS and configuration.
- Recover files, volumes, or systems based on selected backup type.
- Maintain application-aware workflows for workloads that need them.
New DPX development: agentless Proxmox backup for VM-level recovery
Catalogic is expanding DPX to support agentless Proxmox VE protection. This path is designed for broad VM protection without installing a DPX client in every VM, with centralized policy management and lower operational overhead across Proxmox clusters.
Use agentless backup for broad VM coverage
Agentless Proxmox backup is the default direction for operational VM protection when teams want centralized protection without deploying backup clients inside every VM.
- Good fit for general-purpose VMs
- Reduces agent deployment and maintenance
- Simplifies protection across many VMs
- Useful for VMware-to-Proxmox migration projects
- Best for VM-level recovery workflows
Use agent-based backup for application depth
Agent-based DPX backup remains the recommended choice for critical applications, databases, and systems where the recovery target is application, file system, volume, or OS, not only the VM object.
- Better fit for application-aware recovery
- Supports guest OS and workload-level protection
- Enables granular recovery where supported
- Useful for SQL Server, Exchange, Oracle, SAP HANA, and similar workloads where applicable
- Reduces dependence on hypervisor snapshot consistency alone
Recover Proxmox workloads at the right level
A Proxmox recovery strategy should not force every incident into a full VM restore. DPX should be aligned to recovery choice: file, volume, application, VM, or full system depending on the selected protection path.
File recovery
Restore selected files from agent-based backups and, where documented, from agentless Proxmox VM backup workflows.
Volume recovery
Use DPX block-level protection for supported guest operating systems when volume-level restore is required.
Application recovery
Use agent-based DPX for supported applications that need consistency and application-aware recovery workflows.
VM recovery
Use the new agentless Proxmox protection path for full VM recovery as DPX Proxmox integration becomes available.
Bare Metal Recovery
Use BMR for supported guest operating systems and scenarios where full system rebuild is required.
Archive recovery
Recover from longer-retention copies stored on tape, object storage, or other DPX-supported archive targets.
Design Proxmox backup around storage reality
Proxmox environments are not all built the same way. Some use local ZFS. Some use Ceph RBD. Some use shared NFS. Others mix several storage models across clusters. DPX architecture planning should acknowledge this directly and map protection to the real storage design.
- Identify Proxmox cluster layout and node count.
- Identify storage type: local, shared, ZFS, Ceph, NFS, or mixed.
- Decide which workloads need agent-based backup.
- Decide which VMs can use agentless protection.
- Place vStor close enough to protected workloads for recovery performance.
- Replicate or archive backup data for disaster recovery.
- Test restore workflows before production migration.
Use vStor as the DPX backup target
Position Catalogic vStor as the primary DPX backup repository for Proxmox protection. vStor should anchor both agent-based recovery workflows and the new agentless Proxmox path where support is documented.
- Centralized DPX backup repository
- Backup target for agent-based workloads
- Backup target for new agentless Proxmox workflows where supported
- Replication support for disaster recovery design
- Efficient restore path for operational recovery
- Archive source for longer retention workflows
Build ransomware recovery into Proxmox backup
Proxmox adoption should not reduce ransomware recovery maturity. Use DPX with immutable storage, replicated copies, archive, and tested restore procedures so Proxmox workloads can be recovered after deletion, encryption, or infrastructure compromise.
- Immutable backup storage
- Offsite backup copies
- Archive to object storage or tape
- Restore testing and runbooks for Proxmox clusters
- Separation between production infrastructure and backup storage
Planning a VMware-to-Proxmox migration?
Many organizations are evaluating Proxmox VE as part of a broader virtualization strategy. Backup should be part of that decision from the start. DPX can help teams protect workloads during platform transition by supporting established enterprise backup methods and adding Proxmox-specific agentless protection as the DPX hypervisor roadmap expands.
Recommended messaging:
Proxmox support and compatibility notes
Keep this section as a marketing-level compatibility summary. Verify exact support details in the current DPX Compatibility Guide and Proxmox-specific DPX documentation when published.
| Area | Recommended positioning |
|---|---|
| Proxmox VE | Position as a target platform for new DPX agentless development |
| Proxmox VMs | Protect with agent-based DPX today when guest OS is supported; use agentless coverage as DPX Proxmox support becomes available |
| Windows guests | Protect with DPX client using file-level, block-level, and BMR features where supported |
| Linux guests | Protect with DPX client using supported Linux capabilities by distribution and version |
| Debian guests | Mention carefully because DPX Block Data Protection is not currently available for Debian |
| LXC containers | Mention as a Proxmox workload type and claim support only when product documentation confirms the model |
| Ceph RBD | Mention as a common Proxmox storage architecture; avoid implementation-specific support claims until documentation confirms details |
| vStor | Position as DPX backup storage and recovery repository |
| Legacy Proxmox positioning | Mention only when explaining existing Catalogic Proxmox support history or legacy positioning |
| Agentless Proxmox | Mark as new DPX development until GA documentation is published |
Always verify supported Proxmox VE versions, guest operating systems, storage types, backup modes, and restore options in the current DPX Compatibility Guide before designing production backup policy.
Common DPX deployment patterns for Proxmox
Agent-based protection for critical VMs
Install the DPX client in supported Windows or Linux VMs and protect applications, file systems, volumes, and operating systems with the right DPX backup type.
Agentless protection for broad VM coverage
Use the new agentless Proxmox protection path for general VM-level backup and recovery when available for your Proxmox version and storage design.
Hybrid Proxmox protection
Use agentless coverage for broad VM protection and agent-based backup for databases and application servers needing deeper recovery.
Proxmox cluster with vStor
Protect Proxmox workloads to vStor for centralized backup storage, operational recovery, replication, and archive workflows.
VMware and Proxmox side by side
Use DPX to protect mixed hypervisor environments while teams evaluate or migrate workloads from VMware to Proxmox.
Proxmox ransomware recovery
Use immutable vStor storage, replicated recovery points, offsite archive, and tested restore procedures for cyber recovery readiness.
Technical resources for Proxmox backup with DPX
Give administrators a direct route from marketing to implementation details. Until Proxmox-specific documentation is published, use compatibility guidance, agent-based support references, vStor details, and recovery documentation.
Microsoft Windows backup
See Catalogic positioning for Windows workload protection with DPX.
Red Hat Enterprise Linux backup
Review Linux workload backup positioning for RHEL environments.
Microsoft SQL Server backup
Review SQL Server protection scenarios where agent-based depth is needed.
Long-term Retention and Archival
Review DPX archive and retention options for longer policy windows.
DPX modern hypervisor protection
Track DPX direction for modern hypervisor coverage expansion.
Proxmox backup FAQ
Does Catalogic DPX protect Proxmox VE?
Catalogic is expanding DPX to support Proxmox VE protection. The recommended message is agent-based protection for workloads on Proxmox today, with agentless Proxmox protection being added as part of current DPX development.
What is the difference between agent-based and agentless Proxmox backup?
Agent-based backup installs the DPX client inside the guest VM and protects operating systems, file systems, volumes, and supported applications. Agentless backup protects VMs at the Proxmox hypervisor level without installing a DPX client in every VM.
When should I use agent-based DPX backup for Proxmox?
Use agent-based backup for critical workloads that need application-aware recovery, file or block backup, Bare Metal Recovery, or guest-level restore workflows.
When should I use agentless DPX backup for Proxmox?
Use agentless backup for broad VM-level protection where centralized management and lower agent maintenance matter more than deep application-specific recovery.
Does DPX support both Windows and Linux VMs on Proxmox?
DPX can protect supported Windows and Linux guest operating systems with agent-based backup. Exact capabilities depend on guest OS, version, file system, and compatibility guidance.
Does DPX protect Proxmox LXC containers?
LXC should be described carefully. If DPX Proxmox development includes LXC support, it should be stated directly in product documentation. If initial implementation is VM-focused, avoid claiming LXC support before documentation confirms it.
Does DPX replace Proxmox Backup Server?
DPX should not be framed as a one-for-one replacement for every Proxmox Backup Server use case. Position DPX as an enterprise backup and recovery platform for organizations that need centralized policy, ransomware recovery, long-term retention, archive, guest-level application protection, and mixed-platform support.
Can DPX help with VMware-to-Proxmox migration?
Yes. DPX can be positioned as a backup continuity layer for organizations moving workloads to Proxmox. Agent-based protection can follow supported workloads after migration, and new agentless Proxmox protection can provide VM-level coverage as integration becomes available.
Can DPX store Proxmox backups on immutable storage?
Position vStor and DPX immutable backup storage as part of a Proxmox ransomware recovery architecture. Confirm workflow-level details as Proxmox agentless documentation is published.
Where should users check exact Proxmox support?
Use the current DPX Compatibility Guide and Proxmox-specific DPX documentation when published for exact support details.
Evaluating Proxmox VE for production?
Talk to Catalogic about agent-based and agentless DPX protection for Proxmox workloads.
Protect Proxmox VE with Catalogic DPX
Use DPX to protect Proxmox workloads with agent-based backup for supported guest systems and new agentless Proxmox protection for VM-level recovery.
Request a Demo