Migrating to Another Active Site

You can also use the disaster recovery feature to migrate FTL operations to a different site, even though no disaster has occurred.

This task uses the following terminology:
Site F (from site)
The site that currently hosts FTL operations, the site from which you are migrating FTL operations.
Site T (to site)
A site that you designate as the new active site, the site to which you are migrating FTL operations.
Complete these task steps during scheduled downtime.

Procedure

  1. Start a disaster recovery realm server at site T.
    This realm server will become the new primary realm server in step 7.

    You may also start affiliated realm servers at site T as backups and satellites of this realm server.

  2. Ensure that persistence clusters are enabled for disaster recovery.
    Within each cluster that is configured for disaster recovery, ensure that the set of persistence servers at site F is the primary set.
  3. Ensure that persistence servers are running at site T.
    Complete this step for each persistence cluster that participates in the migration.
  4. Stop all publishing activity, and wait for the persistence servers to finish replicating the data.
    In the persistence clusters status table and its servers list sub-tables, compare the history values of all the servers. When they match, replication is complete.

    Verify replication for each participating persistence cluster.

  5. Stop all persistence servers at site F.
  6. Stop all realm servers at site F.
  7. Stop and restart the realm server at site T.
    Supply appropriate parameters so that this server becomes the new primary realm server.
  8. Activate the persistence servers at site T.
    1. Using the browser GUI of the primary realm server at site T, navigate to the clusters grid, and ensure that the Primary Set column is visible.
    2. Change the primary set of each participating cluster so that the persistence servers at the site T will become the primary set.
    3. After changing the primary server set for all participating persistence clusters, deploy the new realm definition.
  9. Direct application clients to servers at site T.
    Choose only one of these two alternatives:
    • If you remapped the DNS addresses of realm servers and persistence servers.
      1. Verify that the new DNS information has propagated.
      2. Verify that all clients automatically reconnect to servers at site T, and are operating correctly.
    • Otherwise, restart all application clients. Explicitly supply the locations of realm servers at site T.

Result

Site T is now the active site of FTL operations.