cancel
Showing results forΒ 
Search instead forΒ 
Did you mean:Β 

VTL drives going down for some media servers

KS2
Level 5

Data domain VTL drives are going down on few media servers for one library. However, same library drives are working fine on other media servers.

Not able to dismount the tape also from drive. If the VTL drive mounts the tape, It is unable to dismount it.

m d13 s144
Initiating MOVE_MEDIUM from address 512 to 1143
move_medium failed
sense key = 0x5, asc = 0x53, ascq = 0x3, UNKNOWN ERROR, KEY: 0x05, ASC: 0x53, ASCQ: 0x03


Drive seems to be ok after we make it UP. but as soon as it mounts the tape backup fails with below error -

05/07/2015 11:09:53 - Error bptm (pid=7061) error requesting media, TpErrno = Robot operation failed
05/07/2015 11:09:53 - Warning bptm (pid=7061) media id TK0143 load operation reported an error
05/07/2015 11:09:53 - current media TK0143 complete, requesting next media Any
05/07/2015 11:10:49 - Error bptm (pid=7061) NBJM returned an extended error status: All compatible drive paths are down but media is available (2009)
05/07/2015 11:10:49 - Info bptm (pid=7061) EXITING with status 252 <----------
05/07/2015 11:10:50 - Info bpbkar (pid=22019) done. status: 252: extended error status has been encountered, check logs
05/07/2015 11:10:50 - end writing
An extended error status has been encountered, check detailed status  (252)

Device path is fine and able to ping the drive also.

[root@media]# mt -f /dev/rmt/36cbn status
/dev/rmt/36cbn: no tape loaded or drive offline
[root@media]# tpconfig -dev_ping -drive -path /dev/rmt/36cbn
Device Inquiry String: IBM     ULTRIUM-TD2     8711
Device Serial Number: 1002260010
Default Type: 10

I tried deleting and readding few drives but it is still not working as tape is stuck on the VTL drive.

Output from the messages log -

May  7 12:09:51 Media2 tldcd[13653]: [ID 673512 daemon.notice] Processing MOUNT, TLD(11) drive 13, slot 144, barcode TK0143          , vsn TK0143
May  7 12:09:51 Media2 tldcd[13653]: [ID 673512 daemon.notice] Processing MOUNT, TLD(11) drive 13, slot 144, barcode TK0143          , vsn TK0143
May  7 12:09:51 Media2 tldcd[20445]: [ID 534965 daemon.notice] TLD(11) opening robotic path /dev/sg/c2t2l0
May  7 12:09:51 Media2 tldcd[20445]: [ID 534965 daemon.notice] TLD(11) opening robotic path /dev/sg/c2t2l0
May  7 12:09:51 Media2 tldcd[20445]: [ID 765094 daemon.notice] inquiry() function processing library D_DOMAIN RESTORER_L180    5421:
May  7 12:09:51 Media2 tldcd[20445]: [ID 765094 daemon.notice] inquiry() function processing library D_DOMAIN RESTORER_L180    5421:
May  7 12:09:51 Media2 tldcd[20445]: [ID 789843 daemon.notice] TLD(11) initiating MOVE_MEDIUM from addr 512 to addr 1143
May  7 12:09:51 Media2 tldcd[20445]: [ID 789843 daemon.notice] TLD(11) initiating MOVE_MEDIUM from addr 512 to addr 1143
May  7 12:09:52 Media2 tldcd[20445]: [ID 121558 daemon.error] TLD(11) key = 0x5, asc = 0x53, ascq = 0x3, UNKNOWN ERROR, KEY: 0x05, ASC: 0x53, ASCQ: 0x03
May  7 12:09:52 Media2 tldcd[20445]: [ID 121558 daemon.error] TLD(11) key = 0x5, asc = 0x53, ascq = 0x3, UNKNOWN ERROR, KEY: 0x05, ASC: 0x53, ASCQ: 0x03
May  7 12:09:52 Media2 tldcd[20445]: [ID 504737 daemon.error] TLD(11) Move_medium error
May  7 12:09:52 Media2 tldcd[20445]: [ID 504737 daemon.error] TLD(11) Move_medium error
May  7 12:09:52 Media2 tldcd[20445]: [ID 131138 daemon.notice] TLD(11) closing/unlocking robotic path
May  7 12:09:52 Media2 tldcd[20445]: [ID 131138 daemon.notice] TLD(11) closing/unlocking robotic path
May  7 12:09:52 Media2 tldcd[13653]: [ID 765094 daemon.notice] inquiry() function processing library D_DOMAIN RESTORER_L180    5421:
May  7 12:09:52 Media2 tldcd[13653]: [ID 765094 daemon.notice] inquiry() function processing library D_DOMAIN RESTORER_L180    5421:

 

 

Any suggestion here?

1 ACCEPTED SOLUTION

Accepted Solutions

KS2
Level 5

We logged a call with vendor and it seems to be issue with serial number/Drive name mismatch. NBU drive name and serial number was not matching with wat was given on Data domain side.

Deleted the drives and corrected the drive name/Serial number and it worked.

Thanks all for your suggestions.

View solution in original post

7 REPLIES 7

mnolan
Level 6
Employee Accredited Certified

You'll want to contact your VTL vendor for this.  A virtual library really should not have move medium issues!  NetBackup does not know it is virtual, just issues standard commands and is receiving errors back FROM the VTL itself.

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified
This looks like mismatched device mapping to me. Mappings go wrong when there is no Persistent Binding in place between hba and OS, resulting in device paths changing when server is rebooted. To fix this, you need to download the management GUI for the hba and config Persistent Binding. Then delete all devices for this media ser and re-add them using the Device config wizard.

KS2
Level 5

Persistent Binding is in place Marianne. The problem comes when tape mounts to the drive and makes it down and vtl tape gets stuck to it.

 

mph999
Level 6
Employee Accredited

Where you have that unknown error after the d13 s144

Asc/ascq line, send this to the vendor and ask them what it means, it is being sent from the library, robtest is only reporting it.

Then, once wer know the meaning we can go from there.

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

I just had another look at your opening post:

It seems you used robtest to load the tapes and received sense key errors.

This is a hardware error - you need to log a call with your VTL vendor.

KS2
Level 5

We logged a call with vendor and it seems to be issue with serial number/Drive name mismatch. NBU drive name and serial number was not matching with wat was given on Data domain side.

Deleted the drives and corrected the drive name/Serial number and it worked.

Thanks all for your suggestions.

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified