--- title: "Configuring High Availability for COP Server" slug: "configuring-high-availability-for-cop-server" updated: 2026-04-12T08:32:00Z published: 2026-04-12T08:32:00Z canonical: "support.controlup.com/configuring-high-availability-for-cop-server" --- > ## Documentation Index > Fetch the complete documentation index at: https://support.controlup.com/llms.txt > Use this file to discover all available pages before exploring further. # Configuring High Availability for COP Server In COP, you can configure a failover cluster that consists of two COP server nodes. The following article walks you through the installation and configuration of a secondary COP server, and assumes that you have already installed COP on the primary server. If you haven't yet installed COP, see [ControlUp On-Premises Server Installation](/v1/docs/controlup-on-premises-server-installation). ## Feature Overview If the primary COP server or the COP web services are offline, the Real-Time Console and ControlUp Monitor automatically connect to the secondary COP server. To learn how to configure the primary and secondary COP servers, see [ControlUp On-Premises Real-Time Console Installation](/v1/docs/controlup-on-premises-real-time-console-installation). Supported SQL Server Note that this configuration does **not** support SQL Server Express. ## Prerequisites You must meet the following prerequisites in order to use this feature: - [General prerequisites for ControlUp On-Premises](/v1/docs/on-premises-installation-prerequisites-at-a-glance-for-8-1-and-higher). - COP installed. Hybrid Cloud environments don't require this feature because the backend servers are located in the ControlUp Cloud. - High availability database. Important! You must uninstall your current COP server before you can upgrade to higher versions. ## Adding a Failover Server ### Step 1. Back up license file and log files Before installing COP on the secondary server, verify that you have your license file and installation log from the primary COP server installation. During the installation of the secondary COP server, you must provide **the same input data** as you did during the installation of the primary COP server. 1. On the primary COP server, locate the license file ***PrivateCloudLicenseFile.xml***. If configured the same as during the installation of the primary COP server, this file is located in the folder **C:\Smart-X\PrivateCloudLicense**. 2. Back up the installation log from the primary COP server, located in the folder **C:\Users\UserName\AppData\Local\Temp**. For more details about log files, see [ControlUp On-Premises Installation: Log Files](/v1/docs/controlup-on-premises-installation-log-files) . Open the file and navigate through the data you provided during the installation. For example, the mail address is stored in the LICENSE_EMAIL variable. For a full list of variables, see [ControlUp On-Premises Installation: Log file](/v1/docs/controlup-on-premises-installation-log-files#variables). ![Log File listing the the LICENSE_EMAIL variable](https://cdn.document360.io/098100b7-b9da-4bea-b4b9-017140ab863e/Images/Documentation/image-B4GAOWDG.png) ### Step 2. Install COP on the secondary server 1. Follow the steps in [ControlUp On-Premises Server Installation](/v1/docs/controlup-on-premises-server-installation) to run the COP installation on the secondary server. You must provide the same credentials and date as during the installation of the primary COP server. For example, provide the license file from Step 1, and the same user credentials and connection data. 2. After the installation of the secondary COP server is complete, connect to the primary server, open **Start** > **Control Panel**, right-click **ControlUp Server**, and select **Change**. 3. In the Configuration Wizard, click **Alternate Server Configuration**. ![ControlUp On-Premises Server Installation wizard screen](https://cdn.document360.io/098100b7-b9da-4bea-b4b9-017140ab863e/Images/Documentation/image-TODLJVM4.png) 4. Provide the FQDN of the secondary node. You can choose to use the **Browse** button or manually enter the FQDN. Click **Continue**. ![Alternate Failover Server screen](https://cdn.document360.io/098100b7-b9da-4bea-b4b9-017140ab863e/Images/Documentation/image-735P4T43.png) Once the configuration is complete, the next step is to configure the AD LDS instance for ControlUp on the secondary node. ### Step 3. Configure AD LDS 1. Connect to the secondary COP server and open **Control Panel > Programs and Features**. 2. Remove **AD LDS Instance ControlUp-LDS**. ![Programs and Features window with AD LDS Instance ControlUp-LDS selected](https://cdn.document360.io/098100b7-b9da-4bea-b4b9-017140ab863e/Images/Documentation/image-7BPFAN6U.png) 3. Click **Yes** to confirm both warning messages. 4. Open **Active Directory Lightweight Directory Services** on your secondary COP server. ![Active Directory Lightweight Directory Services setup wizard app](https://cdn.document360.io/098100b7-b9da-4bea-b4b9-017140ab863e/Images/Documentation/image-74XTEEXT.png) 5. In the Setup Options windows, select **A replica of an existing instance** and click **Next**. 6. Enter **ControlUp-LDS** in the **Instance name** field and click **Next**. If you don't enter “**ControlUp-LDS**” correctly, the failover feature fails. ![Active Directory Lightweight Directory Services setup wizard app with ControlUp-LDS instance entered](https://cdn.document360.io/098100b7-b9da-4bea-b4b9-017140ab863e/Images/Documentation/image-0TZ3OY2O.png) 7. Change **LDAP port number** to **50500** and **SSL port number** to **50501**, and click **Next** 8. In the **Server** field, enter the **FQDN** of the **primary COP server**, and in the **LDAP port** field, enter **50500** and click **Next**. 9. **Optionally**, if the account you are currently using doesn't have the necessary permissions, select an account that does. Ensure that this user has local administrator permissions on the COP servers. Click **Next**. ![Active Directory Lightweight Directory Services setup wizard with currently logged on user selected](https://cdn.document360.io/098100b7-b9da-4bea-b4b9-017140ab863e/Images/Documentation/image-MCLP535L.png) 10. Select the **Partition DN** checkbox and click **Next**. 11. In **File Locations**, keep the default values as is and click **Next**. 12. Select **Network service account** and click **Next**. 13. Select **Currently logged on user** and click **Next**. 14. Review the installation summary and click **Next**. 15. After installation completes, click **Finish**. 16. To verify if AD LDS was successfully installed, you can view AD LDS in the **Control Panel**. ![Programs and Features window with AD LDS Instance ControlUp-LDS selected](https://cdn.document360.io/098100b7-b9da-4bea-b4b9-017140ab863e/Images/Documentation/image-5I8OHDWX.png) ## Troubleshooting ### AdamUnInstall returned error code 1603 The following error message might appear when uninstalling the COP server with failover nodes configured: > CustomAction AdamUninstall (ControlUp-LDS) returned actual error code 1603 ![Uninstall failed screen with error CustomAction AdamUninstall (ControlUp-LDS) returned actual error code 1603](https://cdn.document360.io/098100b7-b9da-4bea-b4b9-017140ab863e/Images/Documentation/image-06LUW5SE.png) ### Workaround To resolve this issue, first uninstall the ControlUp-LDS instance, and then uninstall the COP server.