Command Reference

Complete reference for all PDU commands including data export, recovery operations, and disk scanning.

Parameter Reference

Configuration file settings and runtime parameters for Binlog scanning, recovery modes, and disk scanning.

System Requirements

Supported Platforms

Linux
Offline Physical Recovery
Use a separate offline working copy

MySQL Versions

5.7.44 · 8.0.28 · 8.0.46
Match the program to the exact source version
Confirm other versions separately

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.

Quick Start

Prepare PDU

Place the matching PDU program in a directory outside the sources.

Configure pdu.ini

Set the source paths. Tasks and output are saved in PDU's launch directory outside the sources.

MYSQL_DATADIR=/recovery-input/mysql/data
BINLOG=/recovery-input/mysql/binlog
RESMODE=tx
RESTYPE=delete

Launch PDU

Enter the PDU directory and start the program.

./pdu

Initialize Database Metadata

Run the bootstrap command to load database structure.

param datadir /recovery-input/mysql/data;
b;
\l;
use appdb;
\dt;

Exported Data Structure

PDU uses its current directory at startup for tasks and output. Exported SQL files are written directly there, and internal task records are stored in .pdu-work. Export table definitions separately with `unload ddl`. Recovery commands generate SQL without writing to the target database. The records in .pdu-work retain the program's success and failure counts, original errors and checkpoints.

./
  orders.sql
  orders_2.sql
  exported DDL
  .pdu-work/
    source and candidate records
    frozen bindings
    native records and checkpoints

Usage Guide