MySQL Enterprise Backup
2832
The information collected by the agent about each MySQL server you are monitoring is sent to the
MySQL Enterprise Service Manager. This server collates all of the information from the agents. As it
collates the information sent by the agents, the MySQL Enterprise Service Manager continually tests
the collected data, comparing the status of the server to reasonable values. When thresholds are
reached, the server can trigger an event (including an alarm and notification) to highlight a potential
issue, such as low memory, high CPU usage, or more complex conditions such insufficient buffer sizes
and status information. We call each test, with its associated threshold value, a rule.
These rules, and the alarms and notifications, are each known as a MySQL Enterprise Advisor.
Advisors form a critical part of the MySQL Enterprise Service Manager, as they provide warning
information and troubleshooting advice about potential problems.
The MySQL Enterprise Service Manager includes a web server, and you interact with it through any
web browser. This interface, the MySQL Enterprise Dashboard, displays all of the information collected
by the agents, and lets you view all of your servers and their current status as a group or individually.
You control and configure all aspects of the service using the MySQL Enterprise Dashboard.
The information supplied by the MySQL Enterprise Agent processes also includes statistical and query
information, which you can view in the form of graphs. For example, you can view aspects such as
server load, query numbers, or index usage information as a graph over time. The graph lets you
pinpoint problems or potential issues on your server, and can help diagnose the impact from database
or external problems (such as external system or network failure) by examining the data from a specific
time interval.
The MySQL Enterprise Agent can also be configured to collect detailed information about the queries
executed on your server, including the row counts and performance times for executing each query.
You can correlate the detailed query data with the graphical information to identify which queries
were executing when you experienced a particularly high load, index or other issue. The query data
is supported by a system called Query Analyzer, and the data can be presented in different ways
depending on your needs.
22.2. MySQL Enterprise Backup
MySQL Enterprise Backup performs hot backup operations for MySQL databases. The product is
architected for efficient and reliable backups of tables created by the InnoDB storage engine. For
completeness, it can also back up tables from MyISAM and other storage engines.
The following discussion briefly summarizes MySQL Enterprise Backup. For more information, see the
MySQL Enterprise Backup manual, available at
http://dev.mysql.com/doc/mysql-enterprise-backup/en/
.
Hot backups are performed while the database is running and applications are reading and writing
to it. This type of backup does not block normal database operations, and it captures even changes
that occur while the backup is happening. For these reasons, hot backups are desirable when your
database “grows up” -- when the data is large enough that the backup takes significant time, and when
your data is important enough to your business that you must capture every last change, without taking
your application, web site, or web service offline.
MySQL Enterprise Backup does a hot backup of all tables that use the InnoDB storage engine. For
tables using MyISAM or other non-InnoDB storage engines, it does a “warm” backup, where the
database continues to run, but those tables cannot be modified while being backed up. For efficient
backup operations, you can designate InnoDB as the default storage engine for new tables, or convert
existing tables to use the InnoDB storage engine.
22.3. MySQL Enterprise Security
MySQL Enterprise Edition provides plugins that implement authentication using external services:
• MySQL Enterprise Edition includes an authentication plugin that enables MySQL Server to use PAM
(Pluggable Authentication Modules) to authenticate MySQL users. PAM enables a system to use a
Summary of Contents for 5.0
Page 1: ...MySQL 5 0 Reference Manual ...
Page 18: ...xviii ...
Page 60: ...40 ...
Page 396: ...376 ...
Page 578: ...558 ...
Page 636: ...616 ...
Page 844: ...824 ...
Page 1234: ...1214 ...
Page 1427: ...MySQL Proxy Scripting 1407 ...
Page 1734: ...1714 ...
Page 1752: ...1732 ...
Page 1783: ...Configuring Connector ODBC 1763 ...
Page 1793: ...Connector ODBC Examples 1773 ...
Page 1839: ...Connector Net Installation 1819 2 You must choose the type of installation to perform ...
Page 2850: ...2830 ...
Page 2854: ...2834 ...
Page 2928: ...2908 ...
Page 3000: ...2980 ...
Page 3122: ...3102 ...
Page 3126: ...3106 ...
Page 3174: ...3154 ...
Page 3232: ...3212 ...