Direkt zum Inhalt

scheduled task did not start

Thread needs solution

Hello, I am testing the software and we will probably buy it. My idea is to set 4 cycles for the backup in 4 weeks with 4 separate INCREMENTAL jobs, each Saturday a FULL and the other days an INCREMENTAL in one cycle, after one week the cycle changes and will be saved on a different directory of a NAS. I set the following schedule: Incremental - START THE TASK EVERY 4 WEEKS ON EACH DAY OF THE WEEK AT 22:30:00, EFFECTIVE FROM FRIDAY 3 DECEMBER 2010.
The first backup was automatically a FULL (correct), the second one an INCREMENTAL (correct) but the third one did not take place, no log update, nothing.
I also have a doubt if the setting is correct, it looks like the cycle would do an INCREMENTAL for 4 weeks every day instead of just for one week and than the new cycle job would start.

Thanks for help

Anhang Größe
log.txt 13.77 KB
0 Users found this helpful

I forgot to mention that after the first INCREMENTAL backup the validation failed (see LOG), does that prevent a job to restart ???

Unless other solution arrives, I wouldn't push scheduler's capabilities to their limit in this way. Especially relying on its ability to glue months' and weeks' boundaries accurately across several cycles. For example, what if it decided that the first week ended at saturday, after the second backup was performed? But this doesn't explain why the validation still runs ( did it run successfully ever? )

Thanks for the answer but I do not understand what you mean by pushing scheduler's capabilities to their limit. I use this kind of cycle now for 7 years with another backup software. Anyway I changed strategy now, setting up just 1 job and after one week I move the directory to another place. Two days ago I deleted these jobs, created 2 new and the validation problem remains. As far as I remember the validation worked once.