I haven't looked at this in depth, but crash plan looks interesting. You could theoretically put the backup NAS at a remote location (friend, $work) and get semi-continuous off site backups. I think you can seed the backup server locally before relocating it. They also have an EC2 AMI to run a backup server on AWS.
Personally, I only have 1TB on my ReadyNAS, which in turn is just the Time Machine archive of our desktop/laptop. Once a month I backup the ReasyNAS to an external drive, which I then stash in my desk at work until next month. It was easy to justify the expense with my comptroller (wife) when she nearly lost her iPhoto library a few years back. -- Mason Turner (mobile) On Jul 21, 2011, at 10:13 AM, Mark Dennehy <[email protected]> wrote: > On 21 July 2011 15:05, Chris Ess <[email protected]> wrote: > Why not use external drive(s)? This is the solution I'm currently > looking at for my home fileserver. > > Same issue as with a second NAS really. > I'm thinking here of a box that starts off with 4x2Tb drives in either > RAID-5+hot spare or RAID-6+hot spare, with further disks being added in later > (I tend to have a lot of HD video files from training). So that's either 2 or > 4Tb to have to backup from day one. Which means a 1-2 disk NAS/external drive > to start with, and which would have to be taken off-site to be secure... > well, you get the idea. Awkward and expensive. > > -- > Mark Dennehy > _______________________________________________ > Discuss mailing list > [email protected] > https://lists.lopsa.org/cgi-bin/mailman/listinfo/discuss > This list provided by the League of Professional System Administrators > http://lopsa.org/
_______________________________________________ Discuss mailing list [email protected] https://lists.lopsa.org/cgi-bin/mailman/listinfo/discuss This list provided by the League of Professional System Administrators http://lopsa.org/
