Exchange lost-flush recovery
Exchange ESE tracks page state to detect stale or misdirected writes. In a Database Availability Group, page patching may replace a bad page from a healthy replica, but a single-copy database or damaged replicas require careful comparison before hard repair.
Understand the symptom
A page can contain structurally valid data yet be older than the state Exchange expects. Recovery correlates page history, log generations, database-copy health and storage events, then prefers a verified replica or restore path before any lossy page removal.
What you may see
ESE detects a page generation that does not match the expected write history.
No healthy replica supplies the required current page.
Log replay or database scanning finds inconsistent page state.
Controller resets, cache faults or path errors coincide with database damage.
Protect the source
A healthier passive database may be replaced before comparison.
Eseutil /p restores structure by removing unrecoverable records or pages.
Database repair cannot correct an unreliable controller, cache, fabric or disk path.
Do this now
Pause automatic reseed, repair and maintenance where operationally safe.
Save copy status, event IDs, page references, logs, checkpoints and replication health.
Keep EDB files, all logs, backups and configuration before choosing a source.
Snapshot or image affected volumes and retain controller, SAN and Windows events.
NEPFOSYS process
NEPFOSYS maps page state, log continuity and health across available databases and backups.
Page-level, restore and extraction paths are tested without changing the best copy.
Priority mailboxes, folders, messages and attachments are checked in the recovered output.
A clear next step
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 reviewQuestions, answered
It is a write reported as completed by storage that was not durably written, or was written to the wrong location.
A healthy replica may supply a replacement page, but copy and log health must first be verified.
No. Lost flushes often require investigation of the entire storage path and its write guarantees.
DFW local · Nationwide mail-in