Home
%3CLINGO-SUB%20id%3D%22lingo-sub-508546%22%20slang%3D%22en-US%22%3ERe%3A%20How%20to%20Properly%20Shutdown%20a%20Failover%20Cluster%20or%20a%20Node%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-508546%22%20slang%3D%22en-US%22%3E%3CP%3EFor%20a%20file%20server%20cluster%20you%20could%20do%20something%20like%20this%2C%20which%20has%20the%20advantage%20of%20not%20needing%20to%20restart%20the%20cluster%20service%20once%20the%20nodes%20have%20been%20rebooted.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CDIV%3E%3CDIV%3E%3CSPAN%3E%23Get%20Nodes%20of%20FSCluster%3C%2FSPAN%3E%3C%2FDIV%3E%3CDIV%3E%3CSPAN%3E%5B%3C%2FSPAN%3E%3CSPAN%3EValidateNotNullOrEmpty%3C%2FSPAN%3E%3CSPAN%3E()%5D%3C%2FSPAN%3E%3CSPAN%3E%24FSNodes%3C%2FSPAN%3E%20%3CSPAN%3E%3D%3C%2FSPAN%3E%3CSPAN%3E%20(%3C%2FSPAN%3E%3CSPAN%3EGet-ClusterNode%3C%2FSPAN%3E%20%3CSPAN%3E-%3C%2FSPAN%3E%3CSPAN%3ECluster%20%3C%2FSPAN%3E%3CSPAN%3E%24FSCluster%3C%2FSPAN%3E%3CSPAN%3E).Name%3C%2FSPAN%3E%3C%2FDIV%3E%3CDIV%3E%3CSPAN%3E%24PrimaryFSNode%3C%2FSPAN%3E%20%3CSPAN%3E%3D%3C%2FSPAN%3E%20%3CSPAN%3E%24FSNodes%3C%2FSPAN%3E%3CSPAN%3E%5B%3C%2FSPAN%3E%3CSPAN%3E0%3C%2FSPAN%3E%3CSPAN%3E%5D%3C%2FSPAN%3E%3C%2FDIV%3E%3CDIV%3E%3CSPAN%3E%24AuxiliaryFSNodes%3C%2FSPAN%3E%20%3CSPAN%3E%3D%3C%2FSPAN%3E%20%3CSPAN%3E%24FSNodes%3C%2FSPAN%3E%3CSPAN%3E%5B%3C%2FSPAN%3E%3CSPAN%3E1%3C%2FSPAN%3E%3CSPAN%3E..%3C%2FSPAN%3E%3CSPAN%3E(%3C%2FSPAN%3E%3CSPAN%3E%24FSNodes.Count%3C%2FSPAN%3E%20%3CSPAN%3E-1%3C%2FSPAN%3E%3CSPAN%3E)%5D%3C%2FSPAN%3E%3C%2FDIV%3E%3CBR%20%2F%3E%3CDIV%3E%3CSPAN%3E%23Turn%20off%20AuxiliaryFSNodes%3C%2FSPAN%3E%3C%2FDIV%3E%3CDIV%3E%3CSPAN%3EGet-VM%3C%2FSPAN%3E%20%3CSPAN%3E-%3C%2FSPAN%3E%3CSPAN%3EName%20%3C%2FSPAN%3E%3CSPAN%3E%24AuxiliaryFSNodes.Name%3C%2FSPAN%3E%20%3CSPAN%3E-%3C%2FSPAN%3E%3CSPAN%3EComputerName%20%3C%2FSPAN%3E%3CSPAN%3E%24HVNodes%3C%2FSPAN%3E%20%3CSPAN%3E%7C%3C%2FSPAN%3E%20%3CSPAN%3EStop-VM%3C%2FSPAN%3E%20%3CSPAN%3E-%3C%2FSPAN%3E%3CSPAN%3EVerbose%3A%3C%2FSPAN%3E%3CSPAN%3E%24Verbose%3C%2FSPAN%3E%3C%2FDIV%3E%3CBR%20%2F%3E%3CDIV%3E%3CSPAN%3E%23Wait%20for%20FSCluster%20to%20failover%20to%20Primary%20Node%3C%2FSPAN%3E%3C%2FDIV%3E%3CDIV%3E%3CSPAN%3EWhile%3C%2FSPAN%3E%3CSPAN%3E%20((%3C%2FSPAN%3E%3CSPAN%3EGet-ClusterGroup%3C%2FSPAN%3E%20%3CSPAN%3E-%3C%2FSPAN%3E%3CSPAN%3ECluster%20%3C%2FSPAN%3E%3CSPAN%3E%24FSCluster%3C%2FSPAN%3E%3CSPAN%3E).OwnerNode%20%3C%2FSPAN%3E%3CSPAN%3E-ne%3C%2FSPAN%3E%20%3CSPAN%3E%24PrimaryFSNode%3C%2FSPAN%3E%3CSPAN%3E)%20%7B%3C%2FSPAN%3E%3C%2FDIV%3E%3CDIV%3E%3CSPAN%3EWrite-Verbose%3C%2FSPAN%3E%20%3CSPAN%3E%22Waiting%20for%20Cluster%20%3C%2FSPAN%3E%3CSPAN%3E%24FSCluster%3C%2FSPAN%3E%3CSPAN%3E%20to%20failover%20to%20%3C%2FSPAN%3E%3CSPAN%3E%24PrimaryFSNode%3C%2FSPAN%3E%3CSPAN%3E%22%3C%2FSPAN%3E%3C%2FDIV%3E%3CDIV%3E%3CSPAN%3EStart-Sleep%3C%2FSPAN%3E%20%3CSPAN%3E-%3C%2FSPAN%3E%3CSPAN%3ESeconds%20%3C%2FSPAN%3E%3CSPAN%3E10%3C%2FSPAN%3E%3C%2FDIV%3E%3CDIV%3E%3CSPAN%3E%7D%3C%2FSPAN%3E%3C%2FDIV%3E%3CBR%20%2F%3E%3CDIV%3E%3CSPAN%3E%23Turn%20off%20PrimaryFSNode%3C%2FSPAN%3E%3C%2FDIV%3E%3CDIV%3E%3CSPAN%3EGet-VM%3C%2FSPAN%3E%20%3CSPAN%3E-%3C%2FSPAN%3E%3CSPAN%3EName%20%3C%2FSPAN%3E%3CSPAN%3E%24PrimaryFSNode.Name%3C%2FSPAN%3E%20%3CSPAN%3E-%3C%2FSPAN%3E%3CSPAN%3EComputerName%20%3C%2FSPAN%3E%3CSPAN%3E%24HVNodes%3C%2FSPAN%3E%20%3CSPAN%3E%7C%3C%2FSPAN%3E%20%3CSPAN%3EStop-VM%3C%2FSPAN%3E%20%3CSPAN%3E-%3C%2FSPAN%3E%3CSPAN%3EVerbose%3A%3C%2FSPAN%3E%3CSPAN%3E%24Verbose%3C%2FSPAN%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-371857%22%20slang%3D%22en-US%22%3EHow%20to%20Properly%20Shutdown%20a%20Failover%20Cluster%20or%20a%20Node%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-371857%22%20slang%3D%22en-US%22%3E%3CP%3EThis%20blog%20will%20discuss%20the%20proper%20process%20for%20shutting%20down%20an%20individual%20node%20in%20a%20Windows%20Server%202012%20R2%20Failover%20Cluster%20or%20the%20entire%20cluster%20with%20all%20the%20nodes.%26nbsp%3B%20Note%3A%26nbsp%3B%20While%20the%20steps%20outlined%20will%20be%20specific%20to%20Windows%20Server%202012%20R2%2C%20the%20process%20applies%20to%20a%20cluster%20of%20any%20OS%20version.%3C%2FP%3E%0A%3CH2%20id%3D%22toc-hId-1705630877%22%20id%3D%22toc-hId-1705630877%22%20id%3D%22toc-hId-1705630877%22%3EShutting%20Down%20a%20Node%3C%2FH2%3E%0A%3CP%3EWhen%20shutting%20down%20or%20rebooting%20a%20node%20in%20a%20Failover%20Cluster%2C%20you%20first%20want%20to%20drain%20(move%20off)%20any%20roles%20running%20on%20that%20server%20(such%20as%20a%20virtual%20machine).%26nbsp%3B%20This%20ensures%20that%20the%20shutting%20down%20of%20a%20node%20is%20graceful%20to%20any%20applications%20running%20on%20that%20node.%26nbsp%3B%3C%2FP%3E%0A%3COL%3E%0A%3COL%3E%0A%3CLI%3EOpen%20Failover%20Cluster%20Manager%20(CluAdmin.msc)%3C%2FLI%3E%0A%3CLI%3EClick%20on%20%E2%80%9C%20%3CSTRONG%3E%20Nodes%20%3C%2FSTRONG%3E%20%E2%80%9D%3C%2FLI%3E%0A%3CLI%3ERight-click%20on%20the%20node%20name%20and%20under%20%E2%80%98%20%3CSTRONG%3E%20Pause%20%3C%2FSTRONG%3E%20%E2%80%99%20click%20on%20%E2%80%98%20%3CSTRONG%3E%20Drain%20Roles%20%3C%2FSTRONG%3E%20%E2%80%99%3C%2FLI%3E%0A%3CLI%3EUnder%20Status%20the%20node%20will%20appear%20as%20%E2%80%98Paused%E2%80%99.%26nbsp%3B%20At%20the%20bottom%20of%20the%20center%20pane%20click%20on%20the%20%E2%80%98Roles%E2%80%99%20tab.%26nbsp%3B%20Once%20all%20roles%20have%20moved%20off%20this%20node%2C%20it%20is%20safe%20to%20shut%20down%20or%20reboot%20the%20node.%3C%2FLI%3E%0A%3C%2FOL%3E%0A%3C%2FOL%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20484px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F90432i694E4B03EAF18660%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CH2%20id%3D%22toc-hId--846526084%22%20id%3D%22toc-hId--846526084%22%20id%3D%22toc-hId--846526084%22%3ETo%20resume%20the%20node%20after%20it%20has%20been%20restarted%E2%80%A6%3C%2FH2%3E%0A%3CP%3EWhen%20the%20node%20is%20once%20again%20powered%20on%20and%20ready%20to%20be%20put%20back%20into%20service%2C%20use%20the%20Resume%20action%20to%20re-enable%20the%20node%20to%20host%20roles.%26nbsp%3B%3C%2FP%3E%0A%3COL%3E%0A%3COL%3E%0A%3CLI%3EOpen%20Failover%20Cluster%20Manager%20(CluAdmin.msc)%3C%2FLI%3E%0A%3CLI%3EClick%20on%20%E2%80%9C%20%3CSTRONG%3E%20Nodes%20%3C%2FSTRONG%3E%20%E2%80%9D%3C%2FLI%3E%0A%3CLI%3ERight-click%20on%20the%20node%20name%20and%20select%20%E2%80%98%20%3CSTRONG%3E%20Resume%20%3C%2FSTRONG%3E%20%E2%80%99%2C%20then%20select%20either%3A%3C%2FLI%3E%0A%3CLI%3E%E2%80%98%20%3CSTRONG%3E%20Fail%20Roles%20Back%20%3C%2FSTRONG%3E%20%E2%80%99%20%E2%80%93%20This%20will%20resume%20the%20node%20and%20move%20any%20roles%20which%20were%20running%20on%20the%20node%20prior%20to%20the%20node%20back.%26nbsp%3B%20Caution%3A%26nbsp%3B%20This%20could%20incur%20downtime%20based%20on%20the%20role%3C%2FLI%3E%0A%3CLI%3E%E2%80%98%20%3CSTRONG%3E%20Do%20Not%20Fail%20Roles%20Back%20%3C%2FSTRONG%3E%20%E2%80%99%20%E2%80%93%20This%20will%20resume%20the%20node%20and%20not%20move%20any%20roles%20back.%3C%2FLI%3E%0A%3C%2FOL%3E%0A%3C%2FOL%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20488px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F90433i49B16F5D405672D3%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CH2%20id%3D%22toc-hId-896284251%22%20id%3D%22toc-hId-896284251%22%20id%3D%22toc-hId-896284251%22%3EShutting%20Down%20a%20Node%20with%20Windows%20PowerShell%C2%AE%3C%2FH2%3E%0A%3COL%3E%0A%3COL%3E%0A%3CLI%3EOpen%20a%20PowerShell%20window%20as%20Administrator%20and%20type%3A%20%3CBR%20%2F%3E%3CA%20href%3D%22http%3A%2F%2Ftechnet.microsoft.com%2Fen-us%2Flibrary%2Fhh847277.aspx%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3ESuspend-ClusterNode%20-Drain%3C%2FA%3E%3C%2FLI%3E%0A%3CLI%3EVerify%20that%20there%20are%20no%20roles%20listed%20under%20%E2%80%9COwnerNode%E2%80%9D%20for%20that%20node%20by%20running%3A%20%3CBR%20%2F%3E%3CA%20href%3D%22http%3A%2F%2Ftechnet.microsoft.com%2Fen-us%2Flibrary%2Fhh847242.aspx%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EGet-ClusterGroup%3C%2FA%3E%3C%2FLI%3E%0A%3CLI%3EThis%20could%20be%20scripted%20with%20the%20following%20syntax%3A%20%3CBR%20%2F%3EPS%20C%3A%5C%26gt%3B%20(Get-ClusterGroup).OwnerNode%20%E2%80%93eq%20%22NodeBeingDrained%22%3C%2FLI%3E%0A%3C%2FOL%3E%0A%3C%2FOL%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3COL%3E%0A%3COL%3E%0A%3CLI%3EShutdown%20or%20restart%20the%20computer%20by%20typing%20either%3A%20%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Ftechnet.microsoft.com%2Fen-us%2Flibrary%2Fhh849839.aspx%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EStop-Computer%20%3C%2FA%3E%3CBR%20%2F%3E%3CA%20href%3D%22http%3A%2F%2Ftechnet.microsoft.com%2Fen-us%2Flibrary%2Fhh849837.aspx%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3ERestart-Computer%3C%2FA%3E%3C%2FLI%3E%0A%3C%2FOL%3E%0A%3C%2FOL%3E%0A%3CH2%20id%3D%22toc-hId--1655872710%22%20id%3D%22toc-hId--1655872710%22%20id%3D%22toc-hId--1655872710%22%3ETo%20resume%20the%20node%20after%20it%20has%20been%20restarted%E2%80%A6%3C%2FH2%3E%0A%3COL%3E%0A%3COL%3E%0A%3CLI%3EOpen%20a%20PowerShell%20window%20as%20Administrator%20and%20type%3A%20%3CBR%20%2F%3E%3CA%20href%3D%22http%3A%2F%2Ftechnet.microsoft.com%2Fen-us%2Flibrary%2Fhh847243.aspx%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EResume-ClusterNode%3C%2FA%3E%3C%2FLI%3E%0A%3C%2FOL%3E%0A%3C%2FOL%3E%0A%3CP%3EOr%20if%20you%20wish%20to%20fail%20back%20the%20roles%20which%20were%20previously%20running%20on%20this%20node%20type%3A%20%3CBR%20%2F%3EResume-ClusterNode%20%E2%80%93Failback%20Immediate%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CH1%20id%3D%22toc-hId-283451130%22%20id%3D%22toc-hId-283451130%22%20id%3D%22toc-hId-283451130%22%3EShutting%20Down%20a%20Cluster%3C%2FH1%3E%0A%3CP%3EShutting%20down%20the%20entire%20cluster%20involves%20stopping%20all%20roles%20and%20then%20stopping%20the%20Cluster%20Service%20on%20all%20nodes.%26nbsp%3B%20While%20you%20can%20shut%20down%20each%20node%20in%20the%20cluster%20individually%2C%20using%20the%20cluster%20UI%20will%20ensure%20the%20shutdown%20is%20done%20gracefully.%26nbsp%3B%3C%2FP%3E%0A%3COL%3E%0A%3COL%3E%0A%3CLI%3EOpen%20Failover%20Cluster%20Manager%20(CluAdmin.msc)%3C%2FLI%3E%0A%3CLI%3ERight-click%20on%20the%20cluster%20name%2C%20select%20%E2%80%98%20%3CSTRONG%3E%20More%20Actions%20%3C%2FSTRONG%3E%20%E2%80%99%2C%20then%20%E2%80%9C%20%3CSTRONG%3E%20Shut%20Down%20Cluster%E2%80%A6%20%3C%2FSTRONG%3E%20%E2%80%9D%3C%2FLI%3E%0A%3CLI%3EWhen%20prompted%20if%20you%20are%20sure%20you%20want%20to%20shut%20down%20the%20cluster%2C%20click%20%E2%80%9C%20%3CSTRONG%3E%20Yes%20%3C%2FSTRONG%3E%20%E2%80%9D%3C%2FLI%3E%0A%3C%2FOL%3E%0A%3C%2FOL%3E%0A%3CH2%20id%3D%22toc-hId-1829747960%22%20id%3D%22toc-hId-1829747960%22%20id%3D%22toc-hId-1829747960%22%3EShutting%20Down%20a%20Cluster%20with%20PowerShell%3C%2FH2%3E%0A%3COL%3E%0A%3COL%3E%0A%3CLI%3EOpen%20a%20PowerShell%20window%20as%20Administrator%20and%20type%3A%20%3CBR%20%2F%3E%3CA%20href%3D%22http%3A%2F%2Ftechnet.microsoft.com%2Fen-us%2Flibrary%2Fhh847316.aspx%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EStop-Cluster%3C%2FA%3E%3C%2FLI%3E%0A%3C%2FOL%3E%0A%3C%2FOL%3E%0A%3CH3%20id%3D%22toc-hId--918922506%22%20id%3D%22toc-hId--918922506%22%20id%3D%22toc-hId--918922506%22%3EControlling%20VM%20Behavior%20on%20Shutdown%3C%2FH3%3E%0A%3CP%3EWhen%20the%20cluster%20is%20shut%20down%2C%20the%20VMs%20will%20be%20placed%20in%20a%20Saved%20state.%26nbsp%3B%20This%20can%20be%20controlled%20using%20the%20OfflineAction%20property.%20%3CBR%20%2F%3E%3CBR%20%2F%3ETo%20configure%20the%20shut%20down%20action%20for%20an%20individual%20VM%20(where%20%22Virtual%20Machine%22%20is%20the%20name%20of%20the%20VM)%3A%3C%2FP%3E%0A%3CPRE%3EGet-ClusterResource%20%22Virtual%20Machine%22%20%7C%20Set-ClusterParameter%20OfflineAction%201%3C%2FPRE%3E%0A%3CTABLE%3E%0A%3CTBODY%3E%0A%3CTR%3E%0A%3CTD%3E%3CSTRONG%3EValue%20%3C%2FSTRONG%3E%3C%2FTD%3E%0A%3CTD%3E%3CSTRONG%3E%20Effect%20%3C%2FSTRONG%3E%3C%2FTD%3E%0A%3C%2FTR%3E%0A%3CTR%3E%0A%3CTD%3E%3CSTRONG%3E%200%20%3C%2FSTRONG%3E%3C%2FTD%3E%0A%3CTD%3EThe%20VM%20is%20turned%20off%3C%2FTD%3E%0A%3C%2FTR%3E%0A%3CTR%3E%0A%3CTD%3E%3CSTRONG%3E%201%20(default)%20%3C%2FSTRONG%3E%3C%2FTD%3E%0A%3CTD%3EThe%20VM%20is%20saved%3C%2FTD%3E%0A%3C%2FTR%3E%0A%3CTR%3E%0A%3CTD%3E%3CSTRONG%3E%202%20%3C%2FSTRONG%3E%3C%2FTD%3E%0A%3CTD%3EThe%20guest%20OS%20is%20shut%20down%3C%2FTD%3E%0A%3C%2FTR%3E%0A%3CTR%3E%0A%3CTD%3E%3CSTRONG%3E%203%20%3C%2FSTRONG%3E%3C%2FTD%3E%0A%3CTD%3EThe%20guest%20OS%20is%20shut%20down%20forcibly%3C%2FTD%3E%0A%3C%2FTR%3E%0A%3C%2FTBODY%3E%0A%3C%2FTABLE%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CH2%20id%3D%22toc-hId-1020401334%22%20id%3D%22toc-hId-1020401334%22%20id%3D%22toc-hId-1020401334%22%3ETo%20start%20the%20cluster%20after%20it%20has%20been%20shut%20down%3C%2FH2%3E%0A%3COL%3E%0A%3COL%3E%0A%3CLI%3ETo%20start%20the%20cluster%20type%3A%20%3CBR%20%2F%3E%3CA%20href%3D%22http%3A%2F%2Ftechnet.microsoft.com%2Fen-us%2Flibrary%2Fhh847289.aspx%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EStart-Cluster%3C%2FA%3E%20%3C%2FLI%3E%0A%3C%2FOL%3E%0A%3C%2FOL%3E%0A%3CP%3E%3CBR%20%2F%3EThanks!%20%3CBR%20%2F%3EElden%20Christensen%20%3CBR%20%2F%3EPrincipal%26nbsp%3BPM%20Manager%20%3CBR%20%2F%3EClustering%20%26amp%3B%20High-Availability%20%3CBR%20%2F%3EMicrosoft%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-371857%22%20slang%3D%22en-US%22%3E%3CP%3EFirst%20published%20on%20MSDN%20on%20Aug%2023%2C%202013%20This%20blog%20will%20discuss%20the%20proper%20process%20for%20shutting%20down%20an%20individual%20node%20in%20a%20Windows%20Server%202012%20R2%20Failover%20Cluster%20or%20the%20entire%20cluster%20with%20all%20the%20nodes.%3C%2FP%3E%3C%2FLINGO-TEASER%3E%3CLINGO-LABS%20id%3D%22lingo-labs-371857%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3Ecluster%20deployment%20planning%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3Eelden%20christensen%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-834289%22%20slang%3D%22en-US%22%3ERe%3A%20How%20to%20Properly%20Shutdown%20a%20Failover%20Cluster%20or%20a%20Node%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-834289%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Elden%2C%3C%2FP%3E%3CP%3E%26nbsp%3BI%20read%20your%20important%20notes%20on%20Hyper-V%20best%20practises%20to%20shut%20down%2F%20restart.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20need%20your%20advise%2C%20second%20thoughts%20on%20shutting%20down%20my%20infrastructure%20for%20cleaning%20my%20rack%20system.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E1-%20Three%20Physical%20Servers%20HP%20Proliant%3C%2FP%3E%3CP%3E2-%20Hyper-V%202016%20Fail%20Over%20Cluster%20roles%3C%2FP%3E%3CP%3E3-%20All%20VM's%20on%20three%20physical%20server%3C%2FP%3E%3CP%3E4-%20One%20HP%20Proliant%20repository%20for%20dedicated%20storage%2C%20not%20related%20to%20Three%20Physical%20server.%3C%2FP%3E%3CP%3E5-%20One%20HP%20Prolaint%20repository%20Storage%20for%20dedicated%20VEEAM%20BACKUP%20STORAGE.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ENow%2C%20I%20have%20notifications%20on%20restart%20required%20due%20to%20critical%20updates%20on%20all%20three%20Physical%20Servers%2C%20including%20VMs%20where%20several%20host%20are%20running.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHow%20can%20I%20achieve%20this%20proper%20shut%20down%20and%20restart.%206%20months%20ago%20I%20blindly%20restarted%20servers%20as%20per%20notifications%20to%20restart%20and%20**bleep**%20my%20VM%20printer%20server%20got%20corrupted%20and%20unable%20to%20start.(%20I%20restored%20it%20via%20VEEAM).%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EShould%20I%20shut%20down%20all%20VMs%20first%20%2C%20then%20physical%20server%20in%20intervals%20like%20each%20servers%20after%205%20minutes%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EPlease%20tell%20me%20the%20sequence%20or%20order.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%20and%20appreciate%20your%20help%20in%20advance.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E

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 will be specific to Windows Server 2012 R2, the process applies to a cluster of any OS version.

Shutting Down a Node

When shutting down or rebooting a node in a Failover Cluster, you first want to drain (move off) any roles running on that server (such as a virtual machine).  This ensures that the shutting down of a node is graceful to any applications running on that node. 

    1. Open Failover Cluster Manager (CluAdmin.msc)
    2. Click on “ Nodes
    3. Right-click on the node name and under ‘ Pause ’ click on ‘ Drain Roles
    4. Under Status the node will appear as ‘Paused’.  At the bottom of the center pane click on the ‘Roles’ tab.  Once all roles have moved off this node, it is safe to shut down or reboot the node.

 

 

To resume the node after it has been restarted…

When the node is once again powered on and ready to be put back into service, use the Resume action to re-enable the node to host roles. 

    1. Open Failover Cluster Manager (CluAdmin.msc)
    2. Click on “ Nodes
    3. Right-click on the node name and select ‘ Resume ’, then select either:
    4. Fail Roles Back ’ – This will resume the node and move any roles which were running on the node prior to the node back.  Caution:  This could incur downtime based on the role
    5. Do Not Fail Roles Back ’ – This will resume the node and not move any roles back.

 

 

Shutting Down a Node with Windows PowerShell®

    1. Open a PowerShell window as Administrator and type:
      Suspend-ClusterNode -Drain
    2. Verify that there are no roles listed under “OwnerNode” for that node by running:
      Get-ClusterGroup
    3. This could be scripted with the following syntax:
      PS C:\> (Get-ClusterGroup).OwnerNode –eq "NodeBeingDrained"

 

    1. Shutdown or restart the computer by typing either:
      Stop-Computer
      Restart-Computer

To resume the node after it has been restarted…

    1. Open a PowerShell window as Administrator and type:
      Resume-ClusterNode

Or if you wish to fail back the roles which were previously running on this node type:
Resume-ClusterNode –Failback Immediate

 

Shutting Down a Cluster

Shutting down the entire cluster involves stopping all roles and then stopping the Cluster Service on all nodes.  While you can shut down each node in the cluster individually, using the cluster UI will ensure the shutdown is done gracefully. 

    1. Open Failover Cluster Manager (CluAdmin.msc)
    2. Right-click on the cluster name, select ‘ More Actions ’, then “ Shut Down Cluster…
    3. When prompted if you are sure you want to shut down the cluster, click “ Yes

Shutting Down a Cluster with PowerShell

    1. Open a PowerShell window as Administrator and type:
      Stop-Cluster

Controlling VM Behavior on Shutdown

When the cluster is shut down, the VMs will be placed in a Saved state.  This can be controlled using the OfflineAction property.

To configure the shut down action for an individual VM (where "Virtual Machine" is the name of the VM):

Get-ClusterResource "Virtual Machine" | Set-ClusterParameter OfflineAction 1
Value Effect
0 The VM is turned off
1 (default) The VM is saved
2 The guest OS is shut down
3 The guest OS is shut down forcibly

 

To start the cluster after it has been shut down

    1. To start the cluster type:
      Start-Cluster


Thanks!
Elden Christensen
Principal PM Manager
Clustering & High-Availability
Microsoft

2 Comments
Occasional Visitor

For a file server cluster you could do something like this, which has the advantage of not needing to restart the cluster service once the nodes have been rebooted.

 

#Get Nodes of FSCluster
[ValidateNotNullOrEmpty()]$FSNodes = (Get-ClusterNode -Cluster $FSCluster).Name
$PrimaryFSNode = $FSNodes[0]
$AuxiliaryFSNodes = $FSNodes[1..($FSNodes.Count -1)]

#Turn off AuxiliaryFSNodes
Get-VM -Name $AuxiliaryFSNodes.Name -ComputerName $HVNodes | Stop-VM -Verbose:$Verbose

#Wait for FSCluster to failover to Primary Node
While ((Get-ClusterGroup -Cluster $FSCluster).OwnerNode -ne $PrimaryFSNode) {
Write-Verbose "Waiting for Cluster $FSCluster to failover to $PrimaryFSNode"
Start-Sleep -Seconds 10
}

#Turn off PrimaryFSNode
Get-VM -Name $PrimaryFSNode.Name -ComputerName $HVNodes | Stop-VM -Verbose:$Verbose
Occasional Visitor

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.