Timeline for Recover a MySQL InnoDB from ibdata1 that won't repair using innodb_force_recovery
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 29, 2021 at 13:44 | history | edited | mustaccio | CC BY-SA 4.0 |
fix dead link
|
| May 6, 2012 at 18:04 | history | migrated | from stackoverflow.com (revisions) | ||
| May 5, 2012 at 16:18 | vote | accept | CommunityBot | ||
| May 4, 2012 at 19:49 | comment | added | user1346416 | Thank you - I am trying these and also in touch with Percona directly. Any other suggestions, much appreciated! | |
| May 4, 2012 at 19:48 | comment | added | ESG |
From the documentation: It is important to understand that these tools are not designed for connecting to a live database and recovering data from it. They work on an offline copy of the data, and it is not safe to use them on a copy that is in use by MySQL.
|
|
| May 4, 2012 at 19:41 | history | answered | ESG | CC BY-SA 3.0 |