KubeVirt workloads
Assess VM disks and supported metadata together.
RED HAT OPENSHIFT
Bring platform-specific recovery scenarios together for KubeVirt virtual machines, persistent data and database workloads.
STEP-BY-STEP GUIDES
Plan OpenShift Virtualization/KubeVirt VM backups with namespace, CSI, RBAC and repository prerequisites; assess database profiles separately.
Open guidePlan the OpenShift recovery point, target namespace, new VM name and StorageClass; distinguish VM/PVC recovery from database restore.
Open guideUSE CASES
Assess VM disks and supported metadata together.
Select PostgreSQL / MySQL streaming scenarios.
Test cluster, CSI and target namespace prerequisites.
DEFINE YOUR SCENARIO
Full backup, changed-block transfer and repository restore scenarios cover KubeVirt VM data and supported metadata. Atomic multi-disk recovery requires additional validation against controller and CSI versions.
Explore PostgreSQL and MySQL logical streaming backup and restore. PostgreSQL point-in-time recovery additionally requires WAL chain integration and target environment validation.
Restoring application PVCs and manifests is a different operation from recovering the entire cluster control plane. etcd, encrypted Secrets and cluster disaster recovery require a separate, version-matched recovery plan.
COMMON QUESTIONS
Not automatically. Each distribution has its own versions, APIs, storage and permissions model to validate. Dedicated assessment pages cover Kubernetes and Rancher environments.
Application and VM restore differ from control plane disaster recovery. We define protected resources and the recovery target together before the demo.
START WITH YOUR INFRASTRUCTURE
Share your workloads and recovery objectives. Let’s define the technical scope together.
MEET ERABACKUP
Share your workloads to start a demo and technical scope discussion.
Your requirements have been recorded for technical assessment.