Our database structure utilizes two roles in the Window Failover Cluster Manager.
- One is for FCI - switching between the active/passive node in the Primary Data center.
- One is for SQL Availability Group setup to copy data from the primary data center to the DR data center. This also use for manual failover in the case of disaster scenario occurs.
Our IT team wants to perform OS patching on these servers regularly on a scheduled down time, the application will be offline when this happens. This helps us out a bit because we don't have to worry about failover to a node while patching another, but instead we can assume we can bring the database offline completely during patching period.
My question is what is the best way to do this since IT team probably does not know much about FCI or Database. I don't want our databases to failover unexpectedly because during this process one of the active SQL node may needs reboot. I'm thinking of giving them the following instruction.
- RDP into the node active Cluster Group, you can find this by running the powershell command: Get-ClusterGroup and find the OwnerNodeValue of the "Cluster Group".
- Open up Failover Cluster Manager Expands to Roles, there are two roles one for AG and one for FCI.
- Right click on each and select "Stop Role"
- Perform patch, restart ect..
- Once done, RDP back in and "Start Role" on the two roles to resume.
Would this work and is it considered good practice? I am hoping to force the failover service to stop so that the SQL nodes don't fail-over to another node during a server reboot.