Page History

Contents

Overview

Moving an existing Uptime Infrastructure Monitor Monitoring Station

Article Contents

...

\n
• Overview \n
• Migrating up.time to the new platform \n
• Back up your current configuration \n
• Download and Install the same up.time version on the new monitoring station \n
• Add your new license to the new monitoring station \n
• Shut down up.time on both the current and new monitoring stations \n
• Move the DataStore \n
• Start up.time on the new monitoring station \n
• Set up other Settings \n
• Validate the Configuration \n

...

Moving an existing up.time 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 up.time monitoring stationUptime Infrastructure Monitor Monitoring Station?

...

Take a few days to determine the average workload that up.time Uptime Infrastructure Monitor places on the system that hosts your monitoring stationMonitoring 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 Monitoring Station belong to the same network space as the original system?

...

Determine if the new monitoring station Monitoring Station is able to resolve the hostnames or IP addresses that you have used for your up.time Uptime Infrastructure Monitor agents. If not, consider updating the hosts file on the new monitoring station Monitoring Station to ensure that you do not have a gap in performance data caused by up.time 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 stationMonitoring Station?

...

If you do not need to migrate configuration settings to the new monitoring stationMonitoring Station, consider performing a clean up.time Uptime Infrastructure Monitor install on the new platform.

...

Do you need to request a new license key for the new monitoring station?

...

Monitoring Station?

The license key used on your current monitoring station Monitoring Station is node locked to the HostID of the monitoring station 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 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 Monitoring Station in a test environment before disabling the original monitoring stationMonitoring Station, please contact licensing@uptimesoftware uptime-support@idera.com to request a temporary test license key.

...

After reviewing these questions, continue with the monitoring station Monitoring Station migration process described below.

...

Migrating Uptime Infrastructure Monitor to the new platform

...

Before migrating the monitoring stationMonitoring Station, you must have the following:

...

\n
• The license key for the new monitoring stationMonitoring Station. \n
• The up.time Uptime Infrastructure Monitor service pack installation package for the same version that is being migrated (available from the Downloads section of the uptime Support site). \n
• The full up.time Uptime Infrastructure Monitor installation package for the same version that is being migrated (available from the Downloads section of the uptime Support site). \n

...

...

Back up your current configuration

...

Review Backing up & Recovering up.timeand Recovering Uptime Infrastructure Monitor for full instructions.

...

Download and Install the same

...

Uptime Infrastructure Monitor version on the new

...

Monitoring Station

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

...

Add your new license to the new

...

Monitoring Station

Log in to Uptime Infrastructure Monitor

...

Login to up.time on the new monitoring stationMonitoring Station. Since Because it will be a fresh up.time 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 stationMonitoring Station.
Enter the new license key when prompted.

...

Shut down

...

Uptime Infrastructure Monitor on both the current and new

...

Monitoring Stations

To stop the up.time services on a Windows platform, stop the following Windows services in the specified order:

...

\nup.time Web Server
\nup.time Data Collector
\nup.time Data Store \n

...

To stop the up.time services on a Unix platform, run the following commands in the specified order:

...

\n# /etc/init.d/uptime_httpd stop
\n# /etc/init.d/uptime_core stop
\n# /etc/init.d/uptime_datastore stop \n

...

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

Move the DataStore

The Uptime Infrastructure Monitor The up.time datastore contains all relevant configuration information for your up.time Uptime Infrastructure Monitor installation. To move the datastore, copy the following directory to the same location on your new monitoring stationMonitoring Station:

...

<uptime_dir>/datastore

...

...

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 stationMonitoring Station, start the up.time services in the following order.

...

On Windows:

...

\nup.time Data Store
\nup.time Data Collector
\nup.time Web Server \n

...

On Unix:

...

\n# /etc/init.d/uptime_datastore start
\n# /etc/init.d/uptime_core start
\n# /etc/init.d/uptime_httpd start \n

...

Uptime Infrastructure Monitor on the new Monitoring Station review - Starting (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) \n\t
• Java Heap Size \n\t
• Scripts and/or plug-in monitors \n\t
• UI Only / Reporting Instance Setting \n

...

Validate the Configuration

...

When the monitoring station Monitoring Station is running on the new system, ensure that all agent systems continue to return new performance data and that up.time Uptime Infrastructure Monitor is registering alerts.

...

If any functionality stops working after moving to the new system, please contact support@uptimesoftware uptime-support@idera.com and provide a description of what is not working along with a Problem Report (Config > Problem Reporting).

...