4

When implementing multiple regions/clusters, sitecore documentation states that each cluster must have its own core database.(https://doc.sitecore.com/developers/90/platform-administration-and-architecture/en/clustering-and-geographic-distribution.html)

Each cluster has its own dedicated core database - core databases cannot be replicated and must be managed per cluster

How do you keep core dbs synced? One of the options we are looking at is to publish from CM server. We tested locally by adding core references in configuration files and a publishing target in core db. It seems to work fine at first sight. Is there any danger in publishing from one core to others?

4

We have always used database-level replication to keep core databases in sync.

I don't have experience doing this with publishing, but I have a couple concerns. These are things that happen when an item is published that you may not want for core databases:

  1. You will lose version history of the items on the destination core database since publishing only keeps one version
  2. Unless you customize it, the HTML cache (presentation cache) will be cleared with each publish, even though you're not publishing content
  3. Any other custom publish:end or publish:end:remote event handlers you've registered for your application
  • I thought db replication wasn't support by sitecore – josedbaez Jan 17 at 12:59
  • Technically that's true, but it's worked well for us. – Dan Sinclair Jan 17 at 13:02
  • We also use DB replication. We have been using since we first launched our site on Sitecore over 2 years ago. We have not had any issues. – Mikeyp Jan 18 at 15:05

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.