--JlIu.4322FVmsW.1mgbMf.6K5NlMS
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary="----_=_NextPart_001_01C62B24.61E0BE5B"
content-class: urn:content-classes:message
------_=_NextPart_001_01C62B24.61E0BE5B
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Although it looks like each day is completely "wide open" for backups,
it could be misleading.
=20
Do you have a schedule for each day of the week that goes from
00:00-23:59:00?
or do you have an "incremental" schedule that goes from Monday 00:00 -
Friday 23:59:59
=20
if each day was entered in separately, (Monday=3D 00:00-23:59:59, =
Tuesday=3D
00:00-23:59:59, etc, etc) then any job that is in the queue at midnight,
any night, is going to fail with a 196.
=20
also, if each day is in one schedule (option 2 above) but the days were
entered individually (ie, select Monday, duration 24 hours, , select
Tuesday, duration 24 hours, etc) then you will get the same effect.
anything in the queue at midnight will fail with a 196........
=20
It won't fail with the 196 right at midnight, however....it will sit in
the queue untill a drive becomes available, then as soon as the drive it
available, it will fail.
=20
if you have the whole week in one schedule, click in the chart window
that shows the open backup window.....if you can click on each
individual day and have that day turn blue, then you'll have troubles.
if you click on any area and the entire window turns blue, then that
means you have one large window configured, which sounds more like what
you want....you may still get occasional 196 errors if you have jobs in
the queue at the point where the start and end of the entire window
rolls over.
=20
Paul
-----Original Message-----
From: veritas-bu-admin AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu] On Behalf Of Justin
Piszcz
Sent: February 6, 2006 7:11 AM
To: veritas-bu AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] Error(196) - Backup Window Closed
=09
=09
Quick question,
=20
I've recently started working in a new environment.
=20
Previously I would have a policy with a schedule such on a
calendar based policy that looked like this:
=20
MON: 10:00PM-6:00AM (inc)
TUE: 10:00PM-6:00AM (inc)
WED: 10:00PM-6:00AM (inc)
THU: 10:00PM-6:00AM (inc)=20
FRI: 10:00PM-6:00AM (inc)
SAT: 10:00PM-6:00AM (inc)
SUN: 10:00PM-6:00AM (full)
=20
The client would only miss the backup window Error(196) if
during that entire time it could not access an available tape drive.
=20
However,=20
=20
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:
=20
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)=20
SAT: 24 HOURS (the entire length from left to right)
SUN: 24 HOURS (the entire length from left to right)
=20
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.
=20
Should I move the policies to a calendar based system or is the
problem exhibited elsewhere?
=20
Thanks,
=20
Justin.
=20
=20
------_=_NextPart_001_01C62B24.61E0BE5B
Content-Type: text/html;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE>Message</TITLE>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2800.1170" name=3DGENERATOR></HEAD>
<BODY>
<DIV><FONT face=3DArial color=3D#800000 size=3D2><SPAN=20
class=3D173274313-06022006>Although it looks like each day is completely =
"wide=20
open" for backups, it could be misleading.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#800000 size=3D2><SPAN=20
class=3D173274313-06022006></SPAN></FONT> </DIV>
<DIV><FONT face=3DArial color=3D#800000 size=3D2><SPAN =
class=3D173274313-06022006>Do you=20
have a schedule for each day of the week that goes from=20
00:00-23:59:00?</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#800000 size=3D2><SPAN =
class=3D173274313-06022006>or do=20
you have an "incremental" schedule that goes from Monday 00:00 - Friday=20
23:59:59</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#800000 size=3D2><SPAN=20
class=3D173274313-06022006></SPAN></FONT> </DIV>
<DIV><FONT face=3DArial color=3D#800000 size=3D2><SPAN =
class=3D173274313-06022006>if=20
each day was entered in separately, (Monday=3D 00:00-23:59:59, =
Tuesday=3D=20
00:00-23:59:59, etc, etc) then any job that is in the queue at midnight, =
any=20
night, is going to fail with a 196.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#800000 size=3D2><SPAN=20
class=3D173274313-06022006></SPAN></FONT> </DIV>
<DIV><FONT face=3DArial color=3D#800000 size=3D2><SPAN =
class=3D173274313-06022006>also,=20
if each day is in one schedule (option 2 above) but the days were =
entered=20
individually (ie, select Monday, duration 24 hours, , select Tuesday, =
duration=20
24 hours, etc) then you will get the same effect.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#800000 size=3D2><SPAN=20
class=3D173274313-06022006>anything in the queue at midnight will fail =
with a=20
196........</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#800000 size=3D2><SPAN=20
class=3D173274313-06022006></SPAN></FONT> </DIV>
<DIV><FONT face=3DArial color=3D#800000 size=3D2><SPAN =
class=3D173274313-06022006>It=20
won't fail with the 196 right at midnight, however....it will sit in the =
queue=20
untill a drive becomes available, then as soon as the drive it =
available, it=20
will fail.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#800000 size=3D2><SPAN=20
class=3D173274313-06022006></SPAN></FONT> </DIV>
<DIV><FONT face=3DArial color=3D#800000 size=3D2><SPAN =
class=3D173274313-06022006>if you=20
have the whole week in one schedule, click in the chart window that =
shows the=20
open backup window.....if you can click on each individual day and have =
that day=20
turn blue, then you'll have troubles.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#800000 size=3D2><SPAN =
class=3D173274313-06022006>if you=20
click on any area and the entire window turns blue, then that means you =
have one=20
large window configured, which sounds more like what you want....you may =
still=20
get occasional 196 errors if you have jobs in the queue at the point =
where the=20
start and end of the entire window rolls over.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#800000 size=3D2><SPAN=20
class=3D173274313-06022006></SPAN></FONT> </DIV>
<DIV><FONT face=3DArial color=3D#800000 size=3D2><SPAN=20
class=3D173274313-06022006>Paul</SPAN></FONT></DIV>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #800000 2px =
solid; MARGIN-RIGHT: 0px">
<DIV></DIV>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft><FONT=20
face=3DTahoma size=3D2>-----Original Message-----<BR><B>From:</B>=20
veritas-bu-admin AT mailman.eng.auburn DOT edu=20
[mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu] <B>On Behalf Of =
</B>Justin=20
Piszcz<BR><B>Sent:</B> February 6, 2006 7:11 AM<BR><B>To:</B>=20
veritas-bu AT mailman.eng.auburn DOT edu<BR><B>Subject:</B> [Veritas-bu] =
Error(196) -=20
Backup Window Closed<BR><BR></FONT></DIV>
<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 based=20
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:=20
10:00PM-6:00AM (inc) </DIV>
<DIV>FRI: 10:00PM-6:00AM (inc)<BR>SAT: 10:00PM-6:00AM (inc)<BR>SUN:=20
10:00PM-6:00AM (full)</DIV>
<DIV> </DIV>
<DIV>The client would only miss the backup window Error(196) if during =
that=20
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=20
incremental and full backups. Instead of specifying a specific =
time, for=20
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=20
(the entire length from left to right)<BR>THU: 24 HOURS (the entire =
length=20
from left to right)<BR>FRI: 24 HOURS (the entire length from left to =
right)=20
<BR>SAT: 24 HOURS (the entire length from left to right)<BR>SUN: 24 =
HOURS (the=20
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=20
queue, I tried increasing that from around 30,000 seconds to 72,000 =
seconds;=20
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 =
problem=20
exhibited elsewhere?</DIV>
<DIV> </DIV>
<DIV>Thanks,</DIV>
<DIV> </DIV>
<DIV>Justin.</DIV>
<DIV> </DIV>
<DIV> </DIV></BLOCKQUOTE></BODY></HTML>
=00
------_=_NextPart_001_01C62B24.61E0BE5B--
--JlIu.4322FVmsW.1mgbMf.6K5NlMS
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D
La version fran=C3=A7aise suit le texte anglais.
---------------------------------------------------------------------------=
---------
This email message from the Bank of Canada is given in good faith, and shal=
l not be
binding or construed as constituting any obligation on the part of the Bank.
This email may contain privileged and/or confidential information, and the =
Bank of
Canada does not waive any related rights. Any distribution, use, or copying=
of this
email or the information it contains by other than the intended recipient is
unauthorized. If you received this email in error please delete it immediat=
ely from
your system and notify the sender promptly by email that you have done so.=20
Recipients are advised to apply their own virus checks to this message upon=
receipt.
---------------------------------------------------------------------------=
---------
L'information communiqu=C3=A9e dans les courriels en provenance de la Banqu=
e du Canada
est soumise de bonne foi, mais elle ne saurait lier la Banque et ne doit au=
cunement
=C3=AAtre interpr=C3=A9t=C3=A9e comme constituant une obligation de sa part.
Le pr=C3=A9sent courriel peut contenir de l'information privil=C3=A9gi=C3=
=A9e ou confidentielle.
La Banque du Canada ne renonce pas aux droits qui s'y rapportent. Toute dif=
fusion,
utilisation ou copie de ce courriel ou des renseignements qu'il contient pa=
r une
personne autre que le ou les destinataires d=C3=A9sign=C3=A9s est interdite=
Si vous recevez
ce courriel par erreur, veuillez le supprimer imm=C3=A9diatement et envoyer=
sans d=C3=A9lai =C3=A0
l'exp=C3=A9diteur un message =C3=A9lectronique pour l'aviser que vous avez =
=C3=A9limin=C3=A9 de votre
ordinateur toute copie du courriel re=C3=A7u.
D=C3=A8s la r=C3=A9ception du pr=C3=A9sent message, le ou les destinataires=
doivent activer leur
programme de d=C3=A9tection de virus pour =C3=A9viter toute contamination p=
ossible.
--JlIu.4322FVmsW.1mgbMf.6K5NlMS--
|
