<p>My standard backup plan was tarring and backing up configs and data to a storage array and cycling out the back files on rolling weekly basis.</p>
<p>When trying new risky things i did a snapshot of current state on dev copy of server and if it failed, could roll back.</p>
<p>Wolf Halton<br>
--<br>
<a href="http://wolfhalton.info">http://wolfhalton.info</a> <br>
Apache developer:<br>
<a href="mailto:wolfhalton@apache.org">wolfhalton@apache.org</a></p>
<div class="gmail_quote">On Aug 2, 2013 1:23 PM, "Nolan Voight" <<a href="mailto:nolan.voight@gmail.com">nolan.voight@gmail.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr"><div>A friend asked me to look over a hosting deal she was considering for her business site--the folks offering it used 'cloud' everywhere possible in the ad copy. I assume this means it's all running on virtual machines, as are most affordable hosting plans these days.<br>
<br></div>What is standard practice for back-up on virtual servers (if there is something approaching standard practice)? Exporting the virtual machine & storing that copy until it's replaced by the succeeding copy? <br>
</div>
<br>_______________________________________________<br>
Ale mailing list<br>
<a href="mailto:Ale@ale.org">Ale@ale.org</a><br>
<a href="http://mail.ale.org/mailman/listinfo/ale" target="_blank">http://mail.ale.org/mailman/listinfo/ale</a><br>
See JOBS, ANNOUNCE and SCHOOLS lists at<br>
<a href="http://mail.ale.org/mailman/listinfo" target="_blank">http://mail.ale.org/mailman/listinfo</a><br>
<br></blockquote></div>