The Kubernetes Disaster Recovery Platform
Portworx Platform Services
Cloud Native storage optimized for containers. Operate at scale. Rule-based automation & flexible thin-provisioning allocation. Any cloud & on any storage.Learn More
Protect mission critical data with self-service backup. Container & application aware. Backup & migrate data anywhere, between clusters, clouds & regions.Learn More
Simplify and automate the deployment of Mongo, Elastic, Kafka, Postgres, Kafka and Cassandra. Empower developers with self-service Day 1 & Day 2 data ops.Learn More
Integrated with GitOps and CI/CD pipelines. Manage storage services with a single-pane interface to provide development teams with self-service capabilities.Learn More
Telemessage Customer Story
With Portworx and HashiCorp we’ve gained the encryption and security, along with the cloud native storage performance and availability, we need with zero downtime and virtually no disruption to our team.
Yossi Shteingart Operations Manager, TeleMessage
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.
Contact us to learn more.