Search Results
https://dev.mysql.com/doc/refman/8.4/en/upgrade-paths.html
A replication topology is upgraded by following the rolling upgrade scheme described at Section 19.5.3, “Upgrading or Downgrading a Replication Topology”, which uses one of the supported single-server methods for each individual server upgrade.
https://dev.mysql.com/doc/refman/8.4/en/xa-restrictions.html
For “external XA,” a MySQL server acts as a Resource Manager and client programs act as Transaction Managers. For “Internal XA”, storage engines within a MySQL server act as RMs, and the server itself acts as a TM. XA transaction support is ...
https://dev.mysql.com/doc/mysql-enterprise-backup/8.4/en/advanced.source.html
To fix a corruption problem in a replication source database, you can restore the backup, taking care not to propagate unnecessary SQL operations to the replica servers: Shut down the source database and then use, for example, the ...Edit the ...
https://dev.mysql.com/doc/mysql-enterprise-backup/8.4/en/backup-incremental-options.html
full-scan: mysqlbackup scans all InnoDB data files in the server data directory to find pages that have been changed since the last backup, and copies them. The alternatives are: history:{last_backup | last_full_backup} The prefix history: followed ... For an overview of incremental backups and usage examples for these options, see Section 4.3.3, “Making a Differential or Incremental Backup” and Section 5.1.3, “Restoring an Incremental ...
https://dev.mysql.com/doc/mysql-enterprise-backup/8.4/en/bugs.compatibility.html
MySQL Enterprise Backup 8.4.8 supports the MySQL Server 8.4.x series for back up and restore for release 8.4.3 and later. It is incompatible with other versions of MySQL Server, for which you should use the MySQL Enterprise Backup of the same ...To ...
https://dev.mysql.com/doc/mysql-enterprise-backup/8.4/en/meb-files-backed-up-myisam.html
Note While MySQL Enterprise Backup can back up non-InnoDB data (like MYISAM tables), the MySQL server to be backed up must support InnoDB (i.e., the backup process will fail if the server was started up with the --innodb=OFF or --skip-innodb ...
https://dev.mysql.com/doc/mysql-enterprise-backup/8.4/en/meb-group-replication.html
When working with a Group Replication setup, mysqlbackup makes the backup information available to all members of the server group by making sure that the backup_history, backup_sbt_history (when using the SBT API), and backup_progress tables are ...
https://dev.mysql.com/doc/mysql-enterprise-backup/8.4/en/restore-use-tts.html
The following is some additional information on partial restores using TTS backups To backup and restore backups created using TTS, extra privileges are required of the user through which mysqlbackup connects to the server; see Section 4.1.2, ...
https://dev.mysql.com/doc/mysql-cluster-manager/8.4/en/mcm-architecture.html
MySQL Cluster Manager is a distributed client/server application consisting of two main components. In MySQL Cluster Manager, there is no single central server or process; all agents collaborate in managing a cluster as a whole. This is illustrated ... This section provides an architectural overview of MySQL Cluster Manager, its components, and their ...
https://dev.mysql.com/doc/mysql-cluster-manager/8.4/en/mcm-attribute-tables-other.html
TcpBind_INADDR_ANY: Bind InAddrAny instead of host name for server part of connection. AllowUnresolvedHostNames: When false (default), failure by management node to resolve host name results in fatal error; when true, unresolved host names are ...