Veritas-bu

[Veritas-bu] media write errors - 84

2000-11-20 17:04:37
Subject: [Veritas-bu] media write errors - 84
From: Collins, Kathy KCollins AT coral-energy DOT com
Date: Mon, 20 Nov 2000 16:04:37 -0600
Hi,

I'm using NetBackup 3.2 with Solaris 2.6 on an E450 connected to an L11000.
I upgraded from NetBackup 3.2 patch 328 to patch 363 on November 3rd.  About
a week later, 
our media errors came along much more frequently.  Although the errors
appear the same as
previous media error in the messages log, the wording is different in the
Problems report of
NetBackup.   Here is a log I've been keeping with the stats on the errors.
Sometimes it looks
like a drive problem, sometimes like a tape problem.  These tapes all have
only 15 to 20 mounts.
The actual error reads "cannot write image to media id DOA763, drive index
2, I/O error", whereas
previous media errors read "write error on media id...".  Both show up with
a status code of 84.

11/11 20:33 DOA763  drive index 5  cannot write image to media id...
11/12 09:33 DOA871  drive index 5  cannot write image to media id...
11/13 07:16 DOA885  drive index 5  cannot write image to media id...
-
replaced drive index 5 (/dev/rmt/5)
-
11/13 20:57 DOA656  drive index 5  cannot write image to media id...
11/14 07:19 DOA885  drive index 5  cannot write image to media id...
11/14 20:35 DOA860  drive index 2  cannot write image to media id...
11/16 06:47 DOA651  drive index 2  cannot write image to media id...
11/16 07:37 DOA651  drive index 5  cannot write image to media id...
11/16 18:35 DOA651  drive index 5  cannot write image to media id...
11/16 23:22 DOA878  drive index 2  cannot write image to media id...
11/17 18:37 DOA860  drive index 2  cannot write image to media id...
11/19 19:45 DOA773  drive index 2  cannot write image to media id...
11/20 02:34 DOA773  drive index 2  cannot write image to media id...
11/20 06:58 DOA763  drive index 2  cannot write image to media id...

I'm having drive index 2 replaced tomorrow, although it didn't stop
the errors in drive index 5.  Does anyone know of this problem and if
it could be related to patch 363?  Any recommendations on what patch
I should jump to assuming that it may be related to the patch?  If I
go directly to 3.4, will I be able to restore my data that was backed
up with 3.2?

Thanks for any feedback.
Regards,
Kathy


Kathy Collins
Coral Energy, L.L.P
Phone: 713.230.3426
kcollins AT coral-energy DOT com




<Prev in Thread] Current Thread [Next in Thread>
  • [Veritas-bu] media write errors - 84, Collins , Kathy KCollins <=