Configuring High Availability for COP Server
  • Dark
    Light
  • PDF

Configuring High Availability for COP Server

  • Dark
    Light
  • PDF

In COP, you can configure a failover cluster that consists of two COP server nodes. This 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 don't have installed COP yet, refer to the ControlUp On-Premises Server Installation guide.

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.

Prerequisites

To use the new feature, make sure you meet the following requirements:

  • General prerequisites for ControlUp On-Premises
  • COP version 8.6.5 or later. Hybrid Cloud environments do not require this feature as the backend servers are located in the cloud
  • Important: To use this feature, uninstall COP server if you want to upgrade to 8.6.5 or 8.7

Adding a Failover Server

Step 1 - Back up license file and log files

Before installing COP on the secondary server, make sure that you have your license file and installation log from the primary COP server installation. During the installation of the secondary COP server, you need to provide the same input data as during the installation of the primary COP server.

  1. On the primary COP server, locate the PrivateCloudLicenseFile.xml. If not configured differently during the installation of the primary COP server, this license file is located in the C:\Smart-X\PrivateCloudLicense folder.

  2. As recommended in the COP installation guide, back up the installation log from the primary COP server which you can find in the C:\Users\UserName\AppData\Local\Temp folder.
    image.png

    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. To see a full list of variables, see the ControlUp On-Premises Installation: Log file article.
    image.png

Step 2 - Install COP on the secondary server

  1. Run the COP installation on the secondary server by following the ControlUp On-Premises Server Installation guide. You need to provide the same credentials and date as during the installation of the primary COP server. Hence, apply the license file from Step 1, the same credentials for the users and the same connection data.

  2. Once the installation of the secondary COP server is complete, connect to the primary server and open Start > Control Panel, right-click ControlUp Server and select Change.

  3. In the Configuration Wizard, click Alternate Server Configuration.
    image.png

  4. Provide the FQDN of the secondary node. You can either use the Browse button or manually type the FQDN. Click Continue.
    image.png

  5. Once the configuration is complete, configure the AD LDS instance for ControlUp on the secondary node.

To configure AD LDS:

  1. Connect to the secondary COP server and open the Control Panel > Programs and Features

  2. Remove AD LDS Instance ControlUp-LDS.
    image.png

  3. Confirm both warning messages by clicking Yes
    image.png

    image.png

  4. Open Active Directory Lightweight Directory Services on your secondary COP server.
    image.png

  5. In the Setup Options windows, select A replica of an existing instance and click Next.
    image.png

  6. Enter ControlUp-LDS in the Instance name field and click Next. Make sure that you correctly type the “ControlUp-LDS”, otherwise the failover feature might not work.
    image.png

  7. Change the LDAP and SSL port numbers to 50500 and 50501 and click Next
    image.png

  8. Enter the FQDN of the primary COP server in the Server field and use port number 50500 as the LDAP port and click Next.
    image.png

  9. Select an account which has sufficient privileges if the currently logged-in account does not have the necessary permissions. Ensure that this user has local administrator rights on the COP servers. Click Next.
    image.png

  10. Mark the Partition DN checkbox as indicated in the screenshot below and click Next.
    image.png

  11. Under File Locations, keep the default values and click Next.
    image.png

  12. Select the Network service account and click Next.
    image.png

  13. Mark the Currently logged on user checkbox. Click Next.
    image.png

  14. Review the installation summary and click Next to install AD LDS.
    image.png

  15. Wait until the wizard completes the installation.
    image.png

  16. Once the setup is complete, click Finish.
    image.png

  17. To check if AD LDS was correctly installed, open the Control Panel and check if the newly installed AD LDS is displayed.
    image.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
image.png

Workaround

To resolve this issue, first uninstall the ControlUp-LDS instance and then the COP server.


Was this article helpful?