Synchronization problems between AMS and VAs
Hi!
We are using Acronis Backup Advanced for vCloud.
We are facing synchronization problems between the VA and the AMS.
As can be seen in the attached images, it happens that there are tasks that at the level of the virtual agent complete around 10:30 PM 06/01/2018 and at the AMS level at 08:54 AM the following day (07/01/2018) the work appears as in process, with a 17% advance. For this example, we focus on the following job: 0109AGESIC-COESYS_System_10PM-Diario-Retencion-15dias.
Additionally, many jobs appear in the "Deploying" state in the AMS and at the VA level they appear as executed + completed, and at the vaults level there are backups of the day.
Attachment | Size |
---|---|
04- VA view - job completed.png | 398.46 KB |
03-AMS view - Machines with agents.png | 459.7 KB |
02-AMS log for the example job.png | 448.26 KB |
01-AMS JOBS View_17%.png | 605.11 KB |

- Log in to post comments

Hello! sorry for the delay.
The following is wath Andrey from support explain to me, and wich works really fine, so please, put an eye on it if you AMS starts to increase the number of unprocessed events.
This is not a final workaround, but you have to track the unprocessed events at least on a daily basis.
Thank you!
Andrey says:
It looks like the sync problem lays in the number of incoming logs from the VAs (appliances).
The same exactly issue is described here:
https://forum.acronis.com/forum/acronis-backup-117-former-acronis-backu…
To resolve the problem, you should:
1. Adjust the registry keys on the AMS
https://kb.acronis.com/content/32587
2. You can set the keys to
Period = 300 (the new value)
PeriodHigh = 300 (the new value)
3. Stop the AMS service!
4. Better to backup the AMS acronis_cms_cards database
5. Execute the command:
DELETE FROM IncomingCards WHERE ObjectType= 7 AND Verb=2 AND Stamp NOT IN ( SELECT MAX(Stamp) FROM IncomingCards WHERE ObjectType=7 AND Verb=2 GROUP BY ObjectID, Machine)
6. Start the AMS service
- Log in to post comments

Thank you for sharing the update\solution for the issue! I'm sure this will help other users in the same situation
- Log in to post comments