VMWare Shutdown
-
Just let the mother nature deal with everything man, and come in the next day and power things up. IT is already full of stress so no need to carry extra worries man
https://i.pinimg.com/originals/b8/6b/00/b86b00a2f6e32e2e564f2f8eaf57fde3.jpg
-
@maximus said in VMWare Shutdown:
Hi,
What is the proper shutdown of VMWare host to prevent damage on the running guest servers? how long does it take to completely shutdown everything?
i have 2 VM host with around 12 guest running on each host.
Like others have said, it depends on what type of servers you are running.
My environment consists of -
Three ESXi hosts with vCenter 6.5 U2 with 35 VM's, mix of Linux and Windows and Two APC UPS (Hosts have dual power supplies with one cord to each UPS) and running an APC VM with powershute software. We do not have a generator but the UPS will run for 35 minutes on battery.
If my users (many remote users) get out in decent time, this process takes about 8-14 minutes and everything is powered down safely. I shutdown small lightly used servers first while waiting on users. Also I use the Shutdown Guest inside vCenter so I don't have to spend time logging into each host and running a shutdown command (I will if I have time).
Powering on is a different beast. Do not let all VM's come up at the same time or your will have a boot storm.
-
Did they discontinue vSphere Mobile Watchlist app for Android? I can't find it on the play store anymore. I use this app to gracefully shutdown or reboot vms.
-
@wrx7m said in VMWare Shutdown:
vSphere Mobile Watchlist
I didn't use it but it looks like it has not been on their since mid-October. That is what I found on their community boards.
-
I shut the VMs down gracefully rather than suspend them. Fortunately, I have not run into issues with pending Windows Updates being installed during this shutdown, although I have heard of such cases and it's something I still have to consider.
-
@Darek-Hamann said in VMWare Shutdown:
I shut the VMs down gracefully rather than suspend them. Fortunately, I have not run into issues with pending Windows Updates being installed during this shutdown, although I have heard of such cases and it's something I still have to consider.
Yes, that can happen a LOT. The more often you reboot, the lower the chances, but it is a pretty huge risk.
-
Couple things for a total cluster shutdown)
- If patching, stage patches to host, and out of bands (if pushing firmware).
- Gracefully shutdown all virtual machines (from in guest, or using VMtools).
- If using vSAN change Maintenance Mode behavior to "Do Nothing"
- Put Hosts in Maintenance Mode.
3b. If patching issue update commands. - Power off hosts once in Maintenance Mode.
- Power back on.
- If patching verifies patches if vSAN change cluster policy back.
-
For vmware, if you are going to shutdown only (no patches), do you always put in maintenance mode first?
-
@wrx7m said in VMWare Shutdown:
For vmware, if you are going to shutdown only (no patches), do you always put in maintenance mode first?
I do if I have the extra few seconds that it takes as my servers will all be powered off anyways.
-
@wrx7m said in VMWare Shutdown:
For vmware, if you are going to shutdown only (no patches), do you always put in maintenance mode first?
- If you have DRS this will force the host to drain VM's off (vMotions are automated).
- If you have vSAN this will make sure you are not about to offline the last good copy of data.
- It's an automated step in how VUM works...
-
@maximus
I believe you can take as a basis the script, published in this article: https://www.starwindsoftware.com/resource-library/starwind-virtual-san-gentle-shutdown-with-powerchute
I hope it will be useful for you
Merry Christmas!
