Pay attention to the cold backup of mysql database

For mysql database cold backup, note that cold backup refers to a complete database provided when the database is shut down normally. Cold backup is a way to copy key files to another location. Advantages: www.2cto.com 1. is a very fast backup method (just copy files) 2. easy to archive (simple copy) 3. it is easy to restore to a certain point in time (you only need to copy the file back) 4. it can be combined with archiving methods to restore the database to the "latest State. 5. Low maintenance and high security. However, cold backup also has the following shortcomings: www.2cto.com 1. When used separately, only the restoration at "a certain time point" can be provided. 2. During the entire backup process, the database must be backed up instead of other work. That is to say, in the cold backup process, the database must be closed. 3. If the disk space is limited, it can only be copied to tape and other external storage devices, and the speed will be very slow. 4. data cannot be restored by table or by user. I started the service for mysql from the server today and found the problem. Because the data volume on the master server is large, I used cold backup to directly cp to the slave server. When I restarted the server mysql, I reported the following error: 130307 9:21:44 InnoDB: error: page 2328 log sequence number 73 1311259268 InnoDB: is in the future! Current system log sequence number 73 815920160. InnoDB: Your database may be uploaded upt or you may have copied the InnoDBInnoDB: tablespace but not the InnoDB log files. SeeInnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.htmlInnoDB : For more information. find the information and find out that during cold backup, you must note that the data table needs to be backed up using the InnoDB Storage engine ib_logfile0 ib_logfile1. This file is used to store the transaction log information of the InnoDB engine and directly copy the above files to start the service from the server. normal