This is a multipart message in MIME format.
--=_alternative 007DF32D86256E14_=
Content-Type: text/plain; charset="us-ascii"
Since multiple clients can be in a class/policy, I'll modify this a
little...
>> "if ~ANY~ automatic schedule runs within a given class [for a client] then
all schedules will be considered to have recently ran [for that client]
for that same class"
Not necessarily, depends on the schedule (frequency and type). If it can
run a full or an incremental (e.g. they have open windows) and both are
due (e.g. it's been more than the specified frequency for the schedule),
it will run the full and will not run the incremental. Even when the full
is done, if the window is still open, the incremental will still not run
unless the window is open long enough for the frequency of the incremental
to make it due again. However, if the window is only open for the
incremental and it starts, but a window for the full opens while the
incremental is still running, the full should start if it's due to run,
and I believe only after the incremental finishes, assuming the window for
the full is still open.
- Scott
"Markham, Richard" <RLMarkham AT hafeleamericas DOT com>
Sent by: veritas-bu-admin AT mailman.eng.auburn DOT edu
01/07/2004 10:55 AM
To: "'Anderson, David'" <Anderson.David AT scrippshealth DOT org>,
"'veritas-bu AT mailman.eng.auburn DOT edu'" <veritas-bu AT mailman.eng.auburn
DOT edu>
cc:
Subject: RE: [Veritas-bu] RE: scheduled production backup did
not run
so basically, you are telling me that if ~ANY~ automatic schedule runs
within a given class then all schedules will be considered to have
recently
ran for that same class ?
-----Original Message-----
From: Anderson, David [mailto:Anderson.David AT scrippshealth DOT org]
Sent: Wednesday, January 07, 2004 10:50 AM
To: 'veritas-bu AT mailman.eng.auburn DOT edu'
Subject: [Veritas-bu] RE: scheduled production backup did not run
Bingo, you hit it right on the head. The backup already ran, therefore to
won't run again until the
elapsed time set in the Schedule Frequency has elapsed. Looks like your
NetBackup is doing just what it is supposed to be doing.
Snip: scheduled production backup did not run a backup under this schedule
did occur around 0100 hours
David Anderson
ScrippsHealth Information Services
anderson.david AT scrippshealth DOT org
"Scripps Information Security"
----------------------------------------------------------------------------
--
This e-mail and any files transmitted with it may contain privileged and
confidential information and are intended solely for the use of the
individual or entity to which they are addressed. If you are not the
intended recipient or the person responsible for delivering the e-mail to
the intended recipient, you are hereby notified that any dissemination or
copying of this e-mail or any of its attachment(s) is strictly prohibited.
If you have received this e-mail in error, please immediately notify the
sending individual or entity by e-mail and permanently delete the original
e-mail and attachment(s) from your computer system. Thank you for your
cooperation.
============================================================================
==
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
--=_alternative 007DF32D86256E14_=
Content-Type: text/html; charset="us-ascii"
<br><font size=2 face="Arial">Since multiple clients can be in a class/policy,
I'll modify this a little...</font>
<br>
<br><font size=2 face="Arial">>> "</font><font size=2 face="Courier
New">if ~ANY~ automatic schedule runs within a given class [for a client] then
all schedules will be considered to have recently ran [for that client] for
that same class"</font>
<br>
<br><font size=2 face="Courier New">Not necessarily, depends on the schedule
(frequency and type). If it can run a full or an incremental (e.g. they
have open windows) and both are due (e.g. it's been more than the specified
frequency for the schedule), it will run the full and will not run the
incremental. Even when the full is done, if the window is still open, the
incremental will still not run unless the window is open long enough for the
frequency of the incremental to make it due again. However, if the window
is only open for the incremental and it starts, but a window for the full opens
while the incremental is still running, the full should start if it's due to
run, and I believe only after the incremental finishes, assuming the window for
the full is still open.</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>"Markham, Richard"
<RLMarkham AT hafeleamericas DOT com></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">01/07/2004 10:55 AM</font>
<br>
<td><font size=1 face="Arial"> </font>
<br><font size=1 face="sans-serif"> To:
"'Anderson, David'" <Anderson.David AT
scrippshealth DOT org>, "'veritas-bu AT mailman.eng.auburn DOT
edu'" <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] RE: scheduled production backup did not
run</font></table>
<br>
<br>
<br><font size=2 face="Courier New">so basically, you are telling me that if
~ANY~ automatic schedule runs<br>
within a given class then all schedules will be considered to have recently<br>
ran for that same class ?<br>
<br>
-----Original Message-----<br>
From: Anderson, David [mailto:Anderson.David AT scrippshealth DOT org]<br>
Sent: Wednesday, January 07, 2004 10:50 AM<br>
To: 'veritas-bu AT mailman.eng.auburn DOT edu'<br>
Subject: [Veritas-bu] RE: scheduled production backup did not run<br>
<br>
<br>
Bingo, you hit it right on the head. The backup already ran, therefore
to<br>
won't run again until the<br>
elapsed time set in the Schedule Frequency has elapsed. Looks like
your<br>
NetBackup is doing just what it is supposed to be doing.<br>
<br>
Snip: scheduled production backup did not run a backup under this schedule<br>
did occur around 0100 hours<br>
<br>
David Anderson<br>
ScrippsHealth Information Services<br>
anderson.david AT scrippshealth DOT org<br>
<br>
<br>
<br>
"Scripps Information Security" <br>
----------------------------------------------------------------------------<br>
--<br>
This e-mail and any files transmitted with it may contain privileged and<br>
confidential information and are intended solely for the use of the<br>
individual or entity to which they are addressed. If you are not the<br>
intended recipient or the person responsible for delivering the e-mail to<br>
the intended recipient, you are hereby notified that any dissemination or<br>
copying of this e-mail or any of its attachment(s) is strictly prohibited.<br>
If you have received this e-mail in error, please immediately notify the<br>
sending individual or entity by e-mail and permanently delete the original<br>
e-mail and attachment(s) from your computer system. Thank you for your<br>
cooperation.<br>
<br>
<br>
============================================================================<br>
==<br>
<br>
_______________________________________________<br>
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu<br>
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu<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 007DF32D86256E14_=--
|
