Netbackup Put Down Drives

[junka]

Hi!!! I Have a netbackup 7.6.0.2 with a scalar i500 with 6 LTO5 drives, 4 off them work fine but the other two netbackup put down, when i tried to put up again netbackup put down again when trie to use the drive. However if i check the i500 the drive mount the tape that netbackup assing for the job.
 

Thanks for your helps

logs

7/11/2016 6:00:21 AM - begin Duplicate
7/11/2016 6:00:21 AM - requesting resource ssjsed1050-hcart2-robot-tld-2-10.167.1.153
7/11/2016 6:00:21 AM - requesting resource V00231
7/11/2016 6:00:21 AM - reserving resource V00231
7/11/2016 6:00:21 AM - awaiting resource ssjsed1050-hcart2-robot-tld-2-10.167.1.153 - No drives are available
7/11/2016 7:30:15 AM - reserved resource V00231
7/11/2016 7:30:15 AM - granted resource 500721
7/11/2016 7:30:15 AM - granted resource IBM.ULTRIUM-TD5.007
7/11/2016 7:30:15 AM - granted resource ssjsed1050-hcart2-robot-tld-2-10.167.1.153
7/11/2016 7:30:15 AM - granted resource V00231
7/11/2016 7:30:15 AM - granted resource IBM.ULTRIUM-TD4.035
7/11/2016 7:30:17 AM - Info bptm(pid=11128) start            
7/11/2016 7:30:17 AM - started process bptm (11128)
7/11/2016 7:30:17 AM - Info bptm(pid=11128) using 65536 data buffer size        
7/11/2016 7:30:17 AM - Info bptm(pid=11128) setting receive network buffer to 263168 bytes      
7/11/2016 7:30:17 AM - Info bptm(pid=11128) start backup           
7/11/2016 7:30:18 AM - Info bptm(pid=11580) start            
7/11/2016 7:30:18 AM - started process bptm (11580)
7/11/2016 7:30:18 AM - Info bptm(pid=11128) setting receive network buffer to 263168 bytes      
7/11/2016 7:30:18 AM - Info bptm(pid=11580) reading backup image          
7/11/2016 7:30:18 AM - Info bptm(pid=11580) using 1 data buffers         
7/11/2016 7:30:18 AM - Info bptm(pid=11580) Waiting for mount of media id V00231 (copy 1) on server ssjsed1050.
7/11/2016 7:30:18 AM - started process bptm (11580)
7/11/2016 7:30:18 AM - mounting V00231
7/11/2016 7:30:19 AM - Info bptm(pid=11580) INF - Waiting for mount of media id V00231 on server ssjsed1050 for reading.
7/11/2016 7:30:19 AM - Info bptm(pid=11128) Waiting for mount of media id 500721 (copy 2) on server ssjsed1050.
7/11/2016 7:30:19 AM - started process bptm (11128)
7/11/2016 7:30:19 AM - mounting 500721
7/11/2016 7:30:19 AM - Info bptm(pid=11128) INF - Waiting for mount of media id 500721 on server ssjsed1050 for writing.
7/11/2016 7:30:26 AM - mounted; mount time: 0:00:08
7/11/2016 7:30:26 AM - Info bptm(pid=11580) V00231            
7/11/2016 7:30:26 AM - Info bptm(pid=11580) INF - Waiting for positioning of media id V00231 on server ssjsed1050 for reading.
7/11/2016 7:30:26 AM - positioning V00231 to file 11
7/11/2016 7:30:26 AM - positioned V00231; position time: 0:00:00
7/11/2016 7:30:26 AM - begin reading
7/11/2016 7:31:04 AM - Error bptm(pid=11128) cannot open ndmp device /dev/alias/nst/1068067742, error code 2 (NDMP_DEVICE_BUSY_ERR)    
7/11/2016 7:33:14 AM - Error bptm(pid=11128) cannot open ndmp device /dev/alias/nst/1068067742, error code 2 (NDMP_DEVICE_BUSY_ERR)    
7/11/2016 7:33:59 AM - Error bptm(pid=11128) cannot open ndmp device /dev/alias/nst/1068067742, error code 2 (NDMP_DEVICE_BUSY_ERR)    
7/11/2016 7:33:59 AM - Warning bptm(pid=11128) media id 500721 load operation reported an error     
7/11/2016 7:33:59 AM - current media 500721 complete, requesting next resource Any
7/11/2016 7:59:44 AM - current media -- complete, awaiting next media Any Reason: Drives are in use, Media Server: ssjsed1050,
     Robot Number: 2, Robot Type: TLD, Media ID: N/A, Drive Name: N/A,
     Volume Pool: Duplicate-All, Storage Unit: ssjsed1050-hcart2-robot-tld-2-10.167.1.153, Drive Scan Host: N/A
    
7/11/2016 8:31:09 AM - current media -- complete, awaiting next media Any Reason: Robotic library is down on server, Media Server: ssjsed1050,
     Robot Number: 2, Robot Type: TLD, Media ID: N/A, Drive Name: N/A,
     Volume Pool: Duplicate-All, Storage Unit: ssjsed1050-hcart2-robot-tld-2-10.167.1.153, Drive Scan Host: N/A
    
7/11/2016 8:33:42 AM - current media -- complete, awaiting next media Any Reason: Drives are in use, Media Server: ssjsed1050,
     Robot Number: 2, Robot Type: TLD, Media ID: N/A, Drive Name: N/A,
     Volume Pool: Duplicate-All, Storage Unit: ssjsed1050-hcart2-robot-tld-2-10.167.1.153, Drive Scan Host: N/A
    
7/11/2016 8:48:12 AM - Info bptm(pid=11128) Waiting for mount of media id 500721 (copy 2) on server ssjsed1050.
7/11/2016 8:48:12 AM - started process bptm (11128)
7/11/2016 8:48:12 AM - mounting 500721
7/11/2016 8:48:12 AM - granted resource 500721
7/11/2016 8:48:12 AM - granted resource IBM.ULTRIUM-TD5.006
7/11/2016 8:48:12 AM - granted resource ssjsed1050-hcart2-robot-tld-2-10.167.1.153
7/11/2016 8:48:13 AM - Info bptm(pid=11128) INF - Waiting for mount of media id 500721 on server ssjsed1050 for writing.
7/11/2016 8:48:16 AM - Error bptm(pid=11128) error requesting media, TpErrno = Robot operation failed     
7/11/2016 8:48:16 AM - Warning bptm(pid=11128) media id 500721 load operation reported an error     
7/11/2016 8:48:16 AM - current media 500721 complete, requesting next resource Any
7/11/2016 8:49:36 AM - current media -- complete, awaiting next media Any Reason: Drives are in use, Media Server: ssjsed1050,
     Robot Number: 2, Robot Type: TLD, Media ID: N/A, Drive Name: N/A,
     Volume Pool: Duplicate-All, Storage Unit: ssjsed1050-hcart2-robot-tld-2-10.167.1.153, Drive Scan Host: N/A
    
7/11/2016 9:04:56 AM - Info bptm(pid=11128) Waiting for mount of media id 500721 (copy 2) on server ssjsed1050.
7/11/2016 9:04:56 AM - started process bptm (11128)
7/11/2016 9:04:56 AM - mounting 500721
7/11/2016 9:04:56 AM - Info bptm(pid=11128) INF - Waiting for mount of media id 500721 on server ssjsed1050 for writing.
7/11/2016 9:04:56 AM - granted resource 500721
7/11/2016 9:04:56 AM - granted resource IBM.ULTRIUM-TD5.004
7/11/2016 9:04:56 AM - granted resource ssjsed1050-hcart2-robot-tld-2-10.167.1.153
7/11/2016 9:05:02 AM - Error bptm(pid=11128) error requesting media, TpErrno = Robot operation failed     
7/11/2016 9:05:02 AM - Warning bptm(pid=11128) media id 500721 load operation reported an error     
7/11/2016 9:05:02 AM - current media 500721 complete, requesting next resource Any
7/11/2016 9:06:31 AM - current media -- complete, awaiting next media Any Reason: Drives are in use, Media Server: ssjsed1050,
     Robot Number: 2, Robot Type: TLD, Media ID: N/A, Drive Name: N/A,
     Volume Pool: Duplicate-All, Storage Unit: ssjsed1050-hcart2-robot-tld-2-10.167.1.153, Drive Scan Host: N/A
    
7/11/2016 10:12:42 AM - Info bptm(pid=11128) Waiting for mount of media id 500721 (copy 2) on server ssjsed1050.
7/11/2016 10:12:42 AM - started process bptm (11128)
7/11/2016 10:12:42 AM - mounting 500721
7/11/2016 10:12:42 AM - Info bptm(pid=11128) INF - Waiting for mount of media id 500721 on server ssjsed1050 for writing.
7/11/2016 10:12:42 AM - granted resource 500721
7/11/2016 10:12:42 AM - granted resource IBM.ULTRIUM-TD5.007
7/11/2016 10:12:42 AM - granted resource ssjsed1050-hcart2-robot-tld-2-10.167.1.153
7/11/2016 10:13:27 AM - Error bptm(pid=11128) cannot open ndmp device /dev/alias/nst/1068067742, error code 2 (NDMP_DEVICE_BUSY_ERR)    
7/11/2016 10:15:36 AM - Error bptm(pid=11128) cannot open ndmp device /dev/alias/nst/1068067742, error code 2 (NDMP_DEVICE_BUSY_ERR)    
7/11/2016 10:16:21 AM - Error bptm(pid=11128) cannot open ndmp device /dev/alias/nst/1068067742, error code 2 (NDMP_DEVICE_BUSY_ERR)    
7/11/2016 10:16:21 AM - Warning bptm(pid=11128) media id 500721 load operation reported an error     
7/11/2016 10:16:21 AM - current media 500721 complete, requesting next resource Any
7/11/2016 10:42:05 AM - current media -- complete, awaiting next media Any Reason: Drives are in use, Media Server: ssjsed1050,
     Robot Number: 2, Robot Type: TLD, Media ID: N/A, Drive Name: N/A,
     Volume Pool: Duplicate-All, Storage Unit: ssjsed1050-hcart2-robot-tld-2-10.167.1.153, Drive Scan Host: N/A
   

[Marianne]

Do you have a NAS filer or is this Quantum 'Direct copy to tape' feature? I found a similar error in another discussion but the OP could never confirm his environment : https://www.veritas.com/community/forums/16-openndmpdevice-cannot-open-ndmp-device-error-code-2-ndmpdevicebusyerr

[Michael_G_Ander]

Could be caused by a mismatch between configured robotic drive in netbackup and the tape device file in the OS.

Have had this problem also with a Netapp, where we had to do the equivalent of persistent binding, and had to set the SCSI reserve option to the one Netbackup used to get the tape used by the filer to stay UP.

The quick "fix" is usually to rerun the Configure Storage Devices, as this corrects the configuration in Netbackup.

I would also make sure there was no hanging ndmp jobs on the filer, as this can give problems with the following ndmp backups.

[junka]

Sorry For the delay but yes is a Quantum Dxi with direct copy to tape, also i waiting for complete the duplicate for restart the library and the Master Server. Hope this resolve the issue

Thanks

[m_defender007]

Are you direct attached to the library (Arbitrated Loop) or are you
going thru a switch (brocade, mcdata etc etc) in fabric mode.

Who's driver stack are you using, SUN's or Qlogics. Sun's stack does
not work correctly with LTO drives on fiber channel.

[Marianne]

m.defender007 are you aware of Quantum DXi 'Direct copy to tape' technology?

And how is SUN drivers relevant when the OP is using NBU on Windows?