SQL Server snapshot recovery

A suspect SQL Server database snapshot is dependent on the source database and cannot be treated as an independent backup.

SQL Server database snapshots store copy-on-write pages in sparse files while unchanged pages still come from the source database. If a sparse file fills, disappears, or becomes corrupt, the snapshot can turn suspect even while the source remains online.

Start a recovery case Call 682-325-7712

Understand the symptom

A snapshot is a page map across its sparse files and the live source database.

WHY

What is happening

When a source page first changes, its original image is copied to the snapshot sparse file. Recovery must identify the source database generation, snapshot metadata, file mappings, disk-space event and requested point in time before deciding whether revert, restore or object extraction is viable.

What you may see

Symptoms that change the recovery path.

Snapshot state is SUSPECT

Queries fail because SQL Server cannot maintain or read the snapshot files.

Sparse file ran out of space

The snapshot could not grow while source pages continued changing.

Snapshot file is missing

A file move, storage outage or cleanup removed part of the snapshot map.

DBCC reports snapshot errors

Consistency checks cannot create or read the internal or user snapshot correctly.

Protect the source

Actions that can make the situation worse.

A snapshot is not a backup

It depends on the source database and does not protect against shared storage failure.

Revert changes the source

Reverting replaces current pages with the snapshot view and can remove later transactions.

Deleting files removes evidence

The sparse file may contain the only retained version of changed pages.

Do this now

Safe steps before evaluation.

Stop snapshot changes

Pause avoidable source writes and do not revert, drop or recreate the snapshot.

Record file and database state

Capture sys.databases, sys.master_files, snapshot creation time, error logs and free-space events.

Preserve the complete set

Copy source files, sparse files, logs, backups and storage metadata together.

Protect the storage layer

Snapshot or image affected volumes before cleanup, repair or file replacement.

NEPFOSYS process

How a data-first evaluation proceeds.

Dependency mapping

NEPFOSYS correlates snapshot pages, sparse files and the matching source-database generation.

Recovery-path testing

Restore, snapshot extraction and source recovery options are tested on protected copies.

Data validation

Priority tables and records are checked against the requested snapshot time and current database state.

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 a database snapshot be restored like a backup?

No. It depends on the source database and cannot be backed up or restored independently.

Does a suspect snapshot mean the source is corrupt?

Not necessarily. The snapshot can fail from sparse-file, space or storage problems while the source remains readable.

Should I run DBCC repair on the source?

Not until the source, snapshot and storage evidence are preserved and the actual corruption scope is known.

DFW local · Nationwide mail-in

Protect the device. Start with the facts.

Start my recovery case