TSM Database backup and DR restore failures

[anitosam]

Hi,

I am facing issues while trying to restore TSM (DR tests) database at DR location and would appreciate any help.

My TSM server (version - 6.2.3.0) is installed on Aix 6.1. We are in the midst of moving away from tape library to a data domain. The primary site has a mix of tape library and data domain whilst the secondary just has a data domain (Non VTL in a NFS mode).

This is my first ever attempt at a TSM database restore hence I do not know if I missed a step or two. I am listing out details of what I have done:

At the DR location
1. Install TSM version 6.2.3.0
2. configure a new instance: /opt/tivoli/tsm/db2/instance/db2icrt -a SERVER -u tsminst1 tsminst1
db2 update dbm cfg using dftdbpath /home/tsminst1

/opt/tivoli/tsm/server/bin/dsmserv loadformat


3. Create a snapshot database backup to fileclass at the primary location . Full backups generally go to tape device class.

4. Copied the dsmserv.opt,volhist and devconf. Modified the devconf to include only the data domain NFS mounts and removed any references to tapes

5. DataDomain async copies the database and the storage pools to the DataDomain at secondary. I took a snapshot and pointed the same to my new Aix server with mount points similar to that on the primary server. So now I have the database backup and volumes at the remote location

6. Uninstalled the older version of TSM clients which comes default with TSM and installed versions similar to the one at primary.

7. manually setup the /home/tsminst1/sqllib/userprofile file
export DSMI_CONFIG=/home/tsminst1/tsmdbmgr.opt
export DSMI_DIR=/usr/tivoli/tsm/client/api/bin64
export DSMI_LOG=/home/tsminst1


8. Updated dsm.opt,dsm.sys for both api and ba clients, is this step needed?

9. Performed a database recovery which fails:

su - tsminst1
/opt/tivoli/tsm/server/bin/dsmserv -i /home/tsminst1 restore db todate=07/08/2012 totime=13:17:35 source=dbs

:::
:::
ANR7811I Using instance directory /home/tsminst1.
ANR4726I The Async I/O support module has been loaded.
ANR4726I The ICC support module has been loaded.
ANR1636W The server machine GUID changed: old value (), new value (d4.b5.71.c5
.19.c4.11.e1.b6.7a.08.63.0n.72.b4.f7).
ANR8200I TCP/IP Version 4 driver ready for connection with clients on port
1500.
rm: 0653-611 Directory /tsm/tsm_archive_log is not empty.
mkdir: 0653-358 Cannot create /tsm/tsm_archive_log.
/tsm/tsm_archive_log: Do not specify an existing file.
ANR4916I Starting point-in-time database restore snapshot to date 07/18/12
13:17:35.
ANR4620I Database backup series 273 operation 0 device class DD_FILECLASS_DB_B
ACKUP.
ANR8340I FILE volume /tsm/datadomain/db_backup/42613860.DSS mounted.
ANR1363I Input volume /tsm/datadomain/db_backup/42613860.DSS opened (sequence
number 1).
ANR1364I Input volume /tsm/datadomain/db_backup/42613860.DSS closed.
ANR8340I FILE volume /tsm/datadomain/db_backup/42627357.DSS mounted.
ANR1363I Input volume /tsm/datadomain/db_backup/42627357.DSS opened (sequence
number 1).
ANR1364I Input volume /tsm/datadomain/db_backup/42627357.DSS closed.
ANR4638I Restore of backup series 273 operation 0 in progress.
ANR0498W Session 1 refused for SERVERXX because restore DB is in progress.
ANR2969E Database restore terminated. DB2 sqlcode: -2033. DB2 sqlerrmc: 136.


Have I missed any of the steps?

What could be wrong here I checked IBM codes but couldn't find any ref for the sqlerrmc?

To try and fix this error, I even tried running DSMAPIPW on the DR test server but it failed with authentication failure and communication failure -50 tcpip.

I guess it failed because of wrong password as I have never started the instance before I do not know of the current password!

Thanks,
Anito

[zatogo]

My experience in doing this a number of times has been that I need to be able to do a TSM DB backup on the DR server after I've created the initial instance but before I do the db restore...

This includes configuring and setting the tsmdbmgr piece and running set dbrecovery command.

[tsmuser10]

Was this ever resolved ? I too am having a similiar situation in restoring the DB

[tsm_dude]

During your TSM API config did you run tsmapipw and set password to TSMDBMGR ?
Also I typically do these steps unless its a fresh system;

- drop your existing DB on DR (dsmserv removedb tsmdb1)
- cleanup all files etc in your log and archlog dirs

I also ensure volhist has only the tape/file whatever is holding your db backup
and the devconf also just has device holding db backup.
make sure your instance user has the DSMI variables
I`m pretty sure DB2 code 2033 is you havent set the tsmdbmgr password