Yesterday, 09:30 AM
I have been using 2 tasks (one for C drive & one for D drive) - full disk backup
Both have been scheduled for 8:00am and the option to run if missed was enabled.
The computer is usually started some time shortly after 8:00
I was finding that the C drive task usually ran first and would fail every now and then.
The D drive task was pretty reliable.
I had wondered if timing was an issue... let's say the computer was started at 8:01
and the HBS task activates before the USB drive was fully on-line.
My work around that seemed to give me more reliable backups:
- disable the HBS schedules
- create a .cmd task that include the 2 backup tasks
- use Windows scheduler to activate the .cmd
Unfortunately the new home release does not have CLI support so I will have to go back
to HBS scheduling. I will monitor my backups more closely to see if I can
find any pattern to the failed updates. (Comment: It would be nice to have CLI
support in the home version)
JD
Both have been scheduled for 8:00am and the option to run if missed was enabled.
The computer is usually started some time shortly after 8:00
I was finding that the C drive task usually ran first and would fail every now and then.
The D drive task was pretty reliable.
I had wondered if timing was an issue... let's say the computer was started at 8:01
and the HBS task activates before the USB drive was fully on-line.
My work around that seemed to give me more reliable backups:
- disable the HBS schedules
- create a .cmd task that include the 2 backup tasks
- use Windows scheduler to activate the .cmd
Unfortunately the new home release does not have CLI support so I will have to go back
to HBS scheduling. I will monitor my backups more closely to see if I can
find any pattern to the failed updates. (Comment: It would be nice to have CLI
support in the home version)
JD