Search Results
https://dev.mysql.com/doc/mysql-enterprise-backup/8.4/en/advanced.replica-backup-restore.html
To backup a replica database, add the --replica-info option to your backup command. To restore the backup on a replica server, follow the same steps outlined in Section 8.1, “Setting Up a New replica”. MySQL Enterprise Backup does not include ...
https://dev.mysql.com/doc/mysql-enterprise-backup/8.4/en/backup-apply-log.html
Example 5.10 Restoring a Backup Directory using copy-back-and-apply-log mysqlbackup --defaults-file=/usr/local/mysql/my.cnf \ --backup-dir=/export/backups/full \ copy-back-and-apply-log However, two alternatives exist for directory backups: Perform ... A directory backup, just like a single-file backup, can be prepared and restored using the copy-back-and-apply-log command as explained at the beginning of Section 5.1, “Performing a Restore ...
https://dev.mysql.com/doc/mysql-enterprise-backup/8.4/en/backup-commands-restore.html
Some clean-up efforts on the target directory for restoration might be needed before performing a full restore (for example, when the backup data is used to set up a new MySQL server or to replace all data of an existing MySQL server). The restore ...
https://dev.mysql.com/doc/mysql-enterprise-backup/8.4/en/backup-history-table-update.html
Rename the original mysql.backup_history table to mysql.backup_history_old, and the mysql.backup_history_new table to mysql.backup_history. Note If you are working with a multiprimary Group Replication setting, make sure these privileges are granted ...
https://dev.mysql.com/doc/mysql-enterprise-backup/8.4/en/backup-incremental-options.html
To include binary log files for the period covered by the incremental backup, instead of --start-lsn, use the --incremental-base option, which provides the necessary information for mysqlbackup to ensure that no gap exists between binary log data ...
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/meb-backup-process.html
This step is skipped if no user-created non-InnoDB tables exist on the database. The following is a very brief outline of the steps performed by mysqlbackup when it creates a backup. In general, this is what happens when you run a backup operation ...
https://dev.mysql.com/doc/mysql-enterprise-backup/8.4/en/meb-performance-space-overview.html
Therefore, to back up as much data as possible during the hot backup phase, you should designate InnoDB as the default storage engine for new tables (which is the default setting for MySQL servers), or convert existing tables to use the InnoDB ...
https://dev.mysql.com/doc/mysql-enterprise-backup/8.4/en/mysqlbackup.dfs-san.html
When system administrators attempt to set up MySQL and MySQL Enterprise Backup in an environment that uses a distributed file system (DFS) or a storage access network (SAN), the MySQL server, the server's data directory, MySQL Enterprise Backup, ...
https://dev.mysql.com/doc/mysql-enterprise-backup/8.4/en/mysqlbackup.incremental.html
To include binary log files for the period covered by the incremental backup, use the --incremental-base option instead, which provides the necessary information for mysqlbackup to ensure that no gap exists between binary log data included in the ...