Catalogic DPX
Enterprise backup and recovery for supported physical, virtual, and application workloads.
Operating System Protection
Current DPX compatibility data lists Canonical Ubuntu 18.04, 20.04, and 22.04 LTS for DPX Client protection. Newer Ubuntu releases, including Ubuntu 24.04 LTS, should be validated against the current DPX Compatibility Matrix or with Catalogic Product and Support before production rollout.
| Coverage area | DPX status for Ubuntu | Planning guidance |
|---|---|---|
| Canonical Ubuntu 18.04 LTS | Supported | Mention as supported, with OS lifecycle caveat |
| Canonical Ubuntu 20.04 LTS | Supported | Mention as supported, with OS lifecycle caveat |
| Canonical Ubuntu 22.04 LTS | Supported | Position as the primary current Ubuntu LTS target |
| Ubuntu 24.04 LTS | Not listed in current DPX compatibility data | Validate before planning production protection |
| File-level backup | Supported | Use for files, directories, and standard filesystem recovery |
| Block-level backup | Supported | Use for efficient volume-level protection on supported configurations |
| IA mapping, selective restore, volume restore | Supported for block backup | Position as recovery flexibility for block backup users |
| Bare Metal Recovery | Supported | Include target disk and multipath limitations in implementation notes |
| Device or SAN Device Server | Supported | Use where the deployment architecture requires it |
| NDMP Proxy | Supported | Treat as an advanced deployment capability |
| Cluster | Not supported | Plan non-cluster Ubuntu protection paths |
| Instant Virtualization for Ubuntu client backup | Not supported | Use other supported recovery workflows |
| Block backup file systems | EXT and XFS | Include XFS caveats in technical notes |
| Agentless VM backup | VMware and Microsoft Hyper-V | Limit agentless planning to documented hypervisor paths |
DPX support does not replace Canonical operating system lifecycle management. Customers should keep Ubuntu systems under an appropriate Canonical support or security maintenance plan.
For Ubuntu systems on hypervisors outside the documented DPX agentless paths, position DPX Client protection inside the guest as the supported coverage angle unless Product has validated a separate agentless integration.
DPX protects Ubuntu through two practical deployment models. For physical servers and many virtualized Ubuntu workloads, install the DPX Client on the Ubuntu system and register it with the DPX Master Server. This enables file-level backup, block-level backup where prerequisites are met, and bare metal recovery for supported configurations. For Ubuntu VMs running on VMware or Microsoft Hyper-V, DPX can also protect the VM through agentless hypervisor workflows.

DPX gives infrastructure teams several recovery paths for Ubuntu, from file restore to full-system recovery. The right method depends on whether the workload is physical, virtual, VMware-based, Hyper-V-based, or deployed on another platform where guest-level protection is the right fit.

Use these patterns to identify the right DPX architecture without overstating platform support.
Install the DPX Client on the Ubuntu server, register it with the DPX Master Server, and configure file-level or block-level backup based on the workload and storage layout.
Use DPX agentless VMware backup where VM-level protection is the goal. This reduces guest-agent management and supports VMware-based recovery workflows.
Use DPX agentless Hyper-V backup for supported Hyper-V environments, or deploy the DPX Client in the guest when block-level guest protection is required.
Use DPX Client protection inside the Ubuntu guest unless a separate DPX integration is validated for that platform. This is the safest positioning for platforms not listed in the DPX agentless compatibility data.
Use file-level backup for directories, user data, configuration files, and general Linux file protection. Add GuardMode where ransomware behavior monitoring is required.
Use DPX Client protection for Ubuntu systems hosting applications, middleware, or custom services. Coordinate application consistency through scripts, maintenance windows, or workload-specific procedures where required.
DPX supports targeted file recovery for Ubuntu workloads so teams can restore files and directories without rebuilding the entire server. This is the preferred recovery path for accidental deletion, configuration rollback, and operational recovery after a limited data issue.
For larger incidents, DPX supports block-level restore and bare metal recovery for supported Ubuntu configurations. This helps recover from server loss, storage failure, or ransomware events where rebuilding the system is faster and safer than manual repair.
Ubuntu backup is not only about restore points. Ransomware and destructive attacks can corrupt production data before a backup job runs. Catalogic GuardMode adds ransomware and anomaly detection designed for backup teams, monitoring filesystem behavior such as suspicious extensions, rapid renames, decoy file modification, high-entropy files, and abnormal long-running modification patterns. For backup storage, vStor adds immutability controls at the snapshot and volume levels. Together, DPX, vStor, and GuardMode create a practical recovery path for Ubuntu systems: detect suspicious activity, preserve clean recovery points, and restore only what is needed.
Review these implementation notes before designing Ubuntu protection policies. Exact deployment prerequisites should be confirmed in the DPX documentation and compatibility matrix.
| Area | Requirement or note |
|---|---|
| Architecture | x64 |
| Minimum memory | 2 GB minimum, 4 GB recommended for enterprise applications |
| Processor | 1 core minimum |
| Disk space | 4 GB minimum free space on the system drive for installation |
| Linux package requirement | libnss3 plug-in required |
| Instant Access mapping | iSCSI packages required |
| Network ports | DPX Client requires documented TCP and UDP ports to be allowed |
| Block Data Protection | DPX Client storage volume must be part of an LVM group |
| LVM free physical extents | Volume group requires at least 10 percent free physical extents |
| File-level backup | Supported with most OS-supported file systems |
| Extended filesystem attributes | Supported with EXT4, EXT3, EXT2, and XFS |
| XFS file-level caveat | For XFS partitions above 1 TB, use block-level backup |
| XFS block-level caveat | XFS BLI support requires V7.2 or later; 64-bit inodes are not supported |
| Agentless VM caveat | Avoid installing the DPX Client on VMs protected using DPX agentless VMware or Hyper-V backup |
This page provides solution guidance. The DPX documentation and compatibility matrix remain the source of truth for exact deployment prerequisites.
Related DPX product pages and platform guidance for teams validating Ubuntu backup, recovery, storage, ransomware detection, and adjacent Linux or hypervisor coverage.
Enterprise backup and recovery for supported physical, virtual, and application workloads.
Microsoft platform protection guidance, including Hyper-V environments.
Related Linux backup and recovery guidance for Red Hat Enterprise Linux.
Guidance for Proxmox environments where guest-level Ubuntu protection may be the right fit.
Catalogic DPX protects supported Ubuntu systems with file-level backup, block-level backup, bare metal recovery, centralized management, immutable backup storage, and ransomware detection. Validate your Ubuntu version and deployment model with Catalogic before rollout.
Request Demo