MySQL Enterprise Backup 4.1 Release Notes  /  Changes in MySQL Enterprise Backup 4.1.2 (2018-07-27)

Changes in MySQL Enterprise Backup 4.1.2 (2018-07-27)

Functionality Added or Changed

  • Important Change: Starting from release 4.1.2, the storage engine of the mysql.backup_history table on a backed-up server has switched from CSV to InnoDB, and a new column for server UUIDs has been added to the table. See Backup History Table Update for the new user privileges required by mysqlbackup due to this change.

  • Important Change: When working with a Group Replication setup, mysqlbackup now makes the backup history available to all members of the server group by making sure that the backup_history table is updated on a primary node after each mysqlbackup operation. See Using MySQL Enterprise Backup with Group Replication for details.

    With the implementation of this feature, the new user privilege of SELECT on performance_schema.replication_group_members is now required by mysqlbackup to work with any server, even when it does not belong to a Group Replication setup. See Grant MySQL Privileges to Backup Administrator for details.

  • The binary log for a backed-up server, instead of being restored always to the data directory on the target server, is now restored by default to the same location it was found on the backed-up server. It can also be restored to a different location specified with the new --log-bin option. (Bug #25141738, Bug #83927)

  • The relay log for a backed-up slave server, instead of being restored always to the data directory on the target slave server, is now restored by default to the same location it was found on the backed-up slave server. It can also be restored to a different location specified with the new --relay-log option. (Bug #25141738, Bug #83927)

  • The backup_history table now includes a server_uuid column, which stores the value of the server_uuid of the backed up server.

  • OAuth is now supported for Oracle Cloud Storage client authentication. Two new options, --cloud-storage-url and --cloud-oauth-token, have been introduced for the purpose. See Cloud Storage Options for details.

Bugs Fixed

  • During an --apply-incremental-backup operation, mysqlbackup attempted to delete the binary log of the backed-up, running server. (Bug #28377502)

  • A mysqlbackup operation on an image stored on an OpenStack cloud storage service sometimes failed with a segmentation fault or a bad URL error. It was because of a race condition caused by an uninitiated variable, which has been eliminated by this fix. (Bug #28189239, Bug #28183729)

  • Backups failed when the --log-bin option on the backed-up server contained a full-path pointing to a location under the server's data directory. (Bug #28044530)

  • A mysqlbackup operation on an image stored on an OpenStack cloud storage service failed with a 401 Unauthorized error when the operation took a long time and the authentication token for the cloud access expired. With this fix, a separate thread in mysqlbackup requests a new token from the OpenStack cloud service in that situation, so that the operation can continue. (Bug #27893174)

  • The maximum value that could be set for the --safe-slave-backup-timeout option was 2700 (seconds), which automatically replaced any larger value. With this fix, there is no longer a maximum limit, even though a high value is not recommended; see the description of --safe-slave-backup-timeout for details. (Bug #27883020)

  • When mysqlbackup performed sanity checks on InnoDB tablespaces and found a space ID mismatch for an FSP header and a page header, the name of the problematic tablespace was not given in the error report. (Bug #27752703)

  • mysqlbackup issued a warning whenever the number of files specified in the system variable innodb_data_file_path of the server to be backed up exceeded 100. With this fix, a warning is issued only if the number of InnoDB data files to be opened exceeds the number specified by the system variable innodb_open_files. (Bug #27701402)

  • An apply-incremental-backup operation failed when individual tablespaces with relative file paths were involved. (Bug #27278876)

  • Backups created with the ---skip-unused-pages option failed validation by the mysqlbackup validate command. (Bug #27102697)

  • mysqlbackup quit unexpectedly when the --disable-manifest option was used in a backup operation. (Bug #26861475)

  • A restore operation for an incremental backup failed when individual tablespaces with relative file paths were involved. (Bug #26442994)