NBU MediaServer DrivePATH Missing

Nbuversions: 7.5

MediaServer: WindowsServer 2008R2

Backup content: SQLServer data

Library: IBM3584

During inspection of NBU, a backup failure job is found in activity monitor, and the status code is 52,

650) this. width = 650; "src =" http://www.bkjia.com/uploads/allimg/131228/055F23T6-0.jpg "title =" new map. BMP "alt =" 182419416.jpg"/>

The MediaServer driver loss path is found in device monitor:

650) this. width = 650; "src =" http://www.bkjia.com/uploads/allimg/131228/055F21O2-1.png "title =" Capture. PNG "alt =" 183015555.png"/>

1 TroubleShooting

First, check dirve on MediaServer:

C: \ Program Files \ Veritas \ Volmgr \ bin> tpconfig-l Type Num Index Type DrNum Status Comment Name Path Robot 0-TLD---bcsyyfx Drive-9 hcart2 8 DOWN-IBM.ULT3580-TD5.009 MISSING_PATH: {4, 0, 6, 0}: 00078AD2A

We can see that the driver with the address {, 0, 6, 0} serial number 00078AD2A has lost the path, which is consistent with the device monitor display. NBU obtains the path of tape drive through the operating system, check the drive status in the Device Manager.

650) this. width = 650; "src =" http://www.bkjia.com/uploads/allimg/131228/055F24256-2.png "title =" Capture. PNG "alt =" 185043514.png"/>

In the Device Manager, Click Show hide device to view Tape dirve. No device with no driver installed is found, and the driver works properly. By checking the properties of each dirve, in the operating system, the driver address with the serial number 00078AD2A is {,} port = 4 bus = 0 target = 5 lun = 0, which corresponds to {0, 6, 0} does not match. No wonder nbu cannot find the path. It may be because the tape driver or bus location has changed, the address under the system has changed, and NBU has not changed accordingly, the configuration in NBU is different from that in the current system. The dirve configuration in NBU is stored in EMM. Then, update the configuration in EMM.

2. reconfigure dirve path

Delete the error dirve and run the tpconfig command.

<NBUinstall_path> \ Volmgr \ bin> tpconfig-delete-drpath-port 4-bus 0-target 6-lun0-asciiname IBM.ULT3580-TD5.009

Restart the NBU Service

<NBUinstall_path> \ Netbackup \ bin> bpdown-f-v <NBUinstall_path> \ Netbackup \ bin> bpup-f-v

View dirve status

<NBUinstall_path> \ Volmgr \ bin> vmoprcmd

If you modify the dirve configuration and restart the NBU service, the dirve status changes to restart, indicating that the process needs to be restarted.

Redefine the new dirve path

Start the Admin Console on the MasterServer and use the wizard "ConfigureStrage Devices" to configure dirve. After selecting MediaServer in the selection wizard, the following error occurs: "error connecting to oprd on xxxx: oprd returned an abnormal status (96)" masterserver cannot connect to mediaserver.

Google found a tutorial and needed to reconfigure mediaserver, as shown below:

1. Disable the NBU service on the MediaServer.

<NBUinstall_path> \ Netbackup \ bin> bpdown-f-v

2. Modify the file vmd. lock In the Volmgr \ misc directory of the NBU installation path and rename or delete it.

3. Start the MediaServer Service

<NBUinstall_path> \ Netbackup \ bin> bpup-f-v

4. Use nbrbutil to configure MediaServer on MasterServer

<NBUinstall_path> \ Netbackup \ bin \ admincmd \ nbrbutil-resetMediaServer xxxx

Xxx is the MediaServer Host Name

Note two points before using the resetMediaServer parameter: first, use nbrbutil-dump to ensure that no device Allocations is stuck in EMM; second, ensure that no backup job is running, and nbrbutil will stop the current job

5 re-use the wizard Configure Strage Devices

After MediaServer is selected, continue to the next step and add a new path for dirve

The vmoprcmd command is used in MediaServer, so the status of the new drive is TLD. Now, the dirve path is added with OK, and the manual backup test is normal.

This article is from the "Study Notes" blog, please be sure to keep this source http://967169.blog.51cto.com/957169/1296716