Below is a link to my one bash script solution (with configuration file) built on ssh, dump/restore, using an ssh authorized_keys for the remote user. I only do nightly incrementals and weekend fulls. If you ask John Sechrest you'll find out I've been writing dump scripting for a long time now... :)
This script has saved my bacon three times now with disk crashes. The restore is easy via ssh and restore (see the script itself for example invocation, since it does a dump over ssh, then runs restore as a cross-check to dump the table of contents). You can get ssh and restore off a live linux CD (knoppix), one-floppy linuxes or the like. If you don't have any network access, in general, any dump-based solution can be restored (in a pinch) by moving the disk drive to the machine with the backup, and rebuilding it there, then moving it back to the busted machine. The script itself is at: http://twiki.loowit.net/bin/view/Main/BackupScripts Why use Korn shell when you can do all that with bash and it already comes standard? In general, bash is a superset of Korn shell functionality, including command-line editing (vi or emacs), command-completion, and all of the function, alias, looping, parameter, and command substitution that Korn shell can do ${FNAME##*?}. bash also adds of some of the csh interactives (all the ! and ^^^ syntax, history, pushd, popd, dirs). You may want to include or exclude filesystems using field 5 of the /etc/fstab... it's the standard way since BSD. Cheers, James -- James Perkins [EMAIL PROTECTED] http://loowit.net/~james -=*=- -=*=- -=*=- -=*=- -=*=- -=*=- -=*=- -=*=- -=*=- -=*=- -=*=- -=*=- O God, I could be bounded in a nut shell and count myself a king of infinite space, were it not that I have bad dreams. -- Hamlet, William Shakespeare _______________________________________________ EuG-LUG mailing list [EMAIL PROTECTED] http://mailman.efn.org/cgi-bin/listinfo/eug-lug
