Search Results
https://dev.mysql.com/doc/mysql-enterprise-backup/8.4/en/backup-progress-report-options.html
This requires a connection to the MySQL server, and therefore, only works when backing up a running MySQL instance. Warning The system variable backup_progress is not yet defined for the MySQL Server. The estimated total is updated as per the data ... There are two options for controlling the progress reporting function of mysqlbackup: --show-progress and --progress-interval: --show-progress[={stderr|stdout|file:FILENAME|fifo:FIFONAME|table|variable}] Command-Line Format --show-progress[=destinations] Type Enumeration Valid Values stderrstdoutfile:FILENAMEfifo:FIFONAMEtablevariable The option instructs mysqlbackup to periodically output short progress reports known as progress indicators on its ...
https://dev.mysql.com/doc/mysql-enterprise-backup/8.4/en/backup-progress-table-update.html
Rename the original mysql.backup_progress table to mysql.backup_progress_old, and the mysql.backup_progress_new table to mysql.backup_progress. Note If you are working with a multiprimary Group Replication setting, make sure these privileges are ...
https://dev.mysql.com/doc/mysql-enterprise-backup/8.4/en/backup-repository-options.html
The backup repository options are divided into two groups: the first one determines the structure of the backup, and the second one provides information on the original structure of the data on the backed-up server for future operations on the ...
https://dev.mysql.com/doc/mysql-enterprise-backup/8.4/en/backup-sbt-history-table-update.html
Rename the original mysql.backup_sbt_history table to mysql.backup_sbt_history_old, and the mysql.backup_sbt_history_new table to mysql.backup_sbt_history. Note If you are working with a multiprimary Group Replication setting, make sure these ...
https://dev.mysql.com/doc/mysql-enterprise-backup/8.4/en/manifest-usage.html
mysqlbackup produces these files for use by database server management tools; it does not consult or modify the manifest files after creating them. Management tools can use the manifest during diagnosis and troubleshooting procedures, for example ...
https://dev.mysql.com/doc/mysql-enterprise-backup/8.4/en/partial.html
In particular, InnoDB tables have internal IDs and other data values that can only be restored to the same instance, not a different MySQL server. In particular, InnoDB tables have internal IDs and other data values that can only be restored to the ... By default, all the files under the database subdirectories in the data directory are included in the backup, so that the backup includes data from all MySQL storage engines, any third-party storage engines, and even any non-database files in that ...
https://dev.mysql.com/doc/mysql-enterprise-backup/8.4/en/platforms.compatibility.html
All applications that connect to the backed-up and the restored servers are always consistent on their use of letter cases when referring to the database and table names. MySQL Enterprise Backup is by nature cross-platform compatible when running ...
https://dev.mysql.com/doc/mysql-enterprise-backup/8.4/en/restore-performance.html
This section describes the performance considerations for restoring a database server with MySQL Enterprise Backup. The restore operation (except for Table-Level Restore) is always performed with the database server shut down. on the database ...
https://dev.mysql.com/doc/mysql-enterprise-backup/8.4/en/what-is-new.html
MySQL Enterprise Backup 8.4 marks the start of a new series of LTS (Long Term Support) releases. MySQL Enterprise Backup 8.4 is recommended for use on production systems. The MySQL Enterprise Backup.x LTS releases will focus on security and bug ...
https://dev.mysql.com/doc/mysql-cluster-manager/8.4/en/mcm-collect-logs.html
When an mcmd agent receives the collect logs command from the mcm agent it is connected with, it sets up a TCP server socket using port 0 by default, and lets the operating system assign the actual port number. All agents in the site are then ...