DocsUsage Guide

Usage Guide

Learn how to configure PDU, scan sources and export recoverable data

System Requirements

Supported Platforms

  • Linux
  • Offline Physical Recovery
  • Use a separate offline working copy

MongoDB Versions

  • 6.0.0 / 7.0.0 / 8.0.0
  • Match the program to the exact source version
  • Confirm other versions separately

This documentation applies to Linux and source versions MongoDB 6.0.0, 7.0.0 and 8.0.0. Freeze source copies and launch PDU from a directory outside the sources. State and output use the launch directory without separate path settings. Confirm other versions and special layouts separately.

Quick Start

1

Prepare PDU

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

2

Configure pdu.ini

Set MONGODBDATA. State and output use the directory where PDU is launched.

MONGODBDATA=/recovery-input/mongodb/source/dbpath
3

Launch PDU

Enter the PDU directory and start the program.

./pdu
4

Initialize Database Metadata

Run the bootstrap command to load database structure.

param sourceversion 8.0.0; param sourcekind copy; param sourcefrozen true; b; \l; use appdb; \dt;

Exported Data Structure

Collection data is exported as BSON files or Canonical Extended JSON line files. Recovery commands generate offline candidate data without writing to the target database. Native records retain sources, success, failure, unresolved dependencies, original errors and checkpoints.

./
  <published BSON or Extended JSON files>
  <catalog, batch records and checkpoints>
  incident.sqlite3
  source-<id>/<mode>-<format>/

# Use the actual filenames reported by PDU.
MongoDB 文档