[Veritas-bu] Cleaning Frequency

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_01C2ED4A.F18DA570
Content-Type: text/plain; charset="iso-8859-1"

Hi all,
 
We are running Netbackup 3.4 with an L700 tape robot populated with DLT7000
drives.
 
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.
 
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.
 
What do other people do with these drives?
 
thanks, Phil

Phil Weber 
Egg Distributed Hosts - UNIX Systems Engineer 
Phone: 01384 26 4136 
Mobile: 

-----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 
 
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 : 
CLIENT_CONNECT_TIMEOUT = 7200
CLIENT_READ_TIMEOUT = 7200
 
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. 
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.)
 
Any ideas about the 60 sec timeout?
 
Regards
 
Marianne van den Berg 
Senior Support Engineer 
MGX Solutions 
Tel:  +27 11 695 2064 
Fax: +27 11 695 2291 
Mobile: +27 82 468 8107 
mailto: marianne.vandenberg AT mgxsolutions.co DOT za
<mailto:marianne.vandenberg AT mgxsolutions.co DOT za> 
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.

 


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.  
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_01C2ED4A.F18DA570
Content-Type: text/html; charset="iso-8859-1"

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


<META content="MSHTML 6.00.2600.0" name=GENERATOR></HEAD>
<BODY style="COLOR: #000000; FONT-FAMILY: Comic Sans MS">
<DIV><SPAN class=045063412-18032003><FONT size=2>Hi all,</FONT></SPAN></DIV>
<DIV><SPAN class=045063412-18032003><FONT size=2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=045063412-18032003><FONT size=2>We are running Netbackup 3.4 
with an L700 tape robot populated with DLT7000 drives.</FONT></SPAN></DIV>
<DIV><SPAN class=045063412-18032003><FONT size=2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=045063412-18032003><FONT size=2>After running out of cleaning 
tapes &amp; so not cleaning drives for several weeks, I found that the robot 
was 
not complaining about many drives needing cleaning &amp; so investigated.&nbsp; 
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.</FONT></SPAN></DIV>
<DIV><SPAN class=045063412-18032003><FONT size=2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=045063412-18032003><FONT size=2>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.</FONT></SPAN></DIV>
<DIV><SPAN class=045063412-18032003><FONT size=2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=045063412-18032003><FONT size=2>What do other people do with 
these drives?</FONT></SPAN></DIV>
<DIV><SPAN class=045063412-18032003><FONT size=2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=045063412-18032003><FONT size=2>thanks, 
Phil</FONT></SPAN></DIV>
<P><B><FONT face=Arial size=2>Phil Weber</FONT></B> <BR><FONT face=Arial 
color=#808080 size=2>Egg Distributed Hosts - UNIX Systems Engineer</FONT> 
<BR><FONT face=Arial color=#808080 size=2>Phone: 01384 26 4136</FONT> <BR><FONT 
face=Arial color=#808080 size=2>Mobile: </FONT></P>
<DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma 
size=2>-----Original Message-----<BR><B>From:</B> Marianne Van den Berg 
[mailto:Marianne.VandenBerg AT mgxgroup DOT com]<BR><B>Sent:</B> 03 March 2003 
14:13<BR><B>To:</B> NBUList (E-mail)<BR><B>Subject:</B> [Veritas-bu] 
bpcr_connect timeout during select after 60 seconds<BR><BR></FONT></DIV>
<DIV><FONT size=2><SPAN class=625385013-03032003>Hi </SPAN></FONT></DIV>
<DIV><FONT size=2><SPAN class=625385013-03032003></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT size=2><SPAN class=625385013-03032003>My customer is getting the 
above message in bpbrm on the media server since last night (Everything has 
been 
working fine all along).</SPAN></FONT></DIV>
<DIV><FONT size=2><SPAN class=625385013-03032003>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 : 
</SPAN></FONT></DIV>
<DIV><FONT size=2><SPAN class=625385013-03032003>CLIENT_CONNECT_TIMEOUT = 
7200</SPAN></FONT></DIV>
<DIV><FONT size=2><SPAN class=625385013-03032003>CLIENT_READ_TIMEOUT = 
7200</SPAN></FONT></DIV>
<DIV><FONT size=2><SPAN class=625385013-03032003></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT size=2><SPAN class=625385013-03032003>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. </SPAN></FONT></DIV>
<DIV><FONT size=2><SPAN class=625385013-03032003>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).</SPAN></FONT></DIV>
<DIV><FONT size=2><SPAN class=625385013-03032003>(NBU 3.4 patch 
4.)</SPAN></FONT></DIV>
<DIV><FONT size=2><SPAN class=625385013-03032003></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT size=2><SPAN class=625385013-03032003>Any ideas about the 60 sec 
timeout?</SPAN></FONT></DIV>
<DIV><FONT size=2><SPAN class=625385013-03032003></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT size=2><SPAN class=625385013-03032003>Regards</SPAN></FONT></DIV>
<DIV><FONT size=2><SPAN class=625385013-03032003></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT size=2><SPAN class=625385013-03032003></SPAN></FONT><FONT 
size=2><STRONG>Marianne van den Berg <BR></STRONG>Senior Support Engineer 
<BR><STRONG>MGX&nbsp;Solutions <BR></STRONG>Tel:&nbsp; +27 11 695 2064 <BR>Fax: 
+27 11 695 2291 <BR>Mobile: +27 82 468 8107 <BR>mailto: <A 
href="mailto:marianne.vandenberg AT mgxsolutions.co DOT za">marianne.vandenberg 
AT mgxsolutions.co DOT za</A></DIV><FONT 
color=#800080 size=1>
<P align=justify><EM><STRONG>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.</STRONG></EM></P></FONT></FONT>
<DIV>&nbsp;</DIV><CODE><FONT SIZE=3><BR>
<BR>
This private and confidential e-mail has been sent to you by Egg.<BR>
The Egg group of companies includes Egg Banking plc<BR>
(registered no. 2999842), Egg Financial Products Ltd (registered<BR>
no. 3319027) and Egg Investments Ltd (registered no. 3403963) which<BR>
carries out investment business on behalf of Egg and is regulated<BR>
by the Financial Services Authority.  <BR>
Registered in England and Wales. Registered offices: 1 Waterhouse Square,<BR>
138-142 Holborn, London 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 with<BR>
'received in error' as the subject and then delete it from your<BR>
mailbox.<BR>
</FONT></CODE>
</BODY></HTML>

------_=_NextPart_001_01C2ED4A.F18DA570--