Health monitor fails for same pool members in multiple pools

Hi Guys

 

 

 

the HA nodes are the Production nodes are identical, what will happen is that the production VM's will be clonned and moved to the DR site,

 

even though the same pool members are used in mulitple pools, the pools are not identical, one pool will have production nodes and HA nodes were as the other pool will only have the HA nodes, the reason for this is in a event that the front end production nodes is under strain we will bring up the HA nodes, this additional front ends could cause strain on the SQL backend, when this happens they will brake the sql repliction between the sql clusters and we will bring up the the 2nd pool that consist of just the HA nodes they will then talk to a different sql cluster to eleviate the load.

 

 

Reciprocol Update is enabled,

 

 

i have for now disabled the node checks for these HA nodes, there is a scheduled DR run on the 23rd Feb and then i will be able to see if this makes a difference

 

 

 

Regards

 

 

A