Deploying Cross-site Replication
Before you deploy cross-site replication, you should also consider the following:
- How to set up each site so that the same spaces are defined on each site.
- How to synchronize the initial loading of data into the spaces on both sites.
- What strategy is used to have clients switch over to using the DR site, if a disaster occurs and the primary site is down.
- What strategy is used to synchronize the data and bring the primary site back online after the DR site has been running in its place.
- Defining Spaces
Cross-site replication works across all spaces in a metaspace. If data is written to a space on the primary site, that same space must already be created on the DR site for cross-site replication to succeed. - Setting Up Cross-Site Replication on the DR Site
To use cross-site replication, you may find it is easier to set up your DR site first as you do not configure the router_discovery setting of the remote site definition on the DR site. On the primary metaspace, the router_discovery setting is composed of the router listen URLs for all of the as-router executables running on the DR site. So, to configure the primary site, you must know how the as-routers have been started on the DR site. - Setting Up Cross-Site Replication on the Primary Site
- Monitoring Cross-site Replication
- An Example of Simple Cross-site Replication
Copyright © Cloud Software Group, Inc. All rights reserved.