Configuring a Directory server to be a disaster recovery server excludes the server from load balancing. A disaster recovery server only activates if it takes over as the main server during a Directory failover.
Before you begin
What you should know
- If a Directory server is at a remote location or has a slow connection, you can enable the disaster recovery option so that it does not slow down the system by participating in load balancing.
- A disaster recovery server does not accept client connections unless it becomes the main server during a Directory failover.
- Roles such as the Media Router, Health Monitor, and Report Manager are often hosted on Directory servers. If you are enabling disaster recovery, you must enable the Force execution on highest priority server option on all roles that are hosted on Directory servers. This ensures that these roles do not continue to run on the disaster recovery server after the primary Directory server is back online. For more information, see "Role failover".
- From the Config Tool home page, open the System task, and click the Roles view.
- Select the Directory Manager () role, and click the Directory servers tab.
At the bottom of the server list, click
An extra column, Disaster recovery, is displayed in the list.
Select Disaster recovery for one or more Directory
NOTE: The Disaster recovery option only applies to Directory servers, not to Gateways.
- Click Apply.
The server is excluded from load balancing and only accepts client connections if it becomes the main server during a Directory failover.