compared with
Current by Ethan Lively
on Aug 19, 2020 15:18.

(show comment)
This line was removed.
This word was removed. This word was added.
This line was added.

Changes (1)

View Page History
With this change, a higher rate of failure in restores has been seen in the MySQL 5.7 and higher versions. This has been accounted to the {color:#172b4d}data consistency standards that InnoDB adheres to.{color} {color:#172b4d}The reason relates to how InnoDB works.{color} {color:#172b4d}A short version is, w{color}{color:#172b4d}hen an attempt to restore a database is made, internally an attempt to restore to a temporary MySQL instance is made. However, the{color} {color:#172b4d}temporary MySQL instance{color} {color:#172b4d}fails to start, when only partial databases are restored. This is due to the nature of InnoDB, where it looks for the other databases referenced in the logs, that were not restored. On failing to find the same, it fails to start the temporary instance.{color}

{color:#212529}MySQL has provided the innodb_force_recovery option, which{color} {color:#212529}instructs InnoDB to start up in a recovery mode, telling it to skip various portions of the InnoDB start-up process. However, this option can also be destructive, hence it is recommended to use this option carefully.{color} {color:#172b4d}Also, Wwe recommend that if needed, start with a low value and{color} {color:#212529}increase it only as needed.{color}