HDR,RSS and ER

Hello all, I will be implementing ER in the very near future and have an ok grasp on the basics I think. The current setup is with a Primary Node, a Secondary node running an HDR instance, and a Tertiary Node running RSS. The ER configuration will be from the Primary node to the Tertiary node to a new instance. My question is about the sqlhosts file setup on the secondary node to allow for failing to that instance. I have the primary and tertiary setup with groups (master, subscriber1) but what would be in for the secondary configuration in the 3 sqlhosts files? and what needs to change in the config upon failover/switchover to the secondary (HDR) instance? Thanks for any help/advice anyone has. -eric.

ER will always connect to the primary node in a cluster. I would suggest placing all of the nodes in a single group so that you can easily support fail-over. This way,ER would connect to the CURRENT primary node of the cluster and would automatically fail-over if the primary is off-line. g_er_node_name group - - i=1primary_node .... g=g_er_node_namesecondary_node ... g=g_er_node_namerss_node ... g=g_er_node_name On Monday, October 12, 2015 10:42 AM, ERIC KIMBLE <eric.kimble@portlandoregon.gov> wrote: Hello all, I will be implementing ER in the very near future and have an ok grasp on the basics I think. The current setup is with a Primary Node, a Secondary node running an HDR instance, and a Tertiary Node running RSS. The ER configuration will be from the Primary node to the Tertiary node to a new instance. My question is about the sqlhosts file setup on the secondary node to allow for failing to that instance. I have the primary and tertiary setup with groups (master, subscriber1) but what would be in for the secondary configuration in the 3 sqlhosts files? and what needs to change in the config upon failover/switchover to the secondary (HDR) instance? Thanks for any help/advice anyone has. -eric. ******************************************************************************* Forum Note: Use "Reply" to post a response in the discussion forum.

Thanks Madison for the response. I think I understand and just need to makes sure. The option i=1 to designate the server group and then having all 3 of the nodes in that group should/will not affect the HDR and RSS environments from running? here's my sqlhosts example now. #dbservername nettype hostname servicename options #RSS node disignation rss_tcp onsoctcp db3 555555 #node db1 primary instance primary_tcp node db2 HDR hdr_tcp scooby group - - i=1 primary_tcp onsoctcp db1 555555 g=scooby hdr_tcp onsoctcp db2 555555 g=scooby er_tcp onsoctcp db3 666666 g=scooby

There is no impact to the other servers. The i= number is used by ER to identify the server group (i.e. cluster) that it should replicate to. [1]Sent from Yahoo Mail for iPad On Oct 12, 2015, 12:37:10 PM, ERIC KIMBLE wrote: Thanks Madison for the response. I think I understand and just need to makes sure. The option i=1 to designate the server group and then having all 3 of the nodes in that group should/will not affect the HDR and RSS environments from running? here's my sqlhosts example now. #dbservername nettype hostname servicename options #RSS node disignation rss_tcp onsoctcp db3 555555 #node db1 primary instance primary_tcp node db2 HDR hdr_tcp scooby group - - i=1 primary_tcp onsoctcp db1 555555 g=scooby hdr_tcp onsoctcp db2 555555 g=scooby er_tcp onsoctcp db3 666666 g=scooby ********************************************************************** ********* Forum Note: Use "Reply" to post a response in the discussion forum. References 1. https://yho.com/footer0