Skip to main content

ATI 2021 - Backup fails without any notification in the logs

Thread needs solution

A scheduled backup of data/folders frequently (not always) fails with the message "The last backup has failed" (original message in German: "Das letzte Backup ist fehlgeschlagen"). A manual start of the backup is always successful. 

The backup target is an internal HDD; the PC (Windows 11) is up and running at the scheduled time.

I analysed the log with MVPAssistant: the failed job does not leave a single notification in the logs.

0 Users found this helpful

Torsten, with only the information above it is impossible to guess at any reason for the backup to fail.

The second issue here is simply that Acronis did not do any testing of ATI 2021 running on Windows 11 and technically will not support that usage / ATI 2021 is unsupported / out of support - so any problems that might be identified would have to be reproduced using ACPHO before Acronis would even consider them!

Unfortunately, I can't provide any more information for the said reason that the execution does not leave any tracks (I even do not receive an e-mail upon completion of the failed backup). I should have mentioned though that I use the most recent version (39287).

But since ATI 2021 is not supported on Windows 11 (note: I am very disappointed that this relatively new version is no longer supported at all), I now have to look for an alternative backup solution after many years of using ATI.

Torsten, ATI 2021 does work with Windows 11 as far as I know with the exception of the Archive feature. 

Acronis have changed their business model regarding perpetual licenses and have moved to a subscription license model only starting with ACPHO.  Existing perpetual licenses will continue to work for as long as the host OS allows them to do so.

If ATI 2021 works when started manually, then it suggests that it is only the scheduling option which is hitting issues here, so the schedule 2 logs would be a place to look for any issues.  The log is not very clear to work with but you should be able to identify the scheduled backup launch time in the log to see if it is attempted to be started?

If you create an Acronis System Report zip file, then it will include the Windows System & Application event logs that you could extract and double-click on to open, then look at the same time period to see if there are any corresponding entries around the time when the scheduler should be launching the backup task.

Steve, thank you for helping me on the issue.

Within the Schedule2 logs there was no entry related to this issue. However, I found the following at backup start time in the applog:

"Scheduler failed to run task  with GUID '52FF0F1B-8D3C-464C-8558-591105E10520' because of error 5 (Access is denied.)."

I need now to research for the cause of this error.

Attachment Size
603129-326942.jpg 208.63 KB

Torsten, that error suggests that Acronis is not running under an Administrator user account when the task is scheduled.

ATI is running under an admin account, the only account on my PC.

I should probably mention that another scheduled backup - for the C-partition - is executed just fine without any problems.