Red Hat OpenShift has become a default platform for enterprise cloud-native orchestration. With Red Hat OpenShift Virtualization, virtual machines run alongside containerized applications on the same KVM-based platform, which lets infrastructure teams consolidate VMware-era workloads onto the same control plane they use for cloud-native apps.
OpenShift provides day-1 and day-2 capabilities for the platform itself. It does not provide application-aware backup, cross-cluster mobility, or ransomware recovery for the workloads running on it. That is the gap CloudCasa fills.
Through its Software as a Service (SaaS) and Self-hosted model options versions, CloudCasa can provide flexibility for a user’s data protection requirements. It can run entirely inside the customer’s environment without any external dependencies. CloudCasa agents run on protected clusters and communicate only to a customer-owned CloudCasa server; the server stores its catalog in customer-owned MongoDB; and backup data lands in customer-owned S3-compatible, NFS, or SMB storage. This makes it the right fit for air-gapped, sovereign, or regulated environments where data residency and offline operation are non-negotiable.
Whether you’re simply protecting Red Hat OpenShift / Red Hat OpenShift Virtualization, looking to integrate disaster recovery capabilities into your data protection strategies, or simply looking for better governance and restore capabilities your cloud native infrastructure, CloudCasa can be a great platform for simplifying these day-2 operations.
This document describes a reference architecture for protecting Red Hat OpenShift and OpenShift Virtualization workloads with CloudCasa Self-Hosted, deployed on-premises only, with both a primary and a secondary on-premises site.