I have a multi-subnet AlwaysON AG with one primary and one secondary replica in synchronous commit mode. Due to hardware maintenance the IP address of the secondary node will change.
Is there any actions I should take or anything I should be aware of from a SQL Server, AlwaysON Availability Groups and WSFC perspective?
Best Answer
This shouldn't be a problem if the node ip itself is changing. It's only a slight issue if cluster resource ips are changing.
From the WSFC point of view, assuming that the subnet does not change, there shouldn't be anything needed here.
From SQL Server/AlwaysOn AGs... assuming the subnet does not change:
From an overall point of view:
This may not be an exhaustive list, but should give you an idea and the most critical areas to look at.