Disaster Recovery

You can use the disaster recovery feature to resume FTL communications after the main operations site becomes disabled. Application systems can continue after the interruption using replicated persistence data at a remote disaster recovery site.

FTL offers two disaster recovery (DR) models: the classic model and the simplified model. New users of FTL must generally use the simplified DR model. The classic DR model remains fully supported. You can migrate from the classic DR model to the simplified DR model. See Selecting a Disaster Recovery Model for more details.

The TIBCO_HOME/ftl/<n.n>/samples/yaml directory contains the following samples:

• dr (the classic DR model)

• dr-secure (the classic DR model, with authentication and TLS)

• dr-simple (the simplified DR model)

• dr-simple-secure (the simplified DR model, with authentication and TLS)

• satellite-dr (DR for satellite sites, using the classic DR model for the hub)

For an overview of disaster recovery, and a discussion of the assumptions and prerequisites of this feature, see Disaster Recovery Concepts.

To configure persistence clusters for DR, see Persistence Configuration for Disaster Recovery.

To monitor the health of DR operations, see Monitoring for Disaster Recovery.

You must select either the classic or the simplified DR model. Most new users of FTL must use the simplified DR model. Pre-existing DR deployments (prior to release 7.3) fall under the classic model. See Selecting a Disaster Recovery Model.

Then, depending on your DR model, refer to Classic Disaster Recovery or Simplified Disaster Recovery.

If you want to migrate from the classic DR model to the simplified DR model, see Migrating to Simplified Disaster Recovery.

If you have configured routes for persistence (also known as store forwarding or wide-area forwarding), and you want to configure disaster recovery for persistence services running at your satellite sites, see Disaster Recovery for Routes.