<div dir="ltr">On Fri, Feb 22, 2013 at 11:32 AM, Jonathan Meek <span dir="ltr"><<a href="mailto:jonathan.l.meek@gmail.com" target="_blank">jonathan.l.meek@gmail.com</a>></span> wrote:<br><div class="gmail_extra"><div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>Thanks for sharing your thoughts on backups. I hope I didn't give the impression that all was lost when my hard drive appears to have failed. I had everything backed up ahead of time but since I got it to boot one last time and it prompted me to backup I figured I would back it up since it is only data that I backup off my rigs. (Haven't started backing up any configuration stuff but that's for another time when I am not working full force on a master's degree)<br>
<br></div>But in the future plan to implement the suggestions I see here. <br><br>Regards, <br><br>Jonathan</div></blockquote><div><br></div><div style>Hi Jonathan,</div><div style><br></div><div style>I hope you didn't take it that I was specifically targeting your post -- I just happened to read your post while waiting on something else to finish and it inspired me to write a message I'd been meaning to for a while. The topic of how to "burn in", "test", "repair", etc., hard drives has been a frequent topic of discussion and I wanted to share my feelings on it.</div>
<div style><br></div><div style>Unlike JD and Ron (and others), I don't bother with anything resembling a system image for desktop systems. I backup a list of installed packages and the contents of /etc, to be sure, but for the most part, I assume I'll be doing a reinstall in my restore strategy, and I'm ok with that strategy. For servers, of course, images are nice, because downtime is more critical there.</div>
<div style><br></div><div style>Good luck with the master's degree!</div><div style><br></div><div style>David</div></div></div></div>