vStor for block backups
vStor is a primary destination for DPX block backups. A vStor volume must be configured before it is used as a backup destination. Place the repository so it remains accessible during the recovery scenarios you plan to test.
OpenStack VM Backup
OpenStack Backup for Windows and Linux VMs
OpenStack backup with Catalogic DPX agents for Windows and Linux VMs. File and block backup, application recovery and supported full-system restores.
OpenStack backup from inside the guest operating system
Catalogic DPX provides OpenStack backup through a client installed inside each protected Windows or Linux VM. Customers use this agent-based approach to back up VMs deployed on OpenStack. The backup method and available restore options depend on the guest operating system, application and storage configuration.
Persistent application servers and file services need backups of the data they hold. DPX lets backup administrators define protection for these workloads, including scheduled jobs and retention policies. OpenStack operators manage the instance infrastructure and coordinate replacement instances when recovery requires them.
- File-level backup covers selected files and directories on supported guests.
- Block-level backup protects supported volumes, with incremental transfers after the initial base backup.
- Application-specific workflows protect supported databases and Microsoft applications.
- Bare Metal Recovery restores a system environment where the guest and recovery target meet DPX requirements.
Deploying DPX Client in OpenStack instances
Each protected instance is registered as a DPX client node. The DPX Master Server holds the catalog and schedules jobs; the backup destination receives the protected data using the protocol required by the backup method.
Client and backup configuration
Install the Windows or Linux DPX Client in the guest, then register its hostname or IP address with the DPX Master Server. Select the data to protect and a compatible backup destination for each job.
Choose schedules and retention according to the workload’s recovery requirements. Application backups also require the relevant DPX configuration for the supported application and version.
Network and recovery access
Configure tenant network routes, security groups and firewalls so the client can communicate with the DPX infrastructure. For example, block backup to vStor uses NFS, while block restore to the client uses iSCSI. Check the documented protocols and ports for the selected workflow.
Include replacement instances and recovery boot environments in network planning. A successful backup job alone does not establish that the recovery destination can reach the stored data. Test the intended restore path before relying on it in production.
Supported guest systems for OpenStack VM backup
The table summarizes the DPX 4.16 compatibility matrices for Windows Server and Linux guests. Versions are listed separately for each backup method because support differs between file backup, block backup and Bare Metal Recovery. Check the linked matrices and operating-system pages for filesystem and application restrictions.
These entries describe guest-level DPX support. An OpenStack distribution or deployment is not certified by this table. Validate the guest configuration and intended restore procedure for your environment.
| Guest OS | File backup versions | Block backup versions | BMR versions |
|---|---|---|---|
| Windows Server | 2025, 2022, 2019, 2016, 2016 Core | 2025, 2022, 2019, 2016, 2016 Core | 2025, 2022, 2019, 2016, 2016 Core |
| Red Hat Enterprise Linux | 7.0–7.9, 8.0–10.2 | 7.0–7.9, 8.1–10.2 | 7.0–7.9, 8.1–10.2 |
| AlmaLinux | 8.5–10.2 | 8.5–10.2 | 8.5–10.2 |
| Rocky Linux | 8.8–10.2 | 8.8–10.2 | 8.8–10.2 |
| CentOS Linux | 7.5–7.9, 8.0–8.3 | 7.5–7.9, 8.0–8.3 | 7.5–7.9, 8.0–8.1 |
| Oracle Linux | 7.1–7.9, 8.0–8.10, 9.0–10.1 | 7.3–7.9, 8.1–8.10, 9.0–10.1 | 7.5–7.9, 8.1–8.10, 9.0–10.1 |
| SUSE Linux Enterprise Server | 12 up to SP5, 15 up to SP7 | 12 up to SP5, 15 up to SP7 | 12 SP2–3 |
| Ubuntu | 18.04, 20.04, 22.04, 24.04 | 18.04, 20.04, 22.04, 24.04 | 18.04, 20.04, 22.04, 24.04 |
| Debian | 10.7, 11.3, 12.2, 13.2 | Not supported | Not supported |
Linux block backup requires LVM. The volume containing the DPX Client installation must belong to an LVM volume group with at least 10% free physical extents. Supported Linux filesystems are EXT and XFS; AlmaLinux 9.0 and Oracle Linux 9.0 support EXT only. Linux Instant Virtualization is not supported.
For the Linux BMR versions listed here, each physical disk on the recovery target must be smaller than 2 TB, and multipath devices are not supported. Linux BMR also excludes software RAID and fake RAID. BMR does not support ReFS; Windows Storage Spaces configuration is not restored by system-level recovery. Check these constraints before selecting a full-system recovery method.
Recovery
Recovery procedures for OpenStack workloads
DPX recovery follows the backup method used for the guest. File backups restore selected files and directories. Block backups support selective and volume restores on compatible systems. Application recovery follows the documented procedure for the protected database or application.
For a failed instance, the OpenStack team prepares the replacement compute, storage and networking needed for recovery. DPX then restores the protected guest data using the applicable procedure. Bare Metal Recovery requires a compatible target booted with the DPX recovery media and network access to the backup storage.
Test guest boot and application operation as part of the recovery exercise. Record any required driver or network adjustments, along with the time needed to provision an instance and restore its data. These steps establish the recovery procedure for your deployment.
Backup storage protection and ransomware detection
Backup storage controls and suspicious-activity detection serve different parts of recovery planning. Configure the controls required for your repository and review detection results when choosing a restore point.
vStor deletion locks
vStor supports deletion locks for volumes and snapshots. Multifactor authentication must be enabled to use the deletion-lock controls. Flexible snapshot locks can be changed or removed with MFA; fixed snapshot locks remain in place until their retention period expires.
A snapshot deletion-lock policy applies to new snapshots after the policy is enabled. Existing snapshots are unchanged, and the policy cannot be configured on replica volumes or volumes with an active offload relationship. Repository planning must account for these restrictions.
GuardMode monitoring and scans
GuardMode monitors filesystem activity for ransomware-like patterns and alerts administrators to suspicious behavior. Its role is detection. Review the supported platform and configuration before enabling monitoring on a guest.
On vStor, GuardMode can scan mounted filesystems for suspicious files. The results support investigation and restore-point selection. Use these findings together with incident analysis and recovery testing; a scan result alone does not guarantee that a recovered application is safe to run.
Backup destinations and retention
Select storage according to the backup method and retention requirements. Primary backup destinations and archive destinations have different roles; they are not interchangeable for every job type.
Disk directory for file backup
A DPX DiskDirectory device stores backups in a directory that acts as a virtual tape device. Storage design must account for disk failure; a backup in a local directory alone does not protect against failure of that disk.
Tape copies
DPX supports tape storage for file backups and archive workflows. Plan retention, media handling and recovery access together, including the device server and tape library required to read the retained copies.
Cloud archives of block data
DPX can archive block backups from vStor to supported cloud storage, including Amazon S3 and Microsoft Azure Blob Storage. The backup instance must exist on vStor before the archive job is created. Include archive retrieval in recovery testing.
Workloads and backup planning
Agent-based protection applies to supported guest systems with data that needs to be retained and recovered. The workload's recovery requirements determine which DPX method to use.
Linux application and file servers
File backup covers configuration files and persistent data on supported Linux guests. Block backup is an option when the distribution, filesystem and LVM layout meet the requirements. Debian guests use file-level protection.
Windows Server workloads
Supported Windows guests can use file and block backups. Application-specific protection requires a supported combination of Windows and application versions. Assess system recovery separately against the BMR matrix.
Database and application recovery
DPX provides application-specific backup methods for supported workloads. Select the method from the application's documentation rather than assuming that all guest-level backups provide application consistency.
Retention across infrastructure
OpenStack guests can be included in DPX protection alongside other supported servers. Define retention and recovery procedures for each workload, and record the infrastructure dependencies needed to restore it.
OpenStack backup FAQ
Does this OpenStack backup method require an agent?
Yes. Install DPX Client inside each protected instance. The workflow described here uses guest-level backup and recovery. DPX 4.16 lists VMware, Hyper-V and Proxmox VE in its agentless virtual-environment compatibility guide.
Is this backup managed through OpenStack Horizon?
Backup jobs and restores in this workflow are managed through DPX. OpenStack operators handle instance provisioning and infrastructure operations. This page describes protection of guest data and does not offer Horizon self-service backup or orchestration of Nova, Cinder or Glance resources.
Can DPX back up Debian instances?
The DPX 4.16 matrix lists file backup for Debian 10.7, 11.3, 12.2 and 13.2. Block backup and Bare Metal Recovery are not supported for these Debian versions.
Can DPX recover a complete guest system?
Bare Metal Recovery is available for the operating-system versions listed in the BMR matrix, subject to filesystem, disk and recovery-target restrictions. Prepare and test a compatible target. OpenStack infrastructure recreation remains part of the operator’s recovery procedure.
Can backups be retained in cloud storage?
DPX supports cloud archival of block data backed up to vStor. A backup instance must already exist on vStor before the archive job is created. Choose a supported cloud destination and test the archive recovery procedure.
Review your backup requirements
Discuss your OpenStack guest systems and recovery requirements with Catalogic. A review can cover client deployment, compatible backup methods and the storage needed for recovery.
Discuss backup for your OpenStack VMs
Review your guest operating systems and applications with Catalogic to plan DPX backup jobs and recovery procedures for your OpenStack environment.
Request a demo