ELM Enterprise Manager 7.0 includes the features and functionalities to migrate an ELM Server from one Windows server to another without any delays or loss of data. This seamless transition takes advantage of the flexibility built into the architecture. Specifically, the Agents can be configured to send data sets to one or more ELM Servers.

In the supported migration process, the Agents send all the data to their current ELM Server. Then, from the current ELM Server, the Agents are configured to send in parallel the event and performance data to a newly installed ELM Server. The original ELM Server is then decommissioned leaving the new installation.

The technologies to reliably migrate an ELM Server to new hardware or a virtual image is built into ELM Enterprise Manager 7.0

Products Affected

ELM Enterprise Manager 7.0

Prerequisites

  • Confirm the version of the current deployment of ELM Enterprise Manager. The build number is available in the About ELM Enterprise Manager… under Help on the MMC toolbar. Both the current and the new ELM Server will need to be on the same build. The best practice is to migrate from and to the most current build of ELM Enterprise Manager.
  • Download the current version of ELM Enterprise Manager 7.0. The .exe installation package is available after a short registration at Product Downloads. Save a copy on the new Windows Server and the current ELM Server (if it is not already on the posted build).
  • Save a copy of the current ELM serial number. It is available on the Software License Agreement, the Support and Maintenance Agreement and in the ELM Console under the ELM Server context menu >Properties>Licensing tab.
  • Contact Sales and request a temporary migration license.
  • Copy, save and rename the EEMSVR.dat file from the current ELM deployment. It will be used to migrate the current ELM Server settings and configurations to the new deployment. The EEMSVR.dat file is located under the Program Files(x86) > ELM Enterprise Manager.
  • Copy and save the SQL Server instance for each database in the current deployment of ELM. They are located in the ELM Console under the ELM Server context menu. Select the Database Settings… and copy the Server and Database fields for the Primary Database, the Failover Database and the Archive Database.
  • Save a copy of the IP v4 Address of the new Windows Server.
  • From the new ELM Server Console, expand Monitoring and Management and All Agents. Select the Agent installed on the original ELM Server from the results pane and select Properties from the context menu. Note License type from the Licensing tab and the selected Maintenance and Monitoring Categories. The assigned Monitors should also be recorded to ensure the new Agent is collecting the same data as the current ELM Server. A screenshot of the Monitor Items tab will simplify this task. Close.

Procedure

Step 1: Update or Upgrade ELM to the Current Posted Build
Step 2: Prepare the Current ELM Server for Migration
  1. Convert the current ELM deployment to the temporary migration licence. From the ELM Console, open the ELM Server context menu and select Properties. From there, select the licensing tab and the Edit/Activate button. Copy the migration license serial number provided by the TNT Software Sales Department and paste it into the field. Activate the license.
  2. From the Windows Start Menu, under ELM Enterprise Manager, select the ELM Control Panel. Alternately, it is also available from the Control Panel and as a Tool accessed from the Menu tab in the ELM Dashboard. Select the IP Trusts tab, and paste the new server IP v4 address into the Trusted Servers field. Add the address and close.
Step 3: Install and Configure the New ELM Server
  1. Run the download package of ELM Enterprise Manager 7.0. The first step is to launch the EEM70_xxx.exe install package as an administrator. Then, select the components that are installed on the current ELM Server with the exception of the Agent. Be sure to uncheck the Service Agent to avoid exceeding the licensed Agent quantities. And finally, add the Service Logon name/password and agree to the ELM Enterprise Manager Licensing terms.
  2. Select the Install button to initiate the process. When complete, let the ELM Console and ELM Dashboard open. Select the Finish button and cancel the Agent Deployment Wizard when it opens.
  3. Convert the 30-day download evaluation license to the purchased license. From the ELM Console, open the ELM Server context menu and select Properties. From there, select the licensing tab and the Edit/Activate button. Copy the serial number originally installed in the current ELM Server and paste it into the field. Activate the license.
  4. Migrate the configurations to the new ELM Server. First, go the Services on the new ELM Server and stop the ELM Enterprise Manager Server (EEMSVR) service. Then, copy the renamed EEMSVR.dat file from the original deployment and paste it into the Programs File(x86) > ELM Enterprise Manager directory. Rename the default file and convert the copied file back to EEMSVR.dat. Restart the EEMSVR service.
  5. Update the Agent Configurations for the new ELM Server. From the new ELM Console, right click on All Agents and select All Tasks and Update All Agent Configurations. This will launch a Wizard. Select Next and when completed, Finish.
Step 4: Connect the New ELM Server to the Current Databases
  1. Since both the ELM Servers are in full operation, duplicate data is being stored. The original ELM Server continues to store all the data into the Primary, Failover and Archive databases. Alternately, the new ELM Server is using the run-time databases available in the download.
  2. Configure the new ELM Server to store the data in the current databases. From the new ELM Console right-click on the ELM Server and from the context menu, select Database Settings, and the Connections tab. Paste the SQL Server instance from the current database in the server fields for the Primary, Failover, and Archive Databases. Also, paste in the Database names and execute the Create buttons. Finally, test the connection and close.
  3. Redirect the original ELM Server to its local run-time databases. Again, from the Connection tab, use (LocalDB)\TNT_Data as the Server for both the Primary and Failover databases. Create the databases with the current names and Test. Turn off Archiving by removing the checkmark from the Enable Archive Database option.
Step 5: Transfer Agent to the new ELM Server
  1. Remove the Agent from the original ELM Server system. From the new ELM Server Console, expand Monitoring and Management and All Agents. Select the Agent installed on the original ELM Server from the results pane and select Properties from the context menu. Delete the Agent.
  2. Add an Agent to monitor the new ELM Server. From the All Agents context menu, select New and Agents. Add the new ELM Server name and follow the Wizard to assign the License, Categories, and Monitors from the original ELM Server Agent.
Step 6: Decommission Original ELM Server
  1. Run the new ELM Server and original ELM Server in parallel until the successful migration has been confirmed.
  2. Power down the original ELM Server machine or image to preserve configurations and setting as a reference
  3. Once the migration license has expired, uninstall ELM from the original server. From the Control Panel or install package, uninstall the original ELM Server and components including the local run-time databases

Excluded from the ELM Migration Process

  • SNMP and Syslog supported systems and devices will have to reconfigured to transmit data to the new ELM Servers.
  • Custom configurations created by modifying the Registry Settings will not be transferred to the ELM Server through the EEMSVR.dat file. These settings will require manual updating.