Just wanting to get some advice from others who have maybe gone down this route as i've only ever had to work with a single core DB setup and currently considering options for new setup of prod using 2 clusters.
This is all in relation to Sitecore 8.2 (update 5/7) and Sitecore 9 soon.
Say we wanted to setup Sitecore on 2 DCs so for DR purposes if one goes down the other would remain active, CM would remain on 1 DC only.
1 DB server (Core,Master, Web, session)
1 DB server (Core2,Web2, Session2)
Basically similar to description here: https://doc.sitecore.com/developers/90/platform-administration-and-architecture/en/clustering-and-geographic-distribution.html
There is this statement there:
Each cluster has its own dedicated core database - core databases cannot be replicated and must be managed per cluster. When you set up a new cluster, you can copy the existing core database from your existing cluster to get started.
This setup is not recommended if you are managing extranet users in the core database
There is also this link: https://doc.sitecore.com/developers/90/platform-administration-and-architecture/en/scale-databases.html
If you have multiple Content Delivery clusters, consider dedicating a core database to each cluster
Replication of the core database is not officially supported - refer to the following article for information about supported SQL scaling features: https://kb.sitecore.net/articles/423602
So my questions are:
- In this scenario do we need to keep core DB's synched in situations where site doesn't have any login functionality and doesn't use WFFM?
- In other sites where we do use Virtual Users to authenticate users and based on roles show specific parts of site, and do use WFFM. Do we need to sync the Core DB. (Users are not managed in Sitecore, uses 3rd party authentication)
- What is the best method to do this sync given replication is not supported (in an Active/Active scenario where both DCs are Active eg 4 Content Delivery Servers are active) and also in Active/Passive scenario where a couple of hours of downtime is acceptable.