Direkt zum Inhalt

Acronis BR 11.5 - Error during schedule job

Thread needs solution

Hi there.

1 of my office backup machines has a problem at 'All machines with agents' -> 'Last connection' and 'Last successful backup'. The dates infos are not updating even though the backup jobs have ran for quite sometimes. What could be the problem?

Screenshot of the problem has been attached.

Regards, Samsul.

Anhang Größe
acronis_-_infos_not_updating.jpg 114.83 KB
0 Users found this helpful
frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Beiträge: 250
Kommentare: 7092

Hello ning,

If any of the agent machines' data is displayed incorrectly on the Management Server, it usually caused by a desynchronization between Acronis Management Server and Management agents (agent machines).

1. Check connection using telnet from Acronis Management Server to the Management Agent (agent machine) and from the Agent to AMS on port 9876, as described in this article. If it does not work – you are facing a connection issue. Please refer to Acronis Backup Advanced: Connection to Remote Components Fails.

2. Is it possible to connect to the Agent directly (select machine with Agent and click Direct connection)? Are the data the same or the information is updated on the agent's side? 

3. Make sure the antivirus software does not block communication and data traffic between the Management Server and Management Agents (agent machines). Information is processed in “cards” stored in the Outbox folder on the agent machine.

Make sure that this folder is excluded from the antivirus check: 
Windows XP,2003 C:\Documents and Settings\All Users\Application Data\Acronis\BackupAndRecovery\MMS\Outbox 
Windows Vista,7,2008,2012,8 C:\ProgramData\Acronis\BackupAndRecovery\MMS\Outbox 

Acronis Software: Making Acronis Products Compatible with Antivirus Software will help to set up exclusions.

4. Run AMS Troubleshooting script on the machine with AMS. Use parameter -fix:all

Thank you,