<div dir="ltr">Hi Luca,<div><br></div><div>Thank you for your interst in the Disaster Recovery ansible solution, it is great to see users get familiar with it.</div><div>Please see my comments inline</div><div><br></div><div>Regards,</div><div>Maor</div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Feb 5, 2018 at 7:54 PM, Yaniv Kaul <span dir="ltr"><<a href="mailto:ykaul@redhat.com" target="_blank">ykaul@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="auto"><div><div class="gmail-h5"><div><br><div class="gmail_extra"><br><div class="gmail_quote">On Feb 5, 2018 5:00 PM, "Luca 'remix_tj' Lorenzetto" <<a href="mailto:lorenzetto.luca@gmail.com" target="_blank">lorenzetto.luca@gmail.com</a>> wrote:<br type="attribution"><blockquote class="gmail-m_-2209079700082506263quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div class="gmail-m_-2209079700082506263elided-text">Hello,<br>
<br>
i'm starting the implementation of our disaster recovery site with RHV<br>
4.1.latest for our production environment.<br>
<br>
Our production setup is very easy, with self hosted engine on dc<br>
KVMPDCA, and virtual machines both in KVMPDCA and KVMPD dcs. All our<br>
setup has an FC storage backend, which is EMC VPLEX/VMAX in KVMPDCA<br>
and EMC VNX8000. Both storage arrays supports replication via their<br>
own replication protocols (SRDF, MirrorView), so we'd like to delegate<br>
to them the replication of data to the remote site, which is located<br>
on another remote datacenter.<br>
<br>
In KVMPD DC we have some storage domains that contains non critical<br>
VMs, which we don't want to replicate to remote site (in case of<br>
failure they have a low priority and will be restored from a backup).<br>
In our setup we won't replicate them, so will be not available for<br>
attachment on remote site. Can be this be an issue? Do we require to<br>
replicate everything?<br></div></blockquote></div></div></div></div></div></div></blockquote><div><br></div><div>No, it is not required to replicate everything.</div><div>If there are no disks on those storage domains that attached to your critical VMs/Templates you don't have to use them as part of yout mapping var file</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="auto"><div><div class="gmail-h5"><div><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail-m_-2209079700082506263quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div class="gmail-m_-2209079700082506263elided-text">
What about master domain? Do i require that the master storage domain<br>
stays on a replicated volume or can be any of the available ones?<br></div></blockquote></div></div></div></div></div></div></blockquote><div><br></div><div><br></div><div>You can choose which storage domains you want to recover.</div><div>Basically, if a storage domain is indicated as "master" in the mapping var file then it should be attached first to the Data Center.</div><div>If your secondary setup already contains a master storage domain which you dont care to replicate and recover, then you can configure your mapping var file to only attach regular storage domains, simply indicate "dr_master_domain: False" in the dr_import_storages for all the storage domains. (You can contact me on IRC if you need some guidance with it)</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="auto"><div><div class="gmail-h5"><div><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail-m_-2209079700082506263quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div class="gmail-m_-2209079700082506263elided-text">
<br>
I've seen that since 4.1 there's an API for updating OVF_STORE disks.<br>
Do we require to invoke it with a frequency that is the compatible<br>
with the replication frequency on storage side.</div></blockquote></div></div></div></div></div></div></blockquote><div><br></div><div><br></div><div>No, you don't have to use the update OVF_STORE disk for replication.</div><div>The OVF_STORE disk is being updated every 60 minutes (The default configuration value), </div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="auto"><div><div class="gmail-h5"><div><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail-m_-2209079700082506263quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div class="gmail-m_-2209079700082506263elided-text"> We set at the moment<br>
RPO to 1hr (even if planned RPO requires 2hrs). Does OVF_STORE gets<br>
updated with the required frequency?<br></div></blockquote></div></div></div></div></div></div></blockquote><div><br></div><div><br></div><div>OVF_STORE disk is being updated every 60 minutes but keep in mind that the OVF_STORE is being updated internally in the engine so it might not be synced with the RPO which you configured.</div><div>If I understood correctly, then you are right by indicating that the data of the storage domain will be synced at approximatly 2 hours = RPO of 1hr + OVF_STORE update of 1hr</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="auto"><div><div class="gmail-h5"><div><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail-m_-2209079700082506263quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div class="gmail-m_-2209079700082506263elided-text">
<br>
I've seen a recent presentation by Maor Lipchuk that is showing the<br>
"automagic" ansible role for disaster recovery:<br>
<br>
</div><a href="https://www.slideshare.net/maorlipchuk/ovirt-dr-site-tosite-using-ansible" rel="noreferrer" target="_blank">https://www.slideshare.net/mao<wbr>rlipchuk/ovirt-dr-site-tosite-<wbr>using-ansible</a><br>
<br>
It's also related with some youtube presentations demonstrating a real<br>
DR plan execution.<br>
<br>
But what i've seen is that Maor is explicitly talking about 4.2<br>
release. Does that role works only with >4.2 releases or can be used<br>
also on earlier (4.1) versions?<br></blockquote></div></div></div><div dir="auto"><br></div></div></div><div dir="auto">Releases before 4.2 do not store complete information on the OVF store to perform such comprehensive failover. I warmly suggest 4.2!</div><div dir="auto">Y.</div></div></blockquote><div><br></div><div>Indeed,</div><div>We also introduced several functionalities like detach of master storage domain , and attach of "dirty" master storage domain which are depndant on the failover process, so unfortunatly to support a full recovery process you will need oVirt 4.2 env.</div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="auto"><div dir="auto"><br></div><div dir="auto"><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail-m_-2209079700082506263quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span class="gmail-">
<br>
I've tested a manual flow of replication + recovery through Import SD<br>
followed by Import VM and worked like a charm. Using a prebuilt<br>
ansible role will reduce my effort on creating a new automation for<br>
doing this.<br>
<br>
Anyone has experiences like mine?<br>
<br>
Thank you for the help you may provide, i'd like to contribute back to<br>
you with all my findings and with an usable tool (also integrated with<br>
storage arrays if possible).<br></span></blockquote></div></div></div></div></blockquote><div><br></div><div>Please feel free to share your comments and questions, I would very appreciate to know your user expirience.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="auto"><div dir="auto"><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail-m_-2209079700082506263quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span class="gmail-">
<br>
Luca<br>
<br>
(Sorry for duplicate email, ctrl-enter happened before mail completion)<br>
</span><div class="gmail-m_-2209079700082506263elided-text"><span class="gmail-"><br>
<br>
--<br>
"E' assurdo impiegare gli uomini di intelligenza eccellente per fare<br>
calcoli che potrebbero essere affidati a chiunque se si usassero delle<br>
macchine"<br>
Gottfried Wilhelm von Leibnitz, Filosofo e Matematico (1646-1716)<br>
<br>
"Internet è la più grande biblioteca del mondo.<br>
Ma il problema è che i libri sono tutti sparsi sul pavimento"<br>
John Allen Paulos, Matematico (1945-vivente)<br>
<br>
Luca 'remix_tj' Lorenzetto, <a href="http://www.remixtj.net" rel="noreferrer" target="_blank">http://www.remixtj.net</a> , <<a href="mailto:lorenzetto.luca@gmail.com" target="_blank">lorenzetto.luca@gmail.com</a>><br></span>
______________________________<wbr>_________________<br>
Users mailing list<br>
<a href="mailto:Users@ovirt.org" target="_blank">Users@ovirt.org</a><br>
<a href="http://lists.ovirt.org/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.ovirt.org/mailman<wbr>/listinfo/users</a><br>
</div></blockquote></div><br></div></div></div>
</blockquote></div><br></div></div>