I'm an advocate of calendar-based scheduling, so I'll kick in my 2 cents
worth ...
You got a "17.30_mon_calendar" full backup Monday evening because (1)
you have a window there, (2) you have "retry after run day" and (3) the
schedule does not yet have a backup. It's kind of like NetBackup thinks
you had a backup scheduled sometime in the past and it was missed.
Yesterday was the "day after run day". It's good, because you now have
a backup ... even if it wasn't one of your specified days. :-)
I think you should consider a couple of changes, though. First, a
window that crosses midnight may not do what you would expect. I'm not
sure what to expect, so I avoid them. Second, you garner considerable
risk by specifying dates for backups to take place (At some point,
you'll catch up to and pass your last date and all of a sudden will
schedule no more backups ... something NetBackup will do (or not do)
very quietly!).
Better to make all schedules calendar-based. Please consider this
example ... more or less intended to replace your schedules as I
interpret your intention (non-calendar details omitted).
Schedule: 17.30_mon_calendar
Type: Full Backup
Retention Level: 5 (3 months)
Calendar sched: Enabled
Allowed to retry after run day
Monday, Week 5
Daily Windows:
Monday 18:30:00 --> Monday 23:55:00
Tuesday 18:30:00 --> Tuesday 23:55:00
Note: "Monday, Week 5" above really means the last Monday of each month.
Note: I could have a window every day if I wanted everyday to be a
potential "retry after run day" day.
Schedule: 17.30_full
Type: Full Backup
Retention Level: 3 (4 weeks)
Calendar sched: Enabled
Allowed to retry after run day
Monday, Week 1
Monday, Week 2
Monday, Week 3
Monday, Week 4
Daily Windows:
Monday 17:20:00 --> Monday 23:55:00
Tuesday 17:20:00 --> Tuesday 23:55:00
Note: On month's with only 4 Mondays, this schedule will not result in a
job in Week 4, since the "17.30_mon_calendar" will override it.
Schedule: 17.30_mon_inc
Type: Cumulative Incremental Backup
Retention Level: 3 (4 weeks)
Calendar sched: Enabled
Allowed to retry after run day
Sunday, Week 1 Sunday, Week 2
Tuesday, Week 1 Tuesday, Week 2
Wednesday, Week 1 Wednesday, Week 2
Thursday, Week 1 Thursday, Week 2
Friday, Week 1 Friday, Week 2
Saturday, Week 1 Saturday, Week 2
... (etc for other 3 weeks of the month) ...
Daily Windows:
Sunday 17:30:00 --> Sunday 23:55:00
Monday 17:30:00 --> Monday 23:55:00
Tuesday 17:30:00 --> Tuesday 23:55:00
Wednesday 17:30:00 --> Wednesday 23:55:00
Thursday 17:30:00 --> Thursday 23:55:00
Friday 17:30:00 --> Friday 23:55:00
Saturday 17:30:00 --> Saturday 23:55:00
Note: Monday's are omitted from this schedule, but it would be OK to
include them, as this incremental will normally be overridden by one of
the ful backups each Monday.
Note: Even though the retention is set to 4 weeks on this schedule,
these incremental images will only be useful for about 3 weeks, as the
full that they are based on will expire a few days to about a week sooner.
Note: I changed the differential to a cumulative because I could ;-)
Hope this helps, Bob!
cheers, wayne
Wayne T. Smith ~ WTS at Maine.edu ~ Systems Software Analyst
Information Technology Services ~ Systems and Operations group
University of Maine System ~ http://www.Maine.edu/
Bob Stump wrote, in part, on 6/12/2006 6:01 PM:
> I have years of experience with frequency based scheduling but I have
> always shied away from calendar based. Today I made my first attempt
> and I cannot see where I made a mistake. Please review this and help
> me if you can. Thanks.
>
>
> Here is the problem
> The calendar based backup started on the first day that I made this
> policy active even though it is not suppose to be active until the
> last Monday of the month.
>
> Here is the strategy
> 1. full backup every monday night excluding last monday of the month
> with 1 month retention
> allow tuesday full for any failures that may occur on monday
> 3. last monday of each month run a calendar full backup with 3 month
> retention
> retries allowed after runday which would be tuesday night.
> 2. incremental backup every night except monday nights with 1 month
> retention
>
> Here is the bppllist:
> Policy Name: groupwise01-09
>
> Policy Type: Standard
> Active: yes
> Effective date: 06/12/2006 08:00:00
> Client Compress: no
> Follow NFS Mounts: no
> Cross Mount Points: no
> Collect TIR info: no
> Block Incremental: no
> Mult. Data Streams: yes
> Client Encrypt: no
> Checkpoint: no
> Policy Priority: 25
> Max Jobs/Policy: Unlimited
> Disaster Recovery: 0
> Residence: dssu_grp
> Volume Pool: Novell
> Keyword: (none specified)
>
> HW/OS/Client: Novell NetWare gw01
> Novell NetWare gw02
> Novell NetWare gw03
> Novell NetWare gw04
> Novell NetWare gw05
> Novell NetWare gw06
> Novell NetWare gw07
> Novell NetWare gw08
> Novell NetWare gw09
>
> Include: /FS
>
> Schedule: 17.30_mon_calendar
> Type: Full Backup
> Maximum MPX: 10
> Synthetic: 0
> PFI Recovery: 0
> Retention Level: 5 (3 months)
> Number Copies: 1
> Fail on Error: 0
> Residence: dssu04
> Volume Pool: (same as policy volume pool)
> Calendar sched: Enabled
> Allowed to retry after run day
> SPECIFIC DATE 0 - 06/26/2006
> SPECIFIC DATE 1 - 07/31/2006
> SPECIFIC DATE 2 - 08/28/2006
> SPECIFIC DATE 3 - 09/25/2006
> SPECIFIC DATE 4 - 10/30/2006
> SPECIFIC DATE 5 - 11/27/2006
> SPECIFIC DATE 6 - 12/25/2006
> Monday, Week 5
> Daily Windows:
> Monday 18:30:00 --> Tuesday 04:00:00
> Tuesday 17:30:00 --> Wednesday 04:00:00
>
> Schedule: 17.30_mon_full
> Type: Full Backup
> Frequency: every 5 days
> Maximum MPX: 10
> Synthetic: 0
> PFI Recovery: 0
> Retention Level: 3 (1 month)
> Number Copies: 1
> Fail on Error: 0
> Residence: dssu04
> Volume Pool: (same as policy volume pool)
> EXCLUDE DATE 0 - 06/26/2006
> EXCLUDE DATE 1 - 07/31/2006
> EXCLUDE DATE 2 - 08/28/2006
> EXCLUDE DATE 3 - 09/25/2006
> EXCLUDE DATE 4 - 10/30/2006
> EXCLUDE DATE 5 - 11/27/2006
> EXCLUDE DATE 6 - 12/25/2006
> Daily Windows:
> Monday 17:20:00 --> Tuesday 04:00:00
> Tuesday 17:30:00 --> Wednesday 04:00:00
>
> Schedule: 17.30_mon_inc
> Type: Differential Incremental Backup
> Frequency: every 12 hours
> Maximum MPX: 10
> Synthetic: 0
> PFI Recovery: 0
> Retention Level: 3 (1 month)
> Number Copies: 1
> Fail on Error: 0
> Residence: (specific storage unit not required)
> Volume Pool: (same as policy volume pool)
> Daily Windows:
> Sunday 17:30:00 --> Monday 04:00:00
> Tuesday 17:30:00 --> Wednesday 04:00:00
> Wednesday 17:30:00 --> Thursday 04:00:00
> Thursday 17:30:00 --> Friday 04:00:00
> Friday 17:30:00 --> Saturday 04:00:00
> Saturday 17:30:00 --> Sunday 04:00:00
> ------------------------------------------------------------------------
>
> _______________________________________________
> Veritas-bu maillist - Veritas-bu at mailman.eng.auburn.edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
>
|
