When epo is clustered, you have to use the virtual cluster name and IP for clients to connect to, not any individual primary or secondary node names/ip's. That way if the cluster fails over to one of the other nodes, the connection is not lost, as the connection is made to the cluster itself that controls which node is active and receiving the traffic.
Was my reply helpful?
If this information was helpful in any way or answered your question, will you please select Accept as Solution in my reply and together we can help other members?
You set up the sql cluster the same way you did epo and use the virtual ip/hostname of the sql cluster for epo to connect to instead of any individual node.
Was my reply helpful?
If this information was helpful in any way or answered your question, will you please select Accept as Solution in my reply and together we can help other members?
Ok let us know if you have further questions on that.
Was my reply helpful?
If this information was helpful in any way or answered your question, will you please select Accept as Solution in my reply and together we can help other members?
I've set up the sql cluster the same way as I did for ePO and use the virtual sql ip/hostname of the sql cluster for ePO to connect to instead of any individual node.
SQL Cluster Validation:
I try to figure out the issue and found a solution by modifying Pri DB (DBA) IP to Virtual SQL IP.
Did the SQL Cluster Validation steps again. It works like a charm! Thank you! 😄
Glad to hear it!
Was my reply helpful?
If this information was helpful in any way or answered your question, will you please select Accept as Solution in my reply and together we can help other members?
Corporate Headquarters
6220 America Center Drive
San Jose, CA 95002 USA