Skip to main content
Skip table of contents

How to Manually Synchronize the UMS ID

When the main UMS ID is not synchronized between the IGEL UMS Servers, UMS ID status under UMS Administration > Global Configuration > UMS ID reads "Not in sync, please restart server", see UMS ID. However, even when you restart the UMS Server, the UMS ID sometimes remains unsynchronized. In this case, the manual synchronization is required.


Environment

  • UMS 12.01.100 or higher

  • High Availability (HA) or Distributed UMS environment

Instructions

The manual synchronization of the UMS ID includes the following steps:

  1. Locating the server holding the main UMS ID

  2. Creating a backup of the UMS ID on that server

  3. Restoring the created backup on all servers with the UMS ID unsynchronized and restarting all servers

Locating the Server Holding the Main UMS ID

To find out which server of the HA or Distributed UMS installation holds the Main UMS ID:

  1. Open UMS Console and navigate to UMS Administration > Global Configuration > UMS ID.

  2. Find the server with UMS ID status saying "Main UMS ID".

Creating a Backup of the UMS ID

  1. Open the UMS Administrator on the server with the main UMS ID you located in the previous step.

  2. Go to UMS ID Backup and create a backup as described under UMS ID Backup in the IGEL Administrator.

  3. Transfer the created backup to every server where the UMS ID is not in sync.

Restoring the Backup on All Servers with the UMS ID Unsynchronized

  1. Open the UMS Administrator on every server where the UMS ID is not in sync.

  2. Go to UMS ID Backup and restore the backup as described under UMS ID Backup in the IGEL Administrator.

  3. Repeat the procedure for all servers with the UMS ID unsynchronized.

  4. When the backup restoring procedure is complete, restart all servers if you have not yet done so.
    In the UMS Console, the UMS ID status under UMS Administration > Global Configuration > UMS ID should show that the UMS ID is now synchronized on all servers.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.