<html dir="ltr">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<style id="owaParaStyle" type="text/css">P {margin-top:0;margin-bottom:0;}</style>
</head>
<body ocsi="0" fpstyle="1">
<div style="direction: ltr; font-family: Tahoma; color: rgb(0, 0, 0); font-size: 10px;">
<div style=""> And right here is the point of concern:<br>
<br>
"Explaining it now, it now seems like overkill to take the nightly backup off site since there will be a remote mirror of the data, but I'd rather be over-prepared than under-prepared."<br>
<br>
Yes, it is better to be over-prepared than under-prepared. However, by requiring the off-site component to be a movable hard drive, you are drastically limiting your options. If you split up the requirements:<br>
<br>
1) Ability to restore to "point in time" where POT is a nightly backup stored for two weeks.<br>
2) Ability to store backup sets offsite<br>
<br>
You can put in a backup server or NAS that stores multiple backup sets and then mirror these sets off site. If you like, you can also mirror these to a USB/SATA drive and pull that offsite occasionally... but the former alone would meet the criteria.<br>
<br>
It is worth noting that NO backup solution will be admin-free. You cannot rely on the system to notify you in case of failure, as a failure could also fail to send the notifications. The NAS issue mentioned earlier in this thread would have been resolved
if someone had checked for success on a daily basis. Most other mirroring / backup set issues can be caught by spending 5m a day making sure it's working OK.<br>
</div>
<div><br>
<div style="font-family: Tahoma; font-size: 13px;">
<div style="font-family: Tahoma; font-size: 13px;">
<div style="font-family: Tahoma; font-size: 13px;"><font style="font-family: Courier New;" color="#888888" size="1">-Josh More, CISSP, GIAC-GSLC, GIAC-GCIH, RHCE, NCLP<br>
<a href="mailto:morej@alliancetechnologies.net" target="_blank"><span class="il">morej@alliancetechnologies.net</span></a>
<br>
515-245-7701 </font>
<div style="font-family: Tahoma; font-size: 13px;"></div>
</div>
</div>
</div>
</div>
<div style="font-family: Times New Roman; color: rgb(0, 0, 0); font-size: 16px;">
<hr tabindex="-1">
<div style="direction: ltr;" id="divRpF75272"><font color="#000000" face="Tahoma" size="2"><b>From:</b> cialug-bounces@cialug.org [cialug-bounces@cialug.org] on behalf of Tim Champion [timchampion@gmail.com]<br>
<b>Sent:</b> Thursday, April 15, 2010 13:25<br>
<b>To:</b> Central Iowa Linux Users Group<br>
<b>Subject:</b> Re: [Cialug] suggestions on HDD based backup<br>
</font><br>
</div>
<div></div>
<div>
<div class="gmail_quote">On Thu, Apr 15, 2010 at 12:52 PM, Eric Junker <span dir="ltr">
<<a href="mailto:eric@eric.nu" target="_blank">eric@eric.nu</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="im">On 4/15/2010 11:27 AM, Tim Champion wrote:<br>
> We are planning on going to a hard drive based backup system at work. We<br>
> are a non-profit on a tight budget (I can spend about $1500 on this<br>
> total), so a enterprise level disk-to-disk system isn't feasible. The<br>
<br>
</div>
How many computers are you backing up? How much storage space do you need?<br>
<br>
If you want something that works right out of the box I would suggest<br>
something like the Drobo FS <a href="http://www.drobo.com/" target="_blank">http://www.drobo.com/</a> You do pay a premium<br>
for the ease of use. Instead of swapping drives for off-site backup you<br>
could use a network based backup like Mozy <a href="http://mozy.com" target="_blank">
http://mstorageozy.com</a> or manually<br>
backup to Amazon S3.<br>
<br>
If you want more of a traditional NAS device, I've heard good things<br>
about QNAP <a href="http://www.qnap.com/" target="_blank">http://www.qnap.com/</a><br>
<font color="#888888"><br>
</font></blockquote>
<div><br>
I've looked into many of the online backup services. Our total backup need right now is about 500GB, so the online services like mozy start getting really expensive. Mozy charges 50 cents per GB per month, which would be $250 per month. So, that pretty much
rules that out.<br>
<br>
We are already planning to do a site-to-site data sync between Marshalltown & Ames, but that will be a live sync, and would not protect against accidental deletion. We've all heard the horror stories of places using mirroring or something like a live sync and
then losing data anyway because they did not have a "real" backup. The piece I'm specifically looking at is the nightly backup so we have at least 2 weeks of history of our data. Explaining it now, it now seems like overkill to take the nightly backup off
site since there will be a remote mirror of the data, but I'd rather be over-prepared than under-prepared.<br>
<br clear="all">
Tim Champion<br>
<a href="mailto:timchampion@gmail.com" target="_blank">timchampion@gmail.com</a><br>
<br>
</div>
</div>
<br>
</div>
</div>
</div>
</body>
</html>