A few months ago we installed AOMEI backupper on a Server 2016 box running the SQL Anywhere service and enabled sync for all the DB files so that we have both a daily full server backup and real time sync backup of the DB files.

Now when starting the service after a Windows update reboot it will sometimes fail, up to two or three times, with 'cannot access x.db: another process may be using the file' at a random DB (currently loads about 80 db's) and then proceeds to unload them all and closes.

I tried stopping the AOMEI service before starting SQL Anywhere, but that didn't prevent it. I can only assume that a related Windows service (VSS, SDRSVC, WBEngine) may be used by AOMEI and is causing this, but getting these servers up and running in a timely fashion after the ever increasing number of patches is critical.

Has anyone else experienced this with backup software when starting the server?

Perhaps running Process Monitor and examining the log afterwards?

Thanks