Disaster Recovery in oVirt
summary
oVirt 3.5 replaces slow, single-point-of-failure export backups by adding an ovf store disk that packages VM OVF files on the storage domain and an import data storage domain path that registers VMs into a new engine without copying terabytes of disks. the demo shows importing an NFS domain, choosing clusters and quotas, and registering running VM configurations in minutes instead of days; planned features include cloning templates across domains and converting export domains to data domains.
AI-written summary · about
chapters (13)
- 0:00Disaster recovery in oVirt
- 1:30Storage domains in oVirt
- 2:56Disaster recovery importance
- 4:23Export storage domain limits
- 8:35oVirt 3.5 DR improvements
- 10:42Import storage domains for recovery
- 12:52Import vs export storage domains
- 14:17Future DR plans in oVirt
- 15:20Recovery resources and support
- 16:06Q&A on storage domains
- 17:30Local storage domain transfer
- 19:23Export vs import storage domains
- 21:12Conclusion
related talks
18mAgility Unleashed: Migrating VMs to next generation open source platforms
01h 01mProtect and migrate your compute instances with Zerto
06mVM: When Compute Moves but Data Stays
38mMigrating workloads from VMware to OpenStack
20mFaster Backups, Less Storage: Unlocking Incremental Backups in KubeVirt
15mEscape Hyper‑V: The New Agentless Path to OpenShift Virtualization
23mLive migration from VMware to OpenStack
23mImporting KVM instances from external KVM hosts or QCOW2