Service on a virtual machine fails after snapshot – Milestone VMS


I have a few clusters of ESXi 6.7u1 hosts running several Milestone VMS Recording Server VM’s. After upgrading from ESXi 6.0 to 6.7u1 (hosts are Pivot3, 6.7u1 is version that is supported by the Acuity release we are running), we noticed issues with the Milestone recording servers. The milestone recording servers were going into a failed state in the management server immediately after VEEAM backup kicked off. I narrowed down the issue to VMware snapshots that VEEAM was triggering, and am able to reproduce the issue by manually triggering a snapshot in the vSphere console (not snapshotting active memory or quiescing)


Does anybody have any suggestions on how to troubleshoot this? We are working with Milestone at this point. I didn’t see anything in release notes for ESXi regarding snapshot issues.



View Reddit by pac1085View Source

Related Articles

One Comment

  1. So there are some applications that cant handle the snapshot process. In our case it was Oracle/SQL DB’s. It was mainly around the deletion of a snapshot where the VM is stunned temporarily. This can be up to 1 second or longer it depends on the amount of delta. The fix was to move to an in guest backup. Your application vendor needs to be able to tell you if their application supports VMware Snapshot based backups.

    This KB will help you trouble shoot how long the VM was stunned for


Leave a Reply

Your email address will not be published. Required fields are marked *