1. Forum Rules (PLEASE CLICK HERE TO READ BEFORE POSTING) Click the link to access ADSM.ORG Acceptable Use Policy and forum rules which should be observed when using this website. Violators may be banned from this website. This message will disappear after you have made at least 12 posts. Thank you for your cooperation.

2 TSM servers 1 library

Discussion in 'TSM Server' started by tsmuser10, Apr 5, 2012.

  1. tsmuser10

    tsmuser10 New Member

    Oct 11, 2004
    Likes Received:
    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
  3. moon-buddy

    moon-buddy Moderator

    Aug 24, 2005
    Likes Received:
    Electronics Engineer, Security Professional
    Somewhere in the US
    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.
  4. Harry_Redl

    Harry_Redl Moderator

    Dec 29, 2003
    Likes Received:
    IT Consultant
    Czech Republic

    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:

  5. jharris

    jharris New Member

    May 24, 2004
    Likes Received:
    Victoria, Australia
    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.

Share This Page