Official document address: Chapter 7 Backup and Recovery
7.1 Backup and Recovery Types
7.2 Database Backup Methods
7.3 Example Backup and Recovery Strategy
7.4 Using mysqldump for Backups
7.5 Point-in-Time (Incremental) Recovery
7.6 MyISAM Table Maintenance and Crash Recovery
It is very important to back up the database so that in the event of a problem (such as a system crash, hardware failure, or accidental deletion of data by a user), the data can be restored and restarted and running. Before upgrading the MySQL installation, backups are also an essential protection measure. You can use them to transfer the MySQL installation to another system or set up a replica server.
MySQL provides a variety of backup strategies, from which you can choose the installation method that best suits your needs. This chapter discusses several backup and recovery topics that you should be familiar with:
- Backup type: logical backup or physical backup, full backup or incremental backup, etc.
- How to create a backup.
- Recovery method, including point-in-time recovery.
- Backup scheduling, compression and encryption.
- Table maintenance, enabling the restoration of damaged tables.
Other resources
Resources related to the availability of backup or maintenance data include:
- MySQL Enterprise Edition users can use MySQL Enterprise Edition backup products for backup. For an overview of MySQL enterprise backup products, see 30.2 MySQL Enterprise Backup Overview .
- A forum dedicated to discussing backup issues .
mysqldumpDetailed information can be Chapter 4 MySQL program found in.- The syntax of SQL statements described here in Chapter 13 SQL statement given in.
- For
InnoDBmore information about the backup process, see 15.18.1 InnoDB Backup . - Replication enables you to maintain the same data on multiple servers. This has several benefits, such as allowing clients to query the load distributed on the server, even if a given server is offline or fails, the data is still available, and the use of a copy for backup without affecting the performance of the source. See Chapter 17 copy .
- MySQL
InnoDBcluster is a collection of a series of products that together provide a high-availability solution. A group of MySQL servers can be configured as a cluster by using MySQL Shell. The server cluster has only one source, called the primary source, which acts as a read-write source. Multiple secondary servers are copies of the source server. At least three servers are required to create a high-availability cluster. The client application connects to the main server through the MySQL router. If the master server fails, a slave server will automatically be promoted to the master server, and the MySQL router will route the request to the new master server. - NDB Cluster provides a highly available and redundant version of MySQL for distributed computing environments. See Chapter the NDB Cluster 8.0 MySQL 23 .