<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
[Adding gluster-users]<br>
<br>
<div class="moz-cite-prefix">On 08/29/2013 10:05 PM, Steve Dainard
wrote:<br>
</div>
<blockquote
cite="mid:CAHnsdUtKTqZJLBtBx1F2muC_TG+RkmK=ABU47unfmhK73xPKGw@mail.gmail.com"
type="cite">
<div dir="ltr">Hello all,
<div><br>
</div>
<div>I'm looking for some opinions on our current topology and
how a disaster recovery plan would shake out in the real world
on an ovirt/gluster clustered system.</div>
<div><br>
</div>
<div>Please ignore the RH references in the attached diagram,
we're still on the fence if we're going with support or not.</div>
<div><br>
</div>
<div><img src="cid:part1.08090805.09060904@redhat.com"
alt="Inline image 1" height="356" width="564"></div>
<div><br>
</div>
<div>The Plan</div>
<div>At HQ site:</div>
<div>Two Gluster nodes running as replica's.</div>
<div>~4 Virt notes</div>
<div>1 Manager node (likely running on as separate kvm HA VM)</div>
<div><br>
</div>
<div>
Offsite:</div>
<div>1 Gluster node acting as a geo-replication target</div>
<div>1 Virt node</div>
<div>1 Manager in standby (waiting to recover db backup)</div>
<div>*Even better would be using both nodes at this site as one
striped gluster volume, standby Manager, and Virt nodes to
eliminate the standby Manager box, decrease costs and increase
virt resources, but I'm not sure this is doable quite yet.*</div>
<div><br>
</div>
<div>During regular operations we're replicating our gluster
storage offsite with geo-replication.</div>
<div><br>
</div>
<div>In the event of a disaster (for simplicity we'll say the
server room becomes unusable) I would want to recover the
Manager at the offsite location from a backup, add the
geo-replicated gluster storage domain as the normal domain,
then start spinning up the business critical VM's. With a
router in-place and some external DNS changes we should be
able to keep our VPN accessible and all our internal resources
available to mobile/home workers, or in this simple case even
from our normal office location (already have the site-to-site
VPN active).</div>
<div><br>
</div>
<div>I'm planning on using a vpls solution to extend the VM
subnet and storage/virt subnet across both sites so we don't
need to worry about dns/IP changes in the middle of recovery.</div>
<div><br>
</div>
<div>I think the biggest question so far is can we smoothly
replace the normal storage domain on ovirt with the
geo-replicated storage domain in the DR situation off-site?</div>
<div><br>
</div>
<div>I've tried to layout most of the high level stuff here so
if anyone sees any flaws or potential gotcha's feel free to
chime in. I can provide more detail if necessary.</div>
<div><br>
</div>
<div>Thanks!</div>
<div><br clear="all">
<div><span style="font-family:arial,sans-serif;font-size:16px"><strong>Steve<br>
</strong></span></div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Users@ovirt.org">Users@ovirt.org</a>
<a class="moz-txt-link-freetext" href="http://lists.ovirt.org/mailman/listinfo/users">http://lists.ovirt.org/mailman/listinfo/users</a>
</pre>
</blockquote>
<br>
</body>
</html>