Synology Hyper Backup recovery

A Hyper Backup task that becomes Restore Only is protecting a damaged repository from additional writes—not confirming that every version is recoverable.

Hyper Backup integrity checking evaluates both backup data and the index structure. When corruption is detected, a task can change to Restore Only so new backup activity does not modify the broken target further.

Start a recovery case Call 682-325-7712

Understand the symptom

Versioned backup data and its index must agree for a reliable restore.

WHY

What is happening

Recovery distinguishes damaged repository blocks, missing versions, index inconsistency, bad destination media and transport interruption. Available versions can be compared and extracted from a protected copy while the original target remains unchanged.

What you may see

Symptoms that change the recovery path.

Task status is Restore Only

Hyper Backup has stopped accepting new writes after detecting corruption.

Integrity check finds a broken target

The data or index stage reports inconsistency.

Restore browser cannot list versions

Repository metadata cannot enumerate the expected timeline.

Restore fails on selected files

Specific repository blocks or versions are unreadable.

Protect the source

Actions that can make the situation worse.

Rotation can remove older usable versions

Retention processing may delete data still needed for recovery.

Relink writes metadata

A new task relationship can change the only repository copy.

Source and backup can share a fault

A failing NAS volume may damage both live data and a locally stored backup.

Do this now

Safe steps before evaluation.

Stop the backup task

Pause rotation, integrity repair, relink and destination cleanup.

Copy the full repository

Preserve every backup file, index, database, key, configuration and log.

Record version availability

Capture task state, checked percentage, failed paths and last successful restore.

Check destination health

Preserve SMART, Btrfs, RAID, filesystem and transport events from the target.

NEPFOSYS process

How a data-first evaluation proceeds.

Repository inventory

NEPFOSYS maps versions, indexes, keys and storage damage on the preserved target.

Version comparison

Readable restore points are tested without rotating or rewriting the original.

Selective validation

Priority folders and files are restored and checked from the strongest available version.

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.

What does Restore Only mean?

The task can restore but is blocked from adding new backup data after an integrity problem or incompatible state.

Can an integrity check repair all corruption?

No. It can detect problems and sometimes repair supported cases, but missing or unreadable backup content may remain.

Should I create a new backup to the same target?

No. Use separate storage so the damaged repository and older versions remain preserved.

DFW local · Nationwide mail-in

Protect the device. Start with the facts.

Start my recovery case