Dell PowerStore customers are running more of their production estate on Red Hat® OpenShift®, increasingly alongside virtual machines migrated onto Red Hat OpenShift Virtualization. Many have already put a backup tool in place. Far fewer have solved disaster recovery: a way to fail these environments over to a second site in minutes, not hours.
THE RESULT
Customers keep their data on PowerStore, protect the Kubernetes applications that depend on it, and achieve recovery objectives measured in minutes – without moving persistent data through a third-party data plane or having to add a new storage replication layer.
CloudCasa DR for Dell PowerStore supports Red Hat OpenShift and Red Hat OpenShift Virtualization, for both containerized applications and Kubernetes-native virtual machines. Everyday Red Hat OpenShift backup and restore to Dell storage, including Data Domain, ECS, and PowerScale, runs from the same CloudCasa console that manages DR. CloudCasa uses the PowerStore CSI driver (csi-powerstore) for volume provisioning, and the PowerStore REST API to orchestrate DR failover and failback directly. It does not depend on CSM functionality for DR failover or failback. Today’s integration covers block-based (SCSI) persistent volumes on PowerStore; file-based (NFS/SMB) volume DR is on the CloudCasa roadmap.
| CloudCasa | Typical alternatives | |
|---|---|---|
| Storage-integrated DR | ✓ Array-integrated DR that orchestrates PowerStore’s native replication, shipping today for Dell PowerStore. | ✗ Storage replication alone recovers the volumes, but the Kubernetes side still has to be rebuilt by hand. Software-defined storage overlays add DR, but also add complexity and overhead. |
| Delivery model | ✓ SaaS control plane plus self-hosted option; per-worker-node licensing. | ✗ Typically available in only one delivery model – SaaS-only or self-hosted-only – requiring a change in tooling if deployment needs change. |
| Hybrid Architecture | ✓ Multi-tenant, multi-cluster design that manages protection across on-prem, cloud, and edge environments from a single control plane – with a small footprint and ready for MSP delivery. | ✗ Frequently single-tenant or single-cluster, requiring a separate deployment or control plane per environment – a limited fit for edge or MSP delivery. |
| Scope | ✓ Backup, restore, migration, DR, and in-cluster VM protection in one platform. | ✗ Typically covers only backup or only DR, with replication-based DR sold as a separate product or tied to a specific storage layer. |