Video Screencast Help

Netbackup 7.0 all of a sudden can't UP tape drive! Stopped working suddenly

Created: 27 Mar 2013 | 13 comments

Hi there,

 

After 1 year using the current configuration, we didn't change anything nor did update anything, the backups were running correctly and perfectly.

Since yesterday the backups are no longer happening, syslog shows:

 

Mar 26 23:02:10 SPVVJ-HRSATS-BKP00 tldcd[28195]: [ID 131361 daemon.error] TLD(0) key = 0x3, asc = 0x30, ascq = 0x0, INCOMPATIBLE MEDIUM INSTALLED
Mar 26 23:02:10 SPVVJ-HRSATS-BKP00 tldcd[28195]: [ID 719803 daemon.error] TLD(0) Move_medium error
Mar 26 23:02:55 SPVVJ-HRSATS-BKP00 ltid[11504]: [ID 434987 daemon.error] Operator/EMM server has DOWN'ed drive HP.ULTRIUM4-SCSI.000 (device 0)
Whenever I try to do run a job, it shows error code 2009 or 252.
 
The tape drive stays in this state:
 
drv1.PNG
 
I thought it could be a stuck tape, so I temporarily froze the tape the jobs were trying to write, but the error persists whenever requesting other tapes:
drv2.PNG
 
Can you guys please help me? I'm not an expert in this. Which logs can I see to identify correctly what is happening?
Operating Systems:

Comments 13 CommentsJump to latest comment

Markweiser's picture

I even tried what we beginners do whenever a problem happens, restarting the services, even the server itself I did restart.

Marianne's picture

This error is coming from the robot itself, not NetBackup:

TLD(0) key = 0x3, asc = 0x30, ascq = 0x0, INCOMPATIBLE MEDIUM INSTALLED

The robot itself believes that the tape cannot be mounted in the drive.

Use robtest to manually mount one of these tapes in the drive. 
You will probably get the same error.

Log a call with your hardware vendor.

*** EDIT ***

robtest usage: http://www.symantec.com/docs/TECH83129

 

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

Yasuhisa Ishikawa's picture

Have you tries power cycle of your robot? If not, shutdown the system and try it. Do not do it while the system is running.

I doubt the hardware failure or some defect of robot because this issue happened with multiple tapes. Please check the log of your robot.

Authorized Symantec Consultant(ASC) Data Protection in Tokyo, Japan

Markweiser's picture

Tried some tests:

 

 

READ_ELEMENT_STATUS complete
m d1 s7
Initiating MOVE_MEDIUM from address 1 to 1007
move_medium failed
sense key = 0x5, asc = 0x3b, ascq = 0xe, MEDIUM SOURCE ELEMENT EMPTY
m s7 d1
Initiating MOVE_MEDIUM from address 1007 to 1
move_medium failed
sense key = 0x3, asc = 0x30, ascq = 0x0, INCOMPATIBLE MEDIUM INSTALLED
 
I'll try to reach the vendor about this issue. Do you guys think it is POSSIBLE to be a stuck tape? I don't have physical access to the place where the robot is right now, so I'm not sure if this is happening.
 
Thanks
Marianne's picture

What does 's d ' show?

If there is a tape in the drive, you need to unload it before you try to move it back to a slot:
unload d1

Best to find someone who can physically check the robot...

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

Markweiser's picture

It seems it worked:

 

 

unload d1
Opening /dev/rmt/0cbn, on the local host, please wait...
Error - cannot open /dev/rmt/0cbn (I/O error)
s d
drive 1 (addr 1) access = 1 Contains Cartridge = no
READ_ELEMENT_STATUS complete
m s7 d1
Initiating MOVE_MEDIUM from address 1007 to 1
MOVE_MEDIUM complete
And then I tried to UP the drive:
 
 
drv3.PNG
 
So I tried to restart a job and it seems it's working correctly:
 
drvsucc.PNG
 
Thanks a lot, it seems it has been solved.
 
Just curious, what has happened in this case? Can please tell me? And how can I possibly prevent this? 
 
Again, thanks a lot for your time!
Will Restore's picture

This error usually caused by incorrect barcodes. I don't think it could be stuck tape. Other possibility is barcode reader is dirty or defective. In any event you need someone on site to check/clean/replace the robot.

Will Restore -- where there is a Will there is a way

Marianne's picture

Just curious, what has happened in this case? 

 

We will need to see entire messages file. Without knowing where it all began and initial errors, there is no way that we can tell you....

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

Marianne's picture

Solaris syslog = /var/adm/messages

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

Will Restore's picture

I would look to the source ( tape library ) rather than NetBackup.

Will Restore -- where there is a Will there is a way