Firebird database recovery

A Firebird database can contain recoverable tables even when page, checksum, index, or transaction structures are damaged.

Firebird stores database pages, records, indexes, transaction inventory, and metadata in the FDB. Abrupt shutdown, bad storage, unsafe copying, or hardware faults can produce validation or backup errors.

Understand the symptom

Validation, mend, backup, and logical export have different loss risks.

WHY

What is happening

Firebird documents read-only validation with no_update and warns that mend can ignore damaged records, causing them to be omitted from later backups. Recovery should begin with repeatable copies and a clear record of every command.

What you may see

Symptoms that change the recovery path.

01

Database file appears corrupt

The engine detected invalid page or record structures.

02

Checksum errors

Page contents no longer match stored integrity values.

03

gbak fails partway

A damaged table, record, index, or metadata page blocks logical backup.

04

Application aborts on one table

Corruption may be localized rather than database-wide.

Protect the source

Actions that can make the situation worse.

01

mend can silently discard records

It is a last-resort operation for a duplicate.

02

Validation normally updates orphan pages

Use no_update when the goal is report-only assessment.

03

Copying an open database can be inconsistent

Use supported backup or a quiesced storage-level acquisition.

Do this now

Safe steps before evaluation.

01

Stop application writers

Obtain exclusive, consistent database and storage state.

02

Create multiple protected copies

Keep the original untouched and record hashes before validation.

03

Collect engine context

Preserve Firebird version, page size, character sets, schemas, UDFs, logs, and configuration.

04

Identify critical tables

List business records, time ranges, attachments, and row counts needed first.

NEPFOSYS process

How a data-first evaluation proceeds.

01

Page-level assessment

NEPFOSYS inventories headers, page allocation, transactions, metadata, indexes, and readable tables.

02

Controlled logical extraction

Recoverable records are exported from copies with every skipped structure documented.

03

Relational validation

Table counts, keys, relationships, dates, and application-critical records 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.

Is gfix -validate read-only?

Not by default. Firebird provides no_update for report-only validation.

Will rebuilding indexes restore table data?

Indexes can often be recreated, but they do not replace damaged data pages.

Can a corrupt table be skipped?

Sometimes logical extraction can isolate damage, but omitted records must be documented and validated.

DFW local · Nationwide mail-in

Protect the device. Start with the facts.

Start my recovery case