<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On 9 February 2017 at 15:48, 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:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote"><span class="">On Thu, Feb 9, 2017 at 6:00 PM, Doug Ingham <span dir="ltr"><<a href="mailto:dougti@gmail.com" target="_blank">dougti@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote"><span>On 9 February 2017 at 12:03, Dan Yasny <span dir="ltr"><<a href="mailto:dyasny@gmail.com" target="_blank">dyasny@gmail.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="ltr"><div class="gmail_extra"><br><div class="gmail_quote"><span class="m_1644357432940812966m_5385279511923747685gmail-">On Thu, Feb 9, 2017 at 9:55 AM, Doug Ingham <span dir="ltr"><<a href="mailto:dougti@gmail.com" target="_blank">dougti@gmail.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="ltr">Hi Dan,<br><div class="gmail_extra"><br><div class="gmail_quote"><span>On 8 February 2017 at 18:26, Dan Yasny <span dir="ltr"><<a href="mailto:dyasny@gmail.com" target="_blank">dyasny@gmail.com</a>></span> wrote:<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><span></span><div class="gmail_extra"><div class="gmail_quote"><span><div><br></div></span><div>But seriously, above all, I'd recommend you backup the engine (it comes with a utility) often and well. I do it via cron every hour in production, keeping a rotation of hourly and daily backups, just in case. It doesn't take much space or resources, but it's more than just best practice - that database is the summary of the entire setup.</div><br clear="all"></div></div></div></blockquote><div><br></div></span><div>If you don't mind, may I ask what process you use for backing up your engine? If you use HE, do you keep one server dedicated to just that VM?<br></div><div>I've not had that particular issue in the restore process yet, however I read that it's recommended the HE host is free of virtual load before the backup takes place. And as they need to be done frequently, I'm reading that as a dedicated host...<span class="m_1644357432940812966m_5385279511923747685gmail-m_-816755705011915139HOEnZb"><font color="#888888"><br></font></span></div></div><span class="m_1644357432940812966m_5385279511923747685gmail-m_-816755705011915139HOEnZb"><font color="#888888"><br></font></span></div></div></blockquote><div><br></div></span><div>If you use a dedicated host, you might as well abandon self hosted. HE is nice for small setups with the HA built in for extra fun, but once you scale, it might not be able to cope and you'll need real hardware. You're running a heavy-ish java engine plus two databases after all. </div><div><br></div><div>So as I said, all I do is add the engine-backup command to cron on the engine, and then my backup server comes in and pulls out the files via scp, also through cron. Nothing fancy really, but it lets me sleep at night</div></div></div></div></blockquote><div><br></div></span><div>This particular project has 10 new maxed out servers to back it, and I don't see it outgrowing that for at least a year or so. It's hardly a full DC.<br>I presume the DB will become the heaviest part of the load, and I'm already planning a separate high I/O environment for dedicated HA DB hosts.<br><br></div><div>See the top section of this page:</div></div><a href="http://www.ovirt.org/documentation/self-hosted/chap-Backing_up_and_Restoring_an_EL-Based_Self-Hosted_Environment" target="_blank">http://www.ovirt.org/documenta<wbr>tion/self-hosted/chap-Backing_<wbr>up_and_Restoring_an_EL-Based_<wbr>Self-Hosted_Environment</a><br><br></div><div class="gmail_extra">It seems that I'll always have to keep at least one host free to be able to avoid restore problems. If not, and I were to keep hourly backups, then migrating VMs off the host every hour would just be a pain.</div></div></blockquote><div><br></div></span><div>I don't see the point in an hourly backup. Of what? The DB? The VM? What storage will it be based on?</div><div>I suggest revising the strategy.</div><span class=""><div> </div></span></div></div></div></blockquote><div><br></div><div>Um, that wasn't my suggestion. To be honest, a fortnight's worth of daily engine-backups & snapshots of the engine volume should suffice for us. It's a "Hyperconverged" setup using gluster storage on the compute nodes.<br></div></div><br clear="all"><br>-- <br><div class="gmail_signature" data-smartmail="gmail_signature">Doug</div>
</div></div>