Simplified Disaster Recovery: Setup

Complete the following steps when starting FTL servers for the first time (no state on disk).

For reference, see the sample yaml files in the samples/yaml/dr-simple directory of the FTL installation. Use dr-cluster-sample.json as a starting point for the FTL realm configuration. Parameters for the FTL server yaml configuration file are documented in FTL Server Configuration Parameters.

  1. At the primary site, specify the URLs of the DR site by using the dr parameter in the FTL server yaml configuration file. Also, specify the active persistence services of any DR-enabled persistence clusters used by your applications. See the sample yaml files for an example.

  2. At the DR site site, specify the URLs of the primary site using the dr parameter in the FTL server yaml configuration file. Also, specify the standby persistence services of any DR-enabled persistence clusters used by your applications. See the sample yaml files for an example.

  3. If authentication is configured, ensure that the primary FTL servers can authenticate themselves to the DR site, and vice versa. If TLS is configured, distribute trust files to the primary and DR sites (if needed), and ensure that hostnames match configured certificates.

  4. Optional. Specify auto.init.primary.on.first.startup in the FTL server yaml configuration file at the primary site.

  5. Optional. Specify auto.init.primary.on.no.contact in the FTL server yaml configuration file at both sites.

  6. Start FTL servers at both sites. Follow your strategy for selecting the initial primary site.

    • Case 1. The auto.init.primary.on.first.startup parameter is not specified at either site. In this case, FTL servers at both sites wait (indefinitely) for you to select a primary site. It is not be possible to update the FTL realm configuration or connect clients until you choose a primary site.

      Run the activate_dr command at the intended primary site. The other site automatically takes on the DR role. Do not specify auto_config_update (it is ignored as there is no realm configuration yet).

      Example: tibftladmin -ftls <url> --activate_dr

    • Case 2. The auto.init.primary.on.first.startup parameter is specified at the primary site. No further action is needed; FTL initializes the indicated site as primary, and the other site takes on the DR role.

    • Case 3. FTL servers at the DR site are unable to start.

      If you have specified both auto.init.primary.on.no.contact and auto.init.primary.on.first.startup at the intended primary site, no further action is needed. FTL initializes the indicated site as primary, and the other site takes on the DR role when it comes online.

      Otherwise, run the activate_dr command at the intended primary site. The other site automatically takes on the DR role. Do not specify auto_config_update (it is ignored as there is no realm configuration yet).

      Example: tibftladmin -ftls <url> --activate_dr

  7. Ensure that the FTL server's operating mode is correct (primary or DR) at both sites. See Monitoring for Disaster Recovery.

  8. Initialize the FTL realm configuration. At a minimum, you need to create a persistence cluster with two server sets and the DR enabled flag set. See Persistence Configuration for Disaster Recovery for details.

    The primary server set must contain the persistence services you specified in the FTL server yaml configuration file for the primary site. The other (standby) server set must contain the persistence services you specified in the FTL server yaml configuration file for the DR site.

  9. Ensure that persistence services at the DR site are able to contact the primary site. See Monitoring for Disaster Recovery.

  10. Start client applications and direct them to the primary site. Ensure that application data is replicated to the DR site. See Monitoring for Disaster Recovery.