Results 1 to 4 of 4
  1. #1
    Join Date
    Oct 2004
    Thanked 0 Times in 0 Posts

    Default 2 TSM servers 1 library

    I'm looking for some suggestions on creating a 2nd TSM server. I want to take our current server and make it prod only and the new one for dev/qa both sharing the same 3584

  2. #2
    Moderator moon-buddy's Avatar
    Join Date
    Aug 2005
    Somewhere in the US
    Thanked 233 Times in 228 Posts


    You need to make two logical libraries - each with each set of drives and a control path. The drives cannot share IF you want the tapes to be independent of one another.

  3. #3
    Moderator Harry_Redl's Avatar
    Join Date
    Dec 2003
    Czech Republic
    Thanked 100 Times in 99 Posts



    What Ed is suggesting is one option. Another option is using TSM managed library sharing (one server acts as a Library Manager, other is the Library client).
    - all servers can have access to all drives and all slots
    - no need for partitioning the library (license, work etc.)
    - if Library Manager is out-of-service then no server can access the library (without reconfiguration)

    You can find more here:


  4. #4
    Join Date
    May 2004
    Victoria, Australia
    Thanked 0 Times in 0 Posts


    Yeah, I reckon the best way to tackle this, would be to make the development TSM server a library client of the Production TSM server and run a common scratch pool for all tape library clients to share.

    So, SAN zone in all the tape drives and install the necessary device drivers on the development TSM server.
    Then setup your server to server communications between the production TSM server and the development server.
    On the development server create a tape library of libtype=shared, Primarylibmanager='ProdTSMServerName', thus using the production TSM server as the library manager.
    On the development server create device classes (3592 or LTO for example) with the library name you just created
    On the production server create tape drive paths from the development server to the tape drives, ensuring that the DEVICE address is that shown on the library client (it may be a different SCSI/DEVICE/MOUNT ID that the production TSM server for the same drive).

    To limit the amount of drive resources that the development server has access to, you can either set the drive limit of the device class on the development server (but still allow access to all drives), or only create drive paths on the library manager to a limited subset of the available drives.

    You can do what we did and create a small TSM Library manager instance who's job is only to manage library functions, then ALL TSM servers become library clients. The reason we did this, is initially when we took production TSM down for maintenance, all other TSM library clients (such as development) lost access to their tape drives.

    There's lots of proper IBM documentation around to do this.

Similar Threads

  1. Library sharing problem between 5.5 and 6.1 TSM servers
    By Nicke in forum Tape / Media Library
    Replies: 10
    Last Post: 04-12-2010, 02:38 AM
  2. Sharing Tape library for Four TSM servers
    By tsmboys in forum Tape / Media Library
    Replies: 2
    Last Post: 03-02-2009, 09:27 AM
  3. 2 TSM Servers sharing 1 library - Possible?
    By Blinque in forum Tape / Media Library
    Replies: 4
    Last Post: 04-14-2008, 11:56 PM
  4. How to use the library with two TSM servers?
    By rchoudarapu in forum Tape / Media Library
    Replies: 4
    Last Post: 12-07-2007, 11:37 AM
  5. LTO1 and LTO2 in one Library for several TSM Servers
    By Winfried in forum Tape / Media Library
    Replies: 0
    Last Post: 02-25-2003, 02:48 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts