Perforce server recovery

Helix Core recovery must reunite database metadata, journal history, and versioned depot files at a consistent point in time.

Helix Core stores operational metadata in database tables while versioned file content lives in depot storage. Checkpoints capture database state and journals record later metadata changes. Disk failure can damage any of those layers independently.

Understand the symptom

A checkpoint plus the correct journal sequence rebuilds metadata; depot files supply versioned content.

WHY

What is happening

Perforce documents database recovery from a stored checkpoint followed by accumulated journals. A metadata-only recovery can succeed while depot content is still missing, stale, or corrupt, so both timelines must be validated together.

What you may see

Symptoms that change the recovery path.

01

Database table errors at startup

One or more db.* files are unreadable or inconsistent.

02

Journal replay stops

A journal record, sequence, checksum, or target state is invalid.

03

Revisions list but cannot sync

Metadata exists while archive content is missing or damaged.

04

Replica differs from the primary

Metadata or depot replication stopped at a different change number.

Protect the source

Actions that can make the situation worse.

01

Checkpointing a damaged database preserves bad state

Do not replace the last known-good checkpoint.

02

Skipping journals loses metadata changes

Later changelists, clients, labels, and protections may disappear.

03

Overwriting depots destroys version content

Recovered database rows cannot recreate missing archive bytes.

Do this now

Safe steps before evaluation.

01

Stop all Helix services

Prevent submits, journal writes, replication, rotation, and cleanup.

02

Copy metadata and depots

Preserve P4ROOT and every versioned-file location with ownership and timestamps.

03

Inventory recovery artifacts

Record checkpoint numbers, journal sequence, server IDs, change counters, and replica status.

04

Protect workspace evidence

Keep critical client workspaces and shelved or unsubmitted files.

NEPFOSYS process

How a data-first evaluation proceeds.

01

Timeline assessment

NEPFOSYS maps checkpoints, journals, database tables, change counters, depots, replicas, and storage health.

02

Copy-based reconstruction

Candidate metadata states and journal sequences are rebuilt without altering originals.

03

Depot validation

Changelists, paths, revisions, file hashes, permissions, shelves, and priority syncs 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.

Are checkpoints complete backups?

They rebuild database metadata but do not contain the versioned depot files themselves.

Can a replica replace a failed primary?

It may provide a consistent source, but replication position and depot completeness must be verified.

Can missing submitted files be rebuilt from metadata?

No. Metadata identifies them but cannot recreate absent content bytes.

DFW local · Nationwide mail-in

Protect the device. Start with the facts.

Start my recovery case