MySQL Enterprise Backup 4.1 Release Notes  /  Changes in MySQL Enterprise Backup 4.1.1 (2018-04-27)

Changes in MySQL Enterprise Backup 4.1.1 (2018-04-27)

Functionality Added or Changed

Bugs Fixed

  • mysqlbackup failed to restore a TTS (transportable tablespace) backup if the row format of any TTS tables did not match the InnoDB default row format on the target server. This was because the row format of a table was not included in the backup if the table was created with the InnoDB default row format. With this fix, the row format is now always written to the backup, so that tables are always restored with the right row format. (Bug #27445546)

  • mysqlbackup failed to backup to an Amazon S3 cloud storage. (Bug #27231229)

  • mysqlbackup could not establish a connection to the server with a Unix socket using the option --protocol=SOCKET. (Bug #26977679)

  • mysqlbackup did not indicate in its output whether an established connection with the server was encrypted or not. With this fix, the crucial information is now provided. (Bug #26919023)

  • An apply-log operation failed when more than one process threads were used for the operation and the backup contained encrypted InnoDB tables. (Bug #26495013)

  • On macOS, mysqlbackup failed to determine the relay log file name correctly if the relay log index file name was not specified. (Bug #25574605)

  • mysqlbackup only accepts values for --ssl-mode in upper case. With this fix, the option's value has become case insensitive. (Bug #25548088)

  • After restoring an incremental backup of a slave server, the file ibbackup_slave_info was missing from the meta folder under the backup directory on the target server. (Bug #25097753)

  • When a compressed backup was restored with the --innodb_data_home_dir option pointing to a restore location outside of the data directory, .ibd files were still being copied into the data directory, causing an exception to be thrown at the attempt to start the restored server. (Bug #24826986)