This section documents changes and bug fixes that have been applied in MySQL Enterprise Backup, version 3.5.4.
Since a long time elapsed between the InnoDB Hot Backup 3.0 and the MySQL Enterprise Backup product, and MySQL Enterprise Backup is evolving rapidly, also consult Section B.7, “Comparison of MySQL Enterprise Backup and InnoDB Hot Backup” if you are moving from InnoDB Hot Backup to MySQL Enterprise Backup.
The apply-log operation for an incremental backup could fail on Windows with error similar to:
110406 9:43:23 InnoDB: Operating system error number 0 in a file operation. ... ibbackup: Error: cannot delete
If an error occurred during a backup, the
the backup run could be incorrect in the
Running an incremental backup on a database with per-table tablespaces could fail on Windows systems. (Bug #11765740, Bug #58734)
When an incremental backup was taken of a database using
per-table tablespaces, while
TABLE statements were running, the apply-log phase
could fail, leaving the full backup in an inconsistent state.
(Bug #11766088, Bug #59126)
For a system where the LSN has reached a value exceeding 2**31, an incremental backup could fail with the error message:
mysqlbackup: Error: --incremental is given but --lsn is not or wrong value
A blank value for the
configuration option would cause the
command to fail. This fix allows you to specify multiple
directory names in the
configuration option and specify
innodb_data_home_dir with a blank value.
(Bug #59394, Bug #11766307)
Minor fixes for copyright notices.
Copyright © 2003, 2014, Oracle and/or its affiliates. All rights reserved. Legal Notices