# Configuring High Availability (HA) and Disaster Recovery (DR) from Build 11.5.2627.01 This guide explains how to configure High Availability (HA) and Disaster Recovery (DR) for Endpoint Central using the built-in setup wizard under Admin → High Availability. You'll deploy a Data Center (DC) and Disaster Recovery (DR) with one Active server and one or more standby servers so that Endpoint Central services remain available during hardware failures, network outages, or site-level disasters. To know more about High Availability and Disaster Recovery, click [here](https://www.manageengine.com/products/desktop-central/help/server/high-availability.html). ## Pre-requisites for High Availability Management 1. **High Availability License:** To check whether you have a High Availability license, navigate to Profile > License > Additional Features in the Endpoint Central web console. If you do not have high availability license, contact sales at [sales@manageengine.com](mailto:sales@manageengine.com). 2. **Remote Database:** Check whether you have a remote MSSQL or PGSQL database by navigating to Admin > Database Settings > Database Migration in the Endpoint Central Console. It is mandatory to have a remote MSSQL or PGSQL database in the same domain as the active and standby servers. 3. **Remote Repositories:** Ensure remote repositories are configured on a computer within the same domain, not on the active or standby servers. 4. **Static IP Address:** Required for consistent network identification, ensuring all active and standby servers can reliably locate each other and maintain seamless communication during a switchover. 5. **Virtual IP address:** Identify a free IP within the same subnet as the servers at that site. Verify it's unassigned by running commands such as **ping** (to confirm no response) or **arp -a** (to check the ARP table) from any machine on the same network. Kindly refer to [configure Virtual IP](https://www.manageengine.com/products/desktop-central/help/server/configure-virtual-ip.html). 6. **Mail Server Configuration:** Adding a Mail Server is to receive email alerts for server health and connectivity issues that impact high availability. ![Prerequisites — High Availability and Disaster Recovery](https://cdn.manageengine.com/sites/meweb/images/desktop-central/help/server/image1_modified.png) ## Select Deployment Configuration Navigate to **Setup Architecture > High Availability/Disaster Recovery**. Before selecting a configuration, understand how each deployment places your machines and choose the one that best fits your infrastructure needs. ### High Availability **High Availability** — Both Active and Standby servers are deployed at the same site (same subnet). ![Select Deployment Configuration — High Availability selected](https://cdn.manageengine.com/sites/meweb/images/desktop-central/help/server/image2_modified.png) ### Disaster Recovery **Disaster Recovery** — Choose from the following deployment options based on your infrastructure needs: - **Disaster Recovery Deployment with 2 Nodes** — One node at the Data Center site and one node at the Disaster Recovery site. ![Select Deployment Configuration — Disaster Recovery with 2 Nodes](https://cdn.manageengine.com/sites/meweb/images/desktop-central/help/server/image3_modified.png) - **Disaster Recovery Deployment with 3 Nodes** — Two nodes in a High Availability setup at the Data Center site, plus one node at the Disaster Recovery site. - **Disaster Recovery Deployment with 4 Nodes** — High Availability enabled at both the Data Center site and the Disaster Recovery site, with two nodes at each location. ![Select Deployment Configuration — Disaster Recovery with 4 Nodes](https://cdn.manageengine.com/sites/meweb/images/desktop-central/help/server/image4_modified.png) ## Configure High Availability/Disaster Recovery While configuring High Availability/Disaster Recovery, you will be prompted to enter server details. Refer to the section below to learn how to obtain the required details from the machines designated as High Availability and Disaster Recovery. ### Deployment Options #### High Availability Deployment with 2 Nodes Same Site This option deploys both the Data Center server and the High Availability for Data Center server under the same site (same subnet). Provide the following details: ##### Step 1: Configure Data Center (DC) Servers The Data Center (DC) server acts as the Active server. Its details will be pre-filled automatically. ##### High Availability for Data Center (DC HA) Server The High Availability for Data Center server acts as the standby server at the same site. Enter the details of the standby server. - **Display Name:** Enter a name for the High Availability server (e.g., High Availability for Data Center (DC HA)). - **IP Address:** Enter the IP address of the High Availability server (e.g., 10.xx.xx.73). - **Machine Name:** Enter the machine name of the High Availability server (e.g., FOS/FW-SERVER-02). ##### Virtual IP for DataCenter - **IP Address:** Enter the Virtual IP address shared between the Data Center server and High Availability server (e.g., 10.xx.xx.8). ##### Subnet Mask - **Subnet Mask:** Enter the subnet mask applicable to both servers (e.g., 255.xxx.252.0). Once all details are filled in, click **Save & Continue** to proceed. ![Configure DC Servers](https://cdn.manageengine.com/sites/meweb/images/desktop-central/help/server/2nodeimage1.png) ##### Step 2: Notification Email Provide the email address(es) to receive alerts about server health, connectivity issues, and high availability events. Click "Save & Continue". ![Notification Email configuration (HA)](https://cdn.manageengine.com/sites/meweb/images/desktop-central/help/server/2nodeimage2.png) ##### Step 3: Setup High Availability/Disaster Recovery - Restart Required A status page is displayed indicating that a server restart is required. Restart the Active server to activate high availability. > **Note** > > High Availability server details cannot be modified after the restart. Review configurations carefully. Services will be briefly unavailable during the restart. Configurations and data remain intact — no data loss will occur. ![Restart Required to Activate High Availability](https://cdn.manageengine.com/sites/meweb/images/desktop-central/help/server/2nodeimage3.png) ##### Step 4: Server Setup Status (Before Cloning) After the restart, the Server Setup Status page displays the High Availability for Data center server with "Yet to Start" status, along with instructions for cloning and activating the High Availability server. ![Server Setup Status — HA server, Yet to Start](https://cdn.manageengine.com/sites/meweb/images/desktop-central/help/server/2nodeimage4.png) ##### Step 5: Cloning Server Components Follow these steps on the Active Data center server: 1. Stop the Endpoint Central service on the Active Data center server. 2. Open the command prompt in administrator mode and navigate to `\UEMS_CentralServer (Unified Endpoint Management and Security)\bin`. 3. Execute `Clone_Server.bat` (Batch File) to create a backup of server components. ```bat \UEMS_CentralServer\bin>Clone_Server.bat ``` 4. A new zip file "Product.zip" will be created in the `\UEMS_CentralServer` folder. 5. Start the Endpoint Central Server. ![Executing Clone_Server.bat](https://cdn.manageengine.com/sites/meweb/images/desktop-central/help/server/executing_clone_server_bat.png) ![Product.zip file in UEMS_CentralServer directory](https://cdn.manageengine.com/sites/meweb/images/desktop-central/help/server/product.zip_created_in_the_uems_centralserver_directory.png) ## Health Checks After Configuration - **Node Connectivity** — Verifies that the servers can communicate with each other, which is essential for data replication and failure detection. A status of **Reachable** confirms the connection is working properly. - **Patch Store & Software Repository Connectivity** — Displays whether the server can independently access the patch store and software repository. A status of **Reachable** confirms that both sources are accessible and operational. - **Replication Status** — Indicates whether data is being copied from the Active server to the standby server correctly. A status of **Success** confirms that the standby server is fully synchronized with the latest data. - **Upgrade Status** — Indicates whether both servers are running the same software version. A status of **Up to Date** confirms there are no version mismatches. - **Machine Time Difference** — Shows the clock difference between the Active and standby servers. A reading of **0 Seconds — Synchronized** confirms both servers are in perfect time sync. - **Agent & Distribution Server Update Status** — Confirms that all managed devices are aware of the high-availability configuration. A status of **All Updated Successfully** means devices will automatically connect to the standby server during a failover without requiring any manual intervention. ## Support If you have any queries, kindly reach out to [endpointcentral-support@zohocorp.com](mailto:endpointcentral-support@zohocorp.com).