CODEWITHSUNDEEP
sitecoresitecore7
mluker
mluker

Reputation: 702

Sitecore High Availability Architecture

Page 14 of the scaling guide states

The following diagram illustrates the connections between the Web instances and the Sitecore databases for a setup which contains isolated instances within the CM and CD environments

Using this set up I want to have a load balancer in front of CD1 and CD2 lets call it Geo region 1 and another load balancer in front of CD3 and CD4 lets call it geo region 2. I also need to have a DNS resolver that will fail over to geo region 2 as needed (strictly a fail over). It will have to be manually reset back to geo region 1 once all of the issues have been resolved. I am worried about the situation when a user changes their password in the CD1-2 zone and how that information gets back to the CORE db located in the CM1-2 zone.

I was planning on having one publishing target and using SQL Merge Replication between the databases and GEO locations as outlined in the diagram mentioned on page 14 of the scaling guide. It seems this setup will solve all syncing DB issues.

Is this a reasonable/working architecture for a high availability setup?

Scaling guide URL if needed.

Upvotes: 3

Views: 1035

Answers (1)

Ben Golden
Ben Golden

Reputation: 1580

See page 12 of the guide. The answer depends on if you are using the default SQL membership provider or an external provider like Active Directory. If you are using the default membership provider, then you will want to set up replication between your core databases in the CD and CM environments as well as security cache clearing. If you are using an external provider, you can usually skip replication of the core databases and just set up the security cache clearing.

Upvotes: 1

Related Questions