Synology Hyper Backup / Troubleshooting
Synology Hyper Backup Restore Only After an Integrity Check
Confirm the integrity-check finding, preserve recovery options, and identify the evidence needed for a destination-specific recovery plan.
By Andrey Tretyak · Sources last reviewed
Restore Only is a protective state after a corruption finding, not a slow-backup indicator. Identify the recorded finding before deciding what recovery work is appropriate; the status does not identify one specific failed component.[1][2]
Sections
Applicability
- Products
- Synology DSM · Synology Hyper Backup
- Scope
- For DSM 7 Hyper Backup data-backup tasks that changed to Restore Only after an integrity check. An ongoing check or an incomplete time-limited data check is not the same state. This page covers read-only triage, not a storage repair, relink, or task-recreation procedure.[1][2]
- Last verified
Symptoms
- The task no longer performs backups after the integrity check changes its state to Restore Only. Existing versions cannot be deleted through normal task management in this state.[3]
Quick diagnosis
Start with the recorded state and preserve the evidence before choosing a next action.
Read the integrity-check result
Compare the current task state with the integrity-check log. Distinguish a reported corruption result from a check that is still running or a time-limited data-check progress entry.[1]
Record available version information
Inspect Version List for version status and dates without deleting anything. A listed version is useful evidence, not a guarantee that every contained file is recoverable.[3][1]
Write down the version date and status you can actually see. Keep "listed", "browsable" and "successfully restored" as separate observations; do not label a backup tested merely because it appears in Version List.[3][1]
Interactive troubleshooter
Your answers stay in this browser tab. The tool does not connect to your systems or send diagnostic results.
Guided check / step 1
Did the task change to Restore Only after an integrity check?
Confirm the task state and the check context.[1]
Read the complete diagnostic tree without using the controls
- Did the task change to Restore Only after an integrity check?
Confirm the task state and the check context.[1]
- Yes → What does the integrity-check log show?
- No, or uncertain → Preserve and clarify the evidence
- What does the integrity-check log show?
Separate a reported corruption result from progress information.[1]
- The log reports corrupted backup data → Where is the backup stored?
- Only progress is shown, or the result is unclear → Preserve and clarify the evidence
- Where is the backup stored?
Select the actual destination; recovery branches differ.[2]
- Remote Synology NAS → Is a repository modification known?
- USB device → Is a repository modification known?
- Synology C2 → Prepare the C2 recovery handoff
- Another destination, or I am not sure → Preserve and clarify the evidence
- Is a repository modification known?
Inspect the history without moving or editing backup data.[2]
- Yes → Provide the modification history for recovery planning
- No, or history is uncertain → Prepare an investigation without assuming a failed component
- Preserve and clarify the evidence
Record the exact task state, integrity-check result and destination before selecting a recovery procedure. Progress alone does not establish this failure, and an unsupported destination should not inherit the USB, C2 or remote-NAS branch by guesswork.[1][2]
- Prepare the C2 recovery handoff
Use the C2 entry under "Choose the matching Synology recovery branch" below. Preserve source-system findings and the integrity result before planning any task recreation.[2]
- Provide the modification history for recovery planning
Record what was moved, edited or removed and the last known working location/state before using the documented recovery procedure. No guessed relink or move is prescribed here.[2]
- Prepare an investigation without assuming a failed component
Bring the Restore Only state, integrity-check result, destination type, shutdown observations and known repository history to the vendor recovery workflow. Hardware testing and repair require a separate plan; this status does not prove bad RAM or a failed drive.[2]
Detailed diagnosis
1. Separate progress from a corruption result
A time limit can leave the backup-data scan partially covered across runs. Use the logged result and task state, not the percentage alone, to establish whether this Restore Only workflow applies.[1]
2. Identify changes and shutdown history
Review whether the destination repository was moved, edited or removed. For the source NAS, check Log Center for improper shutdowns; include the remote NAS when it is the destination. Record observations without attempting a repair.[2]
3. Identify the destination before recovery planning
Record whether the target is a remote NAS, USB device, Synology C2, or another destination. The vendor procedure has destination-specific branches; a USB compatibility check is not a cloud-storage remedy.[2]
Supported scenarios
Match each explanation to the observation before treating it as the diagnosis.
The check detected corrupted backup data
Hyper Backup stops further backup writes after the corruption finding.[1]
How to check: Confirm the matching logged corruption result rather than inferring corruption from duration.[1]
Repository modification needs investigation
Direct destination changes can make the repository unreadable; hardware-related causes are also possible.[2]
How to check: Document known changes separately from suspected hardware faults.[2]
Next actions and procedure boundaries
Prepare for the documented recovery procedure
Before selecting a recovery procedure, record the Restore Only state, the integrity-check result, the destination type, any known repository move/edit/removal, and relevant improper-shutdown observations. The vendor's memory testing, scrubbing, relink and recreation branches require their own procedures and recovery planning; do not run them from this diagnostic page. Unknown modification history is a reason to seek support, not to guess an original location.[2]
Choose the matching Synology recovery branch
Remote Synology NAS: collect shutdown and repository-history evidence from both systems. In the linked Restore Only article, use the remote Synology backup procedure in step 4 after the cause has been addressed.[2]
USB destination: record the device model and check Synology's compatibility list through step 3 of the same article. Step 4 links the local shared-folder or USB procedure. A USB compatibility check does not diagnose C2.[2]
Synology C2: preserve source-system evidence. After the source-side investigation, the vendor's destination branch leads to the C2 procedure in step 4. Do not apply USB checks or remote-NAS operations to this destination.[2]
These are procedure-selection instructions, not permission to recreate a task. Before repair or recreation, establish a recovery plan and protect retained backups; this page supplies no universal rollback. If the destination or modification history is uncertain, bring that uncertainty to Synology support.[2]
Preserve encrypted-backup recovery access
If the backup is encrypted, confirm that its password or encryption key is available to the authorized recovery operator. Never paste it into a public report. This check does not test or guarantee restoration.[4]
Warnings and boundaries
Editorial verification
The citations beside technical claims show their evidence. HomeLabFix chooses the diagnostic order and states where the evidence stops supporting a conclusion.
- Author and technical editor
- Andrey Tretyak
- Verification basis
- The cited vendor or project documentation plus the page-specific reasoning above.
- Hands-on status
- Direct reproduction is claimed only when a page explicitly describes the tested environment and result. “Last verified” means the cited evidence was reviewed on that date; it does not mean every procedure was reproduced.
- Correction path
- Report a source change, scope error, or reproducible contradiction.
Sources
Links were reviewed on 2026-09-05. Reachability and automated validation do not replace editorial verification of each claim.
- What is backup integrity check for Hyper Backup tasks?
Synology · Tier A · accessed 2026-09-03 - My Hyper Backup task status changes to Restore Only. What can I do?
Synology · Tier A · accessed 2026-09-05 - Backup Tasks
Synology · Tier A · accessed 2026-09-03 - Settings
Synology · Tier A · accessed 2026-09-03