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.

Crash when attempting to restore the Tivoli Storage Manager database

Discussion in 'Restore / Recovery Discussion' started by rischard, Nov 28, 2012.

  1. rischard

    rischard New Member

    Joined:
    Jul 18, 2003
    Messages:
    31
    Likes Received:
    0
    Hello world,
    our environment:
    TSM 5.5.6 on Windows2008 R2
    IBMTape.x64_w08_6233 drivers installed
    Adaptec SCSI Card 29320LP (installed most recent version of drivers: Ultra320 SCSI Driver v7.00.00.12 for Windows 7 & Server 2008R2)
    IBM TS3100 Tape Library - LTO Ultrium 4

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\adpu320\Parameters\Device
    MaximumSGList =dword:0x00000041 (decimal 65)
    I've also ran DSMMAXSG utility to set the MaximumSGList value to 0x41(65) for all HBAs.


    I'my trying to restore TSM DB backed up on tape volume by our previous TSM 5.5.4 (this previous server crashed and we have only tape volumes available). Output of tsm trace log during restore operation:
    10:15:05.698 [12][psntpop.c][1757][]:pvrPsTape GET_TAPE_DRIVE_INFORMATION, maxblocksize 65536
    10:15:05.698 [12][pvrntp.c][1194][]:Opening NTP Volume 123456L4 blocksize=0, Drive DRIVE01 (mt4.0.0.4) maxblocksize=65536.
    10:15:05.698 [12][pvrntp.c][1242][]:Using the NoCopy method (False) with RS = 0 and BS = 0, PVR's blockSize = 32768.
    ...
    10:15:05.714 [12][pvrntp.c][7006][]:Fetching block 5 from NTP drive DRIVE01 (mt4.0.0.4)
    10:15:05.729 [12][pspvr.c][2899][]:ReadFile failed with error code 234 read 32768
    10:15:05.729 [12][pstapiop.c][633][]:pvrPsErr entry, op=R, flag1=0, flag2=0, ErrorCode=234

    I've taken the necessary steps by http://www-01.ibm.com/support/docview.wss?uid=swg21321897 but the result is the same.

    I did database backup to tape on our current TSM 5.5.6. Data are backed up with blockSize=32768. This is output of tsm trace log:
    11:58:32.205 [15][psntpop.c][1757][]:pvrPsTape GET_TAPE_DRIVE_INFORMATION, maxblocksize 65536
    11:58:32.205 [15][pvrntp.c][1194][]:Opening NTP Volume 654321L4 blocksize=0, Drive DRIVE01 (mt4.0.0.4) maxblocksize=65536.
    11:58:32.205 [15][pvrntp.c][1242][]:Using the NoCopy method (False) with RS = 0 and BS = 0, PVR's blockSize = 32768.

    Which more parameters do I have to set if I don't want to write to tape/read from tape with blocksize=32768 but blocksize=65536?


    Many thanks for your responses.
     
  2.  
  3. moon-buddy

    moon-buddy Moderator

    Joined:
    Aug 24, 2005
    Messages:
    6,177
    Likes Received:
    277
    Occupation:
    Electronics Engineer, Security Professional
    Location:
    Somewhere in the US
    Let me get this straight.

    You are trying to restore version 5.5.4 on a TSM server that is on version 5.5.6?

    If I recall correctly, you will hit this bump on the road. The sub-level difference may throw off compatibility issues.
     
  4. rischard

    rischard New Member

    Joined:
    Jul 18, 2003
    Messages:
    31
    Likes Received:
    0
    Hi moon-buddy,
    TSM Windows Administrator’s Guide says in chapter Moving the IBM Tivoli Storage Manager Server:
    The prerequisites for the backup and restore method are:
    The restore operation must be done by a IBM Tivoli Storage Manager server at a code level that is the same as or later than that on the machine that was backed up.

    As I mention above I think the problem will be in blocksize incompatibility between old tsm read/write operations on tape volume and new tsm read/write operations.
     
  5. moon-buddy

    moon-buddy Moderator

    Joined:
    Aug 24, 2005
    Messages:
    6,177
    Likes Received:
    277
    Occupation:
    Electronics Engineer, Security Professional
    Location:
    Somewhere in the US
    Threre you go - there is no control on how to change the block size for read/write operation that I know of.
     
  6. rischard

    rischard New Member

    Joined:
    Jul 18, 2003
    Messages:
    31
    Likes Received:
    0
    We found an interesting article http://************/sit-3.63/portal/kbarticle.php?id=54
    Therefore the tsm 5.5.4 database had to be backed up with set blocksize=32768. But the operation system was Windows 2003 at that time and it's Windows 2008 R2 now. The prerequisitie "The same operating system must be running on both machines" is not satisfied. I'll try to restore db on server with Windows 2003.
     

Share This Page