Migrating to Simplified Disaster Recovery

If you have a pre-existing FTL deployment using the classic DR model, and you want to move to the simplified DR model, perform this procedure.

The main advantage of the simplified DR model is ease of use. The simplified DR model removes the manual administrative steps required by the classic DR model (for example, manipulation of FTL server yaml configuration files or data directories), especially for planned failover or failback.

  1. Upgrade all FTL servers to release 7.3 or better. You must upgrade all FTL servers before starting the transition to simplified DR. See Upgrading or Migrating to a New Release.

  2. Ensure that your enterprise is in a normal state (primary and DR sites online and functioning).

  3. Modify FTL server yaml configuration files at the DR site. Refer to Simplified Disaster Recovery: Setup.

    You must remove drfor and drto from the yaml configuration files. You must add the dr parameter. The auto.init.primary.on.no.contact parameter is optional. The auto.init.primary.on.first.startup flag is irrelevant because FTL server already has state on disk.

  4. Roll the FTL servers at the DR site.

    Restart each FTL server, one-by-one. After each restart, ensure that all persistence services at the DR are operational. See Monitoring for Disaster Recovery.

  5. Modify FTL server yaml configuration files at the primary site. Refer to Simplified Disaster Recovery: Setup.

    You must remove drfor and drto from the yaml configuration files. You must add the dr parameter. The auto.init.primary.on.no.contact parameter is optional. The auto.init.primary.on.first.startup flag is irrelevant because FTL server already has state on disk.

  6. Roll the FTL servers at the primary site.

    Restart each FTL server, one-by-one. After each restart, ensure that all persistence services at the primary site are operational and that client applications continue to function.