Platform Administration and Architecture

Walkthrough: Replicating the Web database using Azure active geo-replication

Abstract

How to gain accelerated publishing speed by using Azure active geo-replication.

You can speed up the publishing of content to multiple Web databases by using Azure active geo-replication. Instead of publishing separately to each Web database, you publish to only one and let Azure replicate that database. But before you can take advantage of geo-replication, you must move the EventQueue and the Properties tables out of the Web database as they can not be replicated.

The traditional publishing configuration

Consider a configuration with a main USA region that handles the content management and two European and Asian affiliate regions. In a traditional publishing configuration, the USA region Content Management (CM) role publishes the content to the Web databases in all three regions, and each regional Web database has its own EventQueue and Properties tables.

Diagram illustrating a traditional publishing configuration.

Region

Content Management role

Web database incl. EventQueue and Properties tables

Content Delivery role

USA

cm_usa

web_usa (publishing target)

cd_usa

Europe

None

web_europe (publishing target)

cd_europe

Asia

None

web_asia (publishing target)

cd_asia

The accelerated replication configuration

By reconfiguring the same scenario to use Azure active geo-replication, the USA region CM role only publishes to the USA region Web database. On completion, Azure active geo-replication replicates the USA region Web database to the European and Asian Web databases. Observe how the three regions a sharing a database containing the EventQueue and Properties tables which can not be replicated.

Diagram illustrating an accelerated replication configuration.

Region

Content Management role

Web database

Content Delivery role

Shared Web database with EventQueue and Properties tables

USA

cm_usa

web_usa (publishing target)

cd_usa

web_shared_system

Europe

None

web_europe (replication target)

cd_europe

Asia

None

web_asia (replication target)

cd_asia

Note

Azure active geo-replication target databases must be configured as read-only.

Deploy the application and storage roles

The main USA region must be deployed as a standard Sitecore installation. The Europe and Asia regions needs to have their Core databases removed.

  1. In the USA region, deploy the CM and CD roles.

  2. In the Europe and Asia regions, deploy the CD role only.

  3. In the Europe and Asia regions, remove the Core database from both regions. The Content Delivery (CD) role is able to run without Core.

  4. Deploy an empty Web database for the EventQueue and the Properties tables.

  5. Configure the CD roles to use the shared Web database.

Configure the Azure active geo-replication

All that is left to do is to configure Azure active geo-replication to replicate data from the USA region Web database ("web_usa") to the Europe and Asia region Web databases ("web_europe" and "web_asia"). Microsoft has excellent documentation for this.