Menu path: UMS Administrator > Backups

Default path to the UMS Administrator:

Linux: /opt/IGEL/RemoteManager/
Windows: C:\Program Files\IGEL\RemoteManager\rmadmin\RMAdmin.exe

Embedded Database

To create a backup of the UMS installation with the embedded database, proceed as follows:

  1. In the left-hand column, select Backups.
  2. Click on Change to change the storage location for your backups.
  3. Click on Create.
  4. Under Backup name, enter a name for the backup.
  5. Select the backup settings under Choose backup settings:
    The following can be selected:
    • Select all: Database, licenses, server configurations, and transfer files (normally, you’ll use this option to ensure that no components are missing from the backup)
    • Legacy: Database
    • All files: Licenses and transfer files (e.g. images, session certificates, etc.)
    • Custom: You can select the data which are to be backed up.

      All certificates are included in the database backup.

      Universal Firmware Updates

      The files of firmware updates are not part of the UMS embedded DB backup. They are not included in the Transfer files backup, and, therefore, have to be copied manually from [IGEL installation directory]/rmguiserver/webapps/ums_filetransfer.
      Or you can simply download the required firmware updates anew.

      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.

  6. Confirm your selection by clicking on OK.
    The data will be saved in the directory you have selected.

    Remember to back up also the UMS Licensing ID, see UMS Licensing ID Backup or UMS Licensing ID Backup on the Command Line.

External Database

The full range of backup options in the UMS Administrator is only available if you use the embedded database for your UMS Server installation.

If you use an external database, proceed as follows to make a complete backup of your system:

  1. For the database itself, use the backup and recovery procedures recommended by the DBMS manufacturer.
  2. Back up server configurations with the UMS Administrator > Backups > Create > Custom > Server configurations:

  3. Certificates, licenses, files, and firmware updates must be backed up separately, i.e. manually copied to a secure storage medium. You can find them here: 
    • [IGEL installation directory]/rmtcserver/*

    • [IGEL installation directory]/rmclient/cacerts

    • [IGEL installation directory]/rmguiserver/https_cert_chain.keystore

    If you do not save the certificates, you will not be able to communicate with the endpoint devices anymore.

    Files and firmware updates

    • [IGEL installation directory]/rmguiserver/webapps/ums_filetransfer (without the WEB-INF folder)

    Device licenses
    • [IGEL installation directory]/rmguiserver/webapps/e08ce61-d6df-4d2b-b44a-14c1ec722c44 (without the WEB-INF folder)
  4. Back up also the UMS Licensing ID, see UMS Licensing ID Backup or UMS Licensing ID Backup on the Command Line.

    If you are using an HA environment, note the following:
    It is always the UMS Licensing ID of the local server that is backed up. Therefore, make sure at first that the local UMS Licensing ID is the same as the main UMS Licensing ID. If not, restart the UMS Server to synchronize the local UMS Licensing ID with the main UMS Licensing ID and then proceed with creating the backup. See also Manual Synchronization of the UMS Licensing ID.

  5. For HA installations only: Save the current IGEL network token. This is usually a token created during the installation, see Installing the First Server in an HA Network. If a new IGEL network token has been generated in the meantime, e.g. if changes to certificates were made (see "High Availability" under Device Communication), this is the token to be backed up.