Chapter 6 Upgrading MySQL Enterprise Monitor Installations
Prev |  | Next

## Chapter 6 Upgrading MySQL Enterprise Monitor Installations

This chapter describes the upgrade process from MySQL Enterprise Monitor 3.0.x, or 2.3.x, to MySQL Enterprise Monitor 3.1.x.

The installation process is identical for both types of upgrade.

## 6.1 General considerations when upgrading MySQL Enterprise Monitor

You cannot use the update installers to change to a different operating system or chip architecture. For example, you cannot update a 32-bit Linux installation to a 64-bit version using an update installer. You must perform a fresh installation instead.

Customizations to `setenv.sh` are lost, as this file is replaced and optimized for MySQL Enterprise Monitor 3.0 during an upgrade.

The installation and configuration of MySQL Enterprise Monitor Agent must be standard before you start the installation. The update installer cannot upgrade agents where you have changed or modified the filenames or directory layout of the installed agent.

Important

The upgrade installer overwrites `items-mysql-monitor.xml`. On Windows, this file is in the `C:\Program Files\MySQL\Enterprise\Agent\share\mysql-monitor-agent` directory and on Unix, in the `/opt/mysql/enterprise/agent/share/mysql-monitor-agent` directory. Back this file up if you have made any changes to it.

Warning

The Upgrade installer for MySQL Enterprise Service Manager overwrites any changes made to the `my.cnf` in your MySQL Enterprise Service Manager installation. Backup the existing `my.cnf` file before starting the upgrade installer.

## 6.2 Upgrading to MySQL Enterprise Monitor 3.1.x

To upgrade from 2.3.x or 3.0.x to 3.1, you must upgrade your MySQL Enterprise Service Manager installation first, and your agents after the MySQL Enterprise Service Manager installation completes successfully.

Important

Due to changes in the TLS support introduced in MySQL Enterprise Monitor 3.0.22, you must upgrade your 3.0 installation (Service Manager and Agents) to at least version 3.0.22 before upgrading to 3.1.0. If you attempt to upgrade your MySQL Enterprise Service Manager from a version earlier than 3.0.22 to 3.1, the MySQL Enterprise Service Manager will be unable to communicate with the MySQL Enterprise Monitor Agents due to the mismatch in supported SSL ciphers.

### Upgrade Installer

The name of the upgrade file varies, but includes the target operating system, the version installed by the upgrade, and the component name. For example, a file named ``mysqlenterprisemanager-3.1.1-windows-update-installer.exe`` updates MySQL Enterprise Service Manager on Windows to version 3.1.1.

Run the installation file and choose the directory of your current installation and whether or not you wish to back up your current installation. The time required to complete the process varies depending upon the nature of the update.

You can run an unattended upgrade, the same way you run an unattended install. To see all the options you can specify during the upgrade process, run the update installer with the `--help` option.

For more information on the unattended upgrade process, see Section 8.1.2, “MySQL Enterprise Service Manager Options”.

### Service Manager Upgrade Process

1. Select the required installation language and click Forward. The Installation Directory dialog is displayed.

2. Confirm the location of your existing installation and click Forward. The Backup of Previous Installation dialog is displayed.

   Note

   If you are upgrading from 2.3, an alert is displayed regarding data which cannot be migrated from 2.3 to 3.1.

3. If you want to backup your existing installation, select Yes and edit the Backup directory field if required.

   If you do not want to backup your existing installation, select No.

   Click Forward to continue.

   The Tomcat Server Option dialog is displayed.

4. Confirm the values in the Tomcat Server Port and Tomcat SSL Port fields.

   Click Forward to continue.

   The Repository Configuration dialog is displayed.

5. Confirm your repository Configuration. Click Forward to continue.

   The upgrade is now ready to install. Click Forward to upgrade your installation, or Back to review or edit any values.

   The upgrade process shuts down the MySQL Enterprise Service Manager services and performs the backup of the existing installation, if you chose to do so, then copies the new files to the installation directory, and starts the new services.

6. As the installation completes, you are prompted to reimport any SSL certificates which may have existed in the previous installation. The installer also provides information on where the certificates were backed up.

   Click OK to continue.

7. The installation completes. You are prompted to launch and configure the application.

### Agent Upgrade to 3.1

1. Select the required installation language and click Forward. The Installation Directory dialog is displayed.

2. Confirm the location of your existing installation.

3. Confirm the location of your existing installation and click Forward. The Backup and Restart Options dialog is displayed.

   - Backup the current installation checkbox, specify an alternate location if required. This option is enabled by default.

     If you do not want to back up your existing installation, deselect this checkbox.

   - Restart Agent immediately after updating all files checkbox. Enabled by default.

     If you want to start your agent manually, at a later time, deselect this checkbox.

   The installation is started and completes.

## 6.3 Restoring from Backup

This section describes how to restore an installation from a backup.

If you chose to back up your current installation, a directory named `backup` is created in the current installation directory. This directory contains copies of the directory or directories that are replaced during the update. In cases where only specific files are replaced, the `backup` directory may contain only these files. To undo the update, stop both the MySQL Enterprise Service Manager and MySQL Enterprise Monitor Agent, delete the files and directories in the installation directory, except for the `backup` directory. Copy the contents of the `backup` directory to the installation directory. Then restart the services.

If you choose to back up your current installation, the installer checks that there is adequate disk space for your repository backup. If there is not enough space, you are given the option of choosing another location; you can also choose not to back up the repository.

Prev | Up | Next
Chapter 5 Monitor Agent Installation | Home | Chapter 7 Post-installation Considerations