Veritas-bu

[Veritas-bu] Addendum to Calendar Based Scheduling Question Posted Earlier

2003-02-21 13:37:07
Subject: [Veritas-bu] Addendum to Calendar Based Scheduling Question Posted Earlier
From: blacksmith AT rogers DOT com (Double Black)
Date: Fri, 21 Feb 2003 13:37:07 -0500
This is a multi-part message in MIME format.

------=_NextPart_000_0768_01C2D9AE.5427B320
Content-Type: text/plain;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

The problem under technote 248400 was fixed in NBU_MP_2

dB
  ----- Original Message -----=20
  From: Dennis Dwyer=20
  To: veritas-bu AT mailman.eng.auburn DOT edu=20
  Sent: Wednesday, February 05, 2003 11:10 AM
  Subject: [Veritas-bu] Addendum to Calendar Based Scheduling Question =
Posted Earlier


  OK ... At the risk of beating this beyond recognition, I went out to =
the Veritas support web site and found several hits on this issue. I =
found a Newsgroup article from Steve Staves titled "Another NBU 4.5 =
Calendar versus Frequency Question" from last August that, although =
short, was very to the point. There were other hits as well to support =
this but the bottom line is (my interpretation):

  #1: If a backup window for a given policy is large (like 5 or 12 =
hours) and the calendar based schedule crosses the midnight hour, you =
will probably get at least two backup schedules submitted for the same =
policy (that appears to be what's happening to us) because of the way =
NBU tracks the days and judges the frequency of the last backup.

  #2: According to multiple folks who have raised this question with =
Veritas ... Veritas doesn't recognize this as a major problem. Their =
solution (per Tech Note 248400) is to make the calendar based schedule =
window a short period of time rather than a long period of time. =
Preferably, just enough to start the policy. I have no idea how this =
will affect failures and restarts or policies that have the entire =
weekend as a window.

  #3: I find it difficult to believe that ArcServeIT (what I consider a =
lesser product to NBU DataCenter and the product I threw out to convert =
to NBU) does calendar based schedule the way I would expect it to be =
done and Veritas thinks their implementation is not a problem.

  I guess we'll still tinker with it off and on but until Veritas =
decides to address this (or at least publish in great detail how to =
implement it so it works every time) we are probably going back to =
Frequency Based Scheduling for the majority of our policies.

  I hope the Veritas folks that review this group will take this item =
back with you and realize the common perception of how Calendar Based =
Scheduling should work (and does work in other products) is not even =
close to what you've implemented in NBU 4.5. You either need to modify =
NBU Calendar Based Scheduling so it works like the users think it will =
work or ... dare I say it ... document how it does work so we will know =
what to expect.

  My thanks to Hampus Lind for his response that pretty much supports =
what I've been able to find in the research.

  Regards,
  Dennis

  Dennis F. Dwyer
  Manager, Systems Software
  Tampa Electric Company

  (813) 225-5181  - Voice
  (813) 275-3599  - FAX

  Visit our corporate website at www.tecoenergy.com

  The Colonel Says: "Time is not a test of the truth"
  Translation: Just because you've always done it that way, doesn't make =
it right
------=_NextPart_000_0768_01C2D9AE.5427B320
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=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2800.1126" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY style=3D"MARGIN-TOP: 2px; FONT: 10pt Arial; MARGIN-LEFT: 2px"=20
bgColor=3D#ffffff>
<DIV>The problem under technote 248400 was fixed in NBU_MP_2</DIV>
<DIV>&nbsp;</DIV>
<DIV>dB</DIV>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
  <DIV style=3D"FONT: 10pt arial">----- Original Message ----- </DIV>
  <DIV=20
  style=3D"BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: =
black"><B>From:</B>=20
  <A title=3Ddfdwyer AT tecoenergy DOT com =
href=3D"mailto:dfdwyer AT tecoenergy DOT com">Dennis=20
  Dwyer</A> </DIV>
  <DIV style=3D"FONT: 10pt arial"><B>To:</B> <A=20
  title=3Dveritas-bu AT mailman.eng.auburn DOT edu=20
  =
href=3D"mailto:veritas-bu AT mailman.eng.auburn DOT edu">veritas-bu AT mailman 
DOT eng.=
auburn.edu</A>=20
  </DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Sent:</B> Wednesday, February 05, =
2003 11:10=20
  AM</DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Subject:</B> [Veritas-bu] Addendum =
to=20
  Calendar Based Scheduling Question Posted Earlier</DIV>
  <DIV><BR></DIV>
  <DIV>OK ... At the risk of beating this beyond recognition, I went out =
to the=20
  Veritas support web site and found several hits on this issue. I found =
a=20
  Newsgroup article from Steve Staves titled "Another NBU 4.5 Calendar =
versus=20
  Frequency Question" from last August that, although short, was very to =
the=20
  point. There were other hits&nbsp;as well to support this but the =
bottom line=20
  is (my interpretation):</DIV>
  <DIV>&nbsp;</DIV>
  <DIV>#1: If a backup window for a given policy is large (like 5 or 12 =
hours)=20
  and the calendar based schedule crosses the midnight hour, you will =
probably=20
  get at least two backup schedules submitted for the same policy (that =
appears=20
  to be what's happening to us) because of the way NBU tracks the days =
and=20
  judges the frequency of the last backup.</DIV>
  <DIV>&nbsp;</DIV>
  <DIV>#2: According to multiple folks who have raised this question =
with=20
  Veritas ... Veritas doesn't recognize this as a major problem. Their =
solution=20
  (per Tech Note 248400) is to make the calendar based schedule window a =
short=20
  period of time rather than a long period of time. Preferably, just =
enough to=20
  start the policy. I have no idea how this will affect failures and =
restarts or=20
  policies that have the entire weekend as a window.</DIV>
  <DIV>&nbsp;</DIV>
  <DIV>#3: I find it difficult to believe that ArcServeIT (what I =
consider a=20
  lesser product to NBU DataCenter and the product I threw out to =
convert to=20
  NBU) does calendar based schedule the way I would expect it to be done =
and=20
  Veritas thinks their implementation is not a problem.</DIV>
  <DIV>&nbsp;</DIV>
  <DIV>I guess we'll still tinker with it off and on but until Veritas =
decides=20
  to address this (or at least publish in great detail how to implement =
it so it=20
  works every time) we are probably going back to Frequency Based =
Scheduling for=20
  the majority of our policies.</DIV>
  <DIV>&nbsp;</DIV>
  <DIV>I hope the Veritas folks that review this group will take this =
item back=20
  with you and realize the common perception of how Calendar Based =
Scheduling=20
  should work (and does work in other products) is not even close to =
what you've=20
  implemented in NBU 4.5. You either need to modify NBU Calendar Based=20
  Scheduling so it works like the users think it will work or ... dare I =
say it=20
  ... document how it does work so we will know what to expect.</DIV>
  <DIV>&nbsp;</DIV>
  <DIV>My thanks to Hampus Lind for his response that pretty much =
supports what=20
  I've been able to find in the research.</DIV>
  <DIV>&nbsp;</DIV>
  <DIV>Regards,</DIV>
  <DIV>Dennis</DIV>
  <DIV>&nbsp;</DIV>
  <DIV>Dennis F. Dwyer<BR>Manager, Systems Software<BR>Tampa Electric=20
  Company</DIV>
  <DIV>&nbsp;</DIV>
  <DIV>(813) 225-5181&nbsp; - Voice<BR>(813) 275-3599&nbsp; - FAX</DIV>
  <DIV>&nbsp;</DIV>
  <DIV>Visit our corporate website at <A=20
  href=3D"http://www.tecoenergy.com";>www.tecoenergy.com</A></DIV>
  <DIV>&nbsp;</DIV>
  <DIV>The Colonel Says: "Time is not a test of the =
truth"<BR>Translation: Just=20
  because you've always done it that way, doesn't make it=20
right</DIV></BLOCKQUOTE></BODY></HTML>

------=_NextPart_000_0768_01C2D9AE.5427B320--