5.6.1.1 Upgrading from MySQL Enterprise Monitor 1.3 to 2.x

5.6.1.1.1 Upgrading to MySQL Enterprise Service Manager 2.x
5.6.1.1.2 Upgrading to MySQL Enterprise Monitor Agent 2.0

To upgrade your existing installation from MySQL Enterprise Monitor 1.3 to MySQL Enterprise Monitor 2.0 or higher, upgrade both the MySQL Enterprise Service Manager and the MySQL Enterprise Monitor Agent on each machine that you are monitoring.

To perform the update process, use an update installer. This ensures that your current configuration information is migrated to the new version of MySQL Enterprise Service Manager.

Before you start the migration, shut down your MySQL Enterprise Service Manager and MySQL Enterprise Monitor Agent on each monitored host. Then, install the updated MySQL Enterprise Service Manager application to migrate the configuration and data of the main application and repository. Once the new MySQL Enterprise Service Manager is running, you can start to update and migrate each agent.

For more information on upgrading your MySQL Enterprise Service Manager, see Section 5.6.1.1.1, “Upgrading to MySQL Enterprise Service Manager 2.x”. For more information on upgrading an MySQL Enterprise Monitor Agent, see Section 5.6.1.1.2, “Upgrading to MySQL Enterprise Monitor Agent 2.0”.

5.6.1.1.1 Upgrading to MySQL Enterprise Service Manager 2.x

Upgrading MySQL Enterprise Service Manager from 1.x to 2.0 or higher requires one of the update installers. The update installer performs a number of operations during installation:

  • A new database, required to support 2.0 functionality, is created.

  • Your core dashboard, user, and rule information is migrated from the old database to the new database.

  • The core configuration parameters for the MySQL Enterprise Service Manager are migrated from MySQL Enterprise Monitor 1.3 are migrated to MySQL Enterprise Monitor 2.x.

The installation of the new software using the update installer follows this basic sequence:

  1. Request the installation language.

  2. Confirm the location of the current MySQL Enterprise Service Manager installation.

  3. Specify whether you want to keep a copy of the old server, application, and database files.

  4. Configure the Tomcat server settings, including whether the new server should support SSL connections from agents.

  5. If requested, the application and database information is backed up and upgraded, before the new application is installed.

The installation process is consistent for all platforms. The following example illustrates the process for Max OS X:

  1. Double-click the update installer. The update installer has update in the file name, for example, mysqlmonitor-2.0.0.7101-osx-update-installer.app.

  2. Confirm the language to use when installing the software.

    Click OK

  3. An information screen shows the application you are installing. Click Next to continue.

  4. Specify, or locate, the previous installation of MySQL Enterprise Service Manager. If you installed the server within the default location, the current version of the application is located automatically.

    Figure 5.13 MySQL Enterprise Monitor: Server Update: Previous Installation

    MySQL Enterprise Monitor: Server Update: Previous Installation

  5. The installer can keep a backup copy of your existing application, including keeping a complete backup of the data stored within your MySQL Enterprise Monitor repository database.

    Figure 5.14 MySQL Enterprise Monitor: Server Update: Backup of Previous Installation

    MySQL Enterprise Monitor: Server Update: Backup of Previous Installation

    Specify the location of the backup (default is to use the backup directory within your installation directory). Note that backing up the database in addition to the main application increases the installation time, as the files are copied. The more data in your repository, the longer the installation process takes.

  6. Specify the Tomcat Server options. The Tomcat Server Port is the default port where you access the MySQL Enterprise Monitor User Interface. If you want to support agents using SSL to communicate to MySQL Enterprise Service Manager, check the Is SSL support required?

  7. Confirm that you want to continue the installation. Once installation has started, the backup of your existing application (and database) starts. This process may take some time. Wait until the process completes.

  8. Once the process has completed, you receive a notification of the installation process, including how to uninstall the application if you want to do so in the future. If any errors occurred, they are reported here.

    Figure 5.15 MySQL Enterprise Monitor: Server Update: Completed installing files

    MySQL Enterprise Monitor: Server Update: Completed installing files

  9. The installation has now completed. You can automatically start the MySQL Enterprise Service Manager and view the attached Readme file by ensuring the checkboxes on this page are selected.

  10. You can now quit the installer.

Once the installation is completed, the first time you login to MySQL Enterprise Monitor User Interface, provide your login credentials, if they do not already exist in the server configuration, or provide a copy of the Advisor jar suitable for your MySQL Enterprise Service Manager version.

Figure 5.16 MySQL Enterprise Monitor: Server Update: Final Setup

MySQL Enterprise Monitor: Server Update: Final Setup

MySQL Enterprise Monitor is now updated. Update each of your agents to MySQL Enterprise Monitor Agent 2.x to ensure that they are providing the correct information to MySQL Enterprise Service Manager.

5.6.1.1.2 Upgrading to MySQL Enterprise Monitor Agent 2.0

To upgrade an agent, use an update installer, which migrates your configuration information while it updates the application files.

Note

The agent log file, mysql-monitor-agent.log, if it exists, is preserved during the upgrade. A new log file, mysql-monitor-agent.log is used by MySQL Enterprise Monitor Agent 2.0.

The core sequence is the same on all platforms. The following section shows the update process on Linux:

  1. Start the update installer.

    shell> ./mysqlmonitoragent-2.0.0.7101-linux-glibc2.3-x86-32bit-update-installer.bin
    

    For MySQL Enterprise Monitor Agent 2.2 and higher, If you have multiple instances of MySQL Enterprise Monitor Agent installed, you can specify a unique name for the agent, which is used to identify the agent startup script (in /etc/init.d and other configuration information. To specify the installation, use the --servicename=mysql-monitor-agent option.

  2. Set the language for the installation process.

    Language Selection
    
    Please select the installation language
    [1] English
    [2] Japanese
    Please choose an option [1] :
    
  3. Confirm or update the location of the installation directory of the previous version.

    ----------------------------------------------------------------------------
    Welcome to the setup wizard for the MySQL Enterprise Monitor Agent Update
    
    ----------------------------------------------------------------------------
    Please specify the directory that contains the previous installation of
    the MySQL Enterprise Monitor Agent
    
    Installation directory [/opt/mysql/enterprise/agent]:
    
  4. Specify whether you want to create a backup of the current application and configuration information, and if so, where the backup directory should be created.

    ----------------------------------------------------------------------------
    Current installation backup
    
    Do you want to create a backup during the update process?
    
    Backup the current installation [Y/n]: Y
    
    
    Backup directory [/opt/mysql/enterprise/agent/patchbackup]:
    
    
  5. Choose whether to enable the Query Analyzer. The Query Analyzer lets you monitor the execution statistics for individual queries executed through your MySQL servers. To enable it, specify the proxy port, MySQL server and MySQL server port that you want to use. If you do not enable Query Analyzer now, you can enable it later. See Section 2.6, “The Query Analyzer Tab”.

    ----------------------------------------------------------------------------
    Query Analyzer Configuration
    
    MySQL Proxy enables query monitoring and analysis by listening on the port
    specified below for client connections that are then passed through to a
    backend MySQL database server. It is not needed for basic monitoring
    functionality, but is required for query monitoring and analysis.
    
    ...
    
    Enable Proxy (recommended) [Y/n]:
    
    
    Proxy Port [6446]:
    
    Backend Host: 127.0.0.1   (cannot be changed)
    
    Backend Port: 3306   (cannot be changed)
    
  6. You are now ready to complete the installation. Confirm that you want to continue.

    ----------------------------------------------------------------------------
    Setup is now ready to begin installing MySQL Enterprise Monitor Agent Update on your computer.
    
    Do you want to continue? [Y/n]:
    
    ----------------------------------------------------------------------------
    Please wait while Setup installs MySQL Enterprise Monitor Agent Update on your computer.
    
     Installing
     0% ______________ 50% ______________ 100%
     #########################################
    
    ----------------------------------------------------------------------------
    Setup has finished installing MySQL Enterprise Monitor Agent Update on your computer.
    
    Restart MySQL Enterprise Monitor Agent now [Y/n]:
    
    View Readme File [Y/n]: n
    

Before connecting your MySQL Enterprise Monitor Agent to your MySQL server, update the grants for the MySQL Enterprise Monitor Agent. Connect to the MySQL server and run this statement to update the required grants:

GRANT CREATE, INSERT
  ON mysql.*
  TO  'mysqluser'@'localhost'
  IDENTIFIED BY 'agent_password';

In the preceding command, replace the mysqluser and agent_password parameters with the values used for connecting your agent to your MySQL server.

Once the update agent has communicated with the MySQL Enterprise Service Manager, the core information about the agent and the MySQL server it is monitoring is migrated to the new data format required by MySQL Enterprise Service Manager 2.x. To migrate the existing stored data, see Section B.6, “Migrating 1.3.x Historical Data to MySQL Enterprise Monitor 2.0”.