Windows Server Backup recovery

A corrupt Windows Server Backup catalog does not automatically mean the underlying backup versions are gone.

Windows Server Backup uses a catalog to identify stored versions and recoverable items. The local catalog can be corrupt or missing while backup data remains on a disk or network share, but damage to the backup target itself requires source preservation first.

Understand the symptom

Catalog restoration and backup-media recovery are separate tasks.

WHY

What is happening

Microsoft provides wbadmin restore catalog for a catalog stored with the backup. Deleting a corrupt local catalog removes its inventory from the snap-in, and new backups can overwrite target space or retention points. If the backup disk, RAID, share, or virtual disk is damaged, repair should not precede imaging and file-set preservation.

What you may see

Symptoms that change the recovery path.

01

No backup versions are listed

The local catalog or machine association cannot enumerate stored recovery points.

02

Catalog is corrupt

The snap-in or wbadmin cannot use its inventory even though backup folders remain.

03

Backup target is offline or unreadable

Disk, network, filesystem, permissions, or media faults block access to the set.

04

VHD or VHDX files exist but will not mount

The backup payload or underlying storage may be incomplete or corrupt.

Protect the source

Actions that can make the situation worse.

01

New backups overwrite retention points

Starting another job on the same target can reuse space needed for older versions.

02

Catalog deletion removes convenient inventory

It does not recover damaged media and can make version discovery harder without preserved metadata.

03

Mounting images read-write changes them

Guest filesystem replay and host writes can alter the only backup payload.

Do this now

Safe steps before evaluation.

01

Disable scheduled backups

Prevent jobs, retention, cleanup, and target rotation from changing the backup set.

02

Preserve the complete hierarchy

Keep WindowsImageBackup, Catalog, MediaId, machine folders, VHD or VHDX files, logs, and timestamps.

03

Record wbadmin evidence

Save get versions output, machine name, target path, errors, and the desired backup date.

04

Protect the backup target

Image or snapshot failing disks, arrays, shares, or virtual storage before catalog restoration or mounting.

NEPFOSYS process

How a data-first evaluation proceeds.

01

Catalog and media inventory

NEPFOSYS maps versions, machine identity, payload files, target health, and requested restore points.

02

Source preservation

Damaged backup storage is acquired before catalog or virtual-disk work.

03

Version and file extraction

Viable backup images are opened from copies and priority volumes, applications, or files are validated.

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 the catalog be restored from the backup target?

Microsoft supports restoring a catalog from a specified backup location when the catalog stored there is intact.

Should I delete a corrupt catalog?

Not before preserving the backup set and determining whether it can be restored. Deletion removes local inventory and does not repair damaged media.

What should I keep from Windows Server Backup?

Preserve the complete WindowsImageBackup directory, catalogs, media ID, machine folder, virtual disks, logs, timestamps, and the original target.

DFW local · Nationwide mail-in

Protect the device. Start with the facts.

Start my recovery case