The single most important thing to remember with calendar based backups is that
after midnight, it's a new day....
So consider these scenarios:
You have a backup job which kicks off every Friday, and the backup window opens
at 6PM and closes at 6AM the following day.
The job queues, starts and finishes before midnight. You will get a Status Code
0 (Successful Completion)
The job queues, starts and finishes well after midnight. You will get a Status
Code 0 (Successful Completion) because the job started during the allocated
backup window. Only starting a job matters with the window, not how long it
runs... except in the next two cases.....
The job queues, starts, runs into an issue and re-queues itself, starts and
finishes before midnight. You will again get a Status Code 0.
The job queues, starts, runs into an issue and re-queues itself except this
time doesn't get to start until after midnight.... Here is where the Retries
Allowed after Runday checkbox comes in.
If that box is checked, then the job will start (provided it is not outside the
6AM close of the backup window) and you will hopefully get a Status Code 0.
If that box is NOT checked, then your job will exit with a Status Code 196 (Job
Not Attempted because backup window closed) regardless of the backup window
closing at 6AM because with the calendar backup, the job can only run on the
day its assigned to... unless that little box is checked.
Hope this clears things up a bit.
________________________________________
From: veritas-bu-bounces AT mailman.eng.auburn DOT edu [veritas-bu-bounces AT
mailman.eng.auburn DOT edu] On Behalf Of Jorge Fábregas [jorge.fabregas AT
gmail DOT com]
Sent: Thursday, August 21, 2008 9:06 PM
To: veritas-bu AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] Calendar Schedules over Midnight & 6.5.2 issue
Hello everyone,
I'm new on this list and also starting with Netbackup so bare with me :)
As I was trying to understand what goes on when I have a calendar-based
schedule with a window that spans midnight I just found out there are some
issues with this & the latest 6.5.2. Please check this scenario...
I perform a full-weekly on Friday (Friday is the only runday) and the window
goes from Friday 6pm until Monday 5am. Assuming "Retries allowed after
runday" is unchecked and that by Friday midnight the job is still queued...
Will the job exit with a 196 exit-status at midnight? Is this the behaviour
now with 6.5.2? Was it always like this?
I used to think that by entering the queue (at Friday 6pm) it was going to
stay there , even after midnight, just as long as it was within the window
timeframe AND because it was started on its runday..it would stay there even
though the next day wasn't a runday. Apparently this changed in 6.5.2 (based
on what I've been reading) and it seems this is the correct behaviour ?
Thanks in advance,
Jorge
_______________________________________________
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
|
