search cancel

Moving/Migrate the UIM Installation from old environment to a new one ( Physical or Virtual)


Article ID: 34382


Updated On:


DX Unified Infrastructure Management (Nimsoft / UIM)


How do I move or migrate my primary installation to a new server?


- This information is generally applicable to all versions of UIM.


Moving the Nimsoft installation generally requires making a copy of the old and moving it to the new. However some steps need to be taken before the move.

1. Are you going to need to change the IP Address, or name of the hub?

a. If so, you are going to need to merge all of the QoS data collected by the old hub into the QoS collected by the new hub. This will be true for any QoS with source of the old hub.

The best option (if possible) is to keep the same server name and IP address if possible. It has been found that even using same hostname but with different upper/lower case can cause issues.

2. If you have tunnels between hubs and will be changing the hub name, or address you will need to recreate the tunnels. This will require some downtime for each subordinate hub.

3. Try to make sure that both your data_engine queue and the your nas queue are empty before you copy the files.

To backup the hub:

1. Shutdown Nimsoft on the hub to be moved.

2. Backup the entire directory

   - Windows c:\program files\nimsoft\
   - Linux /opt/nimsoft

A. If you cannot afford the downtime:
a. Stop the data_engine, nas, wasp and sla_engine probes. This should stop any SQL clients from connecting to the database.

b. If possible, stop all QoS data from being inserted into the data_engine queue. This can be done by moving all of the robots connecting to this hub to another hub and then stopping any probes running on this hub.

3. Copy the Nimsoft directory to the new server.

- Windows c:\program files\nimsoft\
- Linux /opt/nimsoft

4. Install the same version of Nimsoft that was on the old server onto the new server.

A. This step will maintain the current configuration files, but register all of the probes.

B. Do not change the userid, or password of the user accessing the data_base during this install. Keep all of the default values and its install should work perfectly.

5. Post-move

A. Re-establish tunnels
B. Re-establish nas replication
C. Activate the probe not already activated.

6. If the hub does not start correctly, or you loose contact with the other hubs you might need these steps: ONLY IF YOU HAVE MULTIPLE HUBS

A. Stop Nimsoft on the new hub
B. Remove the security.cfg, security.dta and security.bak from the hub directory.
- Windows c:\program files\nimsoft\hub
- Linux /opt/nimsoft/hub
C. Restart Nimsoft. Allow it to run for at least 5 minutes before trying to log in again.

Additional Information

Be sure to keep software compatibility in mind when considering this process.

Compatibility Matrix as of 20.4:

Upgrade Path as of 20.4: