Exclude dates for individual jobs
In BE 2012, exclude dates are on a server level, i.e. they apply to all scheduled jobs. The inability to exclude dates for individual jobs is a serious set-back and would mean that we now CANNOT stop scheduled jobs from running during holidays.
Suppose I have JobA and JobB scheduled to start at 10 p.m. and 2 a.m. respectively. These are daily backup jobs and I do not want them to run on holidays because there is nobody in the office and no updates are done. If a holiday falls on 15 Mar., then I have to exclude 15 Mar from JobA's scheduled run and 16 Mar from JobB's scheduled run. Note the difference in the excluded dates. JobB's 15 Mar run is to backup data from 14 Mar, hence it should not be stopped.
In previous versions of BE, with exclusion dates for individual jobs, the exclusion dates for the above example can be achieved, but BE 2012, it is not possible to have a good exclusion. Suppose I exclude 15 Mar. This means that JobB will only run on 16 Mar to backup data from 14 Mar. This leaves me exposed. Suppose my server crashed on mid-day on 15 Mar. I would have no backup of the 14 Mar data. This means I am more vulnerable with BE 2012 than with previous versions of BE. The alternative is to still do backups on holidays which brings its attendant problems of increased storage requirement and operational problems like how to change tapes.
With BE 2012 being server-centric, the number of jobs will increase and some of them will definitely spill over midnight and the above problem would be magnified.
Do bring back exclude dates for individual jobs.