Error 84 and 41

[Zahid_Haseeb]

I have recently pluged in new Tape Library. I moved all my tapes cartridges from previous Tape Library to the new Tape Library. All Tape Cartridges was workling fine on the old Tape Library but i am facing the below issues on the new Tape Library. See the below snap and Activity Monitor for reference

Environment

Netbackup 7.1 with OS win2008

Netbackup Client 7.1 and also on some machine 6.5.0

Snap of Activity Monitor

Activity Monitor for error 84

4/17/2011 5:35:41 PM - Info nbjm(pid=2740) starting backup job (jobid=167) for client DB-Cluster, policy DotnetDB-Live-Full-Diff, schedule Default-Application-Backup 

4/17/2011 5:35:41 PM - Info nbjm(pid=2740) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=167, request id:{0B0AD0FD-1833-4951-BD59-6AA540B4C2D5}) 

4/17/2011 5:35:41 PM - requesting resource VeritasNBU-hcart-robot-tld-0

4/17/2011 5:35:41 PM - requesting resource VeritasNBU.NBU_CLIENT.MAXJOBS.DB-Cluster

4/17/2011 5:35:41 PM - requesting resource VeritasNBU.NBU_POLICY.MAXJOBS.DotnetDB-Live-Full-Diff

4/17/2011 5:35:41 PM - granted resource VeritasNBU.NBU_CLIENT.MAXJOBS.DB-Cluster

4/17/2011 5:35:41 PM - granted resource VeritasNBU.NBU_POLICY.MAXJOBS.DotnetDB-Live-Full-Diff

4/17/2011 5:35:41 PM - granted resource 3144L1

4/17/2011 5:35:41 PM - granted resource IBM.ULT3580-TD5.001

4/17/2011 5:35:41 PM - granted resource VeritasNBU-hcart-robot-tld-0

4/17/2011 5:35:41 PM - estimated 0 Kbytes needed

4/17/2011 5:35:41 PM - Info nbjm(pid=2740) started backup job for client DB-Cluster, policy DotnetDB-Live-Full-Diff, schedule Default-Application-Backup on storage unit VeritasNBU-hcart-robot-tld-0

4/17/2011 5:35:41 PM - started process bpbrm (5328)

4/17/2011 5:35:42 PM - Info bpbrm(pid=5328) DB-Cluster is the host to backup data from    

4/17/2011 5:35:42 PM - Info bpbrm(pid=5328) reading file list from client       

4/17/2011 5:35:42 PM - connecting

4/17/2011 5:35:44 PM - Info bpbrm(pid=5328) listening for client connection        

4/17/2011 5:35:51 PM - Info bpbrm(pid=5328) INF - Client read timeout = 300     

4/17/2011 5:35:51 PM - Info bpbrm(pid=5328) accepted connection from client        

4/17/2011 5:35:51 PM - Info bphdb(pid=6672) Backup started          

4/17/2011 5:35:51 PM - Info bptm(pid=6068) start           

4/17/2011 5:35:51 PM - Info bptm(pid=6068) using 65536 data buffer size       

4/17/2011 5:35:51 PM - connected; connect time: 00:00:09

4/17/2011 5:35:53 PM - Info bptm(pid=6068) setting receive network buffer to 263168 bytes     

4/17/2011 5:35:53 PM - Info bptm(pid=6068) using 30 data buffers        

4/17/2011 5:35:53 PM - Info bptm(pid=6068) start backup          

4/17/2011 5:35:56 PM - Info bptm(pid=6068) backup child process is pid 5936.5460      

4/17/2011 5:35:56 PM - Info bptm(pid=5936) start           

4/17/2011 5:35:59 PM - Info bptm(pid=6068) media id 3144L1 mounted on drive index 1, drivepath {4,0,2,0}, drivename IBM.ULT3580-TD5.001, copy 1

4/17/2011 5:35:59 PM - mounted

4/17/2011 5:35:59 PM - positioning 3144L1 to file 64

4/17/2011 5:38:24 PM - Error bptm(pid=6068) allow overwrite operation failed to media id 3144L1, drive index 1, address 3139778

4/17/2011 5:38:24 PM - Info bptm(pid=6068) EXITING with status 84 <----------       

4/17/2011 5:38:26 PM - end writing

media write error(84)

4/17/2011 5:38:31 PM - Info bphdb(pid=6672) done. status: 84: media write error  

Activity Monitor for error 41

4/17/2011 5:14:19 PM - Info nbjm(pid=2740) starting backup job (jobid=163) for client DB-Cluster, policy DotnetDB-Live-Full-Diff, schedule Default-Application-Backup 

4/17/2011 5:14:19 PM - Info nbjm(pid=2740) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=163, request id:{1AB4059D-0BE7-4775-84E8-B9983C54583F}) 

4/17/2011 5:14:19 PM - requesting resource VeritasNBU-hcart-robot-tld-0

4/17/2011 5:14:19 PM - requesting resource VeritasNBU.NBU_CLIENT.MAXJOBS.DB-Cluster

4/17/2011 5:14:19 PM - requesting resource VeritasNBU.NBU_POLICY.MAXJOBS.DotnetDB-Live-Full-Diff

4/17/2011 5:14:19 PM - granted resource VeritasNBU.NBU_CLIENT.MAXJOBS.DB-Cluster

4/17/2011 5:14:19 PM - granted resource VeritasNBU.NBU_POLICY.MAXJOBS.DotnetDB-Live-Full-Diff

4/17/2011 5:14:19 PM - granted resource 3144L1

4/17/2011 5:14:19 PM - granted resource IBM.ULT3580-TD5.001

4/17/2011 5:14:19 PM - granted resource VeritasNBU-hcart-robot-tld-0

4/17/2011 5:14:19 PM - estimated 0 Kbytes needed

4/17/2011 5:14:19 PM - Info nbjm(pid=2740) started backup job for client DB-Cluster, policy DotnetDB-Live-Full-Diff, schedule Default-Application-Backup on storage unit VeritasNBU-hcart-robot-tld-0

4/17/2011 5:14:19 PM - started process bpbrm (6112)

4/17/2011 5:14:20 PM - Info bpbrm(pid=6112) DB-Cluster is the host to backup data from    

4/17/2011 5:14:20 PM - Info bpbrm(pid=6112) reading file list from client       

4/17/2011 5:14:20 PM - connecting

4/17/2011 5:14:22 PM - Info bpbrm(pid=6112) listening for client connection        

4/17/2011 5:14:28 PM - Info bpbrm(pid=6112) INF - Client read timeout = 300     

4/17/2011 5:14:29 PM - Info bpbrm(pid=6112) accepted connection from client        

4/17/2011 5:14:29 PM - Info bphdb(pid=7932) Backup started          

4/17/2011 5:14:29 PM - Info bptm(pid=5576) start           

4/17/2011 5:14:29 PM - Info bptm(pid=5576) using 65536 data buffer size       

4/17/2011 5:14:29 PM - connected; connect time: 00:00:09

4/17/2011 5:14:31 PM - Info bptm(pid=5576) setting receive network buffer to 263168 bytes     

4/17/2011 5:14:31 PM - Info bptm(pid=5576) using 30 data buffers        

4/17/2011 5:14:31 PM - Info bptm(pid=5576) start backup          

4/17/2011 5:14:31 PM - Info bptm(pid=5576) backup child process is pid 5564.4264      

4/17/2011 5:14:31 PM - Info bptm(pid=5576) Waiting for mount of media id 3144L1 (copy 1) on server VeritasNBU.

4/17/2011 5:14:31 PM - Info bptm(pid=5564) start           

4/17/2011 5:14:31 PM - mounting 3144L1

4/17/2011 5:15:10 PM - Info bptm(pid=5576) media id 3144L1 mounted on drive index 1, drivepath {4,0,2,0}, drivename IBM.ULT3580-TD5.001, copy 1

4/17/2011 5:15:10 PM - mounted; mount time: 00:00:39

4/17/2011 5:15:10 PM - positioning 3144L1 to file 64

4/17/2011 5:15:53 PM - positioned 3144L1; position time: 00:00:43

4/17/2011 5:15:53 PM - begin writing

4/17/2011 5:15:55 PM - Info bphdb(pid=7932) dbclient(pid=7932) wrote first buffer(size=65536)        

4/17/2011 5:26:10 PM - end writing; write time: 00:10:17

4/17/2011 5:26:15 PM - Info bphdb(pid=7932) done. status: 41: network connection timed out     

network connection timed out(41)

[AbdulRasheed]

Is the new library generating the media id the same way the old library? Note that...

4/17/2011 5:38:24 PM - Error bptm(pid=6068) allow overwrite operation failed to media id 3144L1, drive index 1, address 3139778

This is telling you that NetBackup is detecting 3144L1 as a new tape and trying to overwrite. Make sure that the new library is generating the media id using the same characters in the bar code. You can modify the media id generation rule to match what old library had used.

Caution: Do not blindly enable ALLOW_MEDIA_OVERWRITE in this case.

[Zahid_Haseeb]

Thanks for your kind reply Abdul Rasheed

This is telling you that NetBackup is detecting 3144L1 as a new tape and trying to overwrite.Make sure that the new library is generating the media id using the same characters in the bar code

What is the problem if the new media ID will not be created as same as previous

Caution: Do not blindly enable ALLOW_MEDIA_OVERWRITE in this case.

I think this will overwrite the media Data not the Media ID ?

[RonCaplinger]

Abdul, I thiink the library is reading the barcodes and recognizing the tapes correctly; the drive shows that tape is being forwarded to file position 64:

...."positioning 3144L1 to file 64"

so I think it recognizes the fact that this barcode/media ID existed before.  (That was my first thought, too!)

Zahid, a few more questions: did you change the drive type from, say, HCART3 to HCART?  Did you switch generations of tape drives (I believe the 3580's went through a similar LTO3-to-LTO4 changt)?  And are you using tape drive-based encryption?

[AbdulRasheed]

Hi Zahid,

Q) What is the problem if the new media ID will not be created as same as previous

Typically the mount operation itself will fail as the external media id and internal (recorded in tape) media id are different. I was afraid that if you have ALLOW_MEDIA_OVERWRITE enabled, you would lose data.

Q) I think this will overwrite the media Data not the Media ID ?

ALLOW_MEDIA_OVERWRITE can also overwrite internal media id if it is configured overwrite it.

See response from Ron below, perhaps your problem is not what I had thought earlier. I didn't mean to scare you, sorry!

[Zahid_Haseeb]

Thanks for your kind reply Ron

Drives type on both libraries are HCART. Yes my old Tape Cartridges are LTO4 and my new Tape Library is LTO5, but i think we can use Tape Cartridges i generation backup

[Zahid_Haseeb]

 I didn't mean to scare you, sorry!

No Problem :)

Actually i am using the Barcode on Tape Cartridges and second when i inserted the Tape Cartridges from old Tape Library to the new Tape Library my old Tapr Cartridge got the same Media ID 

[Eric_Zhang]

any progress so far ? Zahid .

[Zahid_Haseeb]

No Eric :(

I am trying one thing. I un plugged my new Tape Library and plugged the Old Library and looking that really i get the same error on the Old Library(in past when i was using the old Tape Library i did not received this error). Still i have not got yet the error on Old Tape Library but looking more