start_time_utc

end_time_utc

consistency_time_utc

meb_version

server_uuid（适用于 4.1.2 及更高版本）

--lock-wait-retry-count现在可以使用 一个新选项 来指定mysqlbackupFLUSH TABLES WITH READ LOCK在备份的最后阶段发出以暂时将数据库置于只读状态的语句之后 尝试的最大重试次数，由于超时而失败. 有关详细信息，请参阅选项的描述。

--uncompress该操作现在支持该选项 ，extract 因此现在可以使用单个命令从压缩的单文件备份中提取和解压缩文件。

对于copy-back-and-apply-log 和 除 之外 的其他单文件操作backup-to-image，当为 --backup-image选项指定相对路径时， mysqlbackup将路径作为相对于 运行mysqlbackup命令的当前工作目录的路径。

该--rename选项现在适用于完全和部分恢复：

When a server using the keyring_file, keyring_encrypted_file, or keyring_aws was backed up, if it did not contain any encrypted InnoDB tables, the keyring file was not included in the backup. That created a problem when, for example, mysqlbackup was used for a server upgrade, in which case the keyring file was not preserved in the process. mysqlbackup now always looks for the keyring data file and copies it when the above-mentioned keyring plugins are active on the server.

Encrypted InnoDB tables can now be included in partial backups and restores using transportable tablespaces (TTS).

The file backup_gtid_executed.sql was not included in a TTS backup for a replica server using GTIDs. The file is now included in a TTS backup as long as the --slave-info option is used.

mysqlbackup now skips copying the binary log for an incremental backup when the backup it is based on does not include the binary log. Also, when restoring onto a server an incremental backup that does not contain the binary log, mysqlbackup now renames any binary log files that have already been restored onto the server by adding to them the .old extension; the same thing happens when an incremental backup is restored with the --skip-binlog option.

当备份正在进行时清除二进制或中继日志文件时，备份现在会失败；当发现服务器上缺少二进制日志文件时，它也会失败 mysqlbackup（但是，如果中继日志文件丢失，备份将继续）。

该--incremental-base选项现在接受一个新值 ， 这使得创建差异备份history:last_full_backup变得容易 。详见说明 。 --incremental-base