ADSM-L

Backing up Devconfig & Volhist to cartridge

2003-01-24 09:35:16
Subject: Backing up Devconfig & Volhist to cartridge
From: Shannon Bach <SBach AT MGE DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Fri, 24 Jan 2003 08:32:45 -0600
TSM Server=MVS OS/390 4.2.3
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.  My problem is that
there doesn't seem to be a way I can easily copy these two file to
cartridge.  The Backup DB  devclass=cart3590 sends the DB backup to
cartridge, but there are no such options for the volhist or devconfig.
Does anyone know of a way to do this?  I searched as many resources
(manuals, redbooks etc.) but could not seem to find anything.  My only
other option would be to cut and paste to a text file which would take a
lot of time.  Any ideas?

Thanks in advance,
Shannon

Madison Gas & Electric Co.
Operations Analyst - Data Center Services
Office 608-252-7260
Fax 608-252-7098
e-mail sbach AT mge DOT com

<Prev in Thread] Current Thread [Next in Thread>