Hi All,
Couple of snapshots are locked on VDP 5.5 appliance and snapshot consolidation is needed. Snapshot consolidation fails as the files are locked. I checked and found that one of the nics on the host (ESXi 1) holds the lock. VDP appliance 5.5 is also registered on ESXi 1.
I vmotion'd the VM VDP appliance 5.5 to ESXi 2 host and then found now one of the nics on ESXi2 holds the lock. I tried consolidating but it failed stating the files are locked.
On ESXi2 I ran the command /sbin/services.sh restart. This Server ESXi 2 has all the VMs running on it including production ones. Once the Command completes the Host ESXi 2 disconnected it self. After couple of minutes it connects again. I found all the VMs on ESXi 2 had a red alarm mark on them. On the VMs alarm tab there was an error stating vSphere HA virtual machine failover failed.
I logged on to Windows and checked and found that the VMs were up and they had not rebooted.
is this a known behavior??? ESXi 2 is running on 5.1.
Also Do I need to move all the VMs from the ESXi host before running /sbin/services.sh restart
Thanks
Vaibhav
Hi,
My initial thought is that your have "Leave VMs Powered On" as the isolation response hence the VMs didnt restart. ESXi host getting disconnected for some time after restarting the services is known because the hostd and vpxa agents have to stop and start. IMO, if the VM are working fine then you can get rid of the alarm, just acknowledge and clear them.
To answer your question, ideally its not required to put the ESXi host in maintenance mode or migrate all VMs before restarting services.sh because it does not affect any VMs. However if you have some mission critical apps on these VMs and have sufficient resources and dont want to take any changes, then you may migrate the VMs first.
-f10
Hi
Welcome to the communities.
When service get restart defintely ddepenedencay service\application will interput till service fully started
Take care!![]()
There won't be any issue to the VMs, If you restart mgmt and vpxa services on it's ESX/ESXi server.
To know more about the alarm "vSphere HA virtual machine failover failed". Refer this KB - 2034571
Thanks all for replying ....
Hi All,
I did some tests in my home lab. I ran the command /sbin/services.sh restart with HA enabled on the Cluster and the isolation response set as Power off/Shutdown/leave power on (I tried with all the options). I even tried on a stand alone host which is not added to the vCenter.
The VM's might break ping but none of the VM's for rebooted. But still you should do this during off hour window and not during production hours.
Hope this helps
