Menu

Part 5: Enterprise Backup & Disaster Recovery with OADP & NooBaa
πŸ“°

Part 5: Enterprise Backup & Disaster Recovery with OADP & NooBaa

DEV Community: kubernetesΒ·Muhammad AdelΒ·7 days ago
#LJmX06ll
#devtokubernetes#devto#dev#openshift#namespace
Reading 0:00
15s threshold

Backing up stateless microservices in Kubernetes is relatively straightforward: export your GitOps manifests, and redeploy.

Virtual Machines, however, are massive stateful engines.

If you take a naive snapshot of a running virtual machine while an active database is processing write transactions in RAM, your restored VM will likely boot into a corrupted filesystem, broken journal logs, or lost transactions (the dreaded "Crash-Consistent" state).

To achieve true enterprise-grade Application Consistency , we must coordinate three distinct layers:

The guest operating system's internal filesystem memory buffers.

The hypervisor virtualization engine (KubeVirt).

The underlying storage array CSI snapshot controller.

In this fifth part of our series, we construct an end-to-end Enterprise Disaster Recovery strategy using OADP (OpenShift API for Data Protection / Velero) and local NooBaa (S3 Object Storage) .

πŸ—οΈ Architecture: The Application-Consistent Backup Workflow

The coordinated backup flow operates in…

Continue reading β€” create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.