Shulou(Shulou.com)05/31 Report--

In this issue, the editor will bring you about how to analyze Netbackup code 98 errors. The article is rich in content and analyzes and narrates it from a professional point of view. I hope you can get something after reading this article.

Two days ago, several backup strategies of nbu suddenly reported an error. The specific error code is error requesting media (tpreq) (98). The specific information of the error is as follows.

17:13:18 on 2012-09-13-Info bphdb (pid=6828388) Backup started

17:13:18 on 2012-09-13-Info bphdb (pid=6840628) Backup started

17:13:18 on 2012-09-13-Info bptm (pid=5632) start

17:13:18 on 2012-09-13-Info bptm (pid=5632) using 65536 data buffer size

17:13:20 on 2012-09-13-Info bptm (pid=5632) setting receive network buffer to 263168 bytes

17:13:20 on 2012-09-13-Info bptm (pid=5632) using 30 data buffers

17:13:20 on 2012-09-13-Info bptm (pid=5632) start backup

17:13:20 on 2012-09-13-Info bptm (pid=5632) backup child process is pid 4608.4996

17:13:20 on 2012-09-13-Info bptm (pid=5632) Waiting for mount of media id 0044L4 (copy 1) on server S4PB02.

17:13:20 on 2012-09-13-Info bptm (pid=4608) start

17:13:20 on 2012-09-13-mounting 0044L4

17:13:24 on 2012-09-13-Error bptm (pid=5632) error requesting media, TpErrno = Robot operation failed

17:13:24 on 2012-09-13-Warning bptm (pid=5632) media id 0044L4 load operation reported an error

17:13:24 on 2012-09-13-current media 0044L4 complete, requesting next resource Any

17:13:28 on 2012-09-13-current media-complete, awaiting next media Any Reason: Media is in use, Media Server: S4PB02

Robot Number: 0, Robot Type: TLD, Media ID: N/A, Drive Name: N/A

Volume Pool: SAP-BACKUP-POOL, Storage Unit: S4PB02-hcart-robot-tld-0, Drive Scan Host: N/A

17:13:30 on 2012-09-13-end writing

Error requesting media (tpreq) (98)

Extract two lines of key information from the above error information:

Error bptm (pid=5632) error requesting media, TpErrno = Robot operation failed

Warning bptm (pid=5632) media id 0044L4 load operation reported an error

This error indicates that the picker operation failed and the 0044L4 tape loading job reported an error.

First, check the screenshot of the running status of the current backup policy.

At present, there are multiple jobs running, and there is only one working drive (with a yellow circle). Normally, two drives can run backup jobs at the same time.

First use the scan command to check the status of the tape library

C:\ Program Files\ Veritas\ Volmgr\ bin > scan

* * *

* SDT_TAPE *

* SDT_CHANGER *

* * *

Device Name: ""

Passthru Name: ""

Volume Header: ""

Port: 3; Bus: 0; Target: 1; LUN: 1

Inquiry: "IBM 3573-TL B.20"

Vendor ID: "IBM"

Product ID: "3573-TL"

Product Rev: "B.20"

Serial Number: "00X4U78N3182_LL0"

WWN: ""

WWN Id Type: 0

Device Identifier: "IBM 3573-TL 00X4U78N3182_LL0"

Device Type: SDT_CHANGER

NetBackup Robot Type: 8

Removable: Yes

Device Supports: SCSI-5

Number of Drives: 2

Number of Slots: 45

Number of Media Access Ports: 3

Drive 1 Serial Number: "9310088198"

Drive 2 Serial Number: "1310242183"

Flags: 0x0

Reason: 0x0

Device Name: ""

Passthru Name: ""

Volume Header: ""

Port: 3; Bus: 0; Target: 2; LUN: 1

Inquiry: "IBM 3573-TL B.20"

Vendor ID: "IBM"

Product ID: "3573-TL"

Product Rev: "B.20"

Serial Number: "00X4U78N3182_LL0"

WWN: ""

WWN Id Type: 0

Device Identifier: "IBM 3573-TL 00X4U78N3182_LL0"

Device Type: SDT_CHANGER

NetBackup Robot Type: 8

Removable: Yes

Device Supports: SCSI-5

Number of Drives: 2

Number of Slots: 45

Number of Media Access Ports: 3

Drive 1 Serial Number: "9310088198"

Drive 2 Serial Number: "1310242183"

Flags: 0x0

Reason: 0x0

Find that the status is normal, and then use the tpconfig command to check the drive status

C:\ Program Files\ Veritas\ Volmgr\ bin > tpconfig-d

Id DriveName Type Residence

SCSI coordinates/Path Status

*

1 IBM.ULT3580-TD4.001 hcart TLD (0) DRIVE=2

{3,0,2,0} UP

2 IBM.ULT3580-TD4.003 hcart TLD (0) DRIVE=1

{3,0,1,0} UP

Currently defined robotics are:

TLD (0) SCSI coordinates = {3pm 0pm 1pm 1}

EMM Server = S4PB02

Found that the drive status is normal, so why only one drive is normal, is it cassette? Try to move a tape in the tape drive and find that it can be moved in and out normally.

On-site check the optical fiber card and LED flashing status of the two drives on the backup server and the rear of the tape drive and find that everything is fine. Some engineer suggested to restart the tape library, here we should pay attention to a problem, if you find a fiber optic card without signal flashing, and there are multiple backup jobs running, then the link is not normal. You need to restart the tape library. After rebooting the tape library, the scan tape machine may return to normal. Or it may be normal to cancel all backup jobs, turn off the tape drive and unplug the flashing drive of the fiber optic card without signal lights. However, here the optical fiber card and indicator status are normal, and the link is also normal. If there is an error in the mounting tape, it is very likely that the slot of the tape has changed. We can update the volume configuration of the update volume configuration to let the drive arm find the correct tape location to solve this problem.

Let's verify it.

After updating OK, the problem is solved. The backup is back to normal and both drives are working.

The above is the editor for you to share how to carry out Netbackup code 98 error analysis, if you happen to have similar doubts, you might as well refer to the above analysis to understand. If you want to know more about it, you are welcome to follow the industry information channel.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.