Veritas-bu

[Veritas-bu] Cleaning Frequency

2003-03-18 10:36:14
Subject: [Veritas-bu] Cleaning Frequency
From: BrochF AT europe.stortek DOT com (Brochart, Fabrice)
Date: Tue, 18 Mar 2003 15:36:14 -0000
This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C2ED64.1C17A7A0
Content-Type: text/plain;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable


You right, sometimes it did it.
NetBackup wait a while before downing the drive.
It depend of the clean number of the cleaning cartridge, but normally
NetBackup didn't Down the drive.

So here are the choice:=20
                                1=B0 TapeAlert (system)
                                2=B0 Cleaning Periodic
                                3=B0 AutoClean with Robotic

First, normally it should be the good choice, your system must support =
it.
Veritas doesn't seem to like it.(?)

Second choice : DLT ask when it need a cleaning , so if you clean it
periodically you may wait a long time between a demand from the drive =
and
the effective clean and it's destructive (abrasive) for the drive head, =
so
life time head is shorter.

Third choice : Good but as Douglas said ,sometimes NetBackup could down =
the
drive due to the time of cleaning (rarely but exist).

As you want.

F@b


-----Message d'origine-----
De : Douglas Ritschel [mailto:dritschel62 AT yahoo DOT com]
Envoy=E9 : mardi 18 mars 2003 15:35
=C0 : Brochart, Fabrice; 'Weber, Philip'; NBUList (E-mail)
Objet : 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_connect 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_CONNECT_TIMEOUT =3D 7200
> CLIENT_READ_TIMEOUT =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


__________________________________________________
Do you Yahoo!?
Yahoo! Platinum - Watch CBS' NCAA March Madness, live on your desktop!
http://platinum.yahoo.com

------_=_NextPart_001_01C2ED64.1C17A7A0
Content-Type: text/html;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2653.12">
<TITLE>RE: [Veritas-bu] Cleaning Frequency</TITLE>
</HEAD>
<BODY>
<BR>

<P><FONT SIZE=3D2>You right, sometimes it did it.</FONT>
<BR><FONT SIZE=3D2>NetBackup wait a while before downing the =
drive.</FONT>
<BR><FONT SIZE=3D2>It depend of the clean number of the cleaning =
cartridge, but normally NetBackup didn't Down the drive.</FONT>
</P>

<P><FONT SIZE=3D2>So here are the choice: </FONT>
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2>1=B0 =
TapeAlert (system)</FONT>
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2>2=B0 Cleaning =
Periodic</FONT>
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2>3=B0 =
AutoClean with Robotic</FONT>
</P>

<P><FONT SIZE=3D2>First, normally it should be the good choice, your =
system must support it. Veritas doesn't seem to like it.(?)</FONT>
</P>

<P><FONT SIZE=3D2>Second choice : DLT ask when it need a cleaning , so =
if you clean it periodically you may wait a long time between a demand =
from the drive and the effective clean and it's destructive (abrasive) =
for the drive head, so life time head is shorter.</FONT></P>

<P><FONT SIZE=3D2>Third choice : Good but as Douglas said ,sometimes =
NetBackup could down the drive due to the time of cleaning (rarely but =
exist).</FONT></P>

<P><FONT SIZE=3D2>As you want.</FONT>
</P>

<P><FONT SIZE=3D2>F@b</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>-----Message d'origine-----</FONT>
<BR><FONT SIZE=3D2>De : Douglas Ritschel [<A =
HREF=3D"mailto:dritschel62 AT yahoo DOT com">mailto:dritschel62 AT yahoo DOT 
com</A>]<=
/FONT>
<BR><FONT SIZE=3D2>Envoy=E9 : mardi 18 mars 2003 15:35</FONT>
<BR><FONT SIZE=3D2>=C0 : Brochart, Fabrice; 'Weber, Philip'; NBUList =
(E-mail)</FONT>
<BR><FONT SIZE=3D2>Objet : RE: [Veritas-bu] Cleaning Frequency</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>NetBackup gets confused if the robot's =
autocleaning</FONT>
<BR><FONT SIZE=3D2>inserts a cleaning tape in a drive at the same =
time</FONT>
<BR><FONT SIZE=3D2>NetBackup attempts to use the drive. There is =
a</FONT>
<BR><FONT SIZE=3D2>collision and NetBackup marks the drive as =
down.&nbsp; </FONT>
</P>
<BR>
<BR>

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

<P><FONT =
SIZE=3D2>__________________________________________________</FONT>
<BR><FONT SIZE=3D2>Do you Yahoo!?</FONT>
<BR><FONT SIZE=3D2>Yahoo! Platinum - Watch CBS' NCAA March Madness, =
live on your desktop!</FONT>
<BR><FONT SIZE=3D2><A HREF=3D"http://platinum.yahoo.com"; =
TARGET=3D"_blank">http://platinum.yahoo.com</A></FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C2ED64.1C17A7A0--

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