Open topic with navigation

# Failover to the Disaster Recovery Site

If the servers at site 1 are no longer viable, activate site 2. Once site 2 is activated, the FTL configuration can be managed at site 2. The messaging functions of site 1 are been available at site 2.

1. Use the REST API to activate the FTL configuration at site 2 (command "activate_dr"). Optionally remove "`drfor`" from the site 2 YAML files.

2. Clients and satellites need to reconnect to site 2. Remap the DNS or restart them.

   Reference files:

   - samples/yaml/satellite-dr/tibftlserver_sat_primary2.yaml
   - samples/yaml/satellite-dr/tibftlserver_sat_dr2.yaml

3. Update the realm configuration to activate messaging at site 2. This requires two changes to the persistence cluster: disable disaster recovery replication, and make site 2's server set the active server set. (Disaster recovery replication can be re-enabled later for a planned failback.)

   Reference files:

   - samples/yaml/satellite-dr/satellite-dr-sample-dr-activate.json

Did you find this helpful?

Yes No
Great!
Thanks for taking the time to give us some feedback.
Sorry about that

Why wasn't this helpful? (check all that apply)

Could not find what I was looking for
Instructions confusing or unclear
Instructions did not work

Want to tell us more?

Please select at least one option or provide details about the issue!!

Error occurred while submitting feedback.

Error2 occurred while submitting feedback.

TIBCO FTL® - Enterprise Edition

Copyright © 2009-2024. Cloud Software Group, Inc. All Rights Reserved.