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


-----Original Message-----
From: Kauffman, Tom [mailto:[EMAIL PROTECTED]]
Sent: Friday, May 24, 2002 2:49 PM
To: [EMAIL PROTECTED]
Subject: Re: Backing up the TSM server itself


If you're trying to have something for use in a recovery environment, I'd be
inclined to us tar instead.

Think about it -- your TSM server is not available, how do you restore the
TSM server files?

(Yes, backup sets will work -- If you created them beforehand AND the system
has compatible tape drives).

We have gone a different route. I've installed the TSM server code on both
our production S7As; it runs on one and just exists on the other (which runs
SAP). In our D/R process, we bring TSM and SAP both up on the same system.
The TSM code is recovered with MKSYSB when we restore the system, and then
we copy in the current device config and volume history files.

Tom Kauffman
NIBCO, Inc

> -----Original Message-----
> From: Rupp Thomas (Illwerke) [mailto:[EMAIL PROTECTED]]
> Sent: Friday, May 24, 2002 12:17 PM
> To: [EMAIL PROTECTED]
> Subject: Backing up the TSM server itself
>
>
> Hi TSM-ers,
>
> I'm backing up the TSM server files to another machine (DEVCONFG.FILE,
> DSMSERV.DSK, DSMSERV.OPT, VOLHIST.FILE). Does it make sense to backup
> the rest of the TSM Server using the TSM client?
> I'm running TSM 4.1.5.0 on AIX 4.3.3
>
> Kind regards and greetings from Austria
> Thomas Rupp
> Vorarlberger Illwerke AG
> MAIL:   [EMAIL PROTECTED]
> TEL:    ++43/5574/4991-251
> FAX:    ++43/5574/4991-820-8251
>
>
>
> --------------------------------------------------------------
> ----------------------------
> Dieses eMail wurde auf Viren geprueft.
>
> Vorarlberger Illwerke AG
> --------------------------------------------------------------
> ----------------------------
>

Reply via email to