MySQL Enterprise Backup 4.1 Release Notes
For MySQL Server 5.7.21 and later: Servers' use of the keyring_encrypted_file and keyring_aws plugins is now supported. See Working with Encrypted InnoDB Tables for details. (Bug #27127898)
Information on the executed GTIDs is now included in the mysqlbackup output and the backup log when the backed-up server has GTIDs enabled. (Bug #25978803)
The buffer size for cloud transfers can now be specified using
the new --cloud-buffer-size
option.
See Cloud Storage Options for details.
HTTP Basic Authentication and non-chunked transfer are now
supported for backup and restore using OpenStack
Swift-compatible object storage services. Two new options,
--cloud-basicauth-url
and
--cloud-chunked-transfer
, have been
introduced for these purposes. See
Cloud Storage Options for details.
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)