<div dir="ltr">crashplan</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Jan 9, 2013 at 11:28 AM, Phil Turmel <span dir="ltr"><<a href="mailto:philip@turmel.org" target="_blank">philip@turmel.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On 01/09/2013 10:49 AM, Ron Frazier (ALE) wrote:<br>
<br>
[trim /]<br>
<div class="im"><br>
> As a side note, in addition to this concern about viruses, having the<br>
> backup drive directly attached to the machine being backed up (not a<br>
> nas), subjects the backup drive to any electrical failures that the<br>
> client machine has. So, the thing that causes you to need the<br>
> backup, can trash the backup. That's the general class of phenomenon<br>
> that I'm trying to avoid. Having the backup drive on a nas avoids<br>
> the potential problem of electrical failure on the client, but does<br>
> not avoid the virus problem without jumping through some hoops.<br>
<br>
</div>The electrical concern is not the only one. If the nas is in the same<br>
building as the subject machine, it is vulnerable to the same fire,<br>
flood, tornado, or asteroid strike. :-) Or theft.<br>
<br>
An offsite rotation is vital, or an equivalent streaming solution.<br>
<span class="HOEnZb"><font color="#888888"><br>
Phil<br>
</font></span><div class="HOEnZb"><div class="h5">_______________________________________________<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>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br>Charles Selfridge<br><br>PBYC IT director<div><br></div><div>(404) 910-3409</div>
</div>