head     1.2;
branch   ;
access   ;
symbols  ;
locks    ; strict;
comment  @# @;


1.2
date     92.12.23.23.15.57;  author romig;  state Exp;
branches ;
next     1.1;

1.1
date     92.04.17.11.03.10;  author romig;  state Exp;
branches ;
next     ;


desc
@A README file.  What more can I say?
@


1.2
log
@misc 2.6beta changes
@
text
@Misc scripts that might make life better/easier.  We use these in our
department, hence the directory name.

daily, weekly, full	Simple scripts that make it easy to start
			several backup runs at one shot.  For dailies
			and weeklies, we start 6 runs where the only
			differences are the host groups and drives.  Its
			a pain to run the 6 all-backups commands by hand
			- these pop up xterm windows with all-backups
			running in each, you just take note of the tape
			ids, load them in the drives, and type return 6
			times. 

backup-db-fixer		We've had infrequent and intermittant problems
			wherein all of the run databases are emptied of
			all/most of their entries.  We run this script
			every hour - it copies the database to a known
			location, and checks it to see if its sane.  If
			it isn't, it renames the copy so that we can
			use it for debugging later and restores the real
			database from the latest good copy (and warns
			folks about what it did).  If the
			database is ok, then it renames the copy to be
			the latest good copy.  

			It saved our bacon several times in November,
			but hasn't caught anything since.

			To use it, edit it carefully, changing things
			that need to change.  Install it in your SDIR
			and create a symlink to wrapper named
			backup-db-fixer in BDIR.  Create a crontab entry
			and let it fly.  Be sure to change $LOOK_FOR.

@


1.1
log
@Initial revision
@
text
@d1 2
a2 3
These are some scripts that may or may not work that I've been playing with 
to make it easier to start backup runs, particularly the daily and weekly
runs (since those are 6 separate backup runs on 6 tapes).
d4 31
a34 1
--- Steve
@
