cancel
Showing results for 
Search instead for 
Did you mean: 

Drive media server down. Code 277

pruvn
Level 5

Hello everyone,

I am using NBU 7.0, Windows 2008 R2, I have got 3 server:

1. Master server

2. Media server 1 (DB server)

3. Media server 2 (File server)

I am using HP tape library MSL 4048.

Yeaterday, drive on media server 1 down, I am trying up this drive but not success. The error code 277. I checked all driver for tape library is OK. Here picture bellow:

 

 

What should I do? Please help me.

Pruvn.

1 ACCEPTED SOLUTION

Accepted Solutions

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

My experience has always been that VERBOSE entry will log additional, helpful info in Event Viewer.

I would try the following:
Stop NBU device manager.
Delete this drive in device manager and rescan. Confirm that device is re-added with correct driver. Check that Windows driver is not used - use manufacturer driver.
Use HBA tool (e.g. Sansurfer if Qlogic; HBAnywhere for Emulex) to confirm settings for the 2 drives are the same.
Start NBU device manager.
Scan from cmd: <install-path>\veritas\volmgr\bin\scan
Ensure both drives are seen.
Check drive status from cmd : <install-path>\veritas\volmgr\bin\vmoprcmd -d

View solution in original post

8 REPLIES 8

tom_sprouse
Level 6
Employee Accredited Certified

The drive only shows down on 1 of the media servers.

1) Check the System / Application Event Logs on PSSDBS05 - Ensure you have no events related to the drive. Also, bptm logging on the media server, may reflect why the drive was downed.

2) Disable Removable Storage Service on all three Windows hosts.

3) Attempt to reset the drive and/or library using any Vendor remote management tools

4) Cycle library if needed 

5) Cycle the media server PSSDBS05 


pruvn
Level 5

Hello tom_sprouse,

The server PMSSDBS05 has two drive but only drive 0 downed. I am restarted Tape library by remote tool, after that I restart server PMSSDBS05 and Master server. But the same error.

Please help me. I truying search but not solution.

Here log bptm:

15:29:02.215 [6364.7616] <2> bptm: instance - 493552406
15:29:02.215 [6364.7616] <2> bptm: INITIATING (VERBOSE = 5): -rptdrv -jobid -1321436191 -jm
15:29:02.216 [6364.7616] <2> bptm: Event NetBackup Terminate Event, pid: 6364 created.
15:29:02.216 [6364.7616] <2> bptm: PORT_STATUS = 0x00000000
15:29:02.216 [6364.7616] <2> drivename_open: Called with Create 0, file HP.ULTRIUM4-SCSI.000
15:29:02.217 [6364.7616] <2> drivename_checklock: Called
15:29:02.217 [6364.7616] <2> report_drives: DRIVE = HP.ULTRIUM4-SCSI.000 LOCK = FALSE CURTIME = 1321864142
15:29:02.217 [6364.7616] <2> drivename_close: Called for file HP.ULTRIUM4-SCSI.000
15:29:02.217 [6364.7616] <2> report_drives: MODE = 1
15:29:02.217 [6364.7616] <2> report_drives: TIME = 1321373798
15:29:02.217 [6364.7616] <2> report_drives: MASTER = pmssapp27
15:29:02.217 [6364.7616] <2> report_drives: SR_KEY = 0 1
15:29:02.217 [6364.7616] <2> report_drives: PATH = {1,0,2,0}
15:29:02.217 [6364.7616] <2> report_drives: MEDIA = L749L4
15:29:02.217 [6364.7616] <2> report_drives: REQID = -1320923501
15:29:02.217 [6364.7616] <2> report_drives: ALOCID = 6380
15:29:02.217 [6364.7616] <2> report_drives: RBID = {202453FB-E3A3-471D-87EF-ECDED07E9E1B}
15:29:02.217 [6364.7616] <2> report_drives: PID = 5584
15:29:02.217 [6364.7616] <2> report_drives: FILE = C:\Program Files\Veritas\NetBackup\db\media\tpreq\drive_HP.ULTRIUM4-SCSI.000
15:29:02.217 [6364.7616] <2> main: Sending [EXIT STATUS 0] to NBJM
15:29:02.217 [6364.7616] <2> bptm: EXITING with status 0 <----------
15:29:02.217 [6364.7616] <2> bptm: NetBackup Terminate Event, pid: 6364 closed.

 

pruvn.

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

Please add VERBOSE entry to vm.conf on PMSSDBS05 (in <install-path\veritas\volmgr).

Restart NetBackup Device Management Service.

Try to UP the drive.

Check Event Viewer Application and System logs on PMSSDBS05 for errors.

 

Old TN that might still be relevant: http://www.symantec.com/docs/TECH30178

Please also disable OS Test Unit Ready. See: http://www.symantec.com/docs/HOWTO56216

pruvn
Level 5

Hello Marianne van den Berg,

How to add VERBOSE entry to vm.conf? On PMSSDBS05 only have this line:

MM_SERVER_NAME = pmssdbs05

I am restarted Netbackup  Device Management Service and try up the drive but the same error.

I checked Event Viewer Application is ok here: TLD(0) going to UP state

I checked Event Viewer system is ok here:The NetBackup Device Manager service entered the running state.

Please help me Marianne,

Thanks

Pruvn.

 

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

Open the file with something like Notepad.

Add a new line at the bottom of the file and type:
VERBOSE

Save and close the file. Restart Device Management service.

Then try to UP and check Event viewer logs.

Please also have a look at the 2 TN's that I have posted above.

pruvn
Level 5

Hello Marianna,

1. I was add VERBOSE, restart Device Management Service, try Up this device but not success.

2. The Event viewer log alway ware not error.

3. I was read http://www.symantec.com/business/support/index?page=content&id=TECH30178 and checked. All driver in device manager OK.

Any Idead for me. Can I remove drive tape in device manager?

Pruvn,

 

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

My experience has always been that VERBOSE entry will log additional, helpful info in Event Viewer.

I would try the following:
Stop NBU device manager.
Delete this drive in device manager and rescan. Confirm that device is re-added with correct driver. Check that Windows driver is not used - use manufacturer driver.
Use HBA tool (e.g. Sansurfer if Qlogic; HBAnywhere for Emulex) to confirm settings for the 2 drives are the same.
Start NBU device manager.
Scan from cmd: <install-path>\veritas\volmgr\bin\scan
Ensure both drives are seen.
Check drive status from cmd : <install-path>\veritas\volmgr\bin\vmoprcmd -d

pruvn
Level 5

Hello Marianna,

You are right, I only do:

- Stop NBU device manager.
- Delete this drive in device manager and rescan.

Now PMSSDBS05 working very good,

Thank you very much Marianna,

Pruvn.