My 2c, this is what I do...
1. mount a harddisk on an old win2k system to my linux laptop (main dev
system) via samba.
2. make compressed tarball over network to that machine:
tar czvf /mnt/whatever/backup/backupdate_dev.tar.gz dev/
3. repeat for email, misc documents, etc. in 4 separate tarballs.  I
*dont* back up anything linux related or re-installable.  if calamity
occurs I'll be reinstalling everything anyway.  This is for 'rm -rf'
typos or harddisk crashes.

takes awhile but everything gets written to a different harddisk.  I
have to do this b/c the laptop is aging and I'm outta disk space, can't
create the tarballs locally.

burn CD occastionally, delete backups occasionally (I keep the last 5).

I do this before taking laptop on a trip, after a significant milestone
reached, every 2-3 weeks, or when somebody tells me horror dataloss
story and I start to feel nervous.

Someday I want most of this to be done via CVS, having changelogs of
source is handy and I miss it.  So why not just use CVS for most
everything?  But that may not be practical, not sure, TBD.

I've survived zero harddisk crashes with this method.  Keeping fingers
crossed that the 'insurance' is never actually needed.

Best,
J

[jlackey ATsign celestialaudio period com]

>
>         Well I do something similar. The last three backups are stored on a hard
> drive in another machine.
>
>         The last backup is burned to DVD-RW.
>
>         The current backup is written to DVD-RAM.
>
>         Every once in a while I burn a backup to DVD-R and take it offsite.
>
>         It's not 100% coverage, but it has served me well so far! I've survived two
> HD crashes using this method. TTYL
>
> ----------------------------------
> Herbert's PIC Stuff:
> http://repatch.dyndns.org:8383/pic_stuff/
>
> --
> http://www.piclist.com hint: To leave the PICList
> mailto:piclist-unsubscribe-request@mitvma.mit.edu
>
>

--
http://www.piclist.com hint: PICList Posts must start with ONE topic:
[PIC]:,[SX]:,[AVR]: ->uP ONLY! [EE]:,[OT]: ->Other [BUY]:,[AD]: ->Ads