MySQL Forums
Forum List  »  Announcements

MySQL Enterprise Backup 4.1.4 has been released
Posted by: Surabhi Bhat
Date: January 24, 2020 07:22AM

Dear MySQL users,

MySQL Enterprise Backup v4.1.4, a new version of the MySQL backup tool, is
now available for download from the My Oracle Support (MOS) website
as our latest GA release. This release will be available on eDelivery (OSDC)
after the next upload cycle. MySQL Enterprise Backup is a commercial
extension to the MySQL family of products.

MySQL Enterprise Backup 4.1.4 only supports MySQL 5.7.
For MySQL 5.6 and earlier, use MySQL Enterprise Backup 3.12.
For MySQL 8.0, use MySQL Enterprise Backup 8.0.

A brief summary of the changes in MySQL Enterprise Backup (MEB)
version 4.1.4 is given below.

Changes in MySQL Enterprise Backup 4.1.4 (2020-01-24)


* Functionality Added or Changed

* Bugs Fixed

Functionality Added or Changed


* When mysqlbackup fails to connect to a server, the
warning returned by mysqlbackup now includes the hostname
and port number for TCP connections, and the socket
information for socket connections. This is particularly
helpful for a Group Replication setup, for which
mysqlbackup might attempt to connect to more than one
host. (Bug #30040027)

* Before the current release, when backing up a server that
used the keyring_okv
( https://dev.mysql.com/doc/refman/5.7/en/keyring-okv-plugin.html )
plugin for InnoDB table encryption, mysqlbackup
must not be run by a sudo user of its operating system.
This restriction has now been removed. (Bug #29020232)

* A new option, --lock-wait-retry-count, can now be used to
specify the maximum number of retries to be attempted by
mysqlbackup after the FLUSH TABLES WITH READ LOCK
statement, issued during the final stage of a backup to
temporarily put the database into a read-only state,
fails due to a timeout. See the description of the option
for details. (Bug #26008480)

* The --uncompress option is now supported for the extract
operation: Files from a compressed single-file backup can
now be extracted and uncompressed with a single command.

Bugs Fixed


* A backup failed for a server containing encrypted InnoDB
tables when mysqlbackup was connected to it with --socket
option. It was because mysqlbackup did not pass the value
of --keyring-migration-socket to the keyring migration
server; this fix makes mysqlbackup pass the option
whenever it connects to the server to be backed up with a
Unix socket or Windows named pipe. (Bug #30082039)

* A compressed and encrypted single-file backup was
sometimes corrupted if the backed-up server was
configured with innodb_file_per_table=OFF. (Bug
#29798621)

* Backups on busy servers failed due to redo log
overwrites, even when the redo log size was big. It was
actually caused by a costly but unnecessary check for
relay log overwrites, which has been removed by this fix.
(Bug #29526337)

* When tables were altered in some ways during backup (for
example, renamed, deleted and then replaced by tables of
the same names, and so on), mysqlbackup reported success
for the backup, but the backup could not be restored.
This fix makes sure all those cases of table alterations
are properly handled by mysqlbackup, so the backup can be
restored. (Bug #29462340)

* When backing up a server that used the keyring_okv
( https://dev.mysql.com/doc/refman/5.7/en/keyring-okv-plugin.html )
plugin for InnoDB table encryption, if the
--host, --user, and --port options were not specified
with the mysqlbackup command via the command line or a
configuration file, the backup failed. It was because in
that case, mysqlbackup had no values for those options it
could use to connect to the server that took care of
keyring operations. With this fix, default values are now
set, so that mysqlbackup connects to the server on
localhost as root and on port 3306 for keyring operations
when those options are not specified. (Bug #29015923)

* A restore operation for a TTS backup failed if the
backed-up server has ANSI_QUOTES
( https://dev.mysql.com/doc/refman/5.7/en/sql-mode.html#sqlmode_ansi_quotes )
as one of its SQL modes, as specified
in its system variable sql-mode. (Bug #28979134)

* Attempts to extract binary log files from a compressed
backup failed with a No such file or directory error when
the size of the binary log files on the backed up server
was greater than 16MB. (Bug #28787312)

* After restoring an incremental backup taken from a MySQL
Community Server with encrypted InnoDB tables, the
keyring file of the restored server became corrupted, so
the server could not be started. (Bug #28422191)

* During the InnoDB buffer pool dump in a backup operation,
mysqlbackup sometimes reported failure for the dump while
it was actually still in progress. The fix prevents the
problem by improving the way mysqlbackup checks for the
status of the dump. (Bug #27185901)

* mysqlbackup tried to connect to a remote host specified
by the --host option, while it was supposed to ignore the
option (see Connection Options
( https://dev.mysql.com/doc/mysql-enterprise-backup/4.1/en/connection-options.html )
for details). With this fix, the option is now ignored.
Note
As a side-effect of this change, on Unix-like platforms,
mysqlbackup command that used the --host option now needs
to use the --protocol=TCP option to indicate explicitly
that mysqlbackup is to connect to localhost using TCP/IP.
(Bug #25911987)

* Backups failed for database containing tables created
with transparent page compression
( https://dev.mysql.com/doc/refman/5.7/en/innodb-page-compression.html ),
with complaints of page corruption. It was
because mysqlbackup did not perform decompression before
data validation, and that has been corrected with this
fix. (Bug #24366571)

* A backup failed at the step when mysqlbackup applied the
FLUSH TABLES tbl_name [, tbl_name] ... WITH READ LOCK
statement on all non-InnoDB tables if any table names
contained reserved words or special characters. It was
because mysqlbackup did not enclose table names in
backticks when issuing the statement, and this fix makes
sure that is done. (Bug #19709505, Bug #74144)

On Behalf of MySQL Release Engineering Team,
Surabhi Bhat

Options: ReplyQuote


Subject
Views
Written By
Posted
MySQL Enterprise Backup 4.1.4 has been released
1342
January 24, 2020 07:22AM


Sorry, you do not have permission to post/reply in this forum.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.