Enabling metro business continuity and regional disaster recovery for critical workloads with Red Hat OpenShift Virtualization

As organizations look at Red Hat OpenShift to modernize their IT infrastructure, a key consideration is that the necessary high availability (HA) and disaster recovery (DR) infrastructure services are available for critical workloads. Is it possible to failover virtual machine (VM) workloads from Berlin to Dublin in regional DR? Can you migrate workloads between New York and New Jersey clusters without interruption? Can I get DR and business continuity (BC) similar to what I have in my existing hypervisor implementation after migrating to Red Hat OpenShift Container Platform? In a traditional hypervisor implementation, the latter metro DR is often referred to as a "metro storage cluster implementation" and is intended to provide maximum availability and uptime by clustering physical datacenters within metrotropolitan distances with active-active storage. In this session, we'll cover: - How to architect OpenShift Virtualization for metro-level availability for VM workloads, similar to traditional hypervisor implementations. We will share examples using Hitachi Global Active Device (GAD) implementing stretched persistent volumes to provide active-active HA for Red Hat OpenShift stretched clusters. - How to architect your OpenShift Virtualization solution to meet and operationalize DR requirements. We will share examples using GitOps and Red Hat Advanced Cluster Management for Kubernetes (RHACM) with Hitachi’s Universal Replicator for scalable, asynchronous DR across regions. - How to migrate VMs from my existing vendor to Red Hat OpenShift efficiently and reenable that similar level of business continuity.