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_01C4F4EB.F3879F20
Content-Type: text/plain
You are absolutely correct Taylor. And we have tried repeatedly to do this,
but they don't understand. I'm still fighting the battle, but of course,
not getting very far. You add some very valuable information to this,
because of the open file issue... many times, it's a one off occurrance.
Especially since I have to go out and touch every client!
I have gotten some additional information from people, and am going to build
a 'standard' exclude list for problematic servers, and see if that helps.
But I want to keep it standard throughout the infrastructure (Wintel/Unix
would each have separate files). I appreciate all the time and help that I
get from you guys, you've made my job a lot easier.
Thanks again!
Jennifer
_____
From: Lewick, Taylor [mailto:tlewick AT hrblock DOT com]
Sent: Friday, January 07, 2005 10:54 AM
To: Jennifer Hooper; veritas-bu AT mailman.eng.auburn DOT edu
Subject: RE: [Veritas-bu] Excluding Files for Successful Jobs
The bigger issue here sounds like you need to educate management. You may
want to explain to them that you don't want to always exclude files that are
causing status 1s. They may just be open at that time, and sometimes during
the backup a process may not be using/opening those files, so you may
actually get a good backup of that file from time to time. Also, now, if
they are open, then they aren't backed up but you are notified. Now your
management is asking you to manually exclude every single file that can
cause a status 1 which can add a lot of complexity and time to managing your
backup infrastructure which is the whole reason you use a product like
NetBackup, to simplify (saying that with a bit of a grin, because we all
know how painful NetBackup-or any Enterprise Backup System-can be from time
to time).
This sounds like a management request along the lines of, "Fine, green,
yellow, red is great, but I only want to see green".
Pass that along to them, I'll take the heat since I am not employed by
them...
Taylor
------_=_NextPart_001_01C4F4EB.F3879F20
Content-Type: text/html
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<TITLE>SQL Restore issue...</TITLE>
<META content="MSHTML 6.00.2800.1479" name=GENERATOR>
<STYLE>@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.25in 1.0in 1.25in; }
P.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
LI.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
DIV.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
A:link {
COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlink {
COLOR: blue; TEXT-DECORATION: underline
}
A:visited {
COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlinkFollowed {
COLOR: blue; TEXT-DECORATION: underline
}
SPAN.EmailStyle17 {
COLOR: navy; FONT-FAMILY: Arial
}
DIV.Section1 {
page: Section1
}
</STYLE>
</HEAD>
<BODY lang=EN-US vLink=blue link=blue>
<DIV dir=ltr align=left><SPAN class=809390219-07012005><FONT face="Trebuchet
MS"
color=#000080 size=2>You are absolutely correct Taylor. And we have tried
repeatedly to do this, but they don't understand. I'm still fighting the
battle, but of course, not getting very far. You add some very valuable
information to this, because of the open file issue... many times, it's a
one off occurrance. Especially since I have to go out and touch every
client! </FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=809390219-07012005><FONT face="Trebuchet
MS"
color=#000080 size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=809390219-07012005><FONT face="Trebuchet
MS"
color=#000080 size=2>I have gotten some additional information from people, and
am going to build a 'standard' exclude list for problematic servers, and see if
that helps. But I want to keep it standard throughout the infrastructure
(Wintel/Unix would each have separate files). I appreciate all the time
and help that I get from you guys, you've made my job a lot
easier.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=809390219-07012005><FONT face="Trebuchet
MS"
color=#000080 size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=809390219-07012005><FONT face="Trebuchet
MS"
color=#000080 size=2>Thanks again!</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=809390219-07012005><FONT face="Trebuchet
MS"
color=#000080 size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=809390219-07012005><FONT face="Trebuchet
MS"
color=#000080 size=2>Jennifer</FONT></SPAN></DIV><BR>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> Lewick, Taylor
[mailto:tlewick AT hrblock DOT com] <BR><B>Sent:</B> Friday, January 07, 2005
10:54
AM<BR><B>To:</B> Jennifer Hooper;
veritas-bu AT mailman.eng.auburn DOT edu<BR><B>Subject:</B> RE: [Veritas-bu]
Excluding
Files for Successful Jobs<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV class=Section1>
<P class=MsoNormal><FONT face=Arial color=navy size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">The bigger issue here
sounds like you need to educate management. You may want to explain to
them that you don't want to always exclude files that are causing status
1s. They may just be open at that time, and sometimes during the backup a
process may not be using/opening those files, so you may actually get a good
backup of that file from time to time. Also, now, if they are open, then
they aren't backed up but you are notified. Now your management is asking
you to manually exclude every single file that can cause a status 1 which can
add a lot of complexity and time to managing your backup infrastructure which
is
the whole reason you use a product like NetBackup, to simplify (saying that
with
a bit of a grin, because we all know how painful NetBackup-or any Enterprise
Backup System-can be from time to time).</SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial color=navy size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY:
Arial"></SPAN></FONT> </P>
<P class=MsoNormal><FONT face=Arial color=navy size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">This sounds like a
management request along the lines of, "Fine, green, yellow, red is great, but
I
only want to see green".</SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial color=navy size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY:
Arial"></SPAN></FONT> </P>
<P class=MsoNormal><FONT face=Arial color=navy size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">Pass that along to
them, I'll take the heat since I am not employed by them...</SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial color=navy size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY:
Arial"></SPAN></FONT> </P>
<P class=MsoNormal><FONT face=Arial color=navy size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY:
Arial">Taylor</SPAN></FONT></P>
<P class=MsoNormal><FONT face="Times New Roman" size=3><SPAN
style="FONT-SIZE: 12pt"></SPAN></FONT> </P></DIV></BODY></HTML>
------_=_NextPart_001_01C4F4EB.F3879F20--
|
