MySQL Enterprise Backup 3.12 Release Notes  /  Changes in MySQL Enterprise Backup 3.12.1 (2015-06-29)

Changes in MySQL Enterprise Backup 3.12.1 (2015-06-29)

Security Notes

  • MySQL Enterprise Backup has been updated to use OpenSSL version 1.0.1m, which has been publicly reported as not vulnerable to CVE-2015-0286. (Bug #20747721)

Bugs Fixed

  • An apply-log operation on a backup created using transportable tablespace (that is, with the --use-tts option) failed if the backed-up database was using non-default page size for its InnoDB tables. (Bug #21030456)

  • An incremental partial backup failed if the --incremental-base option was used. (Bug #20868507)

  • When creating an incremental backup on a Windows platform using the --incremental-base=dir:directory_path option, if the end_lsn value for the last backup was 232 or larger, the value was retrieved as 232-1 by mysqlbackup. This was because mysqlbackup converted the value from string into long integer, instead of long long integer. This fix corrects the data type used during the conversion. (Bug #20839829)

  • A copy-back-and-apply-log operation failed for an image backup if the value used for the innodb_data_file_path option during restore differed from the value got earlier from the server and stored in the backup-my.cnf file during backup. This was because the copy-back and the apply-log phases used the different values supplied for the option. With this fix, the value supplied during restore is used consistently. (Bug #20512332)

  • A backup failed with the error message Failed trying to flush for export if the names of any table mysqlbackup tried to back up contained special characters (spaces, dashes, periods, dollar signs, etc.). With this fix, table names with special characters are now supported. (Bug #20454754, Bug #75722)

  • A validate operation always failed for a compressed image backup with the complaint that the data file fragments were corrupted when the compressed image was big enough to be broken down into multiple fragments. This was because mysqlbackup failed to recognize the file name extensions of the compressed fragments, and that has been corrected by this fix. (Bug #19796216)

  • When the --include-tables or --exclude-tables option was provided with a regular expression for table names containing special characters, mysqlbackup was handling the special characters incorrectly, and hence table names were not filtered properly and tables were copied incorrectly. With this fix, mysqlbackup handles and filters the table names properly and takes backups of the matching tables. (Bug #19765644, Bug #11762160)