cancel
Showing results for 
Search instead for 
Did you mean: 

Frequency Schedule

Andrew_B1
Level 3
I've read many postings on frequency based scheduling but haven't found the answer I'm looking for.

I'm trying to implement a frequency based schedule for a majority of my policies following the method described in this blog entry http://blogs.netapp.com/barandgrill/2008/10/frequency-based.html.  I have three schedules in a policy.
"Full-EOM" Frequency based 26 days start window M-W 18:00-22:00 (added Monday morning about 11 AM)
"Cinc" Frequency based 1 day start window daily 18:00-22:00
"Cinc-EOM" Calendar based last day of month start window daily 18:00-22:00 (added Monday morning about 11 AM)

I expected Full-EOM to run on Monday but did not also did not run on Tuesday either.  Am I missing something?  The Cinc schedule is running instead.

------------------------------------------------------------

Policy Type: MS-Windows-NT
Active: yes
Effective date: 11/25/2009 19:45:31
Backup network drvs: no
Collect TIR info: yes, with move detection
Mult. Data Streams: yes
Client Encrypt: no
Checkpoint: yes
Interval: 30
Policy Priority: 4
Max Jobs/Policy: Unlimited
Disaster Recovery: 0
Collect BMR info: no
Server Group: *ANY*
Keyword: (none specified)
Data Classification: -
Residence is Storage Lifecycle Policy: no

Schedule: Full-EOM
Type: Full Backup
Frequency: every 26 days
Maximum MPX: 2
Synthetic: 0
PFI Recovery: 0
Retention Level: 24 (infinity)
Number Copies: 1
Fail on Error: 0
Server Group: (same as specified for policy)
Residence is Storage Lifecycle Policy: 0
Daily Windows:
Monday 18:00:00 --> Monday 22:00:00
Tuesday 18:00:00 --> Tuesday 22:00:00
Wednesday 18:00:00 --> Wednesday 22:00:00

Schedule: Cinc-EOM
Type: Cumulative Incremental Backup
Maximum MPX: 2
Synthetic: 0
PFI Recovery: 0
Retention Level: 24 (infinity)
Number Copies: 1
Fail on Error: 0
Server Group: (same as specified for policy)
Calendar sched: Enabled
Residence is Storage Lifecycle Policy: 0
Daily Windows:
Sunday 18:00:00 --> Sunday 22:00:00
Monday 18:00:00 --> Monday 22:00:00
Tuesday 18:00:00 --> Tuesday 22:00:00
Wednesday 18:00:00 --> Wednesday 22:00:00
Thursday 18:00:00 --> Thursday 22:00:00
Friday 18:00:00 --> Friday 22:00:00
Saturday 18:00:00 --> Saturday 22:00:00

Schedule: Cinc
Type: Cumulative Incremental Backup
Frequency: every 1 day
Maximum MPX: 2
Synthetic: 0
PFI Recovery: 0
Retention Level: 3 (1 month)
Number Copies: 1
Fail on Error: 0
Server Group: (same as specified for policy)
Residence is Storage Lifecycle Policy: 0
Daily Windows:
Sunday 18:00:00 --> Sunday 22:00:00
Monday 18:00:00 --> Monday 22:00:00
Tuesday 18:00:00 --> Tuesday 22:00:00
Wednesday 18:00:00 --> Wednesday 22:00:00
Thursday 18:00:00 --> Thursday 22:00:00
Friday 18:00:00 --> Friday 22:00:00
Saturday 18:00:00 --> Saturday 22:00:00
7 REPLIES 7

Andy_Welburn
Level 6
Only thing I can think of at the moment - did you run a Full from this policy "just to test"? If so, it could be that it will not attempt to do the next full for another 26 days.

Not sure how the frequency-based Full-EOM & calendar-cased Cinc-EOM are going to interact when they are due to run together!

J_H_Is_gone
Level 6
If you have already taken a FULL, then you will not get another full for 26 days.
as for your Cinc, you have it set to 1 day - I expect you mean it to run once a day.
you should change that to be 12 hours.
if you have it at 1 day and say the last time it ran it really did not start util 21:30, it won't start again for 24 hours at 21:30.... change it to 12 hours and it will always queue up at 18:00.

Andrew_B1
Level 3
I have not run a full backup as a test.  It did spark a thought though.  I've used the schedule name Full-EOM but it was a calendar based schedule set to last day of month.  I deleted the calendar based schedule and created the new frequency based schedule.  So even though the schedule changed the name remained the same.  The last time the Full-EOM calendar based schedule ran on 1/31/2010 so is the frequency based schedule looking at 26 days after the last occurrence of the schedule named Full-EOM regardless of the actual schedule (ie calendar, frequency etc.)?

Marianne
Level 6
Partner    VIP    Accredited Certified
Which version of NBU? Based on the version we can execute commands to predict when next schedules are due to run.
NBU 6.5.x: nbpemreq -predict_all -date <mm/dd/yyyy HH:MM:SS> [-client_filter clientlist] [-policy_filter policylist]

Also check for existence of STREAMS file in /usr/openv/netbackup/db/images/<client_name> on Master server. Deleting this file should reset expected behaviour.
You will have to run run a Full schedule before your Cumulative backups are due, otherwise it will backup all files/folders every day since it has no Full as a basis.

Andrew_B1
Level 3

*policy* is my policy
*client* is my client
I ran nbpemreq -predict_all -date 03/30/2010 -policy_filter *policy* to look at the jobs between now and 3/30/2010.
Predicted worklist including all jobs due to run between now and 3/30/2010 11:59:59 PM
rl client               policy               schedule             type       due time
-- -------------------- -------------------- -------------------- ---------- ------------------
24 *client*            *policy*    Cinc                 4          Wed Feb 24 18:00:00 2010

I have a <install path>\Veritas\NetBackup\db\images\*client*\STREAMS*policy*
The contents of the file is below:
T 0 0
1 1260749508 *policy* Cumulative-Inc 4,0,86400 0 1 F:\Shares
1 1264875266 *policy* Full 0,0,604800 0 0 F:\Shares
1 1265068945 *policy* Differential 1,0,86400 0 0 F:\Shares
1 0 *policy* Cinc-EOM 4,0,0 0 0 F:\Shares
1 1266883246 *policy* Cinc-EOM 0,0,0 0 0 F:\Shares
1 1264982437 *policy* Full-EOM 0,0,2246400 0 0 F:\Shares
1 1266969635 *policy* Cinc 4,0,86400 0 0 F:\Shares

Marianne
Level 6
Partner    VIP    Accredited Certified
 1 1264982437 *policy* Full-EOM 0,0,2246400 0 0 F:\Shares
# bpdbm -ctime 1264982437
1264982437 = Mon Feb  1 02:00:37 2010

Am I right in saying that a Full-EOM ran on 1 Feb @ 02:00? If that's true, I'd expect nbpemreq to predict another Full-EOM on 27 Feb... BUT you only have open windows on Mon, Tue, Wed. The next possible date is Monday 1 March, but nbpemreq did not show this date it it's prediction.
Try to rename STREAMS file to something like oldSTREAMS, run nbpemreq -updatepolicies, then run a predict again and see if the output is different.


Claudio_Veronez
Level 6
Partner Accredited
I have seen that U have a solution for another post

https://www-secure.symantec.com/connect/forums/great-catalog-problem-daylight-saving-error#comment-3635341

reset/change the predict hour for next backup.

can U help me please?