Search Results
https://dev.mysql.com/doc/mysql-enterprise-backup/9.7/en/backup-compression-options.html
You cannot use the --compress option together with the --incremental-with-redo-log-only option. Explicitly specifying a value other than punch-hole for the option through a configuration file or command line automatically enables the --compress ...
https://dev.mysql.com/doc/mysql-enterprise-backup/9.7/en/backup-repository-options.html
For restoring a single-file backup (including incremental, compressed, encrypted, and cloud backups): When using copy-back-and-apply-log to restore a single-file backup, use --backup-dir to supply a temporary folder to store the temporary data of ...
https://dev.mysql.com/doc/mysql-enterprise-backup/9.7/en/backup.compressed.html
You cannot use the --compress option for incremental backups created only with the redo log (i.e., with the --incremental-with-redo-log-only option). To save disk space, you can compress InnoDB backup data files by using the --compress option of ...
https://dev.mysql.com/doc/mysql-enterprise-backup/9.7/en/meb-performance-space-overview.html
An Incremental backup includes all changes to the data since the last backup. When it comes to formulating your backup strategy, performance and storage space are the key considerations. You want the backup to complete quickly, with as little CPU ...
https://dev.mysql.com/doc/mysql-enterprise-backup/9.7/en/restore.html
The table allows you to perform future incremental backups using the --incremental-base=history:{last_backup | last_full_backup} option. The mysqlbackup commands to perform a restore operation are copy-back-and-apply-log and copy-back (for ...
https://dev.mysql.com/doc/mysql-enterprise-backup/9.7/en/server-repository-options.html
For backups:You do not need to specify this option, because its value is retrieved automatically using the database server connection. For backups: You do not need to specify this option, because its value is retrieved automatically using the ...
https://dev.mysql.com/doc/mysql-shell/9.7/en/add-instance-replicaset.html
The safest and most convenient way to provision a new instance is through automatic clone provisioning, which will completely overwrite the state of 'rsadmin@rs-2' with a physical snapshot from an existing replicaset member. To use this method by ...
https://dev.mysql.com/doc/mysql-shell/9.7/en/innodb-cluster-binary-log-purging.html
Instances running 8.0.17 and later support the MySQL Clone plugin, which resolves this issue by providing an automatic provisioning solution which does not rely on incremental recovery, see Section 8.4.6, “Using MySQL Clone with InnoDB Cluster”.
https://dev.mysql.com/doc/mysql-shell/9.7/en/recovery-methods-replicaset.html
You can do this provisioning automatically using one of the following methods: MySQL Clone: Takes a snapshot from an online instance and then replaces any data on the new instance with the snapshot. Incremental Recovery: Relies on MySQL Replication ... When you add new instances to an InnoDB ReplicaSet you need to provision the instances with the existing data that the ReplicaSet ...
https://dev.mysql.com/doc/relnotes/mysql-cluster/9.7/en/news-9-6-0.html
(Bug #38592288) Bugs Fixed The NDB purge process responsible for removing rows from mysql.ndb_binlog_index when a binary log file is purged, assumed that autocommit is enabled, and each DML operation commits immediately. However, if autocommit is ...