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.

Unable to restore TSM DB

Discussion in 'TSM Database' started by purepoizn, Aug 1, 2012.

  1. purepoizn

    purepoizn New Member

    Joined:
    Nov 2, 2011
    Messages:
    3
    Likes Received:
    0
    Hi all.

    This is my first post, and unfortunately it is because of my TSM server crashing, and I need some assistance. I am trying to restore my TSM DB (running on AIX5.3, TSM5.5.0.0).

    I have the TSM DB backup on a volume, and all the original files that are required: dsmserv.dsk, dsmserv.opt, devconfig and volhist. When I run the command, I get the following error:

    ANR7800I DSMSERV generated at 11:40:24 on Nov 8 2007.

    Tivoli Storage Manager for AIX-RS/6000
    Version 5, Release 5, Level 0.0

    Licensed Materials - Property of IBM

    (C) Copyright IBM Corporation 1990, 2007.
    All rights reserved.
    U.S. Government Users Restricted Rights - Use, duplication or disclosure
    restricted by GSA ADP Schedule Contract with IBM Corporation.

    ANR0900I Processing options file /usr/tivoli/tsm/server/bin/dsmserv.opt.
    ANR7811I Using instance directory /usr/tivoli/tsm/server/bin.
    ANR4726I The ICC support module has been loaded.
    ANR0200I Recovery log assigned capacity is 12988 megabytes.
    ANR0201I Database assigned capacity is 70896 megabytes.
    ANR8200I TCP/IP Version 4 driver ready for connection with clients on port
    1500.
    ANR8840E Unable to open device /dev/smc0 with error 6.
    ANR8418E DEFINE PATH: An I/O error occurred while accessing library IBMLIBR.
    ANR0906I Line No. : 50
    ANR0907I Statement : DEFINE PATH IBM_TSM IBMLIBR SRCTYPE=SERVER
    DESTTYPE=LIBRARY DEVICE=/dev/smc0 ONLINE=YES
    ANR3239E Error 262 while creating device class LTO.

    Can anyone help please, this is a critical server, and I am not sure of what to do next? Nothing has changed on the server, so the Atape drivers, etc should not be a problem here, because TSM was up and running fine, with the exact same config...
     
    Last edited: Aug 1, 2012
  2.  
  3. moon-buddy

    moon-buddy Moderator

    Joined:
    Aug 24, 2005
    Messages:
    6,073
    Likes Received:
    269
    Occupation:
    Electronics Engineer, Security Professional
    Location:
    Somewhere in the US
    As pointed by the errors, check the libary and tape drive paths TO MATCH what you have on the OLD TSM server (the configuration before the crash). If you cannot duplicate this, you have to manually tell TSM where in get the DB files from.

    See this under Storage Manager for AIX, Chapter 4
     
    Last edited: Aug 1, 2012
  4. chad_small

    chad_small Moderator

    Joined:
    Dec 17, 2002
    Messages:
    2,197
    Likes Received:
    43
    Occupation:
    AIX/SAN/TSM
    Location:
    Gilbert, AZ
    If you cant recreate the smc0 device in AIX consider creating a manual library and tape drive definition (along with the path) on the "blank" instance. Save the devconfig. Then run the restore and it will tell you it's waiting for a mount to the manual drive. Then in the library (hopefully your library have web access) you can move the tape to the drive. TSM will see the mount and start the restore. It's a more convoluted way to proceed but can save time if configuring the devices is problematic.
     
  5. purepoizn

    purepoizn New Member

    Joined:
    Nov 2, 2011
    Messages:
    3
    Likes Received:
    0
    Hi Chad. Thanks for the response. I have tried the manual method and it still fails. What is strange is that the devconfig and volhist was backed up just before the crash, and nothing has changed. It does not make sense that the paths or devices do not work. Here is the error I get if I create a manual library with one drive:

    Tivoli Storage Manager for AIX-RS/6000
    Version 5, Release 5, Level 0.0

    Licensed Materials - Property of IBM

    (C) Copyright IBM Corporation 1990, 2007.
    All rights reserved.
    U.S. Government Users Restricted Rights - Use, duplication or disclosure
    restricted by GSA ADP Schedule Contract with IBM Corporation.

    ANR0900I Processing options file /usr/tivoli/tsm/server/bin/dsmserv.opt.
    ANR7811I Using instance directory /usr/tivoli/tsm/server/bin.
    ANR4726I The ICC support module has been loaded.
    ANR0200I Recovery log assigned capacity is 12796 megabytes.
    ANR0201I Database assigned capacity is 283632 megabytes.
    ANR8200I TCP/IP Version 4 driver ready for connection with clients on port
    1500.
    ANR8880W Device type of drive F2R11 in library IBMLIBR was determined to be
    GENERIC_TAPE.
    ANR4621I Database backup device class LTO.
    ANR4622I Volume 1: SO0051L3.
    ANR4630I Starting point-in-time database restore (commit).
    ANR0300I Recovery log format started; assigned capacity 12796 megabytes.
    ANR2032E RESTORE DB: Command failed - internal server error detected.
    ANR9999D Thread<1> issued message 2032 from:
    ANR9999D Thread<1> 0x0000000100013660 outMsgf
    ANR9999D Thread<1> 0x0000000100851798 AdmRestoreDb
    ANR9999D Thread<1> 0x00000001001aac9c admRestoreDatabase
    ANR9999D Thread<1> 0x0000000100005ae0 RestoreDb
    ANR9999D Thread<1> 0x0000000100002c14 main
     
  6. purepoizn

    purepoizn New Member

    Joined:
    Nov 2, 2011
    Messages:
    3
    Likes Received:
    0
    Hi Moon-Buddy....this is still the original config, and should it should still work. I have also tried the manual definition, and it also fails..
     
  7. Harry_Redl

    Harry_Redl Moderator

    Joined:
    Dec 29, 2003
    Messages:
    2,256
    Likes Received:
    134
    Occupation:
    IT Consultant
    Location:
    Czech Republic
    Hi,

    it is just a guess - your drive is discovered as GENERIC TAPE (not LTO) - this is usually problem with the wrong device driver used.
    Another thing is, that 5.5.0.0 is full of strange bugs. Maybe you can install higher version of TSM (5.5.6?) and try to restore the DB - after that you have to run "dsmserv upgradedb"

    Harry
     

Share This Page