Use Case

You have a UMS installation with an embedded database and want to migrate to a new UMS Server with the same embedded database.

General Overview

The migration procedure generally involves the following steps:

  1. Backing up the old server. Checklist for the backups:

    (tick) Database

    (tick) Licenses
    (tick) Transfer files
    (tick) Server configurations (host-specific server configurations that differ from the defaults are noted down separately)
    (tick) Firmware updates
    (tick) UMS Licensing ID
  2. Stopping the IGEL RMGUIServer service on the old server
  3. Transferring the created backups to the new server
  4. Adjusting DHCP tag and DNS alias on the new server OR creating a profile with the IP of the new server for remote administration


On the Old Server

  1. On the old server, create a backup under UMS Administrator > Backups and copy it to a storage medium. Include all options in the backup. For detailed instructions, see the "Embedded Database" section under Creating a Backup

    The backup of Server configurations includes most configurations of the Settings area in the UMS Administrator application. Exceptions: Web server port, JWS server port, and ciphers – they are host-specific, i.e. stored separately on each server and cannot be part of any backup. Therefore, you should note the values of these settings if they differ from the defaults and, in the case of recovery/migration procedure, they must be changed on each server manually.

  2. Create a backup of the UMS Licensing ID in the UMS Administrator > UMS Licensing ID Backup. For detailed instructions, see Transferring or Registering the UMS Licensing ID.
  3. Copy all files from the following folders.

    Device licenses

    • [IGEL installation directory]/rmguiserver/webapps/e08ce61-d6df-4d2b-b44a-14c1ec722c44
    Files and firmware updates
    • [IGEL installation directory]/rmguiserver/webapps/ums_filetransfer
  4. Stop the service IGEL RMGUIServer (for instructions, see HA Services and Processes) and set the startup type for it to "Disabled" in order to prevent accidental parallel operation with the new UMS Server.

On the New Server

  1. Install the UMS on the new server. If possible, use the same database user and password. For the installation instructions, see Installing a UMS Server.
  2. Under UMS Administrator > Backups, select the folder with your backup and restore the respective backup file with all options. Wait until the UMS Server fully starts, i.e. the UMS Console can connect with it.
  3. If necessary, transfer host-specific server configurations to the new server.
  4. Transfer the UMS Licensing ID of the previous UMS installation to the new server: UMS Administrator > UMS Licensing ID Backup > Restore. Alternatively, you can register the new UMS Licensing ID, which was created during the installation of the new server. For detailed instructions, see Transferring or Registering the UMS Licensing ID
  5. Copy files from the following folders to the new server – without the WEB-INF folder:

    • [IGEL installation directory]/rmguiserver/webapps/ums_filetransfer  

    • [IGEL installation directory]/rmguiserver/webapps/e08ce61-d6df-4d2b-b44a-14c1ec722c44

  6. Restart the service IGEL RMGUIServer

  7. If ICG is used: All ICGs have to be reinstalled, see ICG Reinstallation after the Migration of the UMS Server.
  8. Adapt, if necessary, the DHCP tag and the DNS alias igelrmserver with the IP or FQDN of the new UMS Server. See Registering Devices Automatically on the IGEL UMS.

    The configuration of the DHCP tag and the DNS alias is not a setting that can be made within the IGEL software. You must configure these within your individual network environment on the corresponding DHCP and DNS servers.

    If you have used and adjusted the DNS alias and the DHCP option, the following step is NOT required since the device can resolve the name igelrmserver correctly.

    In the local configuration, the device always remembers the IP of the UMS Server of its first registration. It is thus possible that the old IP address is displayed under System > Remote Management. Therefore, it makes sense to manually set an entry for remote administration after the migration:

    1. Create a profile in the UMS:
      • Go to System > Remote Management and click Add.
      • Under UMS Server, enter the IP of the new UMS Server.
    2. Apply this profile globally, to the entire structure.

After the procedure is complete, open the UMS Console and go to UMS Administration > UMS Network > Server to check if there is an entry for the previous UMS Server among the listed components. If so, select the entry and click Delete in the context menu.