>Our client backups and DB backups go to a Magstar 3590 Tape Subsystem.
>Currently the Devconfig & Volhist files are kept on DASD and are updated
>automatically when the TSM DB is updated.  We do a full volume backup of
>our DASD every evening after our batch production is finished.  The TSM
>backup of the clients has a window of 18:00 thru 3:00am & after that TSM AM
>processing starts.  This includes backing up the primary stgpools to the
>copy pool and a TSM DB backup to cartridge, which are then taken OFFSITE.
>I have a concern that in the event of a real disaster my volhist(which
>would change) and devconfig(if by some slim chance was changed) would be
>out of sync with the OFFSITE TSM DB backup.  I am thinking a way around
>this would be to copy the volhist and devconfig to cartridge just before
>the TSM DB backup and send this OFFSITE with the rest. ...

I should think that a simple expedient would be to make a timestamped copy of
the files (____.YYYYMMDD+hhmmss) at the appropriate time to have that sent
as part of your disk backups.  A further assurance measure would be to
automatically email or otherwise send (scp, ftp) that modest file to an offsite
location at the time it is created.

  Richard Sims, BU