Veritas-bu

[Veritas-bu] Cleaning Frequency

2003-03-18 16:14:47
Subject: [Veritas-bu] Cleaning Frequency
From: scott.kendall AT abbott DOT com (scott.kendall AT abbott DOT com)
Date: Tue, 18 Mar 2003 15:14:47 -0600
This is a multipart message in MIME format.
--=_alternative 0074B2FA86256CED_=
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

I haven't seen this happen with the L700 since they, according to release=20
notes from a patch over a year ago, added support for hardware cleaning on =

the L700.  You had to have a minimum firmware level on the drives and=20
library, along with the patch that added the support.  Sorry, I can't=20
remember what patch, but it was a 3.4 patch.  The readme specifically said =

STK L700 (or maybe it was STK L-series), so I wouldn't expect it to work=20
this way for any other libraries.

The way it was described to me was that the newer firmware caused the=20
drive to report a specific code when it was being cleaned.  When NetBackup =

sees that code, instead of downing the drive, it waits and then retries.


- Scott





Douglas Ritschel <dritschel62 AT yahoo DOT com>
Sent by: veritas-bu-admin AT mailman.eng.auburn DOT edu
03/18/2003 08:34 AM

=20
        To:     "Brochart, Fabrice" <BrochF AT europe.stortek DOT com>, 
"'Weber, P=
hilip'"=20
<Philip.Weber AT egg DOT com>, "NBUList \(E-mail\)"=20
<veritas-bu AT mailman.eng.auburn DOT edu>
        cc:=20
        Subject:        RE: [Veritas-bu] Cleaning Frequency


NetBackup gets confused if the robot's autocleaning
inserts a cleaning tape in a drive at the same time
NetBackup attempts to use the drive. There is a
collision and NetBackup marks the drive as down.=20



--- "Brochart, Fabrice" <BrochF AT europe.stortek DOT com>
wrote:
> Hi,
>=20
> Effectively, you must not clean your DLT so often.
>=20
> Why you don't use robotic cleaning ??
>=20
> Disable TapeAlert,AutoClean Veritas, and use robotic
> autocleaning, which is
> the better, you can trust me.
>=20
> Hth
>=20
> F@b
>=20
> -----Message d'origine-----
> De : Weber, Philip [mailto:Philip.Weber AT egg DOT com]
> Envoy=E9 : mardi 18 mars 2003 13:36
> =C0 : NBUList (E-mail)
> Objet : [Veritas-bu] Cleaning Frequency
>=20
>=20
> Hi all,
>=20
> We are running Netbackup 3.4 with an L700 tape robot
> populated with DLT7000
> drives.
>=20
> After running out of cleaning tapes & so not
> cleaning drives for several
> weeks, I found that the robot was not complaining
> about many drives needing
> cleaning & so investigated.  I found that Netbackup
> was set to clean these
> every 24 hours which seems far too often - I have
> upped this to 168 hours
> for now.
>=20
> Reading the DLT handbook, it seems to me that we
> shouldn't be cleaning our
> drives automatically at all, just manually cleaning
> if a particular problem
> with a drive.
>=20
> What do other people do with these drives?
>=20
> thanks, Phil
>=20
> Phil Weber=20
> Egg Distributed Hosts - UNIX Systems Engineer=20
> Phone: 01384 26 4136=20
> Mobile:=20
>=20
> -----Original Message-----
> From: Marianne Van den Berg
> [mailto:Marianne.VandenBerg AT mgxgroup DOT com]
> Sent: 03 March 2003 14:13
> To: NBUList (E-mail)
> Subject: [Veritas-bu] bpcr=5Fconnect timeout during
> select after 60 seconds
>=20
>=20
> Hi=20
>=20
> My customer is getting the above message in bpbrm on
> the media server since
> last night (Everything has been working fine all
> along).
> 2 streams are backed up on a W2K client - 1 stream
> backs up fine, the 2nd
> fails with code 54 after 1 minute. The timeouts in
> the media server's
> bp.conf (Tru64) are as follows :=20
> CLIENT=5FCONNECT=5FTIMEOUT =3D 7200
> CLIENT=5FREAD=5FTIMEOUT =3D 7200
>=20
> This is a normal scheduled backup. When the streams
> are limited to 1, the
> backup works fine - it only happens when multiple
> streams are backed up.=20
> I've checked all the bpclntcmd's between the media
> server and the client -
> everything resolves fine. No errors in bpcd log on
> client (all exit code
> 0's).
> (NBU 3.4 patch 4.)
>=20
> Any ideas about the 60 sec timeout?
>=20
> Regards
>=20
> Marianne van den Berg=20
> Senior Support Engineer=20
> MGX Solutions=20
> Tel:  +27 11 695 2064=20
> Fax: +27 11 695 2291=20
> Mobile: +27 82 468 8107=20
> mailto: marianne.vandenberg AT mgxsolutions.co DOT za
> <mailto:marianne.vandenberg AT mgxsolutions.co DOT za>=20
> This e-mail and attachments relating thereto, is
> intended for the
> above-mentioned recipient. If you have received this
> e-mail in error, kindly
> notify the sender and delete it immediately as it
> contains information
> relating to the official business of MGX Solutions
> (Pty) Limited, which is
> confidential, legally privileged and proprietary to
> MGX Solutions (Pty)
> Limited. MGX Solutions (Pty) Limited does not own
> and endorse any other
> content. The views and opinions expressed in this
> e-mail are those of the
> sender unless clearly stated as being those of MGX
> Solutions (Pty) Limited.
>=20
>=20
>=20
>=20
> This private and confidential e-mail has been sent
> to you by Egg.
> The Egg group of companies includes Egg Banking plc
> (registered no. 2999842), Egg Financial Products Ltd
> (registered
> no. 3319027) and Egg Investments Ltd (registered no.
> 3403963) which
> carries out investment business on behalf of Egg and
> is regulated
> by the Financial Services Authority.=20
> Registered in England and Wales. Registered offices:
> 1 Waterhouse Square,
> 138-142 Holborn, London EC1N 2NA.
> If you are not the intended recipient of this e-mail
> and have
> received it in error, please notify the sender by
> replying with
> 'received in error' as the subject and then delete
> it from your
> mailbox.
>=20
>=20
>=20


=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F
Do you Yahoo!?
Yahoo! Platinum - Watch CBS' NCAA March Madness, live on your desktop!
http://platinum.yahoo.com
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu



--=_alternative 0074B2FA86256CED_=
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable


<br><font size=3D2 face=3D"Arial">I haven't seen this happen with the L700 =
since they, according to release notes from a patch over a year ago, added =
support for hardware cleaning on the L700. &nbsp;You had to have a minimum =
firmware level on the drives and library, along with the patch that added t=
he support. &nbsp;Sorry, I can't remember what patch, but it was a 3.4 patc=
h. &nbsp;The readme specifically said STK L700 (or maybe it was STK L-serie=
s), so I wouldn't expect it to work this way for any other libraries.</font>
<br>
<br><font size=3D2 face=3D"Arial">The way it was described to me was that t=
he newer firmware caused the drive to report a specific code when it was be=
ing cleaned. &nbsp;When NetBackup sees that code, instead of downing the dr=
ive, it waits and then retries.</font>
<br>
<br>
<br><font size=3D2 face=3D"Arial">- Scott</font>
<br>
<br>
<br>
<br>
<table width=3D100%>
<tr valign=3Dtop>
<td>
<td><font size=3D1 face=3D"sans-serif"><b>Douglas Ritschel &lt;dritschel62@=
yahoo.com&gt;</b></font>
<br><font size=3D1 face=3D"sans-serif">Sent by: veritas-bu-admin AT mailman DOT 
en=
g.auburn.edu</font>
<p><font size=3D1 face=3D"sans-serif">03/18/2003 08:34 AM</font>
<br>
<td><font size=3D1 face=3D"Arial">&nbsp; &nbsp; &nbsp; &nbsp; </font>
<br><font size=3D1 face=3D"sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; To: &nbs=
p; &nbsp; &nbsp; &nbsp;&quot;Brochart, Fabrice&quot; &lt;BrochF AT europe DOT 
stor=
tek.com&gt;, &quot;'Weber, Philip'&quot; &lt;Philip.Weber AT egg DOT com&gt;, 
&quo=
t;NBUList \(E-mail\)&quot; &lt;veritas-bu AT mailman.eng.auburn DOT 
edu&gt;</font>
<br><font size=3D1 face=3D"sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; cc: &nbs=
p; &nbsp; &nbsp; &nbsp;</font>
<br><font size=3D1 face=3D"sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; Subject:=
 &nbsp; &nbsp; &nbsp; &nbsp;RE: [Veritas-bu] Cleaning Frequency</font></tab=
le>
<br>
<br>
<br><font size=3D2 face=3D"Courier New">NetBackup gets confused if the robo=
t's autocleaning<br>
inserts a cleaning tape in a drive at the same time<br>
NetBackup attempts to use the drive. There is a<br>
collision and NetBackup marks the drive as down. &nbsp;<br>
<br>
<br>
<br>
--- &quot;Brochart, Fabrice&quot; &lt;BrochF AT europe.stortek DOT com&gt;<br>
wrote:<br>
&gt; Hi,<br>
&gt; &nbsp;<br>
&gt; Effectively, you must not clean your DLT so often.<br>
&gt; &nbsp;<br>
&gt; Why you don't use robotic cleaning ??<br>
&gt; &nbsp;<br>
&gt; Disable TapeAlert,AutoClean Veritas, and use robotic<br>
&gt; autocleaning, which is<br>
&gt; the better, you can trust me.<br>
&gt; &nbsp;<br>
&gt; Hth<br>
&gt; &nbsp;<br>
&gt; F@b<br>
&gt; <br>
&gt; -----Message d'origine-----<br>
&gt; De : Weber, Philip [mailto:Philip.Weber AT egg DOT com]<br>
&gt; Envoy=E9 : mardi 18 mars 2003 13:36<br>
&gt; =C0 : NBUList (E-mail)<br>
&gt; Objet : [Veritas-bu] Cleaning Frequency<br>
&gt; <br>
&gt; <br>
&gt; Hi all,<br>
&gt; &nbsp;<br>
&gt; We are running Netbackup 3.4 with an L700 tape robot<br>
&gt; populated with DLT7000<br>
&gt; drives.<br>
&gt; &nbsp;<br>
&gt; After running out of cleaning tapes &amp; so not<br>
&gt; cleaning drives for several<br>
&gt; weeks, I found that the robot was not complaining<br>
&gt; about many drives needing<br>
&gt; cleaning &amp; so investigated. &nbsp;I found that Netbackup<br>
&gt; was set to clean these<br>
&gt; every 24 hours which seems far too often - I have<br>
&gt; upped this to 168 hours<br>
&gt; for now.<br>
&gt; &nbsp;<br>
&gt; Reading the DLT handbook, it seems to me that we<br>
&gt; shouldn't be cleaning our<br>
&gt; drives automatically at all, just manually cleaning<br>
&gt; if a particular problem<br>
&gt; with a drive.<br>
&gt; &nbsp;<br>
&gt; What do other people do with these drives?<br>
&gt; &nbsp;<br>
&gt; thanks, Phil<br>
&gt; <br>
&gt; Phil Weber <br>
&gt; Egg Distributed Hosts - UNIX Systems Engineer <br>
&gt; Phone: 01384 26 4136 <br>
&gt; Mobile: <br>
&gt; <br>
&gt; -----Original Message-----<br>
&gt; From: Marianne Van den Berg<br>
&gt; [mailto:Marianne.VandenBerg AT mgxgroup DOT com]<br>
&gt; Sent: 03 March 2003 14:13<br>
&gt; To: NBUList (E-mail)<br>
&gt; Subject: [Veritas-bu] bpcr=5Fconnect timeout during<br>
&gt; select after 60 seconds<br>
&gt; <br>
&gt; <br>
&gt; Hi <br>
&gt; &nbsp;<br>
&gt; My customer is getting the above message in bpbrm on<br>
&gt; the media server since<br>
&gt; last night (Everything has been working fine all<br>
&gt; along).<br>
&gt; 2 streams are backed up on a W2K client - 1 stream<br>
&gt; backs up fine, the 2nd<br>
&gt; fails with code 54 after 1 minute. The timeouts in<br>
&gt; the media server's<br>
&gt; bp.conf (Tru64) are as follows : <br>
&gt; CLIENT=5FCONNECT=5FTIMEOUT =3D 7200<br>
&gt; CLIENT=5FREAD=5FTIMEOUT =3D 7200<br>
&gt; &nbsp;<br>
&gt; This is a normal scheduled backup. When the streams<br>
&gt; are limited to 1, the<br>
&gt; backup works fine - it only happens when multiple<br>
&gt; streams are backed up. <br>
&gt; I've checked all the bpclntcmd's between the media<br>
&gt; server and the client -<br>
&gt; everything resolves fine. No errors in bpcd log on<br>
&gt; client (all exit code<br>
&gt; 0's).<br>
&gt; (NBU 3.4 patch 4.)<br>
&gt; &nbsp;<br>
&gt; Any ideas about the 60 sec timeout?<br>
&gt; &nbsp;<br>
&gt; Regards<br>
&gt; &nbsp;<br>
&gt; Marianne van den Berg <br>
&gt; Senior Support Engineer <br>
&gt; MGX Solutions <br>
&gt; Tel: &nbsp;+27 11 695 2064 <br>
&gt; Fax: +27 11 695 2291 </font>
<br><font size=3D2 face=3D"Courier New">&gt; Mobile: +27 82 468 8107 <br>
&gt; mailto: marianne.vandenberg AT mgxsolutions.co DOT za<br>
&gt; &lt;mailto:marianne.vandenberg AT mgxsolutions.co DOT za&gt; <br>
&gt; This e-mail and attachments relating thereto, is<br>
&gt; intended for the<br>
&gt; above-mentioned recipient. If you have received this<br>
&gt; e-mail in error, kindly<br>
&gt; notify the sender and delete it immediately as it<br>
&gt; contains information<br>
&gt; relating to the official business of MGX Solutions<br>
&gt; (Pty) Limited, which is<br>
&gt; confidential, legally privileged and proprietary to<br>
&gt; MGX Solutions (Pty)<br>
&gt; Limited. MGX Solutions (Pty) Limited does not own<br>
&gt; and endorse any other<br>
&gt; content. The views and opinions expressed in this<br>
&gt; e-mail are those of the<br>
&gt; sender unless clearly stated as being those of MGX<br>
&gt; Solutions (Pty) Limited.<br>
&gt; <br>
&gt; &nbsp;<br>
&gt; <br>
&gt; <br>
&gt; This private and confidential e-mail has been sent<br>
&gt; to you by Egg.<br>
&gt; The Egg group of companies includes Egg Banking plc<br>
&gt; (registered no. 2999842), Egg Financial Products Ltd<br>
&gt; (registered<br>
&gt; no. 3319027) and Egg Investments Ltd (registered no.<br>
&gt; 3403963) which<br>
&gt; carries out investment business on behalf of Egg and<br>
&gt; is regulated<br>
&gt; by the Financial Services Authority. <br>
&gt; Registered in England and Wales. Registered offices:<br>
&gt; 1 Waterhouse Square,<br>
&gt; 138-142 Holborn, London EC1N 2NA.<br>
&gt; If you are not the intended recipient of this e-mail<br>
&gt; and have<br>
&gt; received it in error, please notify the sender by<br>
&gt; replying with<br>
&gt; 'received in error' as the subject and then delete<br>
&gt; it from your<br>
&gt; mailbox.<br>
&gt; <br>
&gt; <br>
&gt; <br>
<br>
<br>
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=
<br>
Do you Yahoo!?<br>
Yahoo! Platinum - Watch CBS' NCAA March Madness, live on your desktop!<br>
http://platinum.yahoo.com<br>
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F<br>
Veritas-bu maillist &nbsp;- &nbsp;Veritas-bu AT mailman.eng.auburn DOT edu<br>
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu<br>
</font>
<br>
<br>
--=_alternative 0074B2FA86256CED_=--

<Prev in Thread] Current Thread [Next in Thread>