Description

My production MySQL instance has several InnoDB tables that suddenly became inaccessible. Error logs point to corruption, and the application is already down, so I need a solid physical recovery from the raw data files rather than a logical dump. Here is what you will find on my side: • Full datadir and log files, including ibdata1 and all *.ibd files • A recent backup created with mysqldump that I can fall back on if required, but I’d like to keep this as plan B because a straight restore means several hours of downtime and possible data drift Your task is to examine the files, decide the safest InnoDB recovery mode, bring the tables back online, and hand the server back in a consistent state. My expectation is that you work directly with the files—whether that involves Percona Toolkit, innodb_force_recovery levels, or spinning up a temporary instance—so we keep binary-level fidelity. Deliverables • Repaired / restored InnoDB tables, verified with CHECK TABLE or equivalent integrity tests • SQL dump of the fixed database for my archive • Short report describing what was damaged, what tools or commands you used, and any future‐proofing recommendations I can provide SSH access to a staging clone immediately. Let me know your estimated turnaround and the specific toolset you plan to use so I can coordinate downtime windows.