File geodatabase recovery

A corrupt file geodatabase must be preserved as one folder before recovery extracts readable tables and features.

A .gdb directory contains many internal files whose names and relationships are managed by ArcGIS. Deleting, renaming, or copying pieces individually can render the geodatabase unusable.

Understand the symptom

Esri's Recover File Geodatabase tool creates a new output with important limitations.

WHY

What is happening

The official recovery tool reads a corrupt file geodatabase and writes recovered content to a separate output. Esri states that it can recover simple feature classes and tables, but not complex data and relationships. Validation must therefore include domains, relationships, attachments, topology, networks, and other advanced structures.

What you may see

Symptoms that change the recovery path.

01

GDB cannot be opened

Internal tables or system metadata may be unreadable.

02

Feature classes disappear

Catalog metadata or individual table files may be damaged.

03

Editing or export fails

A specific row, geometry, index, or storage read may be corrupt.

04

GDB copied through File Explorer stops working

The folder may have been incomplete or captured while files were changing.

Protect the source

Actions that can make the situation worse.

01

Renaming internal files breaks the database

Their relationships are not user-managed filenames.

02

Recovery output can omit complex structures

A tool run is not proof of completeness.

03

Repairing on failing storage adds damage

Image the source before broad database reads.

Do this now

Safe steps before evaluation.

01

Copy the entire GDB folder

Use a storage-level copy or image that preserves every internal file and timestamp.

02

Stop all GIS writers

Close ArcGIS, services, scripts, sync jobs, and shared access.

03

Collect schema and project evidence

Keep APRX, layer files, models, field lists, domains, relationship notes, and exports.

04

Record exact failures

Note which feature classes, tools, rows, or exports fail and any recent crash.

NEPFOSYS process

How a data-first evaluation proceeds.

01

Storage and GDB assessment

NEPFOSYS separates physical read errors from logical geodatabase corruption.

02

Copy-based extraction

Supported recovery and targeted reads write only to new output locations.

03

Data validation

Features, attributes, counts, spatial references, domains, relationships, attachments, and priority layers are checked.

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.

Can I copy a file geodatabase with File Explorer?

Esri warns that individual file operations can cause data loss. Preserve a closed, complete folder or storage image.

Will Recover File Geodatabase restore everything?

No. Esri documents recovery of simple feature classes and tables, not complex data and relationships.

Should I delete .lock files?

Not before preserving the original folder and confirming no process is using it. Lock symptoms can be secondary to a larger failure.

DFW local · Nationwide mail-in

Protect the device. Start with the facts.

Start my recovery case