--alternative_NB3192_30991
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
HP openview does not have to be installed or running on your system. It c=
an be run from a central server, it polls all the systems on a network, I=
f the drives are seen as thier own entity in a library , HP openview will=
poll them for status. When this happens, it will cause a stall on the de=
vice for less than half a seccocond, however in that time the tape keeps =
running, but NETBACKUP does not know what happened, and why its not at th=
e correct space on the tapes... This is what will cause an 84. =
I have had this happen in envioronments where no one knew about HP op=
enview running. Usually what indicates this is the case, you will have al=
l the reives give you an 84 at the same time, or within the same few secc=
onds. But there are plenty of other reasons for this to happen, if you kj=
eep getting 84s, its not cause of bad media, if the drives check out, and=
are clean, then you have problems somewhere else in the network, or in y=
our server configuration. =
Cheers, =
Jeremy
Thursday, November 17, 2005 11:25 AM
To: CLOWARJ AT Nationwide DOT com
cc: =
From: WebsterR AT mont.disa DOT mil
Subject: RE: [Veritas-bu] status 84 - writing header block, 1117
I have seen a few errors 84 as well. How can you tell if the HP openview=
is installed and running on your system? =
Thanks, =
-----Original Message----- =
From: veritas-bu-admin AT mailman.eng.auburn DOT edu =
[mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu]On Behalf Of =
CLOWARJ AT Nationwide DOT com =
Sent: Thursday, November 17, 2005 9:42 AM =
To: Rolf C =
Cc: veritas-bu AT mailman.eng.auburn DOT edu =
Subject: Re: [Veritas-bu] status 84 - writing header block, 1117 =
Rolf, =
it could be any number of things, If you have Hp openview running it can=
=
poll your drives, and even a stall of just half a seccond while it polls =
can cause an 84. Do you see this happening in a pattern, where all your =
drives have them at roughly thesame time? I have been burried chest deep=
=
in these . Lemme know, There is more to it that just "Bad Media" =
Jeremy =
Thursday, November 17, 2005 10:37 AM =
To: veritas-bu AT mailman.eng.auburn DOT edu =
cc: =
From: "Rolf C" <rolfcolmer AT hotmail DOT com> =
Subject: [Veritas-bu] status 84 - writing header block, 1117 =
Hi all, =
Since some time all my backups fail with a status 84 and the following =
error: =
16:03:47.015 [4428.5964] <2> io_read_media_header: tapemark or blank tape=
=
encountered reading media header, drive index 0 =
16:03:47.031 [4428.5964] <2> io_write_media_header: drive index 0, writin=
g =
media header =
16:03:47.031 [4428.5964] <2> io_ioctl: command (5)MTREW 1 from =
(bptm.c.8612) =
on drive index 0 =
16:03:50.687 [4428.5964] <2> io_write_block: WriteFile() failed err =3D 1=
117 =
16:03:50.687 [4428.5964] <2> set_job_details: Done =
16:03:50.703 [4428.5964] <16> io_write_block: write error on media id =
A00005, drive index 0, writing header block, 1117 =
16:03:50.703 [4428.5964] <2> log_media_error: successfully wrote to error=
=
file - 11/17/05 16:03:50 A00005 0 WRITE_ERROR =
16:03:50.703 [4428.5964] <2> check_error_history: called from bptm line =
19524, EXIT_Status =3D 84 =
I have checked the cables, drivers and used serveral tapes. Cleaned the =
tapedrive with several cleaning cartridges and ran the Device Wizard =
several =
times. =
Anyone any idea how to solve this? =
_______________________________________________ =
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu =
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu =
_______________________________________________ =
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu =
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu =
--alternative_NB3192_30991
Content-Type: text/html; charset="us-ascii"
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE>RE: [Veritas-bu] status 84 - writing header block, 111=
7</TITLE>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dwindows-1=
252">
<META content=3D"MSHTML 6.00.2800.1515" name=3DGENERATOR></HEAD>
<BODY >
<DIV><FONT =
style=3D"FONT-WEIGHT: normal; FONT-SIZE: 8pt; COLOR: #000000; FONT-STYLE:=
normal; FONT-FAMILY: Tahoma">
<DIV> </DIV>
<DIV>HP openview does not have to be installed or running on your system.=
It can =
be run from a central server, it polls all the systems on a network, If t=
he =
drives are seen as thier own entity in a library , HP openview will poll =
them =
for status. When this happens, it will cause a stall on the device for le=
ss than =
half a seccocond, however in that time the tape keeps running, but NETBAC=
KUP =
does not know what happened, and why its not at the correct space on the =
tapes... This is what will cause an 84. </DIV>
<DIV> I have had this happen in envioronments where no =
one =
knew about HP openview running. Usually what indicates this is the case, =
you =
will have all the reives give you an 84 at the same time, or within the s=
ame few =
secconds. But there are plenty of other reasons for this to happen, if yo=
u kjeep =
getting 84s, its not cause of bad media, if the drives check out, and are=
clean, =
then you have problems somewhere else in the network, or in your server =
configuration. </DIV>
<DIV> </DIV>
<DIV> Cheers, </DIV>
<DIV> Jeremy</DIV>
<DIV> </DIV></FONT>
<DIV><I>Thursday, November 17, 2005 11:25 AM<BR>To: =
CLOWARJ AT Nationwide DOT com<BR>cc: <BR>From: WebsterR AT mont.disa DOT
mil<BR>Subject=
: RE: =
[Veritas-bu] status 84 - writing header block, 1117</I><BR><BR></DIV></DI=
V>
<P><FONT size=3D2>I have seen a few errors 84 as well. How can you =
tell if =
the HP openview is installed and running on your system?</FONT> </P>
<P><FONT size=3D2>Thanks,</FONT> </P><BR>
<P><FONT size=3D2>-----Original Message-----</FONT> <BR><FONT size=3D2>Fr=
om: =
veritas-bu-admin AT mailman.eng.auburn DOT edu</FONT> <BR><FONT size=3D2>[<A =
href=3D"mailto:veritas-bu-admin AT mailman.eng.auburn DOT
edu">mailto:veritas-bu=
-admin AT mailman.eng.auburn DOT edu</A>]On =
Behalf Of</FONT> <BR><FONT size=3D2>CLOWARJ AT Nationwide DOT com</FONT>
<BR><FO=
NT =
size=3D2>Sent: Thursday, November 17, 2005 9:42 AM</FONT> <BR><FONT size=3D=
2>To: =
Rolf C</FONT> <BR><FONT size=3D2>Cc: veritas-bu AT mailman.eng.auburn DOT
edu</F=
ONT> =
<BR><FONT size=3D2>Subject: Re: [Veritas-bu] status 84 - writing header b=
lock, =
1117</FONT> </P><BR><BR><BR><BR>
<P><FONT size=3D2>Rolf,</FONT> <BR><FONT size=3D2> it could be any n=
umber of =
things, If you have Hp openview running it can</FONT> <BR><FONT size=3D2>=
poll your =
drives, and even a stall of just half a seccond while it polls</FONT> <BR=
><FONT =
size=3D2>can cause an 84. Do you see this happening in a pattern, where a=
ll =
your</FONT> <BR><FONT size=3D2>drives have them at roughly thesame time?&=
nbsp; I =
have been burried chest deep</FONT> <BR><FONT size=3D2>in these . Lemme k=
now, =
There is more to it that just "Bad Media"</FONT> </P>
<P><FONT size=3D2> Jeremy</FONT> </P>
<P><FONT size=3D2>Thursday, November 17, 2005 10:37 AM</FONT> <BR><FONT s=
ize=3D2>To: =
veritas-bu AT mailman.eng.auburn DOT edu</FONT> <BR><FONT size=3D2>cc:</FONT>
<B=
R><FONT =
size=3D2>From: "Rolf C" <rolfcolmer AT hotmail DOT com></FONT> <BR><FONT =
size=3D2>Subject: [Veritas-bu] status 84 - writing header block, 1117</FO=
NT> =
</P><BR><BR>
<P><FONT size=3D2>Hi all,</FONT> </P>
<P><FONT size=3D2>Since some time all my backups fail with a status 84 an=
d the =
following</FONT> <BR><FONT size=3D2>error:</FONT> </P>
<P><FONT size=3D2>16:03:47.015 [4428.5964] <2> io_read_media_header=
: =
tapemark or blank tape</FONT> <BR><FONT size=3D2>encountered reading medi=
a header, =
drive index 0</FONT> <BR><FONT size=3D2>16:03:47.031 [4428.5964] <2>=
; =
io_write_media_header: drive index 0, writing</FONT> <BR><FONT size=3D2>m=
edia =
header</FONT> <BR><FONT size=3D2>16:03:47.031 [4428.5964] <2> io_io=
ctl: =
command (5)MTREW 1 from</FONT> <BR><FONT size=3D2>(bptm.c.8612)</FONT> <B=
R><FONT =
size=3D2>on drive index 0</FONT> <BR><FONT size=3D2>16:03:50.687 [4428.59=
64] =
<2> io_write_block: WriteFile() failed err =3D 1117</FONT> <BR><FON=
T =
size=3D2>16:03:50.687 [4428.5964] <2> set_job_details: Done</FONT> =
<BR><FONT =
size=3D2>16:03:50.703 [4428.5964] <16> io_write_block: write error =
on media =
id</FONT> <BR><FONT size=3D2>A00005, drive index 0, writing header block,=
=
1117</FONT> <BR><FONT size=3D2>16:03:50.703 [4428.5964] <2> log_med=
ia_error: =
successfully wrote to error</FONT> <BR><FONT size=3D2>file - 11/17/05 16:=
03:50 =
A00005 0 WRITE_ERROR</FONT> <BR><FONT size=3D2>16:03:50.703 [4428.5964] &=
lt;2> =
check_error_history: called from bptm line</FONT> <BR><FONT size=3D2>1952=
4, =
EXIT_Status =3D 84</FONT> </P>
<P><FONT size=3D2>I have checked the cables, drivers and used serveral ta=
pes. =
Cleaned the</FONT> <BR><FONT size=3D2>tapedrive with several cleaning car=
tridges =
and ran the Device Wizard</FONT> <BR><FONT size=3D2>several</FONT> <BR><F=
ONT =
size=3D2>times.</FONT> </P>
<P><FONT size=3D2>Anyone any idea how to solve this?</FONT> </P><BR>
<P><FONT size=3D2>_______________________________________________</FONT> =
<BR><FONT =
size=3D2>Veritas-bu maillist - =
Veritas-bu AT mailman.eng.auburn DOT edu</FONT> <BR><FONT size=3D2> <A =
href=3D"http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu"; =
target=3D_blank>http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu=
</A></FONT> =
</P>
<P><FONT size=3D2>_______________________________________________</FONT> =
<BR><FONT =
size=3D2>Veritas-bu maillist - =
Veritas-bu AT mailman.eng.auburn DOT edu</FONT> <BR><FONT size=3D2><A =
href=3D"http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu"; =
target=3D_blank>http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu=
</A></FONT> =
</P></BODY></HTML>
--alternative_NB3192_30991--
|
