This chapter highlights the new features in MySQL Enterprise Backup 4.0, as well as any significant changes made to MySQL Enterprise Backup with the release of this series.
Supports MySQL 5.7. MySQL Enterprise Backup 4.0 supports MySQL 5.7 (starting with 5.7.9; for any earlier versions of MySQL 5.7 or 5.6, please use MySQL Enterprise Backup 3.12 instead), on which:
Tables in general tablespaces can be backed up and restored. MySQL Enterprise Backup treats these general table spaces similarly as it treats the tablespaces created outside of the database's data directory using the
CREATE TABLE ... DATA DIRECTORY =statement; for details, see the description for the
.blfiles in Table 1.1, “Types of Files in a Backup”.
InnoDB tables with page sizes of 32 and 64KB can be backed up and restored.
Some of the MySQL 5.7 features are not supported by MySQL Enterprise Backup, and some limitations apply for the supported features. See Appendix B, Limitations of MySQL Enterprise Backup for details.
Stores Tape Backup Information on the MySQL Server. Each time an online backup is made to a tape using the System Backup to Tape (SBT) API , an entry is made to the
mysql.backup_sbt_historytable on the backed-up MySQL instance. That facilitates the management of tape backups by allowing easy look-ups for information on them. See Section 9.1, “Backing Up to Tape with Oracle Secure Backup” for details.
Supports Encrypted InnoDB Tablespaces. MySQL Enterprise Backup 4.0.2 and later is capable of backing up and restoring encrypted InnoDB tables. See Chapter 6, Working with Encrypted InnoDB Tables and Section 15.14, “Options for Working with Encrypted InnoDB Tablespaces”.