Migrate primary hub from Win 2003 to Win 2008 64 bit

Document ID : KB000056939
Last Modified Date : 14/02/2018
Show Technical Document Details
Q. Is UMP installed on the Nimsoft primary hub?

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

1. Are you going to need to change 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 a source of the old hub.

The best bet is to keep the same server name and IP address if that is possible.

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

3. If you are still using the report_engine and QoS reports: If you are using QoS reports, either dynamic, or static you will need to include the Reports directory in your move. This directory can be very large. Keep this in mind for the copy. Director path is c:\program files\nimsoft\probes\slm\report_engine\Reports.

4. 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 c:\program files <x86)\nimsoft\
A. If you cannot afford the downtime:
a. Stop the data_engine,report_engine,sla_engine,dap and group_server 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 installation directory to the new server.
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 it install should work correctly.

5. Post-move
A. Re-establish tunnels
B. Re-establish nas replication if appropriate
C. Activate the probe not already activated.

6. If the hub does not start correctly, or you lose 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.dat and security.bak from the directory c:\program files\nimsoft\hub.
C. Restart Nimsoft. Allow it to run for at least 5 minutes before trying to log in again.

How to move the Nimsoft SLM database from one location/database SQLServer to another.

0. Install the SQL server on the new machine if it hasn't installed yet.
1. Using the Infrastructure Manager, deactivate the data_engine, report_engine, and sla_engine (also, the group_server, variable_server, and exchange_monitor if applicable).
2. Using the SQL Server Enterprise Manager or SQL Server Management Studio for SQL server 2005/2008, detach the database from the existing database server.
3. Move the database files (both the database file (mdf) and the log file (ldf)) to the new location or new db server.
4. Using the Enterprise Manager,
reattach the database from the new location to the database server
or the new database server
5. Using Infrastructure Manager, change the data_engine config to reference the new SQL server.
6. Activate the data_engine, and then any other probes that you deactivated in step 1.