It all comes down to what you're backing up On Wed, 22 Dec 2004 14:59:17 -0800, Bob Miller <[EMAIL PROTECTED]> wrote: > larry price wrote: > > > Not as long as I would be if something were to happen today, > > currently all the truly critical unreplaceable data is less than 1G > > total, but growing at about 1-2 Megs per week. > > And that's counting the configuration files. > > You should definitely back that stuff up over the Internet. Rsync to > a host in a different town, if possible. The data rate is small > enough (2 MB/week) that remote rsync is very feasible.
some of it is backed up over the internet, in that it's customer website related code, that's in production elsewhere. backing it up to a redundant server would be ideal but isn't going to happen until the revenue stream is there ;-) Also the portion of it that's not intended for public distribution is not intended for public distribution, and would need to be protected in transit, and in storage. I did see a python program to use a Gmail account as a network file system. I could hack it to encrypt tarballs as mime attachements and put the pathinfo in the subject... , then I could access my backups from any browser... (as long as I didn't lose the private key or forget the passphrase) > > there's about 10G of stuff that would be a pain in the wallet to > > replace, some of which is archived on CD.. > > Might also be a candidate for 'net backup, depending on how fast > your link is and whether it's currently idle. Hmm' I could package my mp3 collection up inchunks of 500-700 MB and make them available via bittorrent, then i'd have a distributed network backup ...( oh wait people get arrested for that) A lot of that 10G is dead code, email archives from dead accounts etc. stuff that I keep around because I need to search it occassionally, but not that I look at regularly, This discussion has been useful to me, I've got a much better idea now of what problems I'm trying to solve and how to go about solving them. I think that for me a disk based backup solution is the way to go since it's relatively robust and allows for quick recovery, this doesn't mean that i won't be doing any network backups. And critical stuff will be archived on CD as it is already. Thanks All, now on to implementation. ps. check these out http://www.kanguru.com/kdisk.html -- http://Zoneverte.org -- information explained Do you know what your IT infrastructure does? _______________________________________________ EUGLUG mailing list euglug@euglug.org http://www.euglug.org/mailman/listinfo/euglug
