Proxmox Backup Server recovery

A Proxmox Backup Server snapshot is only restorable when its manifest, index and every referenced chunk remain consistent.

PBS stores backups as manifests plus fixed or dynamic index files that reference deduplicated chunks. One damaged index can hide an otherwise intact chunk set, while one missing chunk can affect multiple snapshots that share it.

Start a recovery case Call 682-325-7712

Understand the symptom

Chunk reuse makes the datastore efficient and makes source preservation essential.

WHY

What is happening

Each index names content-addressed chunks protected by hashes and checksums. Recovery maps readable indexes to chunk paths, identifies which snapshots share damaged content, and tests full or partial extraction on a copy without pruning unreferenced-looking data.

What you may see

Symptoms that change the recovery path.

Verify job reports bad chunks

Checksum or hash validation fails for one or more referenced objects.

Restore stops on a missing digest

An index points to a chunk that is absent from .chunks.

Index file will not open

The .fidx or .didx structure is truncated or corrupt.

Several backups fail at the same point

Deduplicated snapshots may share one damaged chunk.

Protect the source

Actions that can make the situation worse.

Garbage collection can delete evidence

Incorrect access times or damaged indexes can make needed chunks appear unused.

New backups change shared state

Writers and retention tasks add or remove references during analysis.

Ignoring corrupt chunks creates holes

Partial extraction may substitute zeros and must be reported as incomplete.

Do this now

Safe steps before evaluation.

Pause prune, GC and backups

Stop tasks that modify datastore references or chunk retention.

Preserve indexes and chunks together

Copy manifests, .fidx, .didx, .chunks, logs and configuration as one set.

Keep encryption material

Retain client keys, passwords, fingerprints and the original backup environment.

Record affected snapshots

Save verify output, digests, paths, backup groups and first failure time.

NEPFOSYS process

How a data-first evaluation proceeds.

Reference mapping

NEPFOSYS maps manifests and indexes to available chunks across affected snapshots.

Protected extraction

Readable content is reconstructed from copied indexes and chunks, with missing ranges documented.

Backup validation

Recovered archives and priority files are verified outside the production datastore.

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 one corrupt chunk affect many backups?

Yes. Deduplication allows multiple snapshot indexes to reference the same chunk.

Should I run garbage collection first?

No. Preserve the datastore before any process that can delete chunks considered unreferenced.

Can PBS recover around a missing chunk?

Partial recovery may be possible, but the missing content cannot be recreated from an index alone.

DFW local · Nationwide mail-in

Protect the device. Start with the facts.

Start my recovery case