Cannot manually restart a failed backup task
I had to reboot while an ATI backup task was running. The task has a delayed start of 20 minutes. After the reboot there was no indication that a restart was scheduled and the task display showed the next scheduled run was tomorrow at it's normally scheduled time. But if I tried to manually start the task I would get the error message "Failed to run the scheduled task: The task is already waiting."
Is this expected ATI behavior? If this is a the way it is supposed to work, I think I'll submit Feedback requesting the "Next backup" field show the scheduled restart time or display some other indication.
If this is not the expected behavior I'll contact Acronis Support.
Bobbo_3C0X1 wrote:... I suppose if the delay is the issue though (20 m), you could temporarily set it to 0 or 1 m, save and then see if it kicks off after that, or not.
The 20 minutes has already expired, of course, so I can't try that right now but I'll give it a try the next time I run into this. In the mean time I think I'll submit a Feedback.
Mind if I refer to this thread? I assume your comments carry more weight than mine.
Ha, probably not! But, sure thing. Anything I post here in the forums is up for grabs.
Hello Patrick,
I'll clarify how this scenario is supposed to work and post back to this thread
Hello Patrick,
I've discussed your case with the RnD - looks like an issue in the product. May I ask you to reproduce the issue and send me the following information for investigation:
1. Screenshots of settings in the backup plan (what scheduling options are selected?)
2. Screenshot of the main product screen showing the error and next run time
3. Acronis system report from the affected machine after reproducing the issue
Please upload the requested files to our FTP server (link sent in PM)
Thank you in advance!
I'll see if I can reproduce it. I've replaced several of my backup tasks with new ones since I reported the problem so the problematic task may no longer exist.
Oops. I can't follow directions.
I reproduced the problem but foolishly used Feedback to generate the System Report and I did not attach the screen shots. And now the "failed" task has restarted so another System Report would capture the wrong stuff.
If I can find the generated system report I will FTP it and the associated screen shots.
I've had a couple interactions with the support team on this. They had me try restarting the scheduler during the "Run missed operations after startup" delay for the task in question. It worked! After restarting the scheduler I could manually start the task prior to the "missed operations" delay expiring.
Now support wants to to set up a remote access session with my PC. I figure that's going to be a pain since their remote access will be broken by the reboot that is at the center of the problem.
I think I'll first try defining the scheduler task with a delayed start. That has been recommended for some scheduler-oriented problems in a couple other recent threads on the forum.
Patrick, let us know how that goes. I've seen this work for a few people and at one point in the past, it also helped me. With moving to a PCIe NVME and reinstalling ATI fresh, I haven't had to do this again, but I can't see that it would hurt anyone who did add the delay to the autostart just to buy the service a little more time to start up.
Delayed start did not fix the problem. Stopping and restarting the scheduler did fix it. Maybe the delay isn't long enough.
Interesting. No idea why it would need that much time though.
Could use a destination .bat script to stop and start it as needed, or make it a logon script or scheduled to run at intervals, but doesn't explain the issue or why it's happening like this for you.
As Ekaterina mentions RnD is aware of this, sounds like there could be a bug in some instances though. I'll be interested to hear more about the findings.
Patrick, not likely the issue, but on a wim, I checked the dependent services that Acronis scheduler 2 needs to start and RPC is one of the main ones. Most likely, your RPC is working fine, but you may want to check the Windows event logs for signs of any underlying trouble.
https://superuser.com/questions/397192/how-to-start-the-remote-access-service-if-get-error-1068 was a little interesting too, should you not be able to view event log
After mulling over my documentation for quite a while, Acronis support has finally given me an answer (but no solution):
I have discussed the case with our experts and would like to inform that it is a designed behavior of Acronis True Image 2019 that is delay time is set, we cannot start the manual backup of that particular task as the scheduler service already set the task to run after the delay time expires.
In other words, I can't manually start the backup; I have to wait for ATI to automatically start it. I guess I could try changing the delay timer to zero, but I suspect that would not change the already scheduler restart of the task.
By the way, that "Run missed operations" delay kicks in following a reboot, but a missed operation seems to immediately start following waking from sleep. I think the "Run missed operations" may be Broken as Designed (BaD).
Patrick, the Acronis Scheduler Manager tool should be able to be used to remove a rescheduled failed task if that was needed.
Thanks Steve, but it's probably not worth the effort. I discovered this problem when I rebooted out from under an ATI backup and discovered I could not restart the task manually. That event does not happen very often (except when I'm trying to recreate the problem) and waiting for the delay timer to expire is seldom a hardship.