The auto start "next working date" is based on the last "next working date" used, not the system date.
The nightly (for example) was started on 06/05/12 and finished on the same day of 06/05, running with the next working day of 06/06. Since it finished on 06/05 (For the 6th).. It put the correct next working date of 06/07.
Notice in the example below:
---------------------------------------------------------------------------
* DEDICATED PART OF BACKUP done 23:48:23 on 06/05/12 SCDATA
* NIGHTLY PROCESSING WAS SET UP TO RUN WITH A NEXT WORKING DATE OF
06/07/12-Thursday
-----------------------------------------------------------------------------
Nightly had finished at 23:48:23 on 06/05/12 but the next working day says 06/07/12 a two days jump.
But if this nightly had finished at 12:01 AM on 06/06/12 the message would have been less confusing. It would have said nightly ended on 06/06/12 and the next working date of 06/07/12-Thursday.
Ending the nightly on 06/05 OR 06/06 are both correct, the next working date still needs to be 06/07
Keywords - Kbase Nightly Dates Issueate
Kailer@key2recovery.com
Comments