MySQL Enterprise Backup 8.0 User's Guide  /  Getting Started with MySQL Enterprise Backup  /  What's New in MySQL Enterprise Backup 8.0?

Chapter 3 What's New in MySQL Enterprise Backup 8.0?

This chapter highlights the new features in MySQL Enterprise Backup 8.0, as well as any significant changes made to MySQL Enterprise Backup with the release of this series.

  • Offline backups are no longer supported. Using the old --no-connection and --connect-if-online options with MySQL Enterprise Backup will result in an error. The proper connection options must be supplied to MySQL Enterprise Backup when making a backup. The following options, used during offline backups, have also been removed :

    • --innodb_data_file_path

    • --innodb_log_files_in_group

    • --innodb_log_file_size

    • --innodb_page_size

    • --innodb_checksum_algorithm

    • --keyring_file_data

    • --keyring_okv_conf_dir

    • --log_bin_index

    • --relay_log_index

    • --relay-log-info-file

    • --master-info-file

    • --backup_innodb_log_files_in_group

    • --backup_innodb_log_file_size

    • --backup_innodb_undo_tablespaces

    • --backup_innodb_undo_logs

    • --backup_innodb_page_size

    • --backup_innodb_checksum_algorithm

  • 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.

  • 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.

  • A file now tracks information of external tablespaces for a backup or restore in JSON format. See description for tablespace_tracker in Table 1.1, “Types of Files in a Backup” for details.

  • A new option, --tls-version, specifies the protocols mysqlbackup permits for encrypted connections to MySQL servers.

  • MySQL Enterprise Firewall Overview is now supported.

  • The options --ssl and --ssl-verify-server-cert, already deprecated in MySQL Enterprise Backup 4.1, have now been removed. Use the --ssl-mode option instead to configure the security mode of your connection to the server.

  • HTTP Basic Authentication and non-chunked transfer are now supported for backup and restore using OpenStack Swift-compatible object storage services. See Section 17.15, “Cloud Storage Options” for details.

  • The buffer size for cloud transfers can now be specified using the new cloud-buffer-size option. See Section 17.15, “Cloud Storage Options” for details.

  • Servers' use of the keyring_encrypted_file and the keyring_aws plugins is now supported. Also, irrespective of the keyring plugin type that is used on the server, the keyring data is now stored in the backup in an encrypted file. See Chapter 6, Working with Encrypted InnoDB Tables for details.

  • The server option --secure-auth, deprecated since MySQL 5.7.5, is no longer supported by mysqlbackup.

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

  • Due to the new features and functions of MySQL Enterprise Backup 8.0, more privileges are now required for the user by which mysqlbackup connects to the MySQL Server. See Section 4.1.2, “Grant MySQL Privileges to Backup Administrator” for details.

  • For MySQL Enterprise Backup 8.0.12 and later: 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 Chapter 8, Using MySQL Enterprise Backup with Group Replication for details, including the resulting new user privilege requirement for mysqlbackup to connect to a server, regardless of whether the server belongs to a Group Replication setup.

  • For MySQL Enterprise Backup 8.0.12 and later: OAuth is now supported for Oracle Cloud Infrastructure Object Storage client authentication. Two new options, --cloud-storage-url and --cloud-oauth-token, have been introduced for the purpose. See Section 17.15, “Cloud Storage Options” for details.

  • For MySQL Enterprise Backup 8.0.12 and later: The storage engine of the mysql.backup_history table on a backed-up server has switched from CSV to InnoDB. See here for the special user privileges required by mysqlbackup for the mandatory table migration to happen.

  • For MySQL Enterprise Backup 8.0.13 and later: mysqlbackup now supports transparent page compression for InnoDB tables. The support is enabled by setting the mysqlbackup option --compress-method=punch-hole; see description for the option for details.

  • For MySQL Enterprise Backup 8.0.13 and later: mysqlbackup now supports backup compression (i.e., the use of the --compress and --uncompress options) for incremental backups (except for incremental backups created with the --incremental-with-redo-log-only option).

  • For MySQL Enterprise Backup 8.0.14 and later: mysqlbackup now supports the --ssl-fips-mode option, which controls whether mysqlbackup operates in FIPS mode. See FIPS Support for details.

  • For MySQL Enterprise Backup 8.0.14 and later: mysqlbackup now supports encrypted binary and relay log. See Section 7.4, “Working with Encrypted Binary and Relay Logs” for details.


User Comments
User comments in this section are, as the name implies, provided by MySQL users. The MySQL documentation team is not responsible for, nor do they endorse, any of the information provided here.
Sign Up Login You must be logged in to post a comment.