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/replication-solutions-backups-read-only.html
Note The instructions in this section place the server to be backed up in a state that is safe for backup methods that get the data from the server, such as mysqldump (see Section 6.5.4, “mysqldump — A Database Backup Program”). You should not ...
https://dev.mysql.com/doc/refman/8.0/en/data-dictionary-usage-differences.html
For example: SELECT TABLE_SCHEMA AS table_schema, TABLE_NAME AS table_name FROM INFORMATION_SCHEMA.TABLES WHERE TABLE_NAME = 'users'; mysqldump and mysqlpump no longer dump the INFORMATION_SCHEMA database, even if explicitly named on the command ...
https://dev.mysql.com/doc/refman/8.0/en/log-file-maintenance.html
Log flushing occurs when you execute a FLUSH LOGS statement or a mysqladmin flush-logs, mysqladmin refresh, mysqldump --flush-logs, or mysqldump --master-data command. See Section 15.7.8.3, “FLUSH Statement”, Section 6.5.2, “mysqladmin — A ... As described in Section 7.4, “MySQL Server Logs”, MySQL Server can create several different log files to help you see what activity is taking ...
https://dev.mysql.com/doc/refman/8.0/en/mysql-cluster-backup.html
To distinguish this type of backup from a backup made using mysqldump, we sometimes refer to it as a “native” NDB Cluster backup. The next few sections describe how to prepare for and then to create an NDB Cluster backup using the functionality ...
https://dev.mysql.com/doc/refman/8.0/en/mysql-cluster-install-example-data.html
To create a copy of the entire world database on the SQL node, use mysqldump on the noncluster server to export the database to a file named world.sql (for example, in the /tmp directory). Note The information in this section applies to NDB Cluster ...
https://dev.mysql.com/doc/refman/8.0/en/mysql-cluster-replication-pitr.html
Performing point-in-time recovery of NDB Cluster tables with NDB Cluster and NDB Cluster Replication can be accomplished using a native NDB data backup (taken by issuing CREATE BACKUP in the ndb_mgm client) and restoring the ndb_binlog_index table ... Point-in-time recovery—that is, recovery of data changes made since a given point in time—is performed after restoring a full backup that returns the server to its state when the backup was ...
https://dev.mysql.com/doc/refman/8.0/en/mysql-cluster-upgrade-downgrade.html
Restore a file system that is compatible from a backup taken prior to the upgrade (see Section 9.4, “Using mysqldump for Backups”). Versions Supported for Upgrade to NDB 8.0 Reverting an NDB Cluster 8.0 Upgrade Known Issues When Upgrading or ...
https://dev.mysql.com/doc/refman/8.0/en/ndb-restore-different-number-nodes.html
Note When changing the total number of LCP threads or LQH threads per node group, you should recreate the schema from backup created using mysqldump. $> mysqldump --no-data --routines --events --triggers --databases > myschema.sql Important Once you ... It is possible to restore from an NDB backup to a cluster having a different number of data nodes than the original from which the backup was ...
https://dev.mysql.com/doc/refman/8.0/en/ndb-restore-to-different-version.html
Since it is possible to restore metadata and table data separately, you can in such cases restore the table schemas from a dump made using mysqldump, or by executing the necessary CREATE TABLE statements manually, then import only the table data ...
https://dev.mysql.com/doc/refman/8.0/en/replication-solutions-backups.html
There are therefore two choices: If you are using replication as a solution to enable you to back up the data on the source, and the size of your database is not too large, the mysqldump tool may be suitable. For larger databases, where mysqldump ...