We do our mksysb's to the same tape drive that TSM uses.
We bring down the TSM server so that it does not own the tape device anymore
and then start the mksysb backup.
Haven't had a problem with at all.  Have tested this at our DR hotsite and
works fine.


-----Original Message-----
From: Prather, Wanda [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, August 22, 2001 2:22 PM
To: [EMAIL PROTECTED]
Subject: Re: TSM Bare Restore AIX Different Arch


We do the mksysb's to disk.  Then TSM backs them up.
Then we only need the tape version of mksysb for the TSM server itself.

There is also a companion product to TSM called Bare-Metal restore, that
will take care of this stuff for you.
There is a link to the BMR info on the TSM home page:
http://www.tivoli.com/products/index/storage_mgr/



-----Original Message-----
From: Dave Z [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, August 22, 2001 10:42 AM
To: [EMAIL PROTECTED]
Subject: TSM Bare Restore AIX Different Arch


Folks,

I apologize if this is a FAQ....

(I cannot find a "complete" documented procedure)

:0(


Currently, we use the following procedure to restore systems:

1) Restore the OS using the "cloaner" method as published by IBM:
   a) Boot off of the AIX installation media
   b) Restore system from tape (mksysb)
  (This allows you to recover the OS to dissimilar hardware)
2) Reconstruct the network (including the TSM backup network).
3) Restore all application data (and system data if needed) via TSM.

This methodology does not support a true DR test as our mksysb tapes are
not cut regularly or vaulted.

Unfortunately we do not have a solution that allows us to cut bootable AIX
tapes on a regular basis.  (Not all of the systems have local tape drives.
The procedure can not be automated. etc.)

In the future we must restore all RS/6000s with only our vaulted
installation media (OS and TSM) as well as our vaulted TSM tapes.  Due to
this we must develop procedures for a total bare metal restore of an
RS/6000 using only the OS installation media, TSM backup tapes, and any
relevant TSM disaster recovery reports.

We would like to develop a procedure that details the recovery of a generic
RS/6000 using only installation media, TSM backup, and disaster recovery
reports.

Ideas/Things to consider:

We can not assume that we will recover systems to identical hardware.  As
such we can not simply install a base OS and restore.
 What system files (/etc/passwd, /etc/hosts, etc...) are relevant to the
recovery of the system.
 What system files should not be recovered?  (I.e. kernel, driver specific,
etc.)


Can anyone help with any existing procedures or point me in the proper
direction?

Thanks!


DaveZ

Reply via email to