[+/-]
From time to time there may be updates to the MySQL Enterprise Service Manager or the MySQL Enterprise Monitor Agent. This section describes how to perform an update for either of these components.
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 — in cases such as this you must do a fresh installation.
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.
The name of the update file varies but it shows the target
operating system and the version the update applies to. If a
specific component is being updated it may also appear in the file
name. For example, a file named
would indicate a Windows update to MySQL Enterprise Service Manager version 2.0.0.
mysqlenterprisemanager-2.0.0-windows-update-installer.exe
You may 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.
The method you use for upgrading MySQL Enterprise Monitor components will depend on the upgrade you are performing.
If you are upgrading between major versions (for example, from MySQL Enterprise Monitor 1.3 to merlin 2.0), you should shutdown the MySQL Enterprise Service Manager and each connected MySQL Enterprise Monitor Agent. Once you have shutdown each component, start by updating the MySQL Enterprise Service Manager, and then updating the MySQL Enterprise Monitor Agent on each monitored client.
If you are upgrading between the same major version, for example, MySQL Enterprise Monitor 2.0 to MySQL Enterprise Monitor 2.1, or a minor version, such as MySQL Enterprise Monitor 2.1.1 to MySQL Enterprise Monitor 2.1.2, you can shutdown only the component (agent, or server) you are updating. Using this method, you can perform a 'rolling' upgrade, where you shutdown 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.
The upgrade installer will overwrite
items-mysql-monitor.xml
. On Windows this
file is found 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. You should back this file up if you have made any
changes to it.
If you use the Upgrade installer to update MySQL Enterprise Service Manager and
you have made any changes to the my.cnf
within your MySQL Enterprise Service Manager installation, any changes will be
lost. You should copy the existing my.cnf
file before starting the upgrade installer.
Otherwise, updating is a fairly straightforward process. 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.
If you chose to back up your current installation, a directory
named backup
will be created in the current
installation directory. This directory will contain copies of the
directory or directories that were replaced during the update. In
cases where only specific files are replaced, the
backup
directory may contain only these
files. If you are unhappy with the update simply overwrite the new
files or directories with the originals found in the
backup
directory. Be sure to stop both the
MySQL Enterprise Service Manager and MySQL Enterprise Monitor Agent before restoring the original
files. You can delete or archive this directory when you are
satisfied 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 may also choose not to back up the repository.
To update your Advisors see, Section 2.2.7.4, “Upgrading and Updating Advisors”.