Failure for a DB2 Lan free backup

sunny19

ADSM.ORG Member
Joined
Jan 6, 2010
Messages
66
Reaction score
0
Points
0
PREDATAR Control23

Hi,

We are getting an error as follows for a DB2 backup

SQL2025N An I/O error "12" occurred on media "TSM".


When i checked in the activity log on TSM server, It says


Storage Inaccessible and also when backup is started then when i give the following command


STA_nodename:q mo(It gives waiting for mount point but no volumes are being mounted)


Another error i am seeing in the error log is


05/14/10 14:30:23 ANR8779E (Session: 60684, Origin: STA_nodename) Unable to
open drive /dev/rmt23, error number=23. (SESSION: 60684)
05/14/10 14:30:29 ANR8779E (Session: 60684, Origin: STA_nodename) Unable to
open drive /dev/rmt100, error number=70. (SESSION: 60684)
05/14/10 14:30:36 ANR8779E (Session: 60684, Origin: STA_nodename) Unable to
open drive /dev/rmt106, error number=70. (SESSION: 60684)
05/14/10 14:30:38 ANR8779E (Session: 60684, Origin: STA_nodename) Unable to
open drive /dev/rmt50, error number=16. (SESSION: 60684)




Please help....
 
PREDATAR Control23

is the OS AIX? Check your OS if they are still seeing the rmt devices. Also, check your TSM server for path and drives availability. Check for scratch tapes too. If your data_write_path is set to ANY which you can see from q node nodename f=d, then the backup should go over LAN is lan-free failed. But, if the device error is there even in lan backup, the problem is with devices.
 
PREDATAR Control23

You need to be current on TSM server software, as well as the atape device driver.

Those errnos are sort of meaningless, other than the 16. This is likely stuff going wrong at the device layer, however there were problems within TSM which could cause this type of behavior, or make it worse.
 
PREDATAR Control23

Thanks Sandeep and wildwest,

I can see all the tape devices in Available state. LAN-Free backup is configured fine and we tested LAN-Free for a filesystem backup and it ran fine...Now on TSM server even migrations are failing with the following error.

05/16/10 10:30:07 ANR8779E Unable to open drive /dev/rmt37, error number=59.
(SESSION: 5357, PROCESS: 191)
05/16/10 10:30:09 ANR8779E Unable to open drive /dev/rmt127, error
number=64. (SESSION: 5359, PROCESS: 192)
05/16/10 10:30:09 ANR8779E Unable to open drive /dev/rmt54, error number=65.
(SESSION: 5355, PROCESS: 193)
05/16/10 10:30:10 ANR0513I Process 193 opened output volume 300310L3.
(SESSION: 5355, PROCESS: 193)
05/16/10 10:30:10 ANR8779E Unable to open drive /dev/rmt27, error number=66.
(SESSION: 5361, PROCESS: 189)
05/16/10 10:30:10 ANR8779E Unable to open drive /dev/rmt26, error number=61.
(SESSION: 5356, PROCESS: 190)
05/16/10 10:30:22 ANR8779E Unable to open drive /dev/rmt36, error number=68.
(SESSION: 5360, PROCESS: 194)
05/16/10 10:31:02 ANR8779E Unable to open drive /dev/rmt82, error number=72.
(SESSION: 5237, PROCESS: 183)
05/16/10 10:36:10 ANR8779E Unable to open drive /dev/rmt98, error number=65.
 
PREDATAR Control23

did u seen the path and drive showing online? if they are showing online, try re-defining them. Try running cfgmgr in AIX to re-scan the devices.
 
PREDATAR Control23

did u seen the path and drive showing online? if they are showing online, try re-defining them. Try running cfgmgr in AIX to re-scan the devices.
We did redefine all the drives and i ran cfgmgr too and now the good new is i see LAN-Free backup running fine but when i run the migrations for a storage pool on my TSM server its not able to mount the volume.

As an FYI,

We use VTL not a real Tape library.
 
Top