Contents

Contents Overview
Migrating Uptime Infrastructure Monitor to the new platform Back up your current configuration
Download and Install the same Uptime Infrastructure Monitor version on the new Monitoring Station Add your new license to the new Monitoring Station
Shut down Uptime Infrastructure Monitor on both the current and new Monitoring Stations Move the DataStore
Delete ib_logfile* files
Start Uptime Infrastructure Monitor on the new Monitoring Station Set up other Settings
Validate the Configuration

Overview

Moving an existing Uptime Infrastructure Monitor Monitoring Station deployment to a new system involves a number of steps to prepare for the move and complete the system migration. Before moving to a new platform, answer the questions in this article regarding your migration objectives.
Can the new platform manage the workload produced by the Uptime Infrastructure Monitor Monitoring Station?
Take a few days to determine the average workload that Uptime Infrastructure Monitor places on the system that hosts your Monitoring Station. Next, determine if the new system will be able to handle this additional workload (factoring in any other applications that may be running on the same platform). Also consider if the new system has sufficient disk capacity to handle the historical performance data and new data being gathered from the monitored elements.
Will the new Monitoring Station belong to the same network space as the original system?
Determine if the new Monitoring Station is able to resolve the hostnames or IP addresses that you have used for your Uptime Infrastructure Monitor agents. If not, consider updating the hosts file on the new Monitoring Station to ensure that you do not have a gap in performance data caused by Uptime Infrastructure Monitor being unable to contact agents after being installed on the new system.
Do you need to maintain all configuration settings on the new Monitoring Station?
If you do not need to migrate configuration settings to the new Monitoring Station, consider performing a clean Uptime Infrastructure Monitor install on the new platform.
Do you need to request a new license key for the new Monitoring Station?
The license key used on your current Monitoring Station is node locked to the HostID of the Monitoring Station system. A new key must be generated for the new platform. To receive a new key you must find the HostID of the new Monitoring Station and then follow the instructions in the Moving Your License Key article.
If there is a requirement to run the new Monitoring Station in a test environment before disabling the original Monitoring Station, please contact uptime- support@idera.com to request a temporary test license key.
After reviewing these questions, continue with the Monitoring Station migration process described below.

Migrating Uptime Infrastructure Monitor to the new platform

Before migrating the Monitoring Station, you must have the following: The license key for the new Monitoring Station.
The Uptime Infrastructure Monitor service pack installation package for the same version that is being migrated (available from the Downloads section of the Support site).
The full Uptime Infrastructure Monitor installation package for the same version that is being migrated (available from the Downloads section of the Support site).

Back up your current configuration

Review Backing up and Recovering Uptime Infrastructure Monitor for full instructions.

Download and Install the same Uptime Infrastructure Monitor version on the new Monitoring Station

Use the full Uptime Infrastructure Monitor installation package to install a clean but same version of Uptime Infrastructure Monitor on the new Monitoring Station.

Add your new license to the new Monitoring Station

Log in to Uptime Infrastructure Monitor on the new Monitoring Station. Because it will be a fresh Uptime Infrastructure Monitor install, it will ask you to set the admin password and SMTP server. These values will be reset once the configuration is copied from the old Monitoring Station.
Enter the new license key when prompted.

Shut down Uptime Infrastructure Monitor on both the current and new Monitoring Stations

To stop the Uptime Infrastructure Monitor services review - Starting (or restarting) and Stopping Uptime Infrastructure Monitor

Move the DataStore

The Uptime Infrastructure Monitor datastore contains all relevant configuration information for your Uptime Infrastructure Monitor installation. To move the datastore, copy the following directory to the same location on your new Monitoring Station:
<uptime_dir>/datastore Consider compressing the data within this directory before moving the configuration information to minimize transfer time. Also ensure that file transfers are completed in BINARY mode as datastore files may be corrupted if they are transferred in ASCII.

Delete ib_logfile* files

If the MySQL ib_logfile* size on the old Monitoring Station server differs from the new one, MySQL will fail to start. To avoid this issue, it is best to delete the <uptime_dir>/datastore/data/ib_logfile* files. They will be automatically recreated when the Uptime Infrastructure Monitor Data Store service starts next.

Start Uptime Infrastructure Monitor on the new Monitoring Station

After the datastore directory has been moved to the new Monitoring Station, start Uptime Infrastructure Monitor on the new Monitoring Station review - Start ing (or restarting) and Stopping Uptime Infrastructure Monitor

Set up other Settings

Some settings may not be included with the configuration and performance data and may need to be individually configured. These parameters may include:
SMTP/Email Settings (under Config > SMTP Server) Java Heap Size
Scripts and/or plug-in monitors
UI Only / Reporting Instance Setting

Validate the Configuration

When the Monitoring Station is running on the new system, ensure that all agent systems continue to return new performance data and that Uptime Infrastructure Monitor is registering alerts.
If any functionality stops working after moving to the new system, please contact uptime-support@idera.com and provide a description of what is not working along with a Problem Report (Config > Problem Reporting).