<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Jul 22, 2014 at 6:41 PM, Gary Buhrmaster <span dir="ltr"><<a href="mailto:gary.buhrmaster@gmail.com" target="_blank">gary.buhrmaster@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">On Tue, Jul 22, 2014 at 6:21 PM, Raymond Wagner <<a href="mailto:raymond@wagnerrp.com">raymond@wagnerrp.com</a>> wrote:<br>
.....<br>
<div class="">> On the contrary, for an end user, redundancy is much easier and cheaper to<br>
> implement than backups. If all you want to do is protect against a single<br>
> drive failure, all you need is one extra drive. Backups require at minimum<br>
> double the amount of storage, and proper backups involve multiple times the<br>
> amount of storage in rotation.<br>
<br>
</div>It depends on your definition of the term "backup". Using<br>
the vernacular of something like TSM, an *archive* (a complete,<br>
independent copy) certainly takes multiple times the storage<br>
as each is (essentially) container of the current contents at<br>
a point in time (bare metal restoration is sometimes supported).<br>
A system *backup*, on the other hand, can use a database to<br>
track active and inactive files, and only needs to store one copy<br>
of a file with a particular hash (fancier backup systems might<br>
maintain deltas of changed files, rather than a new copy for<br>
each changed file, and data de-duplication solutions exist<br>
so that only one copy of a particular stream of data (sometimes<br>
entire files, sometimes partial files) needs to be kept on the<br>
backup media). Of course proper archives and backups do also<br>
have multiple copy (and site) requirements, since you can never<br>
tell when the next Chicxulub asteroid will hit (although, I suspect,<br>
TV will be the least of your worries when it does).</blockquote><div> </div><div>Exactly. Webster defines backup as simply "<span style="color:rgb(0,0,0);font-family:Verdana,Arial,Helvetica,sans-serif;font-size:13px;line-height:20px">a copy of computer data".</span></div>
<div><span style="color:rgb(0,0,0);font-family:Verdana,Arial,Helvetica,sans-serif;font-size:13px;line-height:20px"><br></span></div><div><span style="color:rgb(0,0,0);font-family:Verdana,Arial,Helvetica,sans-serif;font-size:13px;line-height:20px">I use the simplest backup strategy known to man... I copy my "important" recordings to an external drive that is only powered on long enough to perform said backup. I run a script based on rsnapshot, so I can do some recovery of deleted files (something that a raid array cannot do). Can't get any more basic. But it means that if one of my recording drives fail, I don't have to tell my wife that I lost an entire season of her favorite show.</span></div>
<div><span style="color:rgb(0,0,0);font-family:Verdana,Arial,Helvetica,sans-serif;font-size:13px;line-height:20px"><br></span></div><div><span style="color:rgb(0,0,0);font-family:Verdana,Arial,Helvetica,sans-serif;font-size:13px;line-height:20px">Simple, and cheap... and actually fast compared to some solutions.</span></div>
<div><span style="color:rgb(0,0,0);font-family:Verdana,Arial,Helvetica,sans-serif;font-size:13px;line-height:20px"><br></span></div></div></div></div>