Download as ODP, PPTX
Uploaded byMaor Lipchuk
Disaster Recovery in oVirt
The document discusses disaster recovery in oVirt, an open-source virtualization management platform developed by Red Hat. It outlines the importance of disaster recovery due to hardware failures, human errors, and the need for constant availability. The presentation also highlights new capabilities introduced in oVirt 3.5 and future plans for improved disaster recovery solutions.
More Related Content
![[RakutenTechConf2014] [D-4] The next step of LeoFS and Introducing NewDB Project](https://cdn.slidesharecdn.com/ss_thumbnails/d4rakutentech2014-leofs-newdb-141105023531-conversion-gate01-thumbnail.jpg?width=640&height=640&fit=bounds)
![[超强腿击术].马中碧](https://cdn.slidesharecdn.com/ss_thumbnails/random-170328144431-thumbnail.jpg?width=640&height=640&fit=bounds)
Disaster Recovery in oVirt
- 1. 1 Disaster Recovery InoVirt Maor Lipchuk March 2015 Senior Software Engineer @ RHEV Red Hat [email protected] Irc.oftc.net server on #ovirt channel
- 2. 2 oVirt in aNutshell ● Open Source project started by Red Hat ● Virtualization management platform ● Built on linux's virtualization you already know: ● kvm, qemu, libvirt ● Manages: Virtual Machines Storage Domains Virtualized networks
- 3. 3 oVirt in aNutshell
- 4. 4 oVirt in aNutshell File Storage Domains ● NFS ● Gluster ● POSIX-Compliant FS ● Local Block Storage Domains ● Fibre Channel ● iSCSI
- 5. 5 Nature always sideswith the hidden flaw Disaster Recovery - Murphy's Laws If there is a worse time for something to go wrong, If there is a worse time for something to go wrong, it will happen then. it will happen then. Smile... tomorrow will be worse. You never run out of things that can go wrong.If your advance is going well, you are walking into an ambush. If there is a possibility of several things going wrong, the one that will cause the most damage will be the one to go wrong
- 6. 6 Disaster Recovery Why dowe need Disaster Recovery? ● Machines and hardware fail ● Humans make mistakes ● Nature is unpredictable ● Customers want access 24/7/365
- 7.
- 8. 8 Disaster Recovery inoVirt ExportExport StorageStorage DomainDomain ● File Storage Domain ● Based on OVF ● Can be used to migrate entities between different setups or Data Centers ● Can be moved between setups ● Can be used to backup entities
- 9. 9 Problems using theExport Domain as a Backup
- 10. 10 Disaster Recovery inoVirt Problem #1 : Scalability Maintain a large amount of storage
- 11. 11 Disaster Recovery inoVirt Problem #2: Copying data takes too long
- 12. 12 Disaster Recovery inoVirt Problem #3: Single point of failure
- 13.
- 14. 14 New capabilities inoVirt 3.5 Metadata OVF_STORE disk Disks
- 15. 15 New capabilities inoVirt 3.5 Import Data Storage Domain
- 16. 16 Disaster Recovery Today yetanother beautiful disaster...
- 17. 17 Disaster Recovery Today Importa Storage Domain after a disaster
- 18. 18 Disaster Recovery Today Attachand activate the Storage Domain on the target Data Center
- 19. 19 Disaster Recovery Today Pickthe entities you want to register from the newly attached Storage Domain
- 20. 20 Disaster Recovery Today Choosea Cluster and Quota for each entity
- 21.
- 22.
- 23. 23 Comparison of DRSolutions
- 24. 24 Now VS TheFuture
- 25. 25 Future Plans ● CloneVMs and Templates from a Storage Domain ● Convert an Export Domain to a Data Domain ● Your contributions are welcome: http://www.ovirt.org/Community
- 26. 26 ● Wiki links www.ovirt.org/Features/ImportStorageDomain ●YouTube videos https://www.youtube.com/watch?v=DLcxDB0MY38 - Detach and attach Storage Domain with entities https://www.youtube.com/watch?v=YbU-DIwN-Wc - Import file Storage Domain https://www.youtube.com/watch?v=T03ai6FrMI4 - Recovery of local Data Center
- 27.
- 28.
Editor's Notes
- #2 Good afternoon, welcome to the oVirt session on Disaster Recovery my name is Maor Lipchuk, I work as a senior software engineer in RedHat, and I currently work on the oVirt project. I want to talk to you about disaster recovery and the new feature introduced in oVirt 3.5 called “Import Storage domain”. I will first say a few words about oVirt, how Disaster Recovery was used before version 3.5 and how it is used today in oVirt 3.5
- #3 ok, How many of you went to the oVirt virtualization lecture oVirt is an open source virtualization managemennt platform, it means it allows the administrator to do anything that is related to virtualization management and manage his virtual environment. It is based on a leading technology like qemu to provide a fullstack for virtualization management. and intends to be an open source alternative to manage virtualization.
- #4 I won't go into specific detail on every element in the architecture which presented here. But in general oVirt consists of a centralized management engine which provides a graphical interface where an administrator can view, provision and manage one resources Hosts which are using the Kernel-based Virtual Machine (KVM). Agents and tools running on hosts including VDSM, QEMU, and libvirt. These tools provide local management for virtual machines, networks and storage. Storage domains to hold virtual resources like virtual machines, templates, ISOs. A database to track the state of and changes to the environment.
- #5 So, today oVirt supports different types of Storage Domains. I would like to go through them very quickly just to give a glance of what oVirt supports today... So, first there is the Network File System which is the NFS There is also the local Storage Domain. Ovirt also supports both block Storage domains, which are the iSCSI Storage domain and the Fibre Channel Storage Domain. Ovirt also supports the Gluster Storage Domain and also any other posix Compliant File System Those are all the Data Storage Domains supported today by oVirt and can be used for adding disks, move disks to and from them, help with the VM hibernate process, and many other scenrios.
- #7 4 reasons why do we need Disaster Recovery Machines & Hardware Fail - while it can be expensive for your company to eliminate any single point of failure in your IT infrastructure, it is really the only way you can be sure that a hardware failure will not interrupt your service and cause the minimal way of data loss Humans Make mistakes - let’s admit it, we are not perfect Customers want access 24/7/365 Nature is unpredictable
- #9 Ok, so as we discussed in one of the previous slides, one of the Storage Domain which oVirt supports is the Export Storage Domain. That type of Storage Domain was used commonly for this specific scenarios that involved migration of Vms and Templats from One Data Center to another. Just a reminder, from the past slide, The export Storage domain acts as a container for Vms and Templates... it can be used for backup purposes, migration between different Data Centers or migrating between different Setups. What are the problems?
- #11 Scalability – peta byte, support a whole Data Center
- #12 Every I\O operation is very expensive
- #15 What was introduced in oVirt 3.5 After going through the different types of Storage Domains, I would like to get a bit “under the hood” of a Storage domain, and describe what does it contains under it... For each Data Storage Domain we have the Meta Data... the meta data is a file, containing all of the meta data relates to the Storage domain, such as name, type., description and so on.... Other trivial contents contained in the Storage Domain are, of course, the disks... The disks are hosted in the Storage Domain, containing also, a meta data, additionally to the data it self which might also contain snapshots, if they got any. One of those disks, is the OVF_STORE disk. The OVF_STORE disk is a special disk introduced lately in oVirt 3.5, this disk is created automatically by the engine, and its main purpose is to contain all of the Vms and the Templates configurations, which have disks on the Storage Domain, in this disk. All of this configuration data, preserved in a XML standard called Open Virtualization Format, or simply OVF. The OVF is a xml representation of the VM or the Template configuration, it is mainly describes all the VM data, such as name, description, number of disks, snapshots and more. Before oVirt 3.5 all of the VM and template OVF files were preserved directly in the Storage Domain at a special path. Now, with this disk introduced in oVirt 3.5 we are able to support Disaster Recovery scenarios and with them the Import Storage Domains feature