Portworx & Red Hat Hands-on Labs Register Now

Highly Resilient, Enterprise-Grade Disaster Recovery

Disasters can take many forms—hardware failures, natural disasters, data breaches—but it’s important to be prepared so your applications don’t suffer extended downtime. Portworx business continuity and disaster recovery (BCDR) provides flexible DR support, ensuring availability, resilience and reliability for container applications.

  • Always-on availability through best-in-class BCDR
  • No data loss with zero RPO synchronous disaster recovery and limited data loss with asynchronous disaster recovery
  • Fast failovers to quickly bring operations back in case of a disaster

 

Using Portworx, Enterprises Can:

Minimize downtime and recover quickly

Manage disaster recovery for minimal downtime with automated DR processes from a single, simple platform

Maintain compliance for any application tier

Meet all your recovery SLAs with up to zero RPO for mission-critical applications

Recover your workloads anywhere

Recover your applications no matter where they’re located—on-prem, public cloud or hybrid-multi cloud environments

Portworx Disaster Recovery

Synchronous Disaster Recovery

Mission-critical applications cannot risk data loss or extended downtime. These applications are the heart of your organization, so they need to be protected with synchronous disaster recovery.

For clusters located within the same metro region, Portworx business continuity and disaster recovery provides zero RPO (Recovery Point Objective) synchronous disaster recovery, meaning any changes made to the production cluster are automatically replicated to the DR cluster. Zero RPO ensures that in the event of a disaster, these applications suffer no data loss.

Synchronous

Asynchronous Disaster Recovery

Using synchronous disaster recovery for all your applications can be cost-prohibitive. Portworx allows you to protect your Tier-2 or Tier-3 applications using asynchronous disaster recovery. These applications have a higher RPO, but can still be recovered quickly in case of a disaster.

Portworx BCDR provides asynchronous DR for clusters located around the globe that have an RPO of 15 minutes or more. Asynchronous replication happens between two clusters as defined by scheduled policies. When disaster strikes, these applications only lose the data within your RPO tolerance.

Asynchronous Disaster Recovery

More from the Portworx Platform

Kubernetes Storage

Cloud-native storage optimized for Kubernetes, with elastic scalability and industry-leading availability.

Learn more
Backup

Protect mission critical data with self-service backup that is container-granular and application-aware. Backup and migrate data anywhere.

Learn more
Database Platform-as-a-Service

Automate and accelerate Day 0 and Day 2 database operations, and empower developers with self-service to databases in minutes.

Learn more
report thumbnail IDC report
Whitepaper
Get the Essential Capabilities of Disaster Recovery for Kubernetes

DXC Customer Story

customer story
After evaluating how it could meet stringent recovery time SLAs, we selected Portworx Enterprise and Portworx Disaster Recovery to power disaster recovery for our Managed Container Services customers.

Jelle Wolthuizen, Product Manager, Managed Container Services, DXC Technology

Frequently Asked Questions

I already have a Kubernetes data protection solution. Do I need one for disaster recovery?

Many Kubernetes data protection solutions claim they offer disaster recovery via backup and restore. Although backup and restore is an important component of any disaster recovery plan, it should not be confused with disaster recovery.

Backup and restore might be an appropriate option for lower tier applications where some amount of data loss is acceptable. The RPO for these applications would be the cadence of backup schedules—whether that’s once a day, once an hour, or every 15 minutes.

However, most Kubernetes data protection solutions are not able to offer replication at the storage level, which means any mission-critical applications only protected by backups are at risk for data loss and downtime. Mission-critical applications require a zero-RPO, synchronous disaster recovery solution, so your organization isn’t risking the disastrous impact of lost data or extended downtime.

What Portworx services do I need for my disaster recovery needs?

Portworx disaster recovery services require your organization to also use Portworx storage services. This is because disaster recovery requires replication at the storage level.

Our infrastructure is complex—it’s multi-region, multi- and hybrid cloud, and uses multiple Kubernetes distributions. Can Portworx handle it?

Long story short, yes. Portworx is completely infrastructure agnostic, so it can support disaster recovery for clusters in any environment—public cloud, private cloud, or on-prem—as well as any application, database, or Kubernetes distribution.

Although synchronous disaster recovery will require clusters to be within the same metro region with a latency of < 10ms, asynchronous disaster recovery supports replication for clusters in any region.

Origami Background image