I've been through a few myself, and found rdiff-backup (lookup in Google) to be the best.
It uses a sophisticated algorithm to determine only the changed bits on your filesystem for each incremental backup. Makes it possible to restore from any specified arbitrary time point without using much extra disk space. A simple cron job can dump the entire filesystem to another machine via SSH every night (assuming you have root access on both devices to keep UID/GID's etc. Only the changed data will be transfered over the wire. I've done a full system reinstall using rdiff-backup (this week actually), so I know it works well. Ryan Quoting Daevid Vincent <[EMAIL PROTECTED]>: > I've just spent the past few days writing this backup script... > > http://resume.daevid.com follow the link for it. > > It will do weekly full backups on Sunday and daily diff backups. It also > does daily dumps of all databases in the mysql db directory then > combines them into a single .tgz file for storage. It is best if you > have /backups as a separate device because I mount it rw and then ro > when finished storing the backups. Simply list what you want at the top > and use the exclude file to omit what you don't. > > Ideally I'd like to make it so it only backs up the mysql databases that > have changed (diff), but I'm not sure how to determine that, as the > directory doesn't seem to change it's date as I would expect, if the > contents within are updated. Hmmm. Ideas? > > Daevid Vincent > http://daevid.com > > Ps. And yes, I sent that as a link in my resume because I'm unemployed > and would love any offers for coding work with PHP, Linux, SQL, etc... > ;-) > > > > -----Original Message----- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED] On Behalf Of Gordon Messmer > > Sent: Wednesday, May 28, 2003 9:05 PM > > To: [EMAIL PROTECTED] > > Subject: Re: backup scripts > > > > > > Richard Humphrey wrote: > > > Is > > > anyone using another method (cpio,dump etc) > > > > I use cpio and this script: > > http://phantom.dragonsdawn.net/~gordon/backup/backup > > > > > and which do you prefer and > > > why? > > > > tar is fine for getting a directory and its contents, but for > > anything > > more complex, it's much harder to live with. cpio and dump are both > > able to back up a directory without its contents, which is > > important if > > you expect that permissions may change (and should be restored) in an > > incremental backup. tar handles only the most basic of situations. > > > > Also, if your filesystem has any features outside of the > > standard POSIX > > spec, dump will be the only tool which will back up and restore them. > > This is important to consider when using XFS and ACLs, for instance. > > > > If you're backing up more than one machine, I recommend using cpio or > > dump in conjunction with amanda, or another backup spooler. > > > > More important, I think, than any other advice is this: > > Make sure your backups work. Attempt to restore your backups > > to a clean > > machine, or alternate root directory. It doesn't matter what > > you use if > > they don't work. If you're satisfied with the restore, then the > > question of tar vs. cpio vs. dump is less important. > > > > > > -- > > redhat-list mailing list > > unsubscribe mailto:[EMAIL PROTECTED] > > https://www.redhat.com/mailman/listinfo/redhat-list > > > > > -- > redhat-list mailing list > unsubscribe mailto:[EMAIL PROTECTED] > https://www.redhat.com/mailman/listinfo/redhat-list > -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED] https://www.redhat.com/mailman/listinfo/redhat-list
