Back Up and Recover Virtual Machines in OpenShift Virtualization

OpenShift Virtualization lets organizations run traditional virtual machines alongside container workloads inside a Kubernetes platform, so enterprises can modernize infrastructure and keep operating their existing VM-based applications.

The technology is built on KubeVirt, an open source project that runs virtual machines inside Kubernetes containers using Kernel-based Virtual Machine (KVM) virtualization. The architecture combines traditional virtualization with container orchestration, which is why protecting VMs in OpenShift differs from hypervisor-based backup.

An OpenShift VM environment typically includes:

Virtual machine definitions stored as Kubernetes resources

Persistent volumes containing VM disks

Networking configurations and policies

Namespace-level access controls

Application and orchestration metadata

A backup system has to capture all of these components to restore a VM successfully. The disk image alone lacks the operational context the VM needs to run within the cluster.

Backup platforms built for Kubernetes therefore use application-aware VM protection. They protect VM storage and Kubernetes metadata together, so administrators can restore workloads quickly.

These platforms also commonly support incremental backups, which store only the changes between backup cycles. That lowers storage consumption and network usage during ongoing protection.

The list below compares Traditional Hypervisor Backup and OpenShift Virtualization Backup point by point:

VM Disk Backup: Traditional Hypervisor Backup = Yes; OpenShift Virtualization Backup = Yes

Kubernetes Resource Capture: Traditional Hypervisor Backup = No; OpenShift Virtualization Backup = Yes

Namespace-Level Protection: Traditional Hypervisor Backup = No; OpenShift Virtualization Backup = Supported

Incremental Backup: Traditional Hypervisor Backup = Optional; OpenShift Virtualization Backup = Built-in

Cross-Cluster Recovery: Traditional Hypervisor Backup = Limited; OpenShift Virtualization Backup = Supported

VM and Container Protection: Traditional Hypervisor Backup = Separate tools; OpenShift Virtualization Backup = Unified protection

Step 1: Identify VM workloads

Map the virtual machines running within OpenShift namespaces and identify their persistent volumes.

Step 2: Capture Kubernetes metadata

Make sure backup workflows include VM definitions, networking policies and namespace configuration.

Step 3: Protect persistent storage

Back up the persistent volumes that contain the VM disk images.

Step 4: Enable incremental backup policies

Use incremental backups to reduce storage consumption and improve performance.

Step 5: Test VM recovery

Check that individual VMs can be restored successfully within the cluster.

Step 6: Automate backup operations

Set up automated protection policies that match your recovery objectives.

Capture VM disk data and Kubernetes metadata together.

Store backup repositories outside the production cluster.

Use incremental backup strategies.

Protect workloads at namespace or label level.

Test VM recovery and disaster recovery procedures regularly.

Following these practices protects both the virtual machines and the container workloads running in OpenShift.

What is OpenShift Virtualization?

It is a feature of Red Hat OpenShift that lets organizations run virtual machines alongside containers within a Kubernetes platform.

What technology powers OpenShift Virtualization?

It is built on KubeVirt, which lets VM workloads run within Kubernetes clusters.

Why must Kubernetes metadata be included in VM backups?

VM configuration, networking policies and scheduling rules are all defined as Kubernetes resources.

Can VMs be backed up at namespace or label level?

Yes. Kubernetes-native backup platforms allow protection policies based on namespaces, labels or individual workloads.

Why are incremental backups important for VM protection?

They capture only changed data blocks, which reduces storage consumption and makes backups more efficient.