cancel
Showing results for 
Search instead for 
Did you mean: 

Netback up error : unable to access drive HP.ULTRIUM3-SCSI.001, drive is locked

netcc
Level 2

we have netbackup for our unix serves . for the last 2 days nectbackup is failing for one of the client .

 

if i go and see the problem it shows that ,

 

"unable to access drive HP.ULTRIUM3-SCSI.001, drive is locked "

 

what could be the reason . can anyone guide to get through this issue

1 ACCEPTED SOLUTION

Accepted Solutions

Marianne
Level 6
Partner    VIP    Accredited Certified

Which Unix 'flavour'? You need to check the OS syslog - for example /var/adm/messages on Solaris.

You also need to check bptm log on the media server.

Are you tape drives shared between media servers?

If you do 'vmoprcmd -d' on all media servers, do they all show up as 'shared'?

The error sounds to me like a media server not knowing that the drive is shared.

Please also let us know your NBU version on master and media servers.

View solution in original post

6 REPLIES 6

Marianne
Level 6
Partner    VIP    Accredited Certified

Which Unix 'flavour'? You need to check the OS syslog - for example /var/adm/messages on Solaris.

You also need to check bptm log on the media server.

Are you tape drives shared between media servers?

If you do 'vmoprcmd -d' on all media servers, do they all show up as 'shared'?

The error sounds to me like a media server not knowing that the drive is shared.

Please also let us know your NBU version on master and media servers.

mrinal_sarkar62
Level 6

Hi Netcc,

Always try to provide us the details of the netbackup version and OS playform details along with clients details(like details of the detabase and client details...etc). wink

These information is always help ful to provide better solution , rather asking for the details, which is a  waste of time. blush

Have you tried to check the device level configuration, if no try the below command:-

/usr/sbin/modinfo | grep sg

If the driver is loaded, output includes a line similar to the following:

141 fc580000 2d8c 116 1 sg (SCSA Generic Revision: 3.5e)

For more details check the "Symantec_Netbackup_Deviceconfig_guide" in page no. 81 if it is an Unix  or Solaris. 

 

Along with above lines u will find other details , but check for the above line only.

 Along with the above command also excute the command provided by  Marianne

 

Thanks.

netcc
Level 2

Our netbackup is running on Windiw version . it has 4 media servers . medis servers  running on IBM AIX . DB is oracle .

 

Backup is running correctly on all 3 media servers except the one .

 

OUR NBU version is 6.0

 

BPRM log says

 

"16:47:15.446 [1946096] <2> drivename_lock: lock failed
16:47:15.446 [1946096] <2> drivename_close: Called
16:47:24.222 [356402] <2> drivename_open: Called with Create 1, file HP.ULTRIUM3
-SCSI.001 "

Will_Restore
Level 6

any lines with <16> error messages ?

netcc
Level 2

i could not see any error with 16

 

09:54:44.173 [2363424] <2> report_drives: MEDIA = A00009
09:54:44.173 [2363424] <2> report_drives: REQID = -1289205925
09:54:44.173 [2363424] <2> report_drives: ALOCID = 27296
09:54:44.173 [2363424] <2> report_drives: RBID = {633CEDD9-0996-4912-A37D-E9DDEF
AC2997}
09:54:44.173 [2363424] <2> report_drives: PID = 1638804
09:54:44.173 [2363424] <2> report_drives: FILE = /usr/openv/netbackup/db/media/t
preq/drive_HP.ULTRIUM3-SCSI.001
09:54:44.173 [2363424] <2> main: Sending [EXIT STATUS 0] to NBJM
09:54:44.173 [2363424] <2> bptm: EXITING with status 0 <----------
09:54:44.403 [1986972] <2> drivename_open: Called with Create 1, file HP.ULTRIUM
3-SCSI.001
09:54:44.403 [1986972] <2> drivename_lock: lock failed
09:54:44.403 [1986972] <2> drivename_close: Called
09:54:52.314 [1753492] <2> drivename_open: Called with Create 1, file HP.ULTRIUM
3-SCSI.000
09:54:52.314 [1753492] <2> drivename_lock: lock failed
09:54:52.314 [1753492] <2> drivename_close: Called
09:54:54.403 [1986972] <2> drivename_open: Called with Create 1, file HP.ULTRIUM
3-SCSI.001

Marianne
Level 6
Partner    VIP    Accredited Certified

As I've said in my previous post:

The error sounds to me like the media server not knowing that the drive is shared.

If you do 'vmoprcmd -d' on this media server, do all the drives show up as 'shared'?