This section documents changes and bug fixes that have been applied in MySQL Enterprise Backup, version 3.5.4.
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
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)
Running an incremental backup on a database with per-table tablespaces could fail on Windows systems. (Bug #11765740, Bug #58734)
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)
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
Minor fixes for copyright notices.