5.6.1 Upgrading MySQL Enterprise Monitor

5.6.1.1 Upgrading from MySQL Enterprise Monitor 1.3 to 2.x
5.6.1.2 Upgrading to MySQL Enterprise Monitor 2.1
5.6.1.3 Upgrading to MySQL Enterprise Monitor 2.2
5.6.1.4 Upgrading to MySQL Enterprise Monitor 2.3

This section describes how to perform an update for the MySQL Enterprise Service Manager or the MySQL Enterprise Monitor Agent, when updates are available for these components.

Upgrade Restrictions

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. Do a fresh installation instead.

You also cannot use the upgrader if you installed the MySQL server for the MySQL Enterprise Service Manager instance outside the MySQL Enterprise Service Manager installation directory.

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

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 you made to the my.cnf within your MySQL Enterprise Service Manager installation. Copy the existing my.cnf file before starting the upgrade installer.

SSL Considerations

The Upgrade installer for MySQL Enterprise Service Manager overwrites any changes you made to the CA certificate files within your MySQL Enterprise Service Manager installation. This includes cacerts for the bundled JRE, and myKeystore for the bundled Tomcat web server. These files are replaced with the bundled CA certificate files, so if custom changes exist (e.g., for an LDAP server with a self-signed certificate) then you must manually re-import the custom changes. These files are backed up during the upgrade, and the locations are logged within the configuration_report.txt log file.

The following example imports one root CA from the backed up file, and uses the default password for keystores in Java which is "changeit". The alias names and path locations may also be different.

$ pwd
/opt/mysql/enterprise/monitor/java/bin

$ ./keytool -importkeystore \
  -srckeystore /opt/mysql/enterprise/monitor/backup/java/lib/security/cacerts \
  -destkeystore /opt/mysql/enterprise/monitor/java/lib/security/cacerts \
  -srcstorepass changeit \
  -deststorepass changeit \
  -srcalias myorigrootca \
  -destalias myrootca

Version Considerations

Warning

The method you use for upgrading MySQL Enterprise Monitor components depends on the upgrade you are performing.

  • To upgrade between major versions (for example, from MySQL Enterprise Monitor 1.3 to MySQL Enterprise Monitor 2.0), start by shutting down the MySQL Enterprise Service Manager and each connected MySQL Enterprise Monitor Agent. First, update the MySQL Enterprise Service Manager, then update the MySQL Enterprise Monitor Agent on each monitored client.

  • To upgrade between the same major version, for example, MySQL Enterprise Monitor 2.2 to MySQL Enterprise Monitor 2.3, or a minor version, such as MySQL Enterprise Monitor 2.3.11 to MySQL Enterprise Monitor 2.3.12, you can shut down only the component (agent, or server) you are updating. Using this method, you can perform a 'rolling' upgrade, where you shut down a single MySQL Enterprise Monitor Agent, upgrade it to the latest agent version, and then restart the agent before moving on to the next monitored instance.

Running the Update Installer

The name of the update file varies, but it shows the target operating system, the version the update applies to, and the component name. (There are separate update installers for the Service Manager and the Agent.) For example, a file named mysqlenterprisemanager-2.3.11-windows-update-installer.exe updates MySQL Enterprise Service Manager on Windows to version 2.3.11.

You install an update in the same way that you initially installed the service manager or the agent; in win32 or unattended mode on Windows; in gtk, text, xwindow, or unattended mode on Unix; and in osx, text , or unattended mode on OS X.

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.

Undoing an Upgrade

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, then overwrite the new files or directories with the originals found in the backup directory. You can delete or archive this directory after you confirm that the update was successful.

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.

Upgrading Advisors

To update your Advisors, see Section 5.2.7.3, “Installing, Updating or Upgrading Advisors After Initial Login”.