In our org. we have a SQL Server DR Cluster set-up, with shared SAN.
there are two nodes (Node1 - 10.10.200.114 & Node2 - 10.10.200.115)
And we have 7 DBs which is using by various applications (SSIS ETLs).
The DR Cluster Name is ClustDRDwh00034, which is using by all the applications.
This is an Active/Standby setup in which, Node1 should be active and if DR incidents happen the the SAN
should be detached from Node1 and attached to Node2 for enable the high availability.
This architecture we need to change, for improve the performance as the Active node load is very high.
The applications (SSIS ETLs) having very complex queries, which may run in parallel, creating resource contention issues.
We are thinking to change this DR Cluster to Always-ON Availability Mode, for mainly .
We are thinking below approaches, please let me know your suggestion/confirm whether this is possible or not...
1. make the two Nodes Active
2. Distribute the DBs into both the Nodes
3. Create two Availability groups, as below
Node1
AG1(DB1,DB2,DB3,DB4 - Primary)
AG2(DB5,DB6,DB7 - Secondary)
Node2
AG1(DB1,DB2,DB3,DB4 - Primary)
AG2(DB5,DB6,DB7 - Secondary)
4. Create a listener with the name same as existing DR Cluster name (ClustDRDwh00034), for AG1 & AG2.
5. All the applications/ETLs need to use the same instance name (ClustDRDwh00034) to connect for DB operation. This will
reduce the application changes, as we are using the same DR Cluster Name as the listener.