not taking the tape!! 2

[BACKUPS2425]

Hi all,

we are backing oracle database... so the problem is this that since 4-5 days we are running the backing and its not taking the tape??? before its was happening successfully but dont know why not taking the tape??? see error below:
-----------------------------------------
11/25/08 13:58:07 nsrd: savegroup info: starting Oracle_App1 (with 1 client(s))
11/25/08 13:58:40 nsrd: media info: suggest mounting 000056 on kapttapp1 for writing to pool 'OracleApp1'
11/25/08 13:58:40 nsrd: media waiting event: Waiting for 1 writable volumes to backup pool 'OracleApp1' tape(s) on kapttapp1
11/25/08 13:58:41 nsrd: media info: loading volume 000056 into rd=kapttapp1:/dev/rmt/4n
11/25/08 13:58:56 nsrd: rd=kapttapp1:/dev/rmt/4n 1:Verify label operation in progress
11/25/08 13:59:03 nsrd: media warning: rd=kapttapp1:/dev/rmt/4n reading: read open error: drive status is
11/25/08 13:59:03 nsrd: rd=kapttapp1:/dev/rmt/4n 1:Eject operation in progress
11/25/08 13:59:43 nsrd: Jukebox 'KA_JB1' failed: expected volume '000056' got 'NULL'.

I am sure there is no problem with tape cartridge because i have changed the tape 3 times ...

please help me.

 

[denisfr]

Hello,

check the order of the drives (take a look at the drive when it mounts the tape in order to see if it is the correct one) and/or the synchronization between NW tape database and your jukebox (nsrjb -IIv or nsrjb -Iv).

I had this kind of problem when NW ask the jukebox to mount a tape, but the tape was not in the right slot, so the jukebox mounts the tape which was on the slot indicated and it was unlabeled (NULL tape name).

Hope this helps.

 

[605]

We do not know what's happening here but talking in general there are several potential issues:
- in a DDS setup, the block size could be different when sharing the drive between storage nodes of different OS.
However, as NW labels are always written with a 32KB block size, this cannot be the issue.
- You load a media into the drive which has been written with a higher density than the reading drive supports.
- You simply load the wrong drive.
No idea how this can happen but my strong guess is that this is the problem.

To check this,
- Load the media into the jukebox drive of your choice.
- Then run "mt -f drive status" for each jukebox drive.
This should return the found block size only on the loaded drive.
- Run "scanner -n -mv device" to verify that the tape can be read.

 

[a060463xyz]

You should post your configuration.
run an inquire and post the output