Blog Post

Failover Clustering
3 MIN READ

How to Properly Shutdown a Failover Cluster or a Node

Elden_Christensen's avatar
Elden_Christensen
Icon for Microsoft rankMicrosoft
Mar 15, 2019
This blog will discuss the proper process for shutting down an individual node in a Windows Server 2012 R2 Failover Cluster or the entire cluster with all the nodes.  Note:  While the steps outlined ...
Updated Aug 08, 2019
Version 4.0
cluster deployment planning
elden christensen
rajuegypt's avatar
rajuegypt
Copper Contributor
Sep 03, 2019

Hi Elden,

 I read your important notes on Hyper-V best practises to shut down/ restart.

 

I need your advise, second thoughts on shutting down my infrastructure for cleaning my rack system.

 

1- Three Physical Servers HP Proliant

2- Hyper-V 2016 Fail Over Cluster roles

3- All VM's on three physical server

4- One HP Proliant repository for dedicated storage, not related to Three Physical server.

5- One HP Prolaint repository Storage for dedicated VEEAM BACKUP STORAGE.

 

Now, I have notifications on restart required due to critical updates on all three Physical Servers, including VMs where several host are running.

 

How can I achieve this proper shut down and restart. 6 months ago I blindly restarted servers as per notifications to restart and **bleep** my VM printer server got corrupted and unable to start.( I restored it via VEEAM).

 

Should I shut down all VMs first , then physical server in intervals like each servers after 5 minutes?

 

Please tell me the sequence or order.

 

Thanks and appreciate your help in advance.