Wrong schedule running when duplicating start times
Hey folks.
I have setup a few NetBackup policies to run full backups in a weekly/monthly/yearly fashion. The three schedules have the following differences:
- Retentions
- Weeky is on "Frequency 1 Week"
- Monthly is "1st Friday of the Month"
- Yearly is manualy selected "1st Friday of the Year"
From what I was told, if you have multiple schedules for the same policy running at the same time, the schedule that had the oldest "Last ran" would execute and the others would be ignored.
I never had a problem betweek weekly and monthly, but the yearly didn't run Jan 3rd for some policies. Instead, the monthly run. These policies are varied in type (*nix, Windows, VMWare, Exchange)
I have all sorts of workarounds in mind, but for a concise solution, I need to know where my logic is off.
That's fine. I knew there was likely to be other factors to take into account so it was just a suggestion.
The point I made with the frequency was to try & show the more obvious impact - we've come across this more than once on the forum - but there is a more 'insidious' aspect we've come to know as 'schedule creep':
It could be due to resource limitations that a job may start a few minutes late - it will now always run a few minutes late. If it gets delayed again ......etc etc. This may well be more than a few minutes if no resources are available due to the fact that other backups are running for hours. Due to the fact that we (as backup admins) always seem to have a lot of backups to squeeze into the smallest possible time then, if something is delaying backups, we could be losing a 'window of opportunity' (pun intended!) to get our backups done earlier.