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

Multiple Media Errors 86,84 causing backups to fail

Created: 21 Jun 2013 • Updated: 07 Jul 2013 | 15 comments
This issue has been solved. See solution.

Hi Experts,

We have been facing multiple media error where most of the times the CONTROL PATH was showing as " DOWN-TLD" and most of the tapes were freezed have to up the path and unfreeze the tapes manually, How to fix this issue??.

 84  media write error 

86  media position error

Thanks,

Nayab

Operating Systems:

Comments 15 CommentsJump to latest comment

Nicolai's picture

Inspect syslog/message log if it's a UNIX system.

Inspect event log on Windows.

Status 86 on LTO drives indicate bad tape drive. Try using a clean tape.

A look at [install_path]netbackup/db/media/errors file shoud give you a good indication if a tape or a subset of tape drives are bad

05/01/13 17:19:57 A22751 0 WRITE_ERROR 13115-TN
05/01/13 17:39:27 A22951 0 WRITE_ERROR 13115-TN
05/01/13 18:14:37 A22651 0 WRITE_ERROR 13115-TN
05/02/13 07:23:37 A21770 0 WRITE_ERROR 13115-TN
 
It's clear from this example that tape drive 13115-TN is bad and should be replaced.

Assumption is the mother of all mess ups.

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

SOLUTION
Nayab.Rasool's picture
05/30/13 14:34:12 BAD033 7 POSITION_ERROR DriveA002
05/30/13 23:04:46 HFD007 4 TAPE_ALERT DriveF004 0x00000000 0x82000100
05/30/13 23:06:58 HFD007 4 TAPE_ALERT DriveF004 0x00000000 0x82000100
05/30/13 23:19:50  4 TAPE_ALERT DriveF004 0x00000000 0x82000100
05/30/13 23:22:03  4 TAPE_ALERT DriveF004 0x00000000 0x82000100
05/30/13 23:39:50  4 TAPE_ALERT DriveF004 0x00000000 0x82000100
05/30/13 23:42:02  4 TAPE_ALERT DriveF004 0x00000000 0x82000100
05/31/13 08:04:25 EFD004 1 TAPE_ALERT DriveF002 0x00001000 0x02000000
05/31/13 11:10:52 AAD017 6 TAPE_ALERT DriveA000 0x20000000 0x02000000
05/31/13 23:03:23 HFD002 4 TAPE_ALERT DriveF004 0x00000000 0x82000100
05/31/13 23:05:35 HFD002 4 TAPE_ALERT DriveF004 0x00000000 0x82000100
05/31/13 23:19:53  4 TAPE_ALERT DriveF004 0x00000000 0x82000100
05/31/13 23:22:05  4 TAPE_ALERT DriveF004 0x00000000 0x82000100
05/31/13 23:43:12 EAD015 7 WRITE_ERROR DriveA002
06/01/13 00:52:49 EAD015 7 TAPE_ALERT DriveA002 0x00001000 0x02000000
06/01/13 08:03:25 EFD004 4 TAPE_ALERT DriveF004 0x00000000 0x82000100
06/01/13 08:05:38 EFD004 4 TAPE_ALERT DriveF004 0x00000000 0x82000100
06/01/13 08:05:54 BFD043 1 TAPE_ALERT DriveF002 0x00001000 0x02000000
06/01/13 08:09:20 GFD019 3 POSITION_ERROR DriveF001
06/01/13 08:14:14 BAD033 11 POSITION_ERROR DriveA008
06/01/13 08:19:51  4 TAPE_ALERT DriveF004 0x00000000 0x82000100
06/01/13 08:21:42 F00002 12 POSITION_ERROR DriveF000
06/01/13 08:22:09  4 TAPE_ALERT DriveF004 0x00000000 0x82000100
06/01/13 08:27:42 BAD033 11 POSITION_ERROR DriveA008
06/01/13 11:24:42 BAD033 10 POSITION_ERROR DriveA005
06/01/13 14:03:39 FFQ035 4 TAPE_ALERT DriveF004 0x00000000 0x82000100
06/01/13 14:05:51 FFQ035 4 TAPE_ALERT DriveF004 0x00000000 0x82000100
06/01/13 14:13:35 DFM014 12 POSITION_ERROR DriveF000
06/01/13 14:19:51  4 TAPE_ALERT DriveF004 0x00000000 0x82000100
06/01/13 14:22:04  4 TAPE_ALERT DriveF004 0x00000000 0x82000100
06/01/13 23:15:46 HFD007 4 TAPE_ALERT DriveF004 0x00000000 0x82000100
06/01/13 23:17:57 HFD007 4 TAPE_ALERT DriveF004 0x00000000 0x82000100
06/01/13 23:29:53  4 TAPE_ALERT DriveF004 0x00000000 0x82000100
06/01/13 23:32:04  4 TAPE_ALERT DriveF004 0x00000000 0x82000100
06/01/13 23:43:21 HFD002 1 TAPE_ALERT DriveF002 0x00001000 0x02000000
06/02/13 00:51:55 EAD015 11 WRITE_ERROR DriveA008
06/02/13 01:39:12 EAD015 11 TAPE_ALERT DriveA008 0x00001000 0x02000000
06/02/13 08:03:47 FFQ035 1 TAPE_ALERT DriveF002 0x00001000 0x02000400
06/02/13 08:16:53 GFD019 1 POSITION_ERROR DriveF002
06/02/13 11:03:22 BFD043 4 TAPE_ALERT DriveF004 0x00000000 0x82000100
06/02/13 11:05:42 BFD043 4 TAPE_ALERT DriveF004 0x00000000 0x82000100
06/02/13 11:19:41 F00002 12 POSITION_ERROR DriveF000
06/02/13 11:19:51  4 TAPE_ALERT DriveF004 0x00000000 0x82000100
06/02/13 11:22:09  4 TAPE_ALERT DriveF004 0x00000000 0x82000100
 
 
 
Thanks,
Nayab
mph999's picture

The Tape Alerts (fields 5 and 6 ) convert to the following :

Flag 33: Eject volume. Severity: Critical
Flag 39: Diagnostics required. Severity: Warning
Flag 56: Unrecoverable unload failure. Severity: Critical
Flag 35: Drive humidity. Severity: Warning
Flag 52: Tape system area write failure. Severity: Critical
Flag 52: Tape system area write failure. Severity: Critical
Flag 52: Tape system area write failure. Severity: Critical
 
These are sent from the hardware, NBU is only reporting them, not causing them
 
Look like hardware issues to me, I would call the hardware vendir and show them this.
 
It is impossible for NetBAckup to cause a Tapealert.
 
Regards,
 
Martin
Regards,  Martin
 
Setting Logs in NetBackup:
http://www.symantec.com/docs/TECH75805
 
Nayab.Rasool's picture

Hey Martin,

So the above errors are not so critical??

Thanks,

Nayab

mph999's picture

Yes, they are critical, but they are not the fault of NBU - hardware errors from what I can tell.

Martin

Regards,  Martin
 
Setting Logs in NetBackup:
http://www.symantec.com/docs/TECH75805
 
huanglao2002's picture

Can you try to see the tape library LED status?

and try to power cycle you tape library?

Nayab.Rasool's picture

Was able to see few error on my tape drives indicating red LED showing different numbers but ma client is not ready to give downtime to reboot the library .... One more thing TAPE DRIVE CLEANING is not happening automatically even we have tape drive inserted what might be the reason as soon as i insert a new cleaning tape its showing ZERO :( , Please advise what can be done.

mph999's picture

" ...  but ma client is not ready to give downtime to reboot the library ...."

Very simple, it stays broken until he does.

You could try a power cycle of the drives/ library - but this looks more serious than that.  Hardware call time I think.

Regarding the cleaning, please start a new thread for this additional problem.

Many thanks,

Martin

Regards,  Martin
 
Setting Logs in NetBackup:
http://www.symantec.com/docs/TECH75805
 
Nayab.Rasool's picture

Yes Martin, I have power cycled the TAPE DRIVES several times but errors coming again n again :( 

mph999's picture

OK, you need to log a hardware call to continue the troubleshooting. As i explained, NBU is not causing these errors.
A big clue is the red LEDs on the drive(s) - this is trying to tell you something is wrong.

There is absolutely nothing that can be done in NBU to fix these TAPEALERTs,

Martin

Regards,  Martin
 
Setting Logs in NetBackup:
http://www.symantec.com/docs/TECH75805
 
Nicolai's picture

From the error file it look like tape drive DriveF004 is bad. Replace it or down it in Netbackup to monitor how backup stability now look like.

Assumption is the mother of all mess ups.

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

Nayab.Rasool's picture

Hi Nicolai,

I have down the drive F004 today earlier in the morning have to see how backup goes tonight. And i can see one tape is inside this drive from past 4Days Is this tape struck ?? can i go ahead and remove this tape maually ??.

Thanks,

Nayab

mph999's picture

Yes, reemove it manually, allow the library to run an inventory, then run an inventory in NetBackup.

Regards,  Martin
 
Setting Logs in NetBackup:
http://www.symantec.com/docs/TECH75805
 
Nayab.Rasool's picture

Hi Martin,

Done , We are calling our Tape Hardware Vendor to help us in servicing the tape drives probably it should fix the problem :)

Thanks,

Nayab

mph999's picture

Excellent news.

Oh, and if they should happen to suggest that the issue is with NetBackup, it isn't.

M

Regards,  Martin
 
Setting Logs in NetBackup:
http://www.symantec.com/docs/TECH75805