Freedom251 › Cloud Disaster Recovery Software
Portworx PX-DR
What Portworx PX-DR is
Portworx PX-DR is a paid disaster-recovery add-on for Kubernetes applications, OpenShift applications, and KubeVirt virtual machines. It supports recovery in on-premises, public-cloud, hybrid, and multicloud environments, with failover orchestration to move workloads to another cluster and failback after the source returns. Synchronous replication is designed for clusters in the same metro area, automatically copying production changes for zero RPO and an RTO under 60 seconds; node-to-node latency must be below 10 ms. Asynchronous replication uses scheduled policies for different regions or data centers, with a stated 15-minute RPO and RTO under 60 seconds. ACM-based DR integrates with Red Hat Advanced Cluster Management for managed OpenShift clusters and supports GitOps workflows. PX-DR requires Portworx storage services because replication occurs at the storage layer. Portworx lists a fully functional trial for up to 30 days, while pricing is available on request.
Who it suits
PX-DR suits organizations running container workloads that need cluster failover across metro, regional, cloud, or hybrid environments. It requires Portworx storage services and is relevant to Kubernetes, OpenShift, and KubeVirt users.
What it does well
- Synchronous zero-RPO replication
- Asynchronous regional recovery
- Failover and failback orchestration
- Supports hybrid and multicloud recovery
- 30-day functional trial
What to know first
- Requires Portworx storage services
- Pricing available on request
- Synchronous mode needs under 10 ms latency
- Paid add-on with no free plan
Plans
| Plan | Billed and limits | Price |
|---|---|---|
| Portworx Disaster Recovery (PX-DR) add-on | Requires Portworx storage services · Disaster Recovery is listed as an add-on | On request |
As portworx.com lists them, read 9 Oct 2026. The maker's own page has the final word.
Verdict
PX-DR provides distinct synchronous and asynchronous recovery models with stated recovery objectives under 60 seconds. Portworx storage dependency and request-based pricing should be assessed before deployment.
Facts from Portworx PX-DR's own pages
- Asynchronous replication
- Asynchronous DR uses scheduled policies between clusters and supports an RPO of 15 minutes or more. · portworx.com, 9 Oct 2026
- Asynchronous use case
- Asynchronous DR is suitable for clusters in different regions or data centers, including when node-to-node latency exceeds 10 ms. · docs.portworx.com, 9 Oct 2026
- Failover and failback
- Portworx DR supports moving applications or workloads to a destination cluster after a disruption and moving them back after the source cluster is restored. · docs.portworx.com, 9 Oct 2026
- GitOps
- ACM-based DR workflows can be managed through GitOps. · docs.portworx.com, 9 Oct 2026
- Headquarters
- Santa Clara, California, United States · portworx.com, 28 Sept 2026
- OpenShift integration
- ACM-based DR integrates with Red Hat Advanced Cluster Management to configure DR for managed OpenShift clusters from the OpenShift console. · docs.portworx.com, 9 Oct 2026
- Purpose
- Portworx Disaster Recovery provides disaster recovery support for container applications, including availability, resilience, and reliability. · portworx.com, 9 Oct 2026
- Recovery objectives
- The documentation states synchronous DR has zero RPO and RTO under 60 seconds; asynchronous DR has a 15-minute RPO and RTO under 60 seconds. · docs.portworx.com, 9 Oct 2026
- Security
- Portworx says it uses threat modeling, vulnerability scanning, periodic penetration testing, and threat monitoring, and has achieved ISO 27001 certification. · portworx.com, 9 Oct 2026
- Storage dependency
- Portworx DR services require Portworx storage services because DR requires storage-level replication. · portworx.com, 9 Oct 2026
- Support
- The Portworx pricing page lists enterprise support as 24 x 7 x 356. · portworx.com, 9 Oct 2026
- Supported environments
- The product page says DR can recover applications on-premises, in public cloud, or in hybrid and multicloud environments. · portworx.com, 9 Oct 2026
- Synchronous replication
- For clusters in the same metro region, synchronous replication automatically copies production-cluster changes to the DR cluster for zero RPO. · portworx.com, 9 Oct 2026
- Synchronous requirements
- Synchronous DR is intended for clusters in the same metro area and requires node-to-node network latency under 10 ms. · docs.portworx.com, 9 Oct 2026
- Trial
- Portworx offers a fully functional trial license for up to 30 days. · portworx.com, 9 Oct 2026
Where Portworx PX-DR stands on Freedom251
- Cloud Disaster Recovery Software#16 of 27