Search Results
https://dev.mysql.com/doc/relnotes/mysql/8.4/en/news-8-4-0.html
(Bug #36301441) Audit log filtering by type, using error as the type, did not work correctly. (Bug #36142157) Following an unplanned shutdown and restart, the file that was in use by the server for writing at the time may be broken or otherwise ...
https://dev.mysql.com/doc/mysql-enterprise-backup/8.4/en/backup-prep-storage.html
Most mysqlbackup operations, including those on single-file backups, write data or metadata to a designated directory referred to as the “backup directory” in this manual. See the description for --backup-dir for details on its usage for ...
https://dev.mysql.com/doc/mysql-enterprise-backup/8.4/en/meb-backup-osb.html
Tape drives are affordable, high-capacity storage devices for backup data. MySQL Enterprise Backup can interface with media management software (MMS) such as Oracle Secure Backup (OSB) to drive MySQL backup and restore jobs. The media management ...
https://dev.mysql.com/doc/mysql-enterprise-backup/8.4/en/meb-scheduled-backups.html
Maintaining a regular backup schedule is an important measure for preventing data loss for you MySQL server. This section discusses some simple means for setting up a schedule for running MySQL Enterprise Backup. For Linux and other Unix-like ...
https://dev.mysql.com/doc/mysql-enterprise-backup/8.4/en/mysqlbackup.backup.html
In the following illustration, we back up an entire MySQL instance to a single file using the backup-to-image command, which appears at the end of the sample command. We specify some of the connection information for the database using the --user ...
https://dev.mysql.com/doc/mysql-enterprise-backup/8.4/en/mysqlbackup.html
The mysqlbackup client is an easy-to-use tool for all backup and restore operations. During backup operations, mysqlbackup backs up: All InnoDB tables and indexes, including: The InnoDB system tablespace, which, by default contains all the InnoDB ...
https://dev.mysql.com/doc/mysql-enterprise-backup/8.4/en/mysqlbackup.usage.html
The following sections describe the command-line options for the different modes of operation of mysqlbackup. Use the hyperlinks at the option names to jump to the detailed descriptions for the options. Note The command options can also be ...
https://dev.mysql.com/doc/mysql-cluster-manager/8.4/en/mcm-backup-agents.html
backup agents [--hosts=host_list] [site_name] host_list: host[, host[, ...]] This command backs up the configuration data for the mcmd agents on the hosts specified in host_list with the --hosts option (short form: -h) for the site named site_name.
https://dev.mysql.com/doc/mysql-cluster-manager/8.4/en/mcm-collect-logs.html
collect logs [cluster_name] This command collects log files and other related files from all hosts. When the name of a cluster (cluster_name) is supplied with the command, it collects all the log files (.log) as well as the configuration files ...
https://dev.mysql.com/doc/mysql-cluster-manager/8.4/en/mcm-delete-backup.html
To delete all backups, run the command on every single backup. If any data nodes or mysqld nodes have been added after the specified backup was created, list their node IDs with the --skip-nodeid option, or the operation will fail with the complaint ...