Skip to main content

Backup tasks sitting on 0% for 3 weeks

Thread needs solution

I have been setting up backup policies for backing up our servers using dedupe and managed vault storage location. My backups are scheduled weekly on friday and saturday evenings. I just checked the console and see that every server (I have 6 using BAR10) was still running a backup started 3 weeks ago - showing as running, and 0% progress. And none of the subsequent scheduled backups have been atempted as they see the previous backup as still being active. Possibly server patching caused the boxes to be re-started which caused the jobs to hang, but I would have tought that they would have failed at this point.

Is there any configuration I can apply to the policy to end a backup task if its duration takes more than a certain time period to run? A timeout basically. Or a way of alerting if a job takes excessive time to run?

Thanks, Paul A

build 10.0.12705

0 Users found this helpful

Hello Paul,

Thank you for finding time to contact us, and report about the issue. I will be glad to help you with it.

It looks like some error occured in the Scheduler, and it got the task stalled. In order to fix the problem, please do the following: 

  1. Stop Acronis services - it will stop the task from running
  2. Update Scheduler as mentioned in this article
    If that doesn't help, please
  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. Recreate the tasks

This should resolve the issue faced. Should it persist, please provide us with Acronis Info from machine in quesiton.

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!

I updated Scheduler on the management server, then ran your utility to delete the tasks after revoking all policies from servers. It may be interesting to note that after running the zap command the tasks still appeared in place. Only after a restart did the tasks list clear down. After the restart I re-assigned policies, and all the tasks were re-created. Will see how the backups run over the weekend and advise accordingly.

Many thanks, Paul

Dear Paul,

Thank you for getting back to me, I really appreciate it.

It's ok that tasks remained on the machine till the reboot, it's a normal behavior. Thank you for following the instructions, and keeping me posted. I will be looking forward to news from you.

Thank you!

Looks like I am still having the same issue with the backupscheduler. All backups have been running for 11 days, stiill showing 0% complete in the console. Any more ideas please?

Paul A

Hello Paul,

Thank you very much for replying.

I apologize for all the trouble but since we have exhausted all of our suggestions here I would recommend to contact our Support team directly for a proper investigation.

I am confident that we will be able to resolve this issue.

If you have additional questions, please let me know.

Thank you.