...
The migration procedure generally involves the following steps:
...
Setting the IP address of the new server through profiles (only necessary, if devices find the UMS via IP)
Stopping the
IGEL RMGUIServer
...
service on the old server
Backing up the old server. Checklist for the backups:
Database
Transfer files
Server configurations (host-specific server configurations that differ from the defaults are noted down separately)
Firmware updates
UMS IDTransferring the created backups to the new server
Adjusting DHCP tag and DNS alias on the new server (only necessary, if devices find the UMS via DNS/DHCP)
Instructions
On the Old Server
If the devices find the UMS via the IP address, they can only connect to the new server if the IP address of the new server is set before the migration. To set the IP address:
Create an OS 11 and an OS 12 profile with the new UMS server IP. The new server needs to get listed under System > Remote Management. For more information, see
...
IGEL OS Base System > Configuration of IGEL OS 12 Device Settings > System > Remote Management and IGEL OS > IGEL OS Reference Manual > System > Remote Management.
Assign the profiles.
Check that all devices got their settings by creating a view with the Last Boot Time criterion under Views. For more information, see How to Create a New View in the IGEL UMS.
...
Stop the service
IGEL RMGUIServer
(for instructions, see IGEL UMS 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.
...
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 of the IGEL UMS.
Include Page | ||||
---|---|---|---|---|
|
Create a backup of the UMS ID in the UMS Administrator > UMS ID Backup. For detailed instructions, see Transferring or Registering the UMS ID.
Create a backup of all the files in the following folder. (You will need to restore them on the new server.)
Include Page | ||||
---|---|---|---|---|
|
...
In the UMS Console, go to UMS Administration > UMS Network > Server and note the process ID of the server.
On the New Server
Install the UMS on the new server. If possible, use the same database user and password. For the installation instructions, see IGEL UMS Installation.
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.
...
Transfer the UMS ID of the previous UMS installation to the new server: UMS Administrator > UMS ID Backup > Restore. Alternatively, you can register the new UMS ID, which was created during the installation of the new server. For detailed instructions, see Transferring or Registering the UMS ID.
Note |
---|
It is recommended to use the same UMS ID. The connection to ILP, App Portal and other services are all dependent on the UMS ID, and would be affected if it changes. |
If necessary, transfer host-specific server configurations to the new server.
Restore the files to
...
the folder, keeping the folder structure of the old server:
Include Page | ||||
---|---|---|---|---|
|
...
...
If the ICG is used: Connect the existing ICGs as described under How to Connect to the ICG after the UMS Server Migration or New Installation with the Same Database.
Restart the service
IGEL RMGUIServer
. If the devices find the UMS via the IP address, they should connect automatically.If the devices find the UMS via DNS/DHCP:
Adjust 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.
...
...
Assign the new server to the old server certificate or create and assign a new certificate with the FQDN of the new server. For more information, see
...
Include Page | ||||
---|---|---|---|---|
|
Include Page | ||||
---|---|---|---|---|
|