Search Results
https://dev.mysql.com/doc/mysql-enterprise-backup/8.4/en/backup-single-file-options.html
In case the argument for --src-entry matches multiple files or folders, they are all extracted into a folder whose pathname, relative to the destination folder, is given by the argument of --dst-entry (unless the argument specifies an absolute path). You use them in combination with the mysqlbackup commands backup-to-image, image-to-backup-dir, backup-dir-to-image, copy-back-and-apply-log, list-image, and extract (not all of the options are applicable to all these commands ...
https://dev.mysql.com/doc/mysql-enterprise-backup/8.4/en/backup-special-options.html
All non-InnoDB tables are locked before suspending, putting them into a read-only state, unless you turn off locking with the --no-locking. These options are for backing up database servers that play specific roles in replication, or contain ...
https://dev.mysql.com/doc/mysql-enterprise-backup/8.4/en/config-file-parameters.html
You can put common connection parameters used for restore operations (for example, user login, host name, etc.) into the configuration file. You can specify mysqlbackup options either on the command line or as configuration parameters inside a ...
https://dev.mysql.com/doc/mysql-enterprise-backup/8.4/en/meb-backup-process.html
In general, this is what happens when you run a backup operation with mysqlbackup: The InnoDB data files, redo log, binary log, and relay log files (except for the log files currently in use) are being copied into the backup, while the database ...
https://dev.mysql.com/doc/mysql-enterprise-backup/8.4/en/meb-faq.html
Those tables are split off from the system tablespaces into separate .ibd files; the tables can then be individually included or excluded from backups, and disk space is freed when the tables are dropped or truncated. This section lists some common ...
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/meb-troubleshooting.html
As mysqlbackup proceeds, it writes progress information into the mysql.backup_progress table. To troubleshoot issues regarding backup and restore with the MySQL Enterprise Backup product, consider the following aspects: Before troubleshooting any ...
https://dev.mysql.com/doc/mysql-enterprise-backup/8.4/en/mysqlbackup.dfs-san.html
Condition 2 though can remain unfulfilled even when condition 1 has been satisfied: for example, mysqlbackup could copy all the pages of a tablespace correctly except for one page for which mysqlbackup has included an old version into the copy.
https://dev.mysql.com/doc/mysql-enterprise-backup/8.4/en/mysqlbackup.incremental.html
No binary log files are copied into the incremental backup if the --start-lsn option is used. In order to that, after making first a full backup that contains all data, you can do one of the following: Performing a series of differential backups.
https://dev.mysql.com/doc/mysql-enterprise-backup/8.4/en/mysqlbackup.restore.html
Use, for example, the copy-back-and-apply-log command, which converts the raw backup into a prepared backup by updating it to a consistent state, and then copies the tables, indexes, metadata, and any other required files onto a target server. To ...