To back up the data stored within your MySQL Enterprise Service Manager, you can
use any of the typical backup solutions, such as the MySQL
Enterprise Backup product or the
command, to back up the
repository database. Once
this database grows to substantial size, you might find that the
binary copy technique of the MySQL Enterprise Backup product is
faster (especially for restoring) than a logical backup using the
mysqldump command. For details, see
MySQL Enterprise Backup User's Guide (Version 3.8.2).
To back up the MySQL Enterprise Monitor data, you specify the host name, user
name, and password that were set during the installation of the
MySQL Enterprise Service Manager. Locate this information in the
configuration_report.txt file that was
generated when MySQL Enterprise Service Manager was installed. The following
example shows a typical report file:
MySQL Enterprise Monitor (Version 184.108.40.20688 : 20081031_152749_r7088) Here are the settings you specified: Application hostname and port: http://127.0.0.1:18080 Tomcat Ports: 18080 - 18443 (SSL) MySQL Port : 13306 Repository Credentials (bundled MySQL): --------------------------------------- service_manager/Password Use the following command to login to the MySQL Enterprise Monitor database: mysql -uservice_manager -pPassword -P13306 -h127.0.0.1
The last line provides the information about how to connect to the server using the standard mysql command line client.
All the MySQL Enterprise Monitor repository information, including your
configuration, rule and historical data is stored within the
To back up this information using
you might use the following command:
shell> mysqldump --single-transaction -uservice_manager -pPassword -P13306 -h127.0.0.1 mem >mem.dump
The above command creates a file,
containing all of the MySQL Enterprise Monitor data.
To ensure consistency in a recovery situation, you may also want to back up the agent configuration and metadata stored on each monitored MySQL server. To do this:
etc subdirectory of each agent
to a backup location. This directory contains the main
mysql-monitor-agent.ini, and the
configuration information for each server being monitored,
which is stored within the
On each server being monitored, back up the
mysql.inventory table, which contains the
unique ID of the MySQL server.
In case the backup process makes the Service Manager unresponsive
for a time, you might also adjust the
agent-backlog-timeout setting as
appropriate, to avoid losing data from the agents during a backup
of the repository database.