DPX Product Overview
Enterprise backup and recovery for Linux, Windows, VMware, Hyper-V, databases, NAS, and application workloads.
OpenStack Workload Backup
OpenStack gives infrastructure teams flexible private cloud operations, but infrastructure snapshots are not the same as enterprise backup. Many OpenStack workloads need recoverable files, application data, database volumes, system state, retention policies, off-host copies, and restore workflows that are independent of the cloud control plane. DPX protects OpenStack workloads from inside the guest operating system. Install the DPX Client in supported Linux or Windows instances, register the client with the DPX Master Server, and apply backup policies based on the workload's recovery requirements.
For OpenStack in 2026, DPX is a workload-level protection solution. DPX core does not provide agentless OpenStack backup. Agent-based protection delivers meaningful advantages for enterprise workloads hosted on OpenStack.
DPX protects what runs inside the instance: files, volumes, operating system data, and supported applications.
Recovery does not depend on OpenStack-native snapshot metadata or tenant self-service backup workflows.
The same DPX model can protect OpenStack instances, physical servers, VMware VMs, Hyper-V VMs, and supported application servers.
For supported databases and applications, DPX can use workload-aware backup methods instead of treating the VM as an opaque disk image.
Backup administrators manage DPX policy, retention, catalog, storage, and restore procedures. OpenStack operators continue managing cloud infrastructure.
Agent-based protection supports restore planning that focuses on clean files, known recovery points, retention, and isolated backup storage.
DPX protects OpenStack workloads by installing the DPX Client inside the guest operating system. Once registered with the DPX Master Server, the instance can be included in backup jobs like other enterprise servers.
This is the most important positioning note on the page. DPX does not currently provide agentless OpenStack backup in the DPX 4.15 compatibility baseline. OpenStack workload protection is agent-based, installed inside the guest operating system.
| Area | 2026 DPX positioning |
|---|---|
| OpenStack agentless backup | Not a DPX core capability in the current DPX 4.15 compatibility baseline |
| DPX agentless virtual environment support | VMware and Microsoft Hyper-V |
| OpenStack workload protection model | Agent-based protection inside the guest OS |
| Supported guest operating systems | Use the DPX Compatibility Guide for the exact Windows and Linux versions |
| File-level backup | Supported for major compatible guest operating systems |
| Block-level backup | Supported for compatible Windows and Linux guests where OS and configuration requirements are met |
| Application backup | Supported where the application and guest OS combination is listed in DPX compatibility |
| OpenStack tenant or project integration | Not a DPX core claim |
| OpenStack Horizon self-service backup | Not a DPX core claim |
| OpenStack Cinder, Nova, Glance, or Ceph orchestration | Not a DPX core claim |
For OpenStack environments, design DPX protection around the guest workload. Validate the exact guest operating system, application, filesystem, volume layout, DPX version, and recovery workflow against the current DPX Compatibility Guide.
DPX provides workload-level protection for OpenStack environments through the same enterprise backup platform used for other physical, virtual, and application workloads.
Back up files and directories inside supported OpenStack instances for configuration, scripts, user data, application directories, and operational file recovery.
Use DPX Block Data Protection for supported Windows and Linux guests where the operating system and volume layout meet compatibility requirements.
After the initial base backup, DPX block backup uses changed-block tracking on the client node so subsequent backups transfer only changed blocks.
Protect supported applications inside OpenStack instances using DPX application backup workflows where the application and OS combination is supported.
Use DPX Bare Metal Recovery for supported operating systems when a full system rebuild path is required for the protected guest.
Use vStor, disk, tape, cloud, and object storage targets depending on retention, recovery, compliance, and cost requirements.
Track protected OpenStack workloads, backup jobs, retention, and restore points through the DPX catalog and management interfaces.
Use DPX cyber-resilience capabilities such as vStor retention controls, backup verification, and GuardMode workflows where supported by the backup type.
Protect OpenStack-hosted workloads alongside VMware, Hyper-V, physical servers, databases, NAS, and enterprise applications in the same DPX environment.
OpenStack continues to provide compute, networking, storage, identity, and tenant/project management. DPX does not need to control the OpenStack layer to protect the workload from inside the instance.
DPX protects the operating system and application data inside each selected instance. The protected instance is treated as a DPX client node, with backup policy, restore points, storage, and retention managed through DPX.
DPX protects enterprise workloads running on OpenStack, not the OpenStack control plane itself. These are the guest-level workloads that benefit from enterprise backup, retention, and recovery.
Protect supported Linux instances running application services, middleware, web services, scripts, and configuration data.
Protect supported Windows instances with file-level, block-level, and application-aware workflows where compatibility requirements are met.
Protect application servers and supporting systems around databases. Use DPX application pages for specific database workflows such as Oracle, SQL Server, and SAP HANA.
Protect shared file repositories, content stores, and operational data hosted inside OpenStack instances.
Protect selected identity, monitoring, automation, and infrastructure service nodes when they hold state that cannot be rebuilt safely.
Use DPX for persistent workloads that have business recovery requirements beyond OpenStack snapshot or rebuild processes.
For OpenStack, DPX support is determined primarily by the guest operating system and application compatibility, not by OpenStack itself. Validate the exact version and configuration against the current DPX Compatibility Guide.
| Guest workload type | DPX protection guidance |
|---|---|
| Supported Windows instances | File-level backup, block-level backup, application-aware backup where supported |
| Supported RHEL, AlmaLinux, Rocky Linux, CentOS, Oracle Linux, SLES, and Ubuntu instances | File-level and block-level backup where supported by the exact version and configuration |
| Debian instances | File-level backup where supported by compatibility |
| Application workloads | Use the specific DPX application compatibility matrix |
| Unsupported or short-lived instances | Use OpenStack rebuild automation or application-level replication instead of claiming DPX support |
For Linux block-level backup, confirm LVM and free physical extent requirements before deployment. Some Linux distributions support Block Data Protection in addition to file-level protection, but exact requirements must be validated before installation.
DPX recovery for OpenStack workloads depends on the backup method used inside the guest. File-level backups support granular recovery of files and directories. Block-level backups support broader recovery options for supported systems. Application backups provide workload-specific recovery where supported by DPX compatibility. For full instance recovery, OpenStack teams should coordinate infrastructure rebuild steps with DPX restore steps — recreating or replacing the OpenStack instance as needed, then restoring protected data or systems from DPX according to the documented recovery procedure.
OpenStack private clouds can host long-lived business systems that need the same ransomware recovery discipline as physical and VMware environments. DPX helps by keeping protected data in enterprise backup storage and supporting recovery-point selection workflows.
DPX stores backup data outside the protected OpenStack instance, reducing dependence on the compromised workload.
Use vStor deletion lock and retention controls where appropriate to reduce exposure to accidental or malicious deletion.
For supported block and VMware backups stored on vStor, DPX can verify that backup data can be accessed after backup completion.
Use GuardMode workflows where supported by the backup type and protected platform to identify suspicious file activity and inform restore decisions.
Use backup metadata, verification results, and operational investigation to select the safest available restore point.
Separate OpenStack administrative access from DPX backup administration and backup storage control.
OpenStack environments often mix fast-changing test workloads with persistent business systems. DPX storage design should reflect the recovery tier of each workload.
Use Catalogic vStor as software-defined backup storage for DPX environments that need scalable capacity, replication, retention controls, and efficient operations.
Use disk targets for operational recovery where recent restore points need faster access.
Use DPX tape support for long-term retention, offline copies, regulatory retention, and air-gapped recovery strategies.
Use object storage or cloud archive strategies for long-term retention and offsite copies where appropriate.
Apply different retention policies based on production, development, test, or application recovery requirements.
Use the same DPX storage strategy across OpenStack, physical servers, VMware, Hyper-V, databases, and file services.
Protect long-running business systems hosted on OpenStack where rebuild automation alone is not enough.
Install DPX Client in supported Linux instances for file-level or block-level protection.
Install DPX Client in supported Windows instances for file-level, block-level, and application-aware protection where supported.
Protect configuration, application directories, logs, stateful data, and supporting files for production application servers.
Use DPX application-specific protection for supported databases running inside OpenStack instances where compatibility requirements are met.
Keep recoverable backup copies outside the instance and use tested DPX restore procedures.
Retain OpenStack workload backups on disk, tape, vStor, cloud, or object storage based on compliance requirements.
Use DPX as a common backup platform across OpenStack workloads and the rest of the enterprise environment.
Use this as a concise technical planning reference. Every OpenStack instance that requires enterprise backup needs the DPX Client installed inside the guest operating system.
| Requirement area | Planning guidance |
|---|---|
| DPX Client | Install inside every OpenStack instance that requires DPX backup |
| Guest OS compatibility | Validate against the current DPX Compatibility Guide |
| Linux client requirements | Confirm memory, CPU, disk, libnss3, iSCSI package, and firewall requirements |
| Linux block backup | Confirm LVM and free physical extent requirements before enabling Block Data Protection |
| Windows block backup | Validate Windows version, application consistency, and VSS requirements |
| Network access | Ensure DPX client ports are reachable between protected instances and DPX infrastructure |
| Storage target | Select vStor, disk, tape, cloud, or object storage based on RPO, RTO, and retention |
| Recovery process | Document how DPX restore coordinates with OpenStack instance rebuild or replacement |
| Security | Separate DPX backup administration from OpenStack tenant and cloud administrator roles |
Do not skip the DPX Client installation for OpenStack instances. Unlike VMware and Hyper-V, DPX core does not provide agentless backup for OpenStack in the current DPX 4.15 compatibility baseline. Every protected OpenStack instance requires the DPX Client installed inside the guest.
Documentation and product resources for private cloud teams planning or operating DPX agent-based protection for workloads running on OpenStack.
Enterprise backup and recovery for Linux, Windows, VMware, Hyper-V, databases, NAS, and application workloads.
Supported guest operating systems, Linux and Windows versions, applications, and backup method requirements.
Software-defined backup storage with replication, deletion lock, and offload for enterprise backup environments.
Suspicious file detection and scan workflows for backup verification and safe restore selection.
For VMware environments, DPX provides agentless VM backup through vCenter and DPX proxy servers.
Talk to Catalogic about protecting Windows and Linux workloads running on OpenStack with DPX Client backup, file-level and block-level recovery, application-aware protection, vStor storage, ransomware recovery planning, and long-term retention.
Request Demo