1. Community Tip: Please Give Thanks to Those Sharing Their Knowledge.
    If you receive helpful answer on this forum, please show thanks to the poster by clicking "LIKE" link for the answer that you found helpful.
  2. Community Tip: Forum Rules (PLEASE CLICK HERE TO READ BEFORE POSTING)
    Click the link above 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 notice will disappear after you have made at least 3 posts.

Server dead, storage okay

Discussion in 'Disaster Recovery Module' started by DanGiles, May 5, 2017.

  1. DanGiles

    DanGiles ADSM.ORG Senior Member

    Joined:
    Oct 25, 2002
    Messages:
    611
    Likes Received:
    15
    Occupation:
    Sr. Storage Admin
    Location:
    Toronto, Ont. Canada
    This isn't exactly a DRM question per se, but it is about disaster recovery. I thought I would try it here before going after IBM support.

    Let's say your server goes belly up, but the storage itself (database, logs, storage pools) is all fine. Is there a way to simply point to the database files and be done with it, or does one need to reformat and restore (and then have to audit all of the pools and containers). The log file directories are all given in the dsmserv.opt file, but the only way I know to tell TSM about the database containers are through DSMSERV FORMAT.

    TSM server 8.1.0 on RHEL 6.9. (This would be the same as for TSM v7)
     
  2.  
  3. LED888

    LED888 ADSM.ORG Moderator

    Joined:
    Oct 15, 2002
    Messages:
    807
    Likes Received:
    62
    Only if it was that simple to just update the dsmserv.opt file to point to the database files.
    The thing is that TSM keeps all its configuration data within the database.
    If you deviate from the recovery process, don't bother to call IBM Support they will inform you what you are doing have never been tested and the results are unknown , and please follow the DR process on recovering the TSM Server.

    When you run the dsmserv format it create the file called dsmserv.dsk.
    Many years ago with TSM 5.5, on an AIX os, and this was a test system.
    I try updating the paths in the dsmserv.dsk file to anther location and db/log file name, I was not able to start the TSM Server. When I put back the original path and file name, I was able to start the TSM Server.

    There are numerous docs about DR on the TSM Server.
    Here is a doc you may find of some interest.
    Recovering a loss or damaged of Tivoli Storage Manager server (without DRM)

    Good Luck,
    Sias
     
  4. marclant

    marclant ADSM.ORG Moderator

    Joined:
    Jun 16, 2006
    Messages:
    2,533
    Likes Received:
    354
    Occupation:
    Accelerated Value Specialist for Spectrum Protect
    Location:
    Canada
    The issue is that in addition to have access to the DB and logs, DB2 needs to be aware of the database. There's likely a way to install your OS, Spectrum Protect (which includes DB2) and from there, there are likely DB2 commands to create the database and catalog it from the existing database files. But I'm not a DBA, so no clue where you'd even start.
     

Share This Page