Hi There,
We have built a test environment with MSSQL cluster before going to production.
Implementations:
1) We have built two virtual application server where we hosted same application.(You can assume it as website)
2) We built two Virtual Windows Failover Clusters and then we have installed SQL Failover Cluster on both the machines by giving a virtual IP.
3) all the SQL DB,Logs, Temps file locations are pointed to individual iSCSI LUN's
4) We found that all the functions are working properly on available nodes.
Servers:
Application: 2 ( APP1: 192.168.1.11, APP2:192.168.1.12
Windows Cluster Nodes: 2 (Node1: 192.168.1.21, Node2: 192.168.1.22)
SQL Cluster Virtual IP: 192.168.1.23
Storage: NAS(iSCSI LUN's)
5) Application servers are pointed to SQL Cluster DB: 192.168.1.23
Questions:
i) We have logged into application which is hosted on 192.168.1.11(remember same application hosted on both the servers for load balancing which is pointing to single DB on cluster on the top of application servers we have load balancer) and tried to modified the data( You can assume we have logged in to application using credentials and edited user data by modifying few columns) then we have logged into the same application hosted on 192.168.1.12 which is pointing to the same DB 192.168.1.23 but we don't see the changes are triggered on this server.
ii) we don't understand this strange behavior even though the two applications are pointing to same clustered DB.
iii) Do we need to take any precaution or configuration changes to be done on SQL cluster.
iv) i don't understand if two same applications on two different servers are point to same DB then I should see the same data in both the application servers as per modification which is not happening in my test scenario.
Please share your thoughts.
Thanks
NagarajChengeli