oVirt Biz Continuity Plan recovery Q/A
Hello all, I am looking into implemented a BCP plan with oVirt, which intends to recover VMs from a secondary SAN LUN (containing VM snapshots from a production oVirt cluster site which is considered to have crashed/burned) and presented to the recovery site oVirt cluster. Since the production cluster is expected to have crashed/burned unexpectedly, leaving the VMs snapshots on the recovery SAN LUN (which is at a different site) intact. However since there can be no Export Domain / Import Domain scenario, I need to know what exact steps I need to perform to re-incorporate/re-hydrate the VMs from the recovery LUN presented to the recover oVirt cluster / KVM hosts. I think that normally an Import Domain offers a "VM Import" tab/option, while regular or non-import Storage Domains don't have the "VM Import" option. I've been trying to track down what exactly is needed in the way of specific steps within the oVirt manager and KVM hosts, besides presenting the recovery SAN LUN to it. Many thanks.
Hi, On Thu, Dec 15, 2022 at 10:12 AM Peter B via Users <users@ovirt.org> wrote:
Hello all, I am looking into implemented a BCP plan with oVirt, which intends to recover VMs from a secondary SAN LUN (containing VM snapshots from a production oVirt cluster site which is considered to have crashed/burned) and presented to the recovery site oVirt cluster. Since the production cluster is expected to have crashed/burned unexpectedly, leaving the VMs snapshots on the recovery SAN LUN (which is at a different site) intact. However since there can be no Export Domain / Import Domain scenario, I need to know what exact steps I need to perform to re-incorporate/re-hydrate the VMs from the recovery LUN presented to the recover oVirt cluster / KVM hosts. I think that normally an Import Domain offers a "VM Import" tab/option, while regular or non-import Storage Domains don't have the "VM Import" option. I've been trying to track down what exactly is needed in the way of specific steps within the oVirt manager and KVM hosts, besides presenting the recovery SAN LUN to it.
Did you check oVirt Disaster Recovery? See also: https://www.ovirt.org/documentation/disaster_recovery_guide/ https://github.com/oVirt/ovirt-ansible-collection/tree/master/roles/disaster... Good luck and best regards, -- Didi
Hello Didi and all, Thank you for that documentation... I actually looked at something similar ( https://www.ovirt.org/develop/release-management/features/storage/importstor... ) before writing. Regarding the Section 3.1 "Disaster Recovery Guide -- Active-Passive" method... I need to understand what this means, "Storage domains that contain virtual machine disks and templates in the primary site must be replicated". What does the document mean by "replicated"? To use the document terminology, we have a Site A (SAN LUN A) and Site B (SAN LUN B) which is asynchronously (3 hour) replication of the VMs, and if Site A goes away, we can present LUN B to Site B oVirt cluster KVM host. After presentation, I assumed I would have to create a new Storage Domain and affix the LUN B to it. However the documentation says "site must be replicated", so what exactly does that mean, compared to what we are doing/thinking? Another thing I noticed in looking into this is an Imported Domain (from an Exp ort Domain) presents a "VM Import" TAB in the Storage Domain details, while a regular Storage Domain setup does not appear to offer that -- unless this is a conditional thing? (And of course when Site A goes down I cannot perform a detach of an exported storage domain.) If I create the Site B oVirt cluster new Storage Domain for the LUN B, will that present a "VM Import" function tab? (In order to grab the VM info from the LUN B and import it into the cluster.) I'm also looking to avoid needing to delve into the Ansible scripts, if the needed functionality for recovery can be done in oVirt/KVM. Many thanks again.
participants (3)
-
Peter B -
siebots＠protonmail.com
-
Yedidyah Bar David