Skip to main content

AMS wrong or out of sync "Backup Plan/Task Status"

Thread needs solution

On our AMS the execution state of "Backup Plans and Tasks" is out of sync with the agents.
On the AMS, wee see some jobs with the execution state "running / xx%", but when we check the job status on the agent, there is no job running/executing.
I think, the AMS/Database is delayed with the job-status.
The taks/jobs are executed on the agent at the scheduled time - but we don't see this on the AMS (console connected to AMS). On the AMS, 24h or more later, the task's are displayed as running - in reality, the task's are finishded since hours.
???
Thank's for any inputs.

0 Users found this helpful

Hello Sascha Abplanalp,

Thank you for posting this question in our forum. I am happy to assist you. 

If the Acronis Management Server and Agents out of sync, you can use the troubleshooting script from our knowledge base to correct this issue.

If you need additional assistance, please create a system report of the affected machine and contact support. You will find all available support options in our Customer handbook.

If there is anything else we can do for you, please let me know.

Thank you.

Hallo Peter

Thank you for the "script".
The outpout is as follows - The errors in the AMS-Log are only "Cannot find the aspect of the instance with" erros, no others.
Actually, the "async" amount of time between the AMS "Backup Plans and Tasks" activity status and the realaty on the agent is ~2 hours.
We realized this problem only since the update to build "ABR11.5A_37687_en-US". We also reinstalled alle Acronis components incl. the virtual appliances (manually cleaned-up the registry and files/folders, importing the agents, create new backup-plans, deploy virtual appliances,...) but the problem accure again.

Checking number of unprocessed events
> WARNING: There are 195327 unprocessed events in AMS database.
Checking event processing speed
> OK
Checking sync database size
> OK
Checking DML database size
> OK
Checking recent errors
> WARNING: There are '27' error(s) in AMS log for past week.
Checking withdrawn machines
> OK
Checking orphan machines
> OK
Checking orphan instance aspects
> OK

Thank you for your assistance.
Kind regards, Sascha

Hello Peter
I've seen, Acronis is using UNIX UTC Timestamps in the database. Maybe this is a time-conversion problem. We relized a async-time from 02:00 hours.
Also the timestamps in the VMs "Last Backup" information is -02:00 hours wrong (the job runs on 12:00, the last backupinformation is set to 10:00).
We use the UTC+01:00 timezone with a +01:00 Daylight-Saving ajustment.

Standard time zone: UTC/GMT +1 hour
Daylight saving time: +1 hour
Current time zone offset: UTC/GMT +2 hours
Time zone abbreviation: CEST - Central European Summer Time

Hello Sascha,

Thank you for your reply.

If you need additional assistance, please create a system report of the affected machine and contact support with a reference to this thread. You will find all available support options in our Customer handbook.

Let me know if you need additional help please.

Thank you.