backup db in wrong volume

[danieleinfn]

Hi,
I try to backup db in 3 volumes but tsm server (6.1.2) uses different tape, before I give:

set dbrecovery DB_CLASS
ANR2782I SET DBRECOVERY completed successfully and device class for automatic
DB backup is set to DB_CLASS.

then:


backup db devclass=DB_CLASS type=full volumenames=EL3506,EL3508,EL3509 scratch=no
ANR2280I Full database backup started as process 5.
ANS8003I Process number 5 started.


I want to use EL3506,EL3508,EL3509 but... from console mode I see that this operation is performed on tape EL2273:

ANR2017I Administrator ADMIN issued command: BACKUP DB devclass=DB_CLASS
type=full volumenames=EL3506,EL3508,EL3509 scratch=no
ANR4559I Backup DB is in progress.
ANR0984I Process 5 for DATABASE BACKUP started in the BACKGROUND at 01:59:24
PM.
ANR2280I Full database backup started as process 5.
ANR0406I Session 61 started for node TSM-SERVER-2-CLIENT (DB2/LINUXX8664)
(Tcp/Ip tsm-server-2.cr.cnaf.infn.it(59709)).
ANR0511I Session 61 opened output volume EL2273.
ANR0407I Session 62 started for administrator ADMIN (Linux86) (Tcp/Ip
ds-07-10.cr.cnaf.infn.it(53535)).
ANR2017I Administrator ADMIN issued command: QUERY PATH
ANR0405I Session 62 ended for administrator ADMIN (Linux86).
ANR0514I Session 61 closed volume EL2273.
ANR0403I Session 61 ended for node TSM-SERVER-2-CLIENT (DB2/LINUXX8664).
ANR0406I Session 63 started for node TSM-SERVER-2-CLIENT (DB2/LINUXX8664)
(Tcp/Ip tsm-server-2.cr.cnaf.infn.it(59710)).
ANR0511I Session 63 opened output volume EL2273.
ANR0514I Session 63 closed volume EL2273.
ANR0403I Session 63 ended for node TSM-SERVER-2-CLIENT (DB2/LINUXX8664).
ANR0406I Session 64 started for node TSM-SERVER-2-CLIENT (DB2/LINUXX8664)
(Tcp/Ip tsm-server-2.cr.cnaf.infn.it(59711)).
ANR0403I Session 64 ended for node TSM-SERVER-2-CLIENT (DB2/LINUXX8664).
ANR0406I Session 65 started for node TSM-SERVER-2-CLIENT (DB2/LINUXX8664)
(Tcp/Ip tsm-server-2.cr.cnaf.infn.it(59712)).
ANR0403I Session 65 ended for node TSM-SERVER-2-CLIENT (DB2/LINUXX8664).
ANR0406I Session 66 started for node TSM-SERVER-2-CLIENT (DB2/LINUXX8664)
(Tcp/Ip tsm-server-2.cr.cnaf.infn.it(59713)).
ANR0403I Session 66 ended for node TSM-SERVER-2-CLIENT (DB2/LINUXX8664).
ANR0406I Session 67 started for node TSM-SERVER-2-CLIENT (DB2/LINUXX8664)
(Tcp/Ip tsm-server-2.cr.cnaf.infn.it(59714)).
ANR0403I Session 67 ended for node TSM-SERVER-2-CLIENT (DB2/LINUXX8664).
ANR0406I Session 68 started for node TSM-SERVER-2-CLIENT (DB2/LINUXX8664)
(Tcp/Ip tsm-server-2.cr.cnaf.infn.it(59715)).
ANR0403I Session 68 ended for node TSM-SERVER-2-CLIENT (DB2/LINUXX8664).
ANR0406I Session 69 started for node TSM-SERVER-2-CLIENT (DB2/LINUXX8664)
(Tcp/Ip tsm-server-2.cr.cnaf.infn.it(59716)).
ANR0403I Session 69 ended for node TSM-SERVER-2-CLIENT (DB2/LINUXX8664).
ANR0406I Session 70 started for node TSM-SERVER-2-CLIENT (DB2/LINUXX8664)
(Tcp/Ip tsm-server-2.cr.cnaf.infn.it(59717)).
ANR0403I Session 70 ended for node TSM-SERVER-2-CLIENT (DB2/LINUXX8664).
ANR0406I Session 71 started for node TSM-SERVER-2-CLIENT (DB2/LINUXX8664)
(Tcp/Ip tsm-server-2.cr.cnaf.infn.it(59718)).
ANR0403I Session 71 ended for node TSM-SERVER-2-CLIENT (DB2/LINUXX8664).
ANR0406I Session 72 started for node TSM-SERVER-2-CLIENT (DB2/LINUXX8664)
(Tcp/Ip tsm-server-2.cr.cnaf.infn.it(59719)).
ANR0403I Session 72 ended for node TSM-SERVER-2-CLIENT (DB2/LINUXX8664).
ANR0406I Session 73 started for node TSM-SERVER-2-CLIENT (DB2/LINUXX8664)
(Tcp/Ip tsm-server-2.cr.cnaf.infn.it(59720)).
ANR0403I Session 73 ended for node TSM-SERVER-2-CLIENT (DB2/LINUXX8664).
ANR0406I Session 74 started for node TSM-SERVER-2-CLIENT (DB2/LINUXX8664)
(Tcp/Ip tsm-server-2.cr.cnaf.infn.it(59721)).
ANR0403I Session 74 ended for node TSM-SERVER-2-CLIENT (DB2/LINUXX8664).
ANR0406I Session 75 started for node TSM-SERVER-2-CLIENT (DB2/LINUXX8664)
(Tcp/Ip tsm-server-2.cr.cnaf.infn.it(59722)).
ANR0403I Session 75 ended for node TSM-SERVER-2-CLIENT (DB2/LINUXX8664).
ANR0406I Session 76 started for node TSM-SERVER-2-CLIENT (DB2/LINUXX8664)
(Tcp/Ip tsm-server-2.cr.cnaf.infn.it(59723)).
ANR0403I Session 76 ended for node TSM-SERVER-2-CLIENT (DB2/LINUXX8664).
ANR0406I Session 77 started for node TSM-SERVER-2-CLIENT (DB2/LINUXX8664)
(Tcp/Ip tsm-server-2.cr.cnaf.infn.it(59724)).
ANR0403I Session 77 ended for node TSM-SERVER-2-CLIENT (DB2/LINUXX8664).
ANR0406I Session 78 started for node TSM-SERVER-2-CLIENT (DB2/LINUXX8664)
(Tcp/Ip tsm-server-2.cr.cnaf.infn.it(59725)).
ANR0403I Session 78 ended for node TSM-SERVER-2-CLIENT (DB2/LINUXX8664).
ANR0406I Session 79 started for node TSM-SERVER-2-CLIENT (DB2/LINUXX8664)
(Tcp/Ip tsm-server-2.cr.cnaf.infn.it(59726)).
ANR0403I Session 79 ended for node TSM-SERVER-2-CLIENT (DB2/LINUXX8664).
ANR0406I Session 80 started for node TSM-SERVER-2-CLIENT (DB2/LINUXX8664)
(Tcp/Ip tsm-server-2.cr.cnaf.infn.it(59727)).
ANR0403I Session 80 ended for node TSM-SERVER-2-CLIENT (DB2/LINUXX8664).
ANR0406I Session 81 started for node TSM-SERVER-2-CLIENT (DB2/LINUXX8664)
(Tcp/Ip tsm-server-2.cr.cnaf.infn.it(59728)).
ANR0403I Session 81 ended for node TSM-SERVER-2-CLIENT (DB2/LINUXX8664).
ANR4550I Full database backup (process 5) completed.
ANR0985I Process 5 for DATABASE BACKUP running in the BACKGROUND completed with
completion state SUCCESS at 02:02:04 PM.

This volume is defined with a different device class as I can see:

q vol EL2273 f=D

Volume Name: EL2273
Storage Pool Name: BABAR_POOL
Device Class Name: 9940B_CLASS
Estimated Capacity: 200.0 G
Scaled Capacity Applied:
Pct Util: 6.3
Volume Status: Filling
Access: Read/Write
Pct. Reclaimable Space: 0.0
Scratch Volume?: Yes
In Error State?: No
Number of Writable Sides: 1
Number of Times Mounted: 6
Write Pass Number: 1
Approx. Date Last Written: 09/21/2009 14:02:01
Approx. Date Last Read: 09/21/2009 13:26:44
Date Became Pending:
Number of Write Errors: 0
Number of Read Errors: 0
Volume Location:
Volume is MVS Lanfree Capable : No
Last Update by (administrator):
Last Update Date/Time: 09/21/2009 13:24:06
Begin Reclaim Period:
End Reclaim Period:
Drive Encryption Key Manager:


What I have to do to backup db in right volumes ?

Thanks

 

[Samuel]

Hello,

It's normal because you have scratch=no!!

For a database you need a scratch tapes, you can use your command but with this option scratch=yes.

It's possible than your backup db don't used all tapes, it depend of the tail of your tapes.

 

[danieleinfn]

Hi Samuel,
I have the same problem with scratch=yes, I see also that I have two device class for the same device: DB_CLASS and 9940B_CLASS, when backup starts TSM uses always the 9940B_CLASS after backup db command:

>q mo
ANR8379I Mount point in device class 9940B_CLASS is waiting for the volume
mount to complete, status: WAITING FOR VOLUME.
ANR8334I 1 matches found.


also if I write dev=db_class in backup command. Why it use "Mount point in device class 9940B_CLASS" ?

 

[wim]

Hi,

your actlog states
ANR0406I Session 61 started for node TSM-SERVER-2-CLIENT (DB2/LINUXX8664)
ANR0511I Session 61 opened output volume EL2273.

So it is TSM-SERVER2-CLIENT which is using volume EL2273 for its regular backup/archive.
There is NO TSM server database backup on EL2273.
If there was a TSM database volume on EL2273 the command 'q vol' would list nothing.

To view your volumes holding the TSM database backup issue 'q volhist type=dbb' or 'q libv'.

Regards. Wim.

 

[Samuel]

Hello,

Change your volume names, select other volume where status=scratch.
Use this command on your library :
select volume_name from libvolumes where status='Scratch' and volume_name like 'EL%' and after you can choice few volumes with status=scratch

 

[Harry_Redl]

Hi,

IMHO you have problem with your API configuration. When running DB backup in TSM 6.1.x you use TSM API and (by default) tsmdbmgr.opt file located in server instance directory (it defines $$_TSMDBMGR_$$ node and this node is used to backup your DB)
Seems your API configuration (enviromental variables?) is pointed to different .opt file with defined node TSM-SERVER-2-CLIENT.
This node is bound to management class which directs its backup to another devclass and as it is now considered as "normal backup", it goes to normal volumes - not DB Backup volumes.
It is a nice error

Harry

 

[danieleinfn]

Hy Harry_redl, I think you are right, from my /etc/profile I have:

export DSMI_LOG=/home/db2inst1/log
#export DSMI_DIR=/opt/tivoli/tsm/client/api/bin64/
export DSMI_DIR=/opt/tivoli/tsm/client/ba/bin
#export DSMI_CONFIG=/home/db2inst1/dsmserv.opt
export DSMI_CONFIG=/opt/tivoli/tsm/client/ba/bin/dsm.opt


and tsm-server-2-client is a node registred to tsm server.

please can you show me some examples of /home/db2inst1/dsmserv.opt , /opt/tivoli/tsm/client/api/bin64/dsm.opt and
/opt/tivoli/tsm/client/api/bin64/dsm.sys file ?

I have read:

http://publib.boulder.ibm.com/infoc...bm.itsm.srv.install.doc/t_srv_prep_dbmgr.html

point 4 but I have some trouble.

Thanks.

 

[Harry_Redl]

Hi,

this API configuration is a bit tricky - I had to follow "manual instance creation" steps to make DB backup work and it is prone to breaking when you install/upgrade client API.

My configuration files are (almost) exactly the same as in the docs:

/home/tsminst1/dsmserv.opt:

COMMmethod TCPIP
tcpport 1500
volumehistory /home/tsminst1/volhist.out

/home/tsminst1/tsmdbmgr.opt:

SERVERNAME TSMDBMGR_TSMINST1

/opt/tivoli/tsm/client/api/bin64/dsm.sys:

*Servername server_a
*COMMMethod TCPip
*TCPPort 1500
*TCPServeraddress node.domain.company.COM

servername TSMDBMGR_TSMINST1
commmethod tcpip
tcpserveraddr localhost
tcpport 1500
passwordaccess generate
passworddir /home/tsminst1/tsminst1
errorlogname /home/tsminst1/tsminst1/tsmdbmgr.log
nodename $$_TSMDBMGR_$$

I have no /opt/tivoli/tsm/client/api/bin64/dsm.opt right now - for DB backup /home/tsminst1/tsmdbmgr.opt should be used.

Hope it helps

Harry

 

[danieleinfn]

yes, it works fine, thank!