This is a multipart message in MIME format.
--=_alternative 005D9D6B86256E31_=
Content-Type: text/plain; charset="us-ascii"
I see the logic, but this is not what I've experienced.
I've done this with a window for each schedule, each evening, one after
another (similar to the Fri night and sat night example), and with one
window for each schedule that spans from Fri night all the way until early
Mon morning (with 3 and 24 days for frequencies). Either way, works the
same way... a normal rotation of fulls and incrementals, with monthly
fulls REPLACING weekly fulls whenever needed.
It appears the scheduler is smart enough to deal with this.
The only issue I can foresee is if you didn't have the windows open at the
same time and had the shorter frequency open before the longer, this would
cause the weekly to run on a night when the monthly would be due but can't
run yet because the window is not open. If the weekly finished while the
window for the monthly was still open, the monthly would start and give
you the two full backups, one after the other. If the window for the
monthly closed before the weekly finished, you'd miss your monthly backup.
That's why I pointed out to use the "same time window" for the weekly and
the monthly.
- Scott
Wayne T Smith <WTSmith AT maine DOT edu>
Sent by: veritas-bu-admin AT mailman.eng.auburn DOT edu
02/04/2004 01:56 PM
To: veritas-bu AT mailman.eng.auburn DOT edu
cc:
Subject: Re: [Veritas-bu] Scheduling?
scott.kendall AT abbott DOT com wrote, in part:
> weekly on fri night and sat night with freq set to 2 or 3 days.
> monthly also set to fri and sat, same time window, with freq set to
> 23 or 24 days and so on...
>
> this allows it to run fri and then retry sat if it fails on fri. with
> the shorter frequency, it makes it run a full on fri even if someone
> manually launched a full on, for example, tuesday (instead of going 10
> days now in this example between fulls). it also "shifts" the backup
> back to fri on the following week after it fails on a fri and then
> runs ok on sat, instead of now running every sat.
But if both freq sets are due, the longer will run on Friday and then
the other will run on Saturday ... so you'll get two backups some weeks.
Maybe what you wanted; maybe not. ;-)
cheers, wayne
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
--=_alternative 005D9D6B86256E31_=
Content-Type: text/html; charset="us-ascii"
<br><font size=2 face="Arial">I see the logic, but this is not what I've
experienced.</font>
<br>
<br><font size=2 face="Arial">I've done this with a window for each schedule,
each evening, one after another (similar to the Fri night and sat night
example), and with one window for each schedule that spans from Fri night all
the way until early Mon morning (with 3 and 24 days for frequencies).
Either way, works the same way... a normal rotation of fulls and
incrementals, with monthly fulls REPLACING weekly fulls whenever needed.</font>
<br>
<br><font size=2 face="Arial">It appears the scheduler is smart enough to deal
with this.</font>
<br>
<br><font size=2 face="Arial">The only issue I can foresee is if you didn't
have the windows open at the same time and had the shorter frequency open
before the longer, this would cause the weekly to run on a night when the
monthly would be due but can't run yet because the window is not open. If
the weekly finished while the window for the monthly was still open, the
monthly would start and give you the two full backups, one after the other.
If the window for the monthly closed before the weekly finished, you'd
miss your monthly backup. That's why I pointed out to use the "same
time window" for the weekly and the monthly.</font>
<br>
<br>
<br><font size=2 face="Arial">- Scott</font>
<br>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td>
<td><font size=1 face="sans-serif"><b>Wayne T Smith <WTSmith AT maine DOT
edu></b></font>
<br><font size=1 face="sans-serif">Sent by: veritas-bu-admin AT
mailman.eng.auburn DOT edu</font>
<p><font size=1 face="sans-serif">02/04/2004 01:56 PM</font>
<br>
<td><font size=1 face="Arial"> </font>
<br><font size=1 face="sans-serif"> To:
veritas-bu AT mailman.eng.auburn DOT edu</font>
<br><font size=1 face="sans-serif"> cc:
</font>
<br><font size=1 face="sans-serif"> Subject:
Re: [Veritas-bu] Scheduling?</font></table>
<br>
<br>
<br><font size=2 face="Courier New">scott.kendall AT abbott DOT com wrote, in
part:<br>
<br>
> weekly on fri night and sat night with freq set to 2 or 3 days. <br>
> monthly also set to fri and sat, same time window, with freq set to
<br>
> 23 or 24 days and so on...<br>
><br>
> this allows it to run fri and then retry sat if it fails on fri.
with <br>
> the shorter frequency, it makes it run a full on fri even if someone <br>
> manually launched a full on, for example, tuesday (instead of going 10 <br>
> days now in this example between fulls). it also "shifts"
the backup <br>
> back to fri on the following week after it fails on a fri and then <br>
> runs ok on sat, instead of now running every sat.<br>
<br>
<br>
But if both freq sets are due, the longer will run on Friday and then <br>
the other will run on Saturday ... so you'll get two backups some weeks. <br>
Maybe what you wanted; maybe not. ;-)<br>
<br>
cheers, wayne<br>
_______________________________________________<br>
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu<br>
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu<br>
</font>
<br>
<br>
--=_alternative 005D9D6B86256E31_=--
|
