Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations biv343 on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

backup db in wrong volume

Status
Not open for further replies.

Danieleinfn

Technical User
Aug 16, 2007
5
IT
Hi,
I try to backup db in 3 volumes but tsm server 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
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top