Matthew McGeary wrote:

>We're in the process of setting up a second TSM server at our head office to 
>split the backup load.  Primary storage is disk, so that's no problem >but we 
>offsite to LTO4 tape.

>My original thought was that we'd set up library sharing using either the 
>current TSM server as the manager or a new TSM server instance that is >solely 
>responsible for library operations.  I'm leaning towards a new, 
>library-manager-only TSM server, with two TSM library clients.

>Where I'm unclear is how DR works with a shared library manager.  Do we go 
>through the process of restoring the TSM library manager instance >first, then 
>the two (or more) library clients?  Or (if we have two libraries available at 
>our DR site) can I restore the two library clients >independently, each 
>attached to their own library?

I recently performed a recovery test with a library manager and one client in 
our TSM test environment. The test environment is a scaled down version of a 
production environment with a library manager and a library client at one site 
and a second library client at another site. The recovery worked just as you 
suspect: I recovered the library manager first and then used the recovered 
library manager to support recovery of the library client.

We used to use a commercial hot site to recover a TSM server with an IBM 3494 
tape library. We had to reconfigure the recovered server to use the TS3500 
library supplied by the hot site. I think you could just as well reconfigure 
each of your library clients to use a non-shared tape library. If you do this 
you will need to update the device configuration files to match the recovery 
site tape infrastructure before starting the database restores and subsequently 
update the TSM databases to match the recovery site tape infrastructure. If the 
hot site provides SCSI libraries the device configuration file updates will 
include adding records showing the storage slot element numbers for tape 
volumes.

Thomas Denier
Thomas Jefferson University Hospital


The information contained in this transmission contains privileged and 
confidential information. It is intended only for the use of the person named 
above. If you are not the intended recipient, you are hereby notified that any 
review, dissemination, distribution or duplication of this communication is 
strictly prohibited. If you are not the intended recipient, please contact the 
sender by reply email and destroy all copies of the original message.

CAUTION: Intended recipients should NOT use email communication for emergent or 
urgent health care matters.

Reply via email to