Troubleshooting MySQL Corruption: When to Choose Stellar Repair for MySQL

How to Use Stellar Repair for MySQL to Fix InnoDB and MyISAM Errors

Corruption in MySQL tables—whether InnoDB or MyISAM—can cause downtime, data loss, and application failures. Stellar Repair for MySQL is a GUI tool designed to recover and repair damaged MySQL databases and table files (.ibd, .frm, .MYD, .MYI). This article gives a step-by-step, actionable guide to using Stellar Repair for MySQL to diagnose, repair, and verify recovered data.

Before you begin

• Backup: Immediately copy damaged files (datadir, .frm, .ibd, .MYD, .MYI) to a safe location.
• Stop MySQL service: Prevent further writes. On many systems:
  • Linux: sudo systemctl stop mysql or sudo service mysqld stop
  • Windows: stop the MySQL service via Services.msc
• Work on copies: Operate on file copies, never the original production files.
• Compatibility: Ensure Stellar Repair for MySQL supports your MySQL version and file types (InnoDB, MyISAM).

Step 1 — Install and launch Stellar Repair for MySQL

1. Download and install Stellar Repair for MySQL from the vendor (follow product instructions).
2. Launch the application. You’ll see options to open corrupted MySQL files or connect directly to a MySQL server.

Step 2 — Choose recovery mode (file-based vs. server-based)

• File-based recovery: Use when you have corrupted table files (.ibd, .frm, .MYD, .MYI) but no working server.
• Server-based recovery: Use when the MySQL server is running but tables are corrupt; connect using host, port, username, and password.

Stellar’s interface typically prompts you to pick a file or connect to the server. Choose based on what you have available.

Step 3 — Load corrupt files or connect to server

• For file-based:
  • Click “Select File” (or similar).
  • Navigate to the copied corrupted file(s) and open them.
• For server-based:
  • Enter host (often localhost), port (default 3306), MySQL username and password, and click “Connect”.
  • Select the damaged database and tables from the list.

Step 4 — Scan and analyze

• Start the scan/recovery process. Stellar will:
  • Parse the file structure.
  • Detect corruption level and errors (InnoDB page corruption, missing index, MyISAM header issues, etc.).
• Wait for the scan to complete. The UI shows status and detected objects (tables, rows, columns).

Step 5 — Preview recovered data

• Once scanning finishes, preview tables and rows in the tool.
• Verify critical columns and sample rows to confirm integrity and correctness.
• Note any fields marked as unrecoverable or partially recovered.

Step 6 — Recover and export

• Choose tables/databases to recover.
• Pick an export option:
  • SQL dump (recommended): Exports CREATE TABLE and INSERT statements so you can re-import into a clean MySQL instance.
  • CSV/Excel: Useful for manual inspection or partial restoration.
  • Direct restore (if supported): The tool may allow direct restore to a running MySQL server—use with caution and only to a non-production instance first.
• Start the export. Save the output SQL file or data files to a secure location.

Step 7 — Recreate schema and import recovered data

1. Start a clean MySQL instance (on same or different host).
2. Create the database(s) if needed.
3. Import the SQL dump:
   • mysql -u root -p your_database < recovered_dump.sql
4. If you exported CSV/Excel, create matching tables and use LOAD DATA INFILE or client tools to import.

Step 8 — Verify and compare

• Run integrity checks:
  • For InnoDB: run CHECK TABLE; verify foreign keys and constraints.
  • For MyISAM: run myisamchk or CHECK TABLE.
• Compare row counts, checksums, or sample queries against backups or application expectations.
• Test application functionality against the restored database.

Troubleshooting common issues

• “Cannot open file” errors: confirm file permissions and confirm you’re using copies, not files still held by MySQL.
• Partial recovery/missing rows: try re-scanning with different options; consult Stellar logs and support.
• Large files/timeouts: increase tool timeout settings or perform recovery on a machine with more memory/disk I/O.
• InnoDB tables with missing .ibd or .frm: recovery may require reconstructing schema manually; use exported CREATE TABLE as reference.

Best practices after recovery

• Replace corrupted production instance only after thorough validation.
• Implement regular automated backups (logical dumps + binary backups).
• Use replication for redundancy and point-in-time recovery with binlogs.
• Monitor disk health and MySQL error logs to detect early signs of corruption.
• Test recovery procedures periodically.

When to contact support or consider professional services

• If critical data remains unrecovered after multiple attempts.
• If the corruption stems from underlying storage failure or RAID issues.
• If you need legal/forensic-level preservation of original file integrity.

Quick checklist

• Backup corrupted files (copy).
• Stop MySQL and work on copies.
• Use file-based or server-based recovery in Stellar.
• Scan, preview, and export recovered data (prefer SQL dump).
• Import into clean server, verify integrity and application behavior.
• Restore production only after full validation.

Using Stellar Repair for MySQL can recover many types of InnoDB and MyISAM corruption, but success depends on damage severity and proper handling of original files. Follow the steps above to maximize recovery chances while minimizing risk to production data.