ADSM-L

Re: Backing up the TSM server itself

2002-05-25 13:15:23
Subject: Re: Backing up the TSM server itself
From: "Seay, Paul" <seay_pd AT NAPTHEON DOT COM>
Date: Sat, 25 May 2002 13:12:55 -0400
We just used mksysb to recover our system at a DR test.  Worked great!  What
we have done is include all the stuff except the database and logs on the
mksysb and run the mksysb right after we do a database backup and backup
volhistory and devconfig.  That way we have everything we need.  We even
have the client code there so it can be ftped to the servers we are
recovering.  That way we do not have to manage any CDs.  The DR vendor
handles the mksysb CDs if required.

We are in the process of automating the mksysb to be put on 3590 cartridges
and use a special primary sequential pool in the TSM database to house the
rotation management, though nothing will ever be written to those tapes by
TSM.  The way you do this is define private volumes to the pool and use
update commands to the volume access and location fields and issue manual
mtlib commands to move the tapes to unavailable status or offsite as
necessary.

We do backup the TSM server just like everyone suggested here.  But, only to
be able to restore something from a previous date and time and a couple of
management file systems not on the mksysb.

Paul D. Seay, Jr.
Technical Specialist
Naptheon, INC
757-688-8180


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