MySQL Enterprise Backup now replicates backup information across all members of a ReplicaSet setup, regardless of whether the backup is performed on the primary or a secondary node. It ensures that the backup_history, backup_sbt_history (if using the SBT API), and backup_progress tables are always updated on the primary node, so that the backup information is replicated to all nodes in the ReplicaSet setup. The feature ensures consistency of backup history and metadata across the ReplicateSet, allows easier management of backups, and enables incremental backups on any one of the secondary nodes, which now has the last backup recorded in its backup_history tables. (WL #16871)

When a TTS image backup taken with full-locking was restored by streaming the image to mysqlbackup, the restore failed due to a tail magic mismatch. (Bug #37196546)

After a backup was finished, the values of the server's status variables Com_stmt_prepare and Com_stmt_close did not match. It was because mysqlbackup, after using prepared statements to query the server, closed its connection to the server prematurely. With this fix, Com_stmt_close is also incremented before mysqlbackup disconnects from the server. (Bug #34624351)