<div class="gmail_quote">
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">I prefer the KISS approach to dealing with RAID when you are trying to<br>do RAID on the cheap.<br><br>Don't get me wrong, RAID has it's place, especially if you want to<br>
spend the money for hardware that makes RAID easy. But for cheap....<br><br>Just throw the three disks in the box. Configure Myth with a<br>different recording volume for each drive, so it can spread the<br>read/write load out however it pleases.<br>
<br>Then - just set up a nightly script to mirror changed files from disk<br>1 -> disk 2, disk 2 - > disk 3, and disk 3 to disk 1. Schedule the<br>script to run when you aren't usually recording or watching stuff.<br>
<br>Now you have faster writes than you would have on raid, at most, only<br>a day of data loss if a disk fails, and a completely simply data<br>recovery path when a drive fails. No RAID config to deal with 3 years<br>from now when a disk fails, and you don't remember how you configured<br>
it in the first place. The system can also spin the disks down<br>individually... if you are only recording one program, two drives can<br>be powered down.<br>
<div>
<div></div></div></blockquote>
<div> </div>Excellent idea... I think I may use a similar approach when I rebuild my server in a few months. Maybe even use rsnapshot (basically rsync and hardlinks) to take snapshots of data from one disk to the next to recover from accidental deletions/corruption.</div>
<div class="gmail_quote"> </div>
<div class="gmail_quote">Obviously, you could selectively choose what folders to backup and how long to preserve the snapshots based on the importance of the data.</div>
<div class="gmail_quote"> </div>
<div class="gmail_quote">I still like having my DB raided across multiple disks for the read speed advantage.</div>