BE2012 Exclude dates - cancels jobs that span midnight
Why oh why Symantec do Exclude Dates cancel jobs that span midnight? Today is Good Friday in the UK, a general holiday day so for neatness I excluded March 29th on our two servers. Net result, our overnight backup that started at 8pm last night (March 28th) cancelled itself just after midnight as it dropped into March 29th! Net result = two servers not backed up.
Surely any designer with an ounce of common sense would let existing jobs run, but prevent new jobs that start on an Exclude date from starting Symantec, I bought your products to safeguard my system not endanger it.
The thread above talks about a fix coming out but (a) it hasn't and (b) that thread is locked - why?
Symantec, please issue a fix for this - it really is not complicated logic to provide for.