Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

error 98 , delay of jobs appearing in AM, Robot Going to Down and up state, Tape Alert Code

Created: 30 Sep 2013 • Updated: 23 Oct 2013 | 6 comments
This issue has been solved. See solution.

Hello House,

I ma having a seroius issue in my environemnt sevaearl issues below:

Error 98 error requesting media (tpreq) (98)
 
Manual initiation Policy taking time to reach AM
Robot Going to Down and up state
Tape Alert Code Type Warning Flag HARD ERROR , from Drive (index 2) Media id
 
Operating Systems:

Comments 6 CommentsJump to latest comment

revaroo's picture

HARD ERROR = hardware error - contact your hardware vendor for assistance.

Marianne's picture

Totally agree with revaroo.

TapeAlert is generated by the firware on the tape drive. NBU is merely reporting the error.

Check /var/adm/messages for device errors.

For ongoing device-level troubleshooting, add VERBOSE entry to /usr/openv/volmgr/vm.conf and restart NBU.

NBU Media Manager messages and errors will now be logged to /var/adm/messages.

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

Nicolai's picture

Robot should not go up and down.

Try first to down index 2. You may need to use nbrbutil to delete existing drive reservation before you can down it. See http://www.symantec.com/docs/HOWTO43779

Check the messages log for SCSI related error messages that may assist you in resolving the error.

Assumption is the mother of all mess ups.

If this post answered your'e qustion -  Please mark as a soloution.

Ayes's picture

Thanks for this.

Another observation is that if a manual backup is initiated,it takes longer time to appear on the AM.

Two dayes ago the bpjobd stopped and we had to start it to be able to view the AM.

Please waht do we need to do to address this

Ayes's picture

Attached is the logs for the master server nbu1 and media server egypt.

Help analyse please.

AttachmentSize
var_adm_messages for master server_media server.zip 32.26 KB
Marianne's picture

You REALLY need to log a call with your hardware support team. 

All of these confirm that you have hardware issues:

Sep 30 03:46:47 ojnbu2 tldcd[23919]: [ID 356779 daemon.notice] TLD(0) issuing initialize_element_status, drive 32 asc=0x40, ascq=0x2

Sep 30 03:46:48 ojnbu2 tldcd[23919]: [ID 997458 daemon.error] TLD(0) cannot clear drive 32 error, drive asc=0x40, ascq=0x2 

Sep 30 07:37:32 egypt tldd[27036]: [ID 985549 daemon.notice] TLD(0) DismountTape ****** from drive 32

Sep 30 07:37:51 egypt tldd[27036]: [ID 896281 daemon.notice] DecodeDismount: TLD(0) drive 32, Actual status: Robotic dismount failure

Sep 30 07:37:52 egypt bptm[19668]: [ID 827104 daemon.warning] TapeAlert Code: 0x03, Type: Warning, Flag: HARD ERROR, from drive Drive011 (index 2), Media Id

Sep 30 07:37:52 egypt bptm[19668]: [ID 938638 daemon.crit] TapeAlert Code: 0x05, Type: Critical, Flag: READ FAILURE, from drive Drive011 (index 2), Media Id

Sep 30 07:37:52 egypt bptm[19668]: [ID 120236 daemon.crit] TapeAlert Code: 0x1e, Type: Critical, Flag: HARDWARE A, from drive Drive011 (index 2), Media Id

Long delays of jobs appearing in AM could be because the resource broker is having problems identifying available resources because of your hardware issue.

bpjobd is a separate issue.
Please ensure that you have latest NBU patches installed on master and media server.

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

SOLUTION