OpenShift 4.11 introduces Kubernetes Native Disaster Recovery
Similar conventional knowledge applies to operating a software cloud and operating a motorcycle: it’s not about preventing accidents, it’s about preparing for them and lessening their effects. Because a motorbike is so small in comparison to other vehicles on the road, it makes sense to wear a helmet, pads, and gloves. This is because you can never completely prevent crashes, but you can be ready for the few you are likely to experience during your time riding the bike in Kubernetes Native
Any computing project will eventually encounter a failure that will cause a server, container, or node to crash. In the greatest systems, this might only occur once a year for a brief period of time. In the worst situation, it might lead to a company’s bankruptcy or the demise of a corporation.
For computing, however, there are helmets and body protection. The armor that knights and samurai wore into battle more than ten years ago, however, was analogous to what OpenShift users were wearing up to this point: strong, possibly even overengineered for the work of riding around the city and highway. Today, we introduce OpenShift Disaster Recovery capabilities, our slick, color-coordinated motorcycling gear.
Disaster Recovery for OpenShift workloads
Killing and replacing nodes is a fundamental aspect of daily operations for cloud-enabled apps, therefore disaster recovery in Kubernetes requires more than just replacing dead nodes. Instead, the focus should be on quickly and at scale getting systems back online. Disaster Recovery for OpenShift workloads comes with all the tools and integrations required to recover from the majority of common outage scenarios, but it’s the container-focused capabilities that really tackle the new challenges.
Red Hat OpenShift Advanced Cluster Management, Red Hat OpenShift Data Foundation, and Red Hat Ceph Storage are just a few of the features that are integrated into Disaster Recovery for OpenShift workloads. Disaster Recovery for OpenShift workloads can handle the nodes, cluster, object stores, and intervening cluster connection bits that support workloads because these are included in OpenShift Platform plus.
This means that OpenShift is now ready to assist you in resolving outages ranging from regional to local. Additionally, OpenShift Disaster Recovery additionally maintains data about all the services and Kubernetes APIs that were operational before the outage, as opposed to reprovisioning each node from a conventional recovery cluster. That entails preserving all pertinent and necessary data, including namespace-specific information, on either the original cluster (in-place restoration) or on a replacement cluster, in order to be able to reproduce workloads (out-of-place restore)
Safety in Numbers
3 techniques that assist disaster recovery and business continuity
OpenShift Data Protection API. In order to have a complete workload backup that can be effectively restored into the same- or into another cluster, an API that enables customers to enable current backup- and data recovery apps to interface with OpenShift workloads is available.
Area-wide DR (TP):
Asynchronous replication and automated block volume protection are handled by RHACM. protection of business operations when a disaster occurs in a specific area.
Regional DR (TP):
RHACM-controlled synchronous replication with multiple clusters provides security against data loss. This offers immediate business functionality protection with a goal of almost zero recovery points (RPO).