PDF (US Ltr)
- 43.3Mb
PDF (A4)
- 43.4Mb
Man Pages (TGZ)
- 297.2Kb
Man Pages (Zip)
- 402.4Kb
Info (Gzip)
- 4.3Mb
Info (Zip)
- 4.3Mb
Search Results
https://dev.mysql.com/doc/refman/8.0/en/mysqldump-stored-programs.html
The other options are disabled by default and must be specified explicitly to dump the corresponding objects. To disable any of these options explicitly, use its skip form: --skip-events, --skip-routines, or --skip-triggers.
https://dev.mysql.com/doc/refman/8.0/en/backup-policy.html
For example, MySQL Enterprise Backup can perform a physical backup of an entire instance, with optimizations to minimize overhead and avoid disruption when backing up InnoDB data files; mysqldump provides online logical backup. It was assumed ...A ...
https://dev.mysql.com/doc/refman/8.0/en/replication-multi-source-provision-replica.html
The best strategy for provisioning such a replica is therefore to use mysqldump to create an appropriate dump file on each source, then use the mysql client to import the dump file on the replica. If you are using GTID-based replication, you need to ... If the sources in the multi-source replication topology have existing data, it can save time to provision the replica with the relevant data before starting ...
https://dev.mysql.com/doc/refman/8.0/en/copying-databases.html
In cases where you need to transfer databases between different architectures, you can use mysqldump to create a file containing SQL statements. Note If GTIDs are in use on the server where you create the dump (gtid_mode=ON), by default, mysqldump ...You can then transfer the file to the other machine and feed it as input to the mysql ...
https://dev.mysql.com/doc/refman/8.0/en/docker-mysql-more-topics.html
Using mysqldump with Docker Besides using MySQL Enterprise Backup to back up a MySQL Server running in a Docker container, you can perform a logical backup of your server by using the mysqldump utility, run inside a Docker container. We also assume ...A MySQL Docker installation is different from a common, non-Docker installation in the following aspects: Only a limited number of binaries are ...
https://dev.mysql.com/doc/refman/8.0/en/replication-snapshot-method.html
To select the appropriate method of dumping the database, choose between these options: Use the mysqldump tool to create a dump of all the databases you want to replicate. This can be more efficient than using mysqldump and importing the file on ...
https://dev.mysql.com/doc/refman/8.0/en/backup-methods.html
Backing up the physical database files makes restore much faster than logical techniques such as the mysqldump command. (See Section 9.4, “Using mysqldump for Backups”.) For InnoDB tables, it is possible to perform an online backup that takes no ...Making a Hot Backup with MySQL Enterprise Backup Customers of MySQL Enterprise Edition can use the MySQL Enterprise Backup product to do physical backups of entire instances or selected databases, tables, or ...
https://dev.mysql.com/doc/refman/8.0/en/mysqlbinlog-backup.html
mysqlbinlog Backup Capabilities mysqlbinlog Backup Options Static and Live Backups Output File Naming Example: mysqldump + mysqlbinlog for Backup and Restore mysqlbinlog Backup Restrictions mysqlbinlog Backup Capabilities mysqlbinlog can read binary ... By default, mysqlbinlog reads binary log files and displays their contents in text ...
https://dev.mysql.com/doc/refman/8.0/en/upgrade-binary-package.html
Logical Upgrade A logical upgrade involves exporting SQL from the old MySQL instance using a backup or export utility such as mysqldump or mysqlpump, installing the new MySQL server, and applying the SQL to your new MySQL instance. Export your ...
https://dev.mysql.com/doc/refman/8.0/en/glossary.html
With MySQL, physical backups are performed by the MySQL Enterprise Backup product, and logical backups are performed by the mysqldump command. (Hot backups have the least interference, cold backups the most.) See Also cold backup, hot backup, ...