Veritas-bu

[Veritas-bu] Cleaning Frequency

2003-03-18 07:54:51
Subject: [Veritas-bu] Cleaning Frequency
From: BrochF AT europe.stortek DOT com (Brochart, Fabrice)
Date: Tue, 18 Mar 2003 12:54:51 -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_01C2ED4D.90CE0240
Content-Type: text/plain;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

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

-----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


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

Phil Weber=20
Egg Distributed Hosts - UNIX Systems Engineer=20
Phone: 01384 26 4136=20
Mobile:=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


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


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.



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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">


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

  have<BR>received it in error, please notify the sender by replying=20
  with<BR>'received in error' as the subject and then delete it from=20
  your<BR>mailbox.<BR></BLOCKQUOTE></FONT></CODE></BODY></HTML>

------_=_NextPart_001_01C2ED4D.90CE0240--

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