Home > Storage > PowerFlex > White Papers > Dell APEX Block Storage for Public Cloud: Microsoft SQL Server Multi-Subnet Failover Clustering Deployment > Validate SQL Server 2022 multi-subnet failover cluster functionality
The main purpose of building a cluster is to ensure that the resources are available in case one of the nodes in the cluster goes down. To ensure that the resources are mapped to the secondary node, you need to manually move the cluster resources from the primary node to the secondary node.
The roles are transferred from current active node SQLNODE-01 to SQLNODE-02 and then from SQLNODE-02 to SQLNODE-03.
Connect to the Failover cluster manager.
Browse to Failover Cluster Manager > Roles > SQL Server (SQLDBFCI).
Right-click the SQL Server cluster object running on SQLNODE-01 and move the Cluster Role. This provides a list of the other passive nodes in the cluster.
Select node SQLNODE-02 and click OK.
The cluster object role is now moved from SQLNODE-01 to SQLNODE-02 and the SQLNODE-01 has become a passive node.
Similarly, move the roles from SQLNODE-02 to SQLNODE-03 and observe that the cluster object becomes online on SQLNODE-03.
Select node SQLNODE-03 and click OK.
The cluster object role is now moved from SQLNODE-02 to SQLNODE-03 and the SQLNODE-02 has become a passive node.