Dear MySQL users,
MySQL Enterprise Backup v3.10.0, a new version of the online MySQL backup
tool, is now available for download from the My Oracle Support (MOS) website
as our latest GA release. This release will be available on eDelivery (OSDC)
after the next upload cycle. MySQL Enterprise Backup is a commercial
extension.
A brief summary of the changes in MySQL Enterprise Backup (MEB)
version 3.10.0 is given below.
Changes in MySQL Enterprise Backup 3.10.0 (2014-03-10)
Functionality Added or Changed
* When using the --skip-unused-pages option for backup
operations, MySQL Enterprise Backup now displays, besides the
number of pages of data skipped, the total amount of memory
saved by using the option. (Bug #15915315)
* In order to enhance security for backed up data, MySQL
Enterprise Backup now provides encryption function for
single-file backups. See Section 7.3, "Encryption for Backups"
and Section 5.1.14, "Encryption Options" for details.
* The compression feature of MySQL Enterprise Backup has been
enhanced by the addition of two compression algorithms: the
LZ4 method (the default for MySQL Enterprise Backup 3.10 and
after) and the LZMA method. Because the LZ4 algorithm, though
faster, produces larger files than the ZLIB algorithm used in
MySQL Enterprise Backup 3.9 and earlier, users of MySQL
Enterprise Backup 3.10 will find an increase in the size of
the compressed files if they use the default values for the
compression options.
* Backups created with the --use-tts option can now be restored
in a single step using the copy-back-and-apply-log subcommand.
* When the apply-log or apply-incremental-backup operation was
performed repeatedly on a backup without using the --force
option, an error message was thrown. From MySQL Enterprise
Backup release 3.10.0 onward, the same action just causes a
message to be returned, saying the operation has already been
performed.
* MySQL Enterprise Backup can now validate data integrity of a
backup directory as well as a backup image file. The
validation function in 3.10 has also become more robust, as it
tries to verify the checksum value of every data page.
* MySQL Enterprise Backup 3.10 introduces two new options for
partial backup: --include-tables and --exclude-tables. The new
options are intended for replacing the older options of
--include, --databases, --databases-list-file, and
--only-innodb-with-frm, which will be deprecated in the near
future.
Bugs Fixed
* mysqlbackup could not read the value of innodb_data_file_path
from the server when it was more than 1024-character long. It
was because mysqlbackup could not read the value from the
configuration files and relied on the SHOW VARIABLES command
(which reads no more than 1024 characters) to access the
parameter. With this fix, innodb_data_file_path can now be
read from the configuration files. (Bug #18038409)
* A backup taken with both the --use-tts=with-full-locking and
--skip-unused-pages options could not be restored. This was
because with --use-tts=with-full-locking used, the apply-log
operation was always skipped (the command did nothing to the
backup), while the expansion of the unused pages was part of
the apply-log operation. This fix separates the expansion from
the apply-log operation, so that the backup can be restored.
(Bug #17764917)
* When a database was initialized with --innodb-file-per-table=0
and had a fixed-size system tablespace, all non-InnoDB files
backed up had zero size. (Bug #17793020)
* After a server restoration from an incremental backup with the
copy-back-and-apply-log subcommand, mysqlbackup returned a
success code even after a file renaming failed during the
restoration process. The restored server thus failed to start
with an assertion error. This fix makes sure a proper error is
thrown when a file renaming fails during a restoration. (Bug
#17539568)
* In a replication setup, when a backup was performed on a
master, the modifications of the tables mysql.backup_history
and mysql.backup_progress were propagated to the slaves,
causing a wrong backup status for the slaves to be registered.
This fix makes MySQL Backup Enterprise disable binary logging
by setting set sql_log_bin=0 during a backup on the master, so
that the backup information will not get replicated to the
slaves. (Bug #17449449)
* When the --messages-logdir option was used and the --trace
option was set to "2" or "3" for an apply-log operation, MySQL
Enterprise Backup created an extra log file. (Bug #17271318)
* When copy-back-and-apply-log was used to restore a backup
created using the --skip-unused-pages option (which is not a
supported use case of copy-back-and-apply-log), MySQL
Enterprise Backup crashed. This fix makes MySQL Enterprise
Backup throw an error instead. (Bug #17281069, Bug #17955913)
* MySQL Enterprise Backup continued to run even after reporting
that --messages-logdir specified a non-existing directory.
This fix makes mysqlbackup exit gracefully upon the error.
(Bug #17268391)
* Because the default value for the parameter
innodb_data_file_path
http://dev.mysql.com/doc/refman/5.6/en/innodb-parameters.html
#sysvar_innodb_data_file_path) had been changed to
"ibdata1:12M:autoextend" since MySQL 5.6.7, during a backup
restoration, if the value of the parameter was not specified
in a configuration file or in the command, mysqlbackup would
still use its default value of "ibdata1:10M:autoextend", which
would cause the restoration to fail. With this fix,
mysqlbackup will use the value of innodb_data_file_path
http://dev.mysql.com/doc/refman/5.6/en/innodb-parameters.html
#sysvar_innodb_data_file_path) as found in the backup's
backup-my.cnf file, but will also issue a warning that,
depending on the configuration of the target server, the user
might need to specify a value for the parameter. (Bug
#16547531)
* With binlogging enabled, MySQL does not necessarily flush the
redo log buffer on commit. The behavior might cause MySQL
Enterprise Backup to take an inconsistent backup, with some of
the transactions (those still in the redo log buffer when the
backup was being taken) possibly missing from the backup. With
this fix, MySQL Enterprise Backup maintains the backup's
consistency by performing a FLUSH ENGINE LOGS on the database
before it records the binglog position and copies the redo log
entries into the backup. (Bug #16401736)
* When the --only-innodb-with-frm option was used, MySQL
Enterprise Backup failed to copy .par and .frm files during
backups. (Bug #15915315)
You can also find more information on the contents of this release in
the change log:
http://dev.mysql.com/doc/mysql-enterprise-backup/3.10/en/meb-news.html
The complete manual for MEB 3.10.0 is at,
http://dev.mysql.com/doc/mysql-enterprise-backup/3.10/en/index.html
The tool is available for download from Oracle Software Delivery
Cloud (http://edelivery.oracle.com/).
You can also download the binaries from MOS, https://support.oracle.com
Choose the "Patches & Updates" tab, and then use the "Product or Family
(Advanced Search)" feature. If you haven't looked at MEB recently,
please do so now and let us know how MEB works for you.
Your feedback is greatly appreciated!
Please report any problems you have at https://bug.oraclecorp.com/
for the product "MySQL Enterprise Backup"
Thanks,
The MySQL build team at Oracle
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql
