DB2 and TSM Cross-node recovery

10 January,2011 by Jack Vamvas

To recover/access the backup image of the database that was backed up from a different server. Typically to access production database from dev/qa

 In the following situation :

Assumption 1 -  is that there are 2 servers : MYSERVER1 and MYSERVER2

MYSERVER1 is the source server

MYSERVER2  is the backup server

 Assumption 2 – The tsm client is installed on the server

 Assumption 3  – In the environment variables  of the particular instance if the SET command is issued , there should be the following  3 variables

 

DSMI_CONFIG=/opt/tsm/client/api/bin/dsm_db2.opt

DSMI_DIR=/opt/tsm/client/api/bin

DSMI_LOG=/db2/tsmlog

 

 In the following example , MYSERVER1 has become unavailable

 Step 1 – create an entry in “/opt/tsm/client/ba/bin/dsm.sys”  on MYSERVER2 such as

 SErvername crossnode_mytsmserver_db2

   COMMMethod           TCPip

   TCPPort              1500

   TCPServeraddress      mytsmserver.net

   NODename             MYSERVER1_DB2

*   passwordaccess generate

 

Step 2- adjust the entry in : “/opt/tsm/client/api/bin/dsm.opt” 

SErvername crossnode_ mytsmserver_db2

 Step 3 – from within the db2 instance

 Now we should be able to query any backup image, provided you have the required details.

 db2adutl query db <dbname> password <my_tsm_passwd>

 Appendix 1 -

 

------------------------MYSERVER1 --------START-----------------------------------------------

 

SErvername  mytsmserver

   COMMMethod         TCPip

   TCPPort            1500

   TCPServeraddress   mytsmserver.net

   NODename MYSERVER1

   passwordaccess generate

 

SErvername mytsmserver_db2

   COMMMethod           TCPip

   TCPPort              1500

   TCPServeraddess      mytsmserver.net

   NODename             MYSERVER1_DB2

   passwordaccess generate

------------------------MYSERVER1 --------FINISH-----------------------------------------------

 

-----------------------MYSERVER2 ----------------START----------------------------------------

SErvername  mytsmserver

SCHEDLOGRETENTION 7 D

   COMMMethod         TCPip

   TCPPort            1500

   TCPServeraddress   mytsmserver.net

   NODename MYSERVER2

   passwordaccess generate

 

SErvername mytsmserver_db2

   COMMMethod           TCPip

   TCPPort              1500

   TCPServeraddess      mytsmserver.net

   NODename             MYSERVER2_DB2

   passwordaccess generate

 

-----------------------MYSERVER2 ----------------FINISH----------------------------------------

Read More

TSM backup client configuration for DB2 on Linux - DBA DB2

TSM losing connection with DB2 - DBA DB2

DB2 - SQL2033N and TSM reason code: 610 - DBA DB2

Author: Jack Vamvas(http://www.dba-db2.com)

Share:

Verify your Comment

Previewing your Comment

This is only a preview. Your comment has not yet been posted.

Working...
Your comment could not be posted. Error type:
Your comment has been saved. Comments are moderated and will not appear until approved by the author. Post another comment

The letters and numbers you entered did not match the image. Please try again.

As a final step before posting your comment, enter the letters and numbers you see in the image below. This prevents automated programs from posting comments.

Having trouble reading this image? View an alternate.

Working...

Post a comment on DB2 and TSM Cross-node recovery

Comments are moderated, and will not appear until the author has approved them.


dba-db2.com | DB2 Performance Tuning | DBA DB2:Everything | FAQ | Contact | Copyright