When Do You Need PDU?
Explore MySQL recovery scenarios and choose a method based on surviving sources.
MySQL data recovery overviewFile Recovery
Choose extraction methods by storage engine and retained metadata.
Database Won’t Start?
Export data directly from a data-directory copy when the instance cannot start.
Damaged IBD Files Make a Table Unreadable?
Choose file extraction or surviving-page recovery using IBD and schema evidence.
Instance Damaged, but Only One Database Needs Recovery?
Recover a selected database while preserving required instance-level metadata.
MyISAM Table Damaged and Records Unreadable?
Extract parseable complete active records from MYD, MYI and matching definitions.
Log and Transaction Recovery
Complete logs, physical history and consistent base copies use their own paths.
Data Deleted by Mistake?
Recover data from before DELETE using Binlog.
Data Updated by Mistake?
Recover data from before UPDATE using Binlog.
Data Changed Incorrectly, with Only Undo or Redo Left?
Choose a recovery path from surviving page views, Undo history and complete Redo.
Need a Table’s Data at an Earlier Point?
Reconstruct one table at a specified historical point using a CREATE/TRUNCATE starting point observed in the logs.
Fragment Recovery
Extract surviving records using frozen sources, clustered identity and explicit definitions.
Diagnosis and Object Recovery
Assess source scope read-only, prepare isolated tasks and retain object definitions and limits.
Tablespace Files Survive, but MySQL Cannot Read Them?
Diagnose read-only, capture deleted files that remain open and prepare reviewable IMPORT tasks.
View, Trigger or Stored Routine Definitions Lost?
Handle views, triggers, routines, events and sparse-dictionary object attributes separately.
Dealing with Data Loss?
PDU provides professional-grade recovery capabilities to help you recover data safely and efficiently.