Waiting state?

Dear Harold!

Thank you for finding time to report about this issue. We highly appreciate such cooperation, and I will be glad to help you.

I’ve carefully checked all our internal resources, and found no mention of a known issue that would match your description. So this situation requires investigation.

Usually “waiting” status is assigned to the task in case it was added to the queue. Our Scheduler designed in such a way that it can run only one backup at a time. No simultaneous backups are possible. Thus in case there’s already a backup running, the next task will get “waiting” status.

Please check whether there are any other backups running. In case all the tasks are idle, and the task in question is still in “Waiting”, then it may be caused by the Scheduler glitch.

1. Update Scheduler as mentioned in this article. Check whether the issue remains.
   Should it be present, please:
2. Remove the machine from the backup policy and AMS.
3. Download Acronis Scheduler Manager . Open command prompt (Start -> Run -> cmd); run schedmgr.exe and issue the following command:
   task zap
   This will erase all traces of the tasks.
4. Reboot the machine
5. Readd it to AMS and redeploy the policy

This should solve the issue caused. But in case it still remains after all the updates, please gather Acronis Info from the problem machine, and submit a support request with the information attached. Keep in mind that should there be any procrastination with the reply, you can always specify us the case number. We will do our best to speed up the process.

Should you need anything else or have any further questions - feel free to contact us at your earliest convenience, we will be happy to help you!

Thank you!