Prowess Data Unloader Complete Manual

PDU recovers MySQL data. This documentation is organized by failure type and includes command and parameter references.

Scope

Source versions: 5.7.44 · 8.0.28 · 8.0.46

Linux

PDU for MySQL

Offline file analysis

This documentation applies to Linux and source versions MySQL 5.7.44, 8.0.28 and 8.0.46. Before recovery, copy the data directory, Binlog, Redo/Undo and schema evidence, and work on a separate copy. Confirm other versions and special layouts separately.

Common entry points

Recovery scenariosChoose a guide by instance, file, or accidental operation.Usage GuideReview configuration, execution order, and outputs.ReferenceFind commands, parameters, supported types, and frequently asked questions.

Recovery scenarios

Confirm the current database state, then select the matching procedure.

File Recovery

InnoDB and MyISAM Data Files

Choose extraction methods by storage engine and retained metadata.

Recover from Corrupted InstanceExport data directly from a data-directory copy when the instance cannot start.Materialdata directoryFRM / SDIOutputData SQL and DDLRecover from Corrupted Data FileChoose file extraction or surviving-page recovery using IBD and schema evidence.MaterialIBDDDLOutputData SQLRecover Single Database DirectoryRecover a selected database while preserving required instance-level metadata.Materialdata directorymetadataOutputDatabase data SQLRecover MyISAM Data FilesExtract parseable complete active records from MYD, MYI and matching definitions.MaterialMYD / MYIDDLOutputComplete active records

Log and Transaction Recovery

Binlog, Undo and Redo

Complete logs, physical history and consistent base copies use their own paths.

Recover Deleted RecordsRecover data from before DELETE using Binlog.MaterialBinlogDDLOutputRecovery SQLRecover Updated RecordsRecover data from before UPDATE using Binlog.MaterialBinlogDDLOutputReverse recovery SQLRecover Data from Undo and RedoChoose a recovery path from surviving page views, Undo history and complete Redo.Materialbase copyUndo / RedoOutputPage views and recovery SQLRecover a Historical Binlog SnapshotReconstruct one table at a specified historical point using a CREATE/TRUNCATE starting point observed in the logs.MaterialROW Binlogendpoint DDLOutputHistorical table row set

Fragment Recovery

Scattered Pages and Schema Evidence

Extract surviving records using frozen sources, clustered identity and explicit definitions.

Recover Scattered InnoDB PagesUse DropScan to scan surviving pages and record possible table definitions, object generations and dependencies for large values.MaterialimagebindingOutputSparse records and dependenciesRecover Dropped Tables Without BackupScan InnoDB pages in a stable image and extract surviving records after schema binding.MaterialimageDDLOutputSurviving data SQL

Diagnosis and Object Recovery

Diagnosis, IMPORT and Object Metadata

Assess source scope read-only, prepare isolated tasks and retain object definitions and limits.

Diagnosis and Native IMPORT AssistanceDiagnose read-only, capture deleted files that remain open and prepare reviewable IMPORT tasks.MaterialIBDprofilesOutputDiagnosis and operation tasksRecover Metadata for Other ObjectsHandle views, triggers, routines, events and sparse-dictionary object attributes separately.MaterialTRG / FRM / DDOutputObject attributes and definitions

Basic workflow

Preserve the original files, identify the problem, then carry out recovery on copies.

  1. 1

    Preserve recovery materials

    Copy the data directory, tablespaces, Binlog and logs, and record the MySQL version.

  2. 2

    Identify the failure type

    Separate instance damage, file damage, accidental DML, and dropped tables.

  3. 3

    Recover from a copy

    Choose the matching commands and record PDU's success and failure counts, original errors and checkpoints.

Reference

Find command syntax, parameter purpose, and version differences.

Command ReferenceSyntax and output descriptionsParameter ReferencePurpose and applicable conditionsSupported Data TypesSource formats and parsing conditionsFrequently Asked QuestionsAnswers to common recovery questions

Supported Data Types

NumericTINYINT, SMALLINT, MEDIUMINT, INT, BIGINT, DECIMAL, FLOAT, DOUBLE, BIT
Text and binaryCHAR, VARCHAR, TEXT, BINARY, VARBINARY, BLOB
Date and timeDATE, TIME, DATETIME, TIMESTAMP, YEAR
Documents and identifiersJSON
Advanced typesENUM, SET, GEOMETRY
Storage dependenciesFRM / SDI, INSTANT, LOB, compression, keyring
MySQL 文档