Security | Threat Detection | Cyberattacks | DevSecOps | Compliance

CloudCasa DR for HPE Alletra with Red Hat OpenShift - PART 2: Failback

CloudCasa completes the disaster recovery cycle by failing a file server application back from Site B (HPE Alletra MP B10000) to its original primary on Site A (HPE Alletra 9060), both running Red Hat OpenShift. In this demo, we create a reverse DR plan, scale down the workload for a clean shutdown, and let CloudCasa orchestrate the two-phase failback: an HPE recover/restore operation that reverses replication at the storage layer, followed by progressive Kubernetes resource restoration, before the file server comes back online on Site A with its data intact.

CloudCasa DR for HPE Alletra with Red Hat OpenShift - PART 1: Failover

CloudCasa orchestrates disaster recovery failover for stateful workloads across two HPE Alletra arrays running Red Hat OpenShift. In this demo, we fail over a file server application from Site A (HPE Alletra 9060) to Site B (HPE Alletra MP B10000), with CloudCasa installing its agent via a single kubectl apply, discovering both clusters and storage systems, mapping the pre-configured HPE replication relationship, and triggering consistency group failover so the workload comes back up on Site B with all data intact.

Enabling Mirantis Self-Service Virtualization with CloudCasa

As enterprises modernize infrastructure, the shift toward self-service virtualization on Kubernetes is accelerating. Platforms such as Mirantis k0rdent AI and k0rdent Enterprise feature KubeVirt-based virtualization, enabling organizations to deliver on-demand infrastructure while maintaining governance controls.

OpenShift Virtualization Backup: How to Protect VMs After Migrating from vSphere

Most OpenShift Virtualization projects start with a simple goal: move virtual machines off a traditional hypervisor and onto a Kubernetes-based platform without forcing every workload to be rewritten. That is a practical goal. Many organizations have VM estates that will not become containers any time soon, and OpenShift Virtualization gives infrastructure teams a way to run those VMs next to containerized applications on the same operational platform.

Longhorn on Production Clusters: Storage Configuration, Tuning, and Gotchas

Longhorn is a lightweight, distributed block storage system built specifically for Kubernetes. It runs entirely inside your cluster, turning local disks on worker nodes into replicated persistent volumes with no external storage array required. That simplicity is what makes it appealing, especially in the Rancher and SUSE ecosystem where it ships as the default storage option. You get persistent storage that is easy to install, easy to understand, and tightly integrated with the Kubernetes lifecycle.

CloudCasa Launches in the NKP Partner Catalog, Expanding Data Protection and Mobility for NKP Users

At Nutanix.NEXT, we’re excited to announce that CloudCasa is launching in the NKP Partner Catalog, giving Nutanix Kubernetes Platform (NKP) solution users an easier way to add Kubernetes-native backup, recovery, disaster recovery, and migration to their environments. This launch builds on CloudCasa’s existing Nutanix Ready foundation and extends that value even further by making CloudCasa available through the NKP Partner Catalog.

Kubernetes Backup: How It Works, What to Protect, and How to Choose a Solution in 2026

Kubernetes backup sounds straightforward until you look closely at what a real application includes. A production workload usually spans Kubernetes resources, cluster configuration, persistent volumes, secrets, service accounts, network policies, and external dependencies such as cloud databases or object storage. Protecting one of those layers helps. Protecting all of them in a coordinated way is what makes recovery practical.

Protecting OpenShift Workloads Without the Complexity: A Conversation Worth Having

DevOps engineers running OpenShift know the platform well. They know how to build on it, scale on it, and operate it under pressure. What they often hit unexpectedly is the question of backup and recovery, especially once OpenShift Virtualization enters the picture. Most of the tooling that exists today wasn’t built with Kubernetes in mind. It was built for something else and extended toward it.

Protect OpenShift Virtualization Before Your MTV Migration Wave Hits

A practical guide to VM-aware data protection for VMware-to-OpenShift migrations VMware exits rarely fail because engineers cannot move bits. They fail because the organization discovers, mid-flight, that it cannot reliably recover those bits once they land somewhere new.