Exchange RDB recovery

An Exchange recovery database that will not mount needs its EDB, log path and recovery state aligned.

A recovery database lets Exchange mount a restored EDB separately so mailbox data can be extracted. Mount failure can come from dirty shutdown, missing or mismatched logs, incorrect paths, database identity, permissions, version mismatch or damaged pages.

Understand the symptom

Creating an RDB does not repair the restored database; it supplies an isolated mount context.

WHY

What is happening

Exchange expects the EDB and transaction logs to form a consistent history and the RDB to reference the correct paths. Soft recovery may replay compatible logs, while a hard repair can remove damaged database structures. The source backup and untouched restore copy are necessary for retrying a safer path.

What you may see

Symptoms that change the recovery path.

01

Mount-Database fails

Exchange rejects the recovery database after it is created.

02

EDB remains in dirty shutdown

Required log replay has not completed.

03

Log prefix or signature mismatch

The supplied logs do not belong to the database history.

04

Mailbox statistics are unavailable

The RDB never reaches a usable mounted state.

Protect the source

Actions that can make the situation worse.

01

Hard repair can discard mailbox data

Structural repair prioritizes database consistency, not preservation of every item.

02

Deleting logs can close recovery paths

A required generation may be the only route to clean shutdown.

03

Mounting in the wrong context changes state

Version, path and server configuration must be controlled.

Do this now

Safe steps before evaluation.

01

Preserve the original restore

Make a second working copy before Eseutil or mount attempts.

02

Collect header and log information

Record database state, log prefix, required generation, signatures and Exchange build.

03

Keep the whole backup set

Protect EDB, logs, checkpoint, catalog and backup metadata together.

04

Document the mailbox target

Identify priority mailboxes, dates and folders before extraction.

NEPFOSYS process

How a data-first evaluation proceeds.

01

Recovery-state analysis

NEPFOSYS correlates EDB headers, log generations, signatures and RDB configuration.

02

Protected replay testing

Compatible soft recovery and alternate restore sources are tested on copies.

03

Mailbox verification

Mounted content and priority mailboxes are checked before export or restore requests.

A clear next step

Preserve the original device before another repair or recovery attempt.

Start a case with the exact symptoms, incident timeline, prior attempts, encryption details, and the files that matter most. NEPFOSYS will route the case to the appropriate DFW intake or nationwide mail-in path.

Start with a case review

Questions, answered

What customers ask before starting.

What is an Exchange recovery database?

It is a special mailbox database used to mount a restored EDB and extract data without replacing the active production database.

Does creating an RDB clean the EDB?

No. The restored database must still have a valid state and compatible log history.

Should I use Eseutil /p if the RDB will not mount?

Not before preserving copies and checking logs, paths, version and header state. Hard repair can discard data.

DFW local · Nationwide mail-in

Protect the device. Start with the facts.

Start my recovery case