Newbie: Service Packing a Node

-

suppose i have 2 node failover cluster , want apply windows service pack 1 node. if have reboot node won't remaining one think first node failed and take place?  if so, what happens cluster when rebooted (updated) node comes on line?

 

 

 

tia,

 

barkingdog

 

 

i things in controlled manner instead of letting server reboot.  letting server reboot automatically work (after all, clusters designed handle hardware outages ), prefer in more control this.

 

move cluster resources node want patch.  patch system , let reboot.  go far pause cluster service on node, isn't necessary.

 

after node reboots, move cluster resources newly patched node see works expected on patched software.  when satisfied test, patch other node.

 

when both nodes patched, balance resources how want them.

 

it possible define preference nodes resource.  means if resource running on 1 node , goes down, automatically fail on other node.  however, when cluster detects preferred node online, automatically move resources preferred node.  not use preference nodes because if happens node, rather testing/troubleshooting on node before allow cluster resources onto it.  otherwise, possible have ping-pong effect if node having sort of intermittent problem , bouncing , down.  not setting preferences, there not automatic failback preferred node; in control of movement of resources in running environment.

 

tgc



Windows Server  >  High Availability (Clustering)



Comments

Post a Comment

Popular posts from this blog

WIMMount (HSM) causing cluster storage to go redirected (2012r2 DC)

-
looking options resolve error , prevent in future. thanks help. hardware: 2 node dell hv cluster running2012r2 dc 8 nic/ea in multiplex mode 4x hyper-v 4x hosts storage: 2x synology nas, accessed through iscsi hosts , cluster relevant logs: log name:      microsoft-windows-failoverclustering/diagnostic source:        microsoft-windows-failoverclustering date:          event id:      2050 task category: none level:         warning keywords:       user:          system computer:      l description: [dcm] filter wimmount found @ unsafe altitude 180700 log name:      system source:        microsoft-windows-failoverclustering date:         event id:      5125 task category: cluster shared volume level:         warning keywords:       user:          system computer: description: cluster shared volume 'volume1' ('cluster disk 1') has identified 1 or more active filter drivers on device stack interfere csv operatio
Read more

Failed to delete the test record dcdiag-test-record in zone test.com

-
ps c:\users\administrator.test> dcdiag /test:dns directory server diagnosis performing initial setup:    trying find home server...    home server = dc02    * identified ad forest.    done gathering initial info. doing initial required tests    testing server: default-first-site-name\dc02       starting test: connectivity          ......................... dc02 passed test connectivity doing primary tests    testing server: default-first-site-name\dc02       starting test: dns          dns tests running , not hung. please wait few minutes...          ......................... dc02 passed test dns    running partition tests on : forestdnszones    running partition tests on : domaindnszones    running partition tests on : schema    running partition tests on : configuration    running partition tests on : test    running enterprise tests on : test.com       starting test: dns          test results domain
Read more

Azure MFA with Azure AD and RDS

-
i have setup following lab in azure , need help. a server (domain controller) , remote desktop services. and server multi factor authentication server. i have setup following one http://www.rdsgurus.com/uncategorized/step-by-step-using-windows-server-2012-r2-rd-gateway-with-azure-multifactor-authentication/ and when im connecting got following error. the user "domain\username", on client computer "xxx.xxx.xxx.xxx", did not meet connection authorization policy requirements , therefore not authorized access rd gateway server. authentication method used was: "ntlm" , connection protocol used: "rpc-http". following error occurred: "23003". also on security log i've got following authentication details: connection request policy name: ts gateway authorization policy network policy name: - authentication provider: radius proxy authentication server: test.test.local authentication type: - eap t
Read more