Calendar Schedule issue
Created: 11 Dec 2012 | Updated: 22 Feb 2013 | 11 comments
This issue has been solved. See solution.
Hello - I have a policy with three VMs in it - it has Calendar based scheduling for daily differentials and weekly fulls.
Fulls run on a Sunday - recurring weekdays and diffs on the other 6 days recurring week days.
Yesterday due to a problem on these systems I was asked to postpone the Daily Diffs - so from the gui I cleared out all the recurring weekdays so nothing was selected - yet last night the backup still ran.
Anyone any idea why this has happened?
thanks
Discussion Filed Under:
Comments 11 Comments • Jump to latest comment
Probably best if we could see your policy:
bppllist policy_name -U
Can you confirm NB versions?
Regards Andy
"Have you still got the box it came in?"
Version is 7.0.1 - can't put the policy up due to Security issues. Diff Schedule is Calendar based and now has no days selected at all yet still ran last night.
How close to the backup going active did you change the policy schedule?
Was changed about 4 hours before
Policy Name:
Policy Type: FlashBackup-Windows
Active: yes
Effective date: 02/03/1991 19:25:54
File Restore Raw: yes
Mult. Data Streams: no
Client Encrypt: no
Checkpoint: no
Policy Priority: 30
Max Jobs/Policy: 3
Disaster Recovery: 0
Collect BMR info: no
Residence: ####
Volume Pool: #####
Server Group: *ANY*
Keyword: (none specified)
Data Classification: -
Residence is Storage Lifecycle Policy: no
Granular Restore Info: no
Ignore Client Direct: no
HW/OS/Client: VMware Virtual_Machi #####
VMware Virtual_Machi #####
VMware Virtual_Machi #####
Include: ALL_LOCAL_DRIVES
Schedule: Full_Weekly
Type: Full Backup
Maximum MPX: 3
Synthetic: 0
PFI Recovery: 0
Retention Level: 24 (10 days) 5 (3 months)
Number Copies: 2
Fail on Error: 0 0
Residence: #####
Volume Pool: ######
Server Group: *ANY* *ANY*
Calendar sched: Enabled
Sunday, Week 1
Monday, Week 1
Sunday, Week 2
Monday, Week 2
Sunday, Week 3
Monday, Week 3
Sunday, Week 4
Monday, Week 4
Sunday, Week 5
Monday, Week 5
EXCLUDE DATE 0 - 01/29/2011
EXCLUDE DATE 1 - 01/30/2011
EXCLUDE DATE 2 - 01/31/2011
EXCLUDE DATE 3 - 05/01/2011
EXCLUDE DATE 4 - 06/05/2011
EXCLUDE DATE 5 - 07/03/2011
EXCLUDE DATE 6 - 08/07/2011
EXCLUDE DATE 7 - 09/04/2011
EXCLUDE DATE 8 - 10/02/2011
EXCLUDE DATE 9 - 11/06/2011
EXCLUDE DATE 10 - 12/04/2011
EXCLUDE DATE 11 - 01/01/2012
EXCLUDE DATE 12 - 02/05/2012
EXCLUDE DATE 13 - 03/04/2012
EXCLUDE DATE 14 - 04/01/2012
EXCLUDE DATE 15 - 05/06/2012
EXCLUDE DATE 16 - 05/13/2012
EXCLUDE DATE 17 - 06/03/2012
EXCLUDE DATE 18 - 07/01/2012
EXCLUDE DATE 19 - 08/05/2012
EXCLUDE DATE 20 - 09/02/2012
EXCLUDE DATE 21 - 10/07/2012
EXCLUDE DATE 22 - 11/04/2012
EXCLUDE DATE 23 - 12/02/2012
EXCLUDE DATE 24 - 01/06/2013
EXCLUDE DATE 25 - 02/03/2013
Residence is Storage Lifecycle Policy: 0
Daily Windows:
Sunday 18:00:00 --> Monday 08:00:00
Schedule: adhocfull
Type: Full Backup
Frequency: every 7 days
Maximum MPX: 8
Synthetic: 0
PFI Recovery: 0
Retention Level: 24 (10 days)
Number Copies: 1
Fail on Error: 0
Residence: (specific storage unit not required)
Volume Pool: #####
Server Group: (same as specified for policy)
Residence is Storage Lifecycle Policy: 0
Daily Windows:
Schedule: Diff-Daily
Type: Differential Incremental Backup
Maximum MPX: 3
Synthetic: 0
PFI Recovery: 0
Retention Level: 24 (10 days) 23 (35 days)
Number Copies: 2
Fail on Error: 0 0
Residence: #####
Volume Pool: #####
Server Group: *ANY* *ANY*
Calendar sched: Enabled
EXCLUDE DATE 0 - 02/18/2011
EXCLUDE DATE 1 - 04/05/2011
EXCLUDE DATE 2 - 07/22/2011
EXCLUDE DATE 3 - 07/23/2011
EXCLUDE DATE 4 - 04/05/2012
EXCLUDE DATE 5 - 04/06/2012
EXCLUDE DATE 6 - 05/11/2012
EXCLUDE DATE 7 - 05/12/2012
Residence is Storage Lifecycle Policy: 0
Daily Windows:
Monday 21:00:00 --> Tuesday 08:00:00
Tuesday 21:00:00 --> Wednesday 08:00:00
Wednesday 21:00:00 --> Thursday 08:00:00
Thursday 21:00:00 --> Friday 08:00:00
Friday 21:00:00 --> Saturday 08:00:00
Saturday 21:00:00 --> Sunday 08:00:00
Schedule: Full_monthly
Type: Full Backup
Maximum MPX: 3
Synthetic: 0
PFI Recovery: 0
Retention Level: 8 (1 year)
Number Copies: 1
Fail on Error: 0
Residence: (specific storage unit not required)
Volume Pool: (same as policy volume pool)
Server Group: (same as specified for policy)
Calendar sched: Enabled
Allowed to retry after run day
Sunday, Week 1
Residence is Storage Lifecycle Policy: 0
Daily Windows:
Sunday 23:00:00 --> Monday 08:00:00
possibly NBPEM did not get updated by the time of regular scheudle.. did you make changes closed to schedule time?
post the bppllist policy_name -U --> you can remove client and policy /stu names... and post it..
How many policies do you have?
If it is a large site then the update and policy timers may not have been removed
Always worth running:
nbpemreq -updatepolicies
after any changes to schedules to force NetBackup to re-read everything and re-set all timers.
If you do a policy listing and then just give us the scheduling details from the bottom of the output it should not be a security issue for you? Or just the schedule windows screenshots?
You can double check the next predicted schedules using the nbpemreq -predict option to see if it wants to run again tonight.
Hope this helps
Authorised Symantec Consultant
Don't forget to give a "Thumbs Up" or mark as "Solution" if someones advice has helped you.
The nbpemreq -predict command returns the three Vms and the Diff Daily policy as predicted work with type 1.
Maybe a bug in that version of NBU....
Why not just disable the policy for now?
Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links
This is what I'm thinking - they still want policy to run on Sunday though - the weekly full.
I've closed the backup windows for the diff-daily policy and now the predicted work returns nothing. I thought this would have worked just bby removing the Calendar days but obviously didn't.
I have noticed that you weekly runs (and the Monthly one) have the following windows:
Calendar sched: Enabled
Sunday, Week 1
Monday, Week 1
Sunday 18:00:00 --> Monday 08:00:00
As these are calendar schedules each day is a new day. This means that you are asking the backup to run at 1800 on Sunday and again at midnight on Monday
You may get away with it if it is a large system and takes a while to back up but if not it will try and run twice.
Your window should be Monday, Week1 Monday 00:05:00 --> 08:00:00
Best not to cross midnight with calendar schedules
Likewise you Daily also crosses midnight so can run at 21:00 on Monday and could then run again just after midnight Tuesday. This would make the next run not actually happen until just after midnight on Wednesday
This would have an effect on any exlcude dates also.
Best tidy all of these up if possible as it could be contributing to your issues and running at unexpected times (I wouldnt expect any to start until midnight during the week apart from on Monday)
Hope this all makes sense and helps
Authorised Symantec Consultant
Don't forget to give a "Thumbs Up" or mark as "Solution" if someones advice has helped you.
Would you like to reply?
Login or Register to post your comment.