Skip to content

Disaster Recovery Flow

To enable Disaster Recovery mode, select the production servers and set them back to Inactive (see Configuration). This action will automatically set the corresponding DR servers to Active.

Note

Only the Production servers have the Active / Inactive button enabled.

If the website and/or API servers are down, manual intervention is required for clients to connect.

There are two possible ways to recover: 1. In the DNS server, change the target URL of the website/API to point to the disaster recovery environment. This is the recommended action and will likely be the simplest solution. 2. Alternatively, browse directly to the disaster recovery environment address.

High Availability Configuration Considerations

In addition to changing the designation of servers as active / inactive, you have to ensure that the relevant servers are listed in the high availability load balancer.

This depends on the types of servers listed in the load balancer:

Services listed in the load balancer Configuration changes required when changing the disaster mode
All Prod services and DR services Nothing to change
however
if you are monitoring the load balancer health checks you will receive many false positives of broken servers.
Production services only Update the load balancer to point to the newly activated DR services
Different load balancer for Production & DR Change the load balancer address inside the server installer load balancer screen.

Note

For the website load balancer configuration, only the second two options are relevant.

Disaster Recovery Fallback to Production Environment

Select the production servers and set them back to Active (see Toggle above). This will set the corresponding DR servers to Inactive.

Return to Production Requires Installing the Services

  1. Select Reset on the server configuration screen.
  2. Reinstall the services.
  3. After completing the installation, wait at least 2 minutes to allow all File Access Manager services to update their configuration.
  4. Set the Production servers to Active.

Production Server Has to be Replaced

If the production server cannot be restored and a new one is required:

  1. In the Server Installer, add a new server to the server list.
  2. Continue through the setup and select Save Configuration.
  3. Restart the Server Installer.
  4. Select the new server in the Server Configuration list, select Edit, and then Deactivate (the new server is not yet ready to be live).
  5. Configure the required services on the new server and install them.
  6. Wait for at least 2 minutes after the installation has completed.
  7. Turn the new server Active.

Fallback Includes the Production Server of the Web Site/API Server

In the event that the fallback includes the production server of the website/API server, manual intervention will be required for clients to reconnect.

The required action will depend on the recovery action taken in the section "Switching on Disaster Recovery mode":

  • If the DNS server was changed, it should be reverted to point to the Production environment.
  • If the DNS server was not changed, you should browse directly to the Production environment address.