Setting Up Cross-Site Replication on the Primary Site
Procedure
- Start your first metaspace member using the additional command line option: -site_name <primary site name>
- Start your ActiveSpaces seeders.
- Ensure your spaces are defined.
- Ensure the appropriate data is pre-loaded into your spaces.
- Start your as-routers.
- Create a remote site definition for your DR site. Use the router_discovery setting you determined in step 6 under Setting Up Cross-Site Replication on the DR Site.
- Wait at least 90 seconds for the as-routers on the primary site to connect to the as-routers on the DR site. If the as-routers on the DR site are up and running, you can see the connections established in the console output of the as-routers on the primary site. However, if they are not up and running, it takes about 90 seconds for the connection attempt to timeout and the status to get updated.
- Use the as-admin command show remote site to ensure the as-routers on the primary site have connected to the as-routers on the DR site. If the as-routers on the primary site cannot connect to the as-routers on the DR site after 90 seconds, the local site state displayed by the show remote site as-admin command is set to offline.
-
Once the as-routers on the primary site have connected to the as-routers on the DR site, start your ActiveSpaces clients.
The as-routers on your primary site do not try to connect to the as-routers on your DR site until you create a remote site definition for the DR site on your primary site and specify the router_discovery setting to use. If an initial connection to the DR site cannot be established by the as-routers, the local site state, displayed by the as-admin command show remote site, is set to offline and the as-routers periodically try to establish a connection. After a connection has been established, the local site state is set to online and cross-site data replication begins.
Copyright © Cloud Software Group, Inc. All rights reserved.