<div dir="ltr">Hi Dan,<br><div class="gmail_extra"><br><div class="gmail_quote">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:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><span class=""></span><div class="gmail_extra"><div class="gmail_quote"><span class=""><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><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...<br></div></div><br>-- <br><div class="gmail_signature" data-smartmail="gmail_signature">Doug</div>
</div></div>