NAS Backup Not Scheduling
My two PC's were both affected by the recently reported problems caused by Acronis where backup destinations and backup schedules were autonomously changed. I have implemented the recommended fixes and, except for one remaining problem, the backups are working again as expected. The remaining problem is that, even though I have recreated the schedule for full system backup to NAS, the backup task still shows as "Next backup: Not scheduled". And this task never runs as scheduled even though a schedule exists for it. If "Back up now" is selected, the task runs as expected. This behavior is exactly the same on both PC's.
I have a workaround because I can periodically manually trigger this task to run; however, my installation of ACPHO was obviously broken by Acronis. I have tried running repair, but that did not fix the problem.
Any suggestions?


- Log in to post comments

The remaining problem is that, even though I have recreated the schedule for full system backup to NAS, the backup task still shows as "Next backup: Not scheduled". And this task never runs as scheduled even though a schedule exists for it. If "Back up now" is selected, the task runs as expected.
Bill, one method that might fix this issue is as follows:
First, make a note (or screen shots) of the problem task settings & options.
Next, use the Delete option for the task and select to only remove the task settings (not to delete everything which would include all the files).
Now, use the option to 'Add existing backup' which is hidden under the caret 'v' to the right of the normal + Add backup option, and navigate to your NAS destination location then select the most recent backup file to be added.
A new backup task will be created using the name of the backup file but will now need to be reconfigured using the button for this purpose (in place of the normal Backup now button).
Reconfigure the Source selection and the Options, including Schedule, Backup type etc.
- Log in to post comments

Ian, thank you for your suggestions. Steve's method worked.
Steve, your suggested method worked. Thank you. The name of the problem full backup was "XPS-8940B". After following your suggested process, the name of the full backup was "XPS-8940B-001". Perhaps the backup name was causing the problem.
- Log in to post comments

Bill, glad the suggestion helped here! The backup name is unlikely to be the issue, the -001 append to the name is normal as new version chains are created. The more likely reason is that the underlying script file became corrupted and deleting / recreating it resolved the issue.
- Log in to post comments