------=_Part_13313_23846832.1139227879819
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Quick question,
I've recently started working in a new environment.
Previously I would have a policy with a schedule such on a calendar based
policy that looked like this:
MON: 10:00PM-6:00AM (inc)
TUE: 10:00PM-6:00AM (inc)
WED: 10:00PM-6:00AM (inc)
THU: 10:00PM-6:00AM (inc)
FRI: 10:00PM-6:00AM (inc)
SAT: 10:00PM-6:00AM (inc)
SUN: 10:00PM-6:00AM (full)
The client would only miss the backup window Error(196) if during that
entire time it could not access an available tape drive.
However,
With the new environment, it uses a frequency based schedule for its
incremental and full backups. Instead of specifying a specific time, for
the daily backups, it looks like this:
MON: 24 HOURS (the entire length from left to right)
TUE: 24 HOURS (the entire length from left to right)
WED: 24 HOURS (the entire length from left to right)
THU: 24 HOURS (the entire length from left to right)
FRI: 24 HOURS (the entire length from left to right)
SAT: 24 HOURS (the entire length from left to right)
SUN: 24 HOURS (the entire length from left to right)
At first, I thought it may be related to how long the job sits in the queue=
,
I tried increasing that from around 30,000 seconds to 72,000 seconds;
however, it does not appear to have solved the issue.
Should I move the policies to a calendar based system or is the problem
exhibited elsewhere?
Thanks,
Justin.
------=_Part_13313_23846832.1139227879819
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
<div>Quick question,</div>
<div> </div>
<div>I've recently started working in a new environment.</div>
<div> </div>
<div>Previously I would have a policy with a schedule such on a calendar ba=
sed policy that looked like this:</div>
<div> </div>
<div>MON: 10:00PM-6:00AM (inc)</div>
<div>TUE: 10:00PM-6:00AM (inc)<br>WED: 10:00PM-6:00AM (inc)<br>THU: 10:00PM=
-6:00AM (inc) </div>
<div>FRI: 10:00PM-6:00AM (inc)<br>SAT: 10:00PM-6:00AM (inc)<br>SUN: 10:00PM=
-6:00AM (full)</div>
<div> </div>
<div>The client would only miss the backup window Error(196) if during that=
entire time it could not access an available tape drive.</div>
<div> </div>
<div>However, </div>
<div> </div>
<div>With the new environment, it uses a frequency based schedule for its i=
ncremental and full backups. Instead of specifying a specific time, f=
or the daily backups, it looks like this:</div>
<div> </div>
<div>MON: 24 HOURS (the entire length from left to right)</div>
<div>TUE: 24 HOURS (the entire length from left to right)<br>WED: 24 HOURS =
(the entire length from left to right)<br>THU: 24 HOURS (the entire length =
from left to right)<br>FRI: 24 HOURS (the entire length from left to right)
<br>SAT: 24 HOURS (the entire length from left to right)<br>SUN: 24 HOURS (=
the entire length from left to right)</div>
<div> </div>
<div>At first, I thought it may be related to how long the job sits in the =
queue, I tried increasing that from around 30,000 seconds to 72,000 seconds=
; however, it does not appear to have solved the issue.</div>
<div> </div>
<div>Should I move the policies to a calendar based system or is the proble=
m exhibited elsewhere?</div>
<div> </div>
<div>Thanks,</div>
<div> </div>
<div>Justin.</div>
<div> </div>
<div> </div>
------=_Part_13313_23846832.1139227879819--
|
