04-01-2013 09:36 AM
Hi All;
I have different policies for monthly backups and daily backups. For all daily policies, i excluded the last day of the month. When all the monthly backups run last day of the month, daily backups dont run until midnight. After midnight, all the daily jobs start running. How can i prevent this situation?
04-01-2013 10:40 AM
04-01-2013 12:29 PM
Please share schedule details, backup window for daily backup schedule.
04-01-2013 11:49 PM
I attached my schedules.
04-02-2013 01:30 AM
I've had a similar problem in the past - wr's post above covers the only solutions that I thought of at the time, although I'd be interested to hear if anyone has any other ways around it!
04-02-2013 04:35 AM
If i set my schedule to run until midnight, it wont be enough backup to finish. Therefore, i have to set it like this. I dont want to exclude both last day of the month and the day after last day because i can forget it excluded and backup may not be run.
04-02-2013 05:28 AM
04-02-2013 05:59 AM
>>If i set my schedule to run until midnight, it wont be enough backup to finish.
This is common misconception. Backup window is for start time not end time. If your backup does not complete before the window it is not going to be terminated.
04-02-2013 06:08 AM
This is common misconception. Backup window is for start time not end time. If your backup does not complete before the window it is not going to be terminated.
Are you sure? Can you explain it in details?
04-02-2013 06:23 AM
>>Are you sure? Can you explain it in details?
Yes, from experience I can say this is the way it works. We have some schedule windows that are a couple hours long but the actual backup job takes almost a full day.
Notice it is called a Start Window not a Backup Window.
"To define a time window during which jobs can start"
04-02-2013 06:24 AM
1) Your schedule starts from 22:00 -- 14:00 ( which means 22:00 to 00:00 is one day and 00:00 to 14:00 is another next day)
2) As you exclude 30th for April month. As windows starts from (30th April 22:00 to 1st May 14:00), here 30th April ends at 00:00.
3) But the window still active till 1st May 14:00 due to which backup runs during the active backup window which is (00:00 to 14:00 1st May).
04-02-2013 06:58 AM
I set daily backup frequency as a daily.
>> This is common misconception. Backup window is for start time not end time. If your backup does not complete before the window it is not going to be terminated.
Then, why are we getting "client backup was not attempted because backup window closed(196)" error? I set my exchange policies as they finish at 00:00 but if it is not completed before 00:00 i am getting the error message as i mentioned.
04-02-2013 07:11 AM
You need to look at the Detailed Status tab to see why the job is not starting at 6pm per the schedule. Perhaps your storage unit is busy for the whole 6 hours?
04-02-2013 07:37 AM
There are a lot of exchange policies starting at the same time. I think netbackup processes these policies from top to down. Policies getting error are the last ones in the policies list. They are waiting for other policies finished and after 00:00, they are getting error message as i mentioned above.
04-02-2013 07:55 AM
04-02-2013 08:08 AM
As Mark says, it sounds like the jobs are queuing - they need to start writing data before the end of the start window.
04-02-2013 08:14 AM
I know that i can solve my problem increasing streams. In fact, i want to learn that it is true or not what wr is said:
>> This is common misconception. Backup window is for start time not end time. If your backup does not complete before the window it is not going to be terminated.
04-02-2013 08:29 AM
04-02-2013 10:03 AM
Right, it's all a matter of Symantec semantics. :)
If the job doesn't start then it cannot finish within the window, thus your Status 196.
This behaviour is what leads folks to have huge start windows when what is really needed is better architecture. But that is hard in practice so most folks take the easy way out which creates your original problem - exclude date apparently not being honored (when in fact it is).
04-02-2013 10:31 AM