Results 1 to 6 of 6
  1. #1
    Newcomer
    Join Date
    Apr 2005
    Posts
    3
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Default 6.1 restore db procedure

    I'm trying to restore a tsm 6.1 database and I must be missing a step. Thought I'd throw this out there before I call IBM. Here's what I've been able to glean from the manual.
    1 install OS (windows 2003 x64) disable UAC - reboot
    2 install TSM
    3 reboot and log back in with db2user1 account created during tsm install
    4 run dsmicfgx and create a new tsm instance
    5 stop the windows services for the tsm instance and db2 instance
    6 open the db2 command line processor and quit to a command prompt
    7 db2idrop server1
    8 remove all files from the d:\tsm\db, log, etc directories (and the d:\server1 directory??)
    9 restore the volhist, dsmserv.opt, devconfig.out files to d:\tsm\server1
    10 create a text file dbdir.txt with database paths "d:\tsm\db"
    11 from the server1 directory run "c:\program files\tivoli\tsm\server\dsmserv" restore db on=dbdir.txt

    ANR0900I Processing options file D:\tsm\server1\dsmserv.opt.
    ANR7800I DSMSERV generated at 17:36:33 on Mar 13 2009.

    Tivoli Storage Manager for Windows
    Version 6, Release 1, Level 0.0

    Licensed Materials - Property of IBM

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

    ANR4726I The ICC support module has been loaded.
    ANR1636W The server machine GUID changed: old value (), new value (bf.27.cf.10-
    .39.8e.11.de.87.6a.00.15.5d.00.f4.00).
    ANR8200I TCP/IP Version 4 driver ready for connection with clients on port
    1500.
    ANR4654I The restore db to most current time can not be done since contents of
    the active or archive log directories have been changed. The DB will be
    restored to the last full or full plus incremental state.
    ANR4620I Database backup series 346 operation 0 device class FILECLASS.
    ANR8340I FILE volume D:\TSM\FILES\41101073.DBV mounted.
    ANR1363I Input volume D:\TSM\FILES\41101073.DBV opened (sequence number 1).
    ANR1364I Input volume D:\TSM\FILES\41101073.DBV closed.
    ANR8340I FILE volume D:\TSM\FILES\41101734.DBV mounted.
    ANR1363I Input volume D:\TSM\FILES\41101734.DBV opened (sequence number 1).
    ANR1364I Input volume D:\TSM\FILES\41101734.DBV closed.
    ANR8340I FILE volume D:\TSM\FILES\41101419.DBV mounted.
    ANR1363I Input volume D:\TSM\FILES\41101419.DBV opened (sequence number 2).
    ANR1364I Input volume D:\TSM\FILES\41101419.DBV closed.
    ANR4638I Restore of backup series 346 operation 0 in progress.
    ANR2969E Database restore terminated. DB2 sqlcode: -2033. DB2 sqlerrmc: 406.
    ANR1794W TSM SAN discovery is disabled by options.

    I'll gladly RTFM if someone would point me to TFM. I found the information on the "on=dbdir.txt" parameter in the docs for moving the database. Running dsmicfgx is just a guess. It seems to get farther along...

    BTW The webcast mentions a database upgrade guide several times. Anybody know where to find it? Thanks for any help.

  2. #2
    Moderator Harry_Redl's Avatar
    Join Date
    Dec 2003
    Location
    Czech Republic
    Posts
    2,208
    Thanks
    3
    Thanked 98 Times in 97 Posts

  3. #3
    Member
    Join Date
    Feb 2007
    Posts
    7
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Default

    Hi,

    Im getting the same error? were you able to sort your issue out?

  4. #4
    Newcomer
    Join Date
    Apr 2005
    Posts
    3
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Default Resolved

    The answer is in the docs. Unfortunately it's spread out in about 5 different locations.

    Run dsmicfgx and create a new tsm instance. This will create some configuration files we needed for the restore (tsmdbmgr.env tsmdbmgr.opt)
    Open the db2 command line processor and quit to a command prompt
    net stop “tsm server1”
    net stop "DB2 - DB2TSM1 - SERVER1"
    db2idrop Server1
    db2icrt -u db2user1 Server1
    set DB2INSTANCE=Server1
    db2set -i server1 DB2_VENDOR_INI=d:\tsm\server1\tsmdbmgr.env
    db2stop
    db2start
    set DSMI_CONFIG=d:\tsm\server1\tsmdbmgr.opt
    “c:\program files\tivoli\tsm\server\dsmsutil.exe” UPDATEPW /NODE:$$_TSMDBMGR_$$ /PASSWORD:TSMDBMGR /VALIDATE:NO
    A bogus directory is created during the initial instance creation. Remove these files (\server1 in root of any drive).
    Remove all files from the d:\tsm\db, log and archlog KEEP files in d:\tsm\server1
    Restore/replace the volhist.out, dsmserv.opt, devconfig.out files to d:\tsm\server1
    Create a text file dbdir.txt with database paths "d:\tsm\db"
    From the server1 directory run "c:\program files\tivoli\tsm\server\dsmserv" restore db on=dbdir.txt

  5. #5
    Member
    Join Date
    Feb 2007
    Posts
    7
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Default

    Thanks, it worked!!

  6. #6
    Member
    Join Date
    Mar 2009
    Posts
    14
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Default Combine Volhist 5.3.6 and Volhist 6.1

    Stevehess,

    I have TSM 5.3.6 and TSM 6.1 servers in Production. As TSM 5.3.6 will decommission very soon. How can I combine both database into TSM 6.1 server?

    Please advice

    Quote Originally Posted by stevehess View Post
    The answer is in the docs. Unfortunately it's spread out in about 5 different locations.

    Run dsmicfgx and create a new tsm instance. This will create some configuration files we needed for the restore (tsmdbmgr.env tsmdbmgr.opt)
    Open the db2 command line processor and quit to a command prompt
    net stop “tsm server1”
    net stop "DB2 - DB2TSM1 - SERVER1"
    db2idrop Server1
    db2icrt -u db2user1 Server1
    set DB2INSTANCE=Server1
    db2set -i server1 DB2_VENDOR_INI=d:\tsm\server1\tsmdbmgr.env
    db2stop
    db2start
    set DSMI_CONFIG=d:\tsm\server1\tsmdbmgr.opt
    “c:\program files\tivoli\tsm\server\dsmsutil.exe” UPDATEPW /NODE:$$_TSMDBMGR_$$ /PASSWORD:TSMDBMGR /VALIDATE:NO
    A bogus directory is created during the initial instance creation. Remove these files (\server1 in root of any drive).
    Remove all files from the d:\tsm\db, log and archlog KEEP files in d:\tsm\server1
    Restore/replace the volhist.out, dsmserv.opt, devconfig.out files to d:\tsm\server1
    Create a text file dbdir.txt with database paths "d:\tsm\db"
    From the server1 directory run "c:\program files\tivoli\tsm\server\dsmserv" restore db on=dbdir.txt

Similar Threads

  1. TSM upgrade from 5.3.4 to 5.5 Procedure
    By rlopezlo in forum TSM Server
    Replies: 6
    Last Post: 07-23-2008, 08:57 AM
  2. Extend and DSMFT procedure
    By tsmhelum in forum Performance Tuning
    Replies: 1
    Last Post: 08-25-2006, 04:15 AM
  3. START / STOP Procedure
    By ReneM in forum Backup / Archive Discussion
    Replies: 6
    Last Post: 07-18-2006, 09:20 AM
  4. weird backup procedure
    By toneysamuel in forum TSM Server
    Replies: 1
    Last Post: 10-02-2005, 11:17 AM
  5. Successful DR Test - My Procedure
    By mikeymac in forum Backup / Archive Discussion
    Replies: 0
    Last Post: 06-02-2004, 05:14 PM

Tags for this Thread

Posting Permissions

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