NAS Codex › Synology › Synology Hyper Backup task in restore-only state after an integrity check: what Synology says
Synology Hyper Backup task in restore-only state after an integrity check: what Synology says
A Hyper Backup task shows that it is restore-only after a backup integrity check. Synology's DSM 7 Hyper Backup help explains what that state means, what it warns can corrupt backup data, how integrity checks are run and scheduled, and how to restore data, including from damaged backup versions. This page collects those facts in one place.
Written against: Synology DSM 7 help for Hyper Backup (Backup Tasks, Settings and Restoration). Last Updated: November 2026. Vendor menus and wording change between versions; if yours differ, follow the vendor page linked under Sources.
Before anything else: if the data on this NAS is not backed up somewhere else, copy it off first. Do not continue with any step on this page until you have.
Fast Answer
Synology says a task enters restore-only state when something wrong is found during the integrity check: data in the task is no longer backed up, and existing backup versions cannot be deleted. You can still restore. Go to Restore > Data, or open Backup Explorer to pick files from a version. With Hyper Backup on DSM 6.1 or later you can partially restore files from previously damaged backup versions; damaged files are skipped. Never modify or delete files directly in a backup destination: Synology says it corrupts the stored backup data.
What restore-only means
Synology's help for Hyper Backup tasks says that if something wrong is found during the integrity check, the backup task will enter a restore-only state. In that state, data in the task is not backed up anymore, and existing backup versions cannot be deleted.
In short, the task stops protecting new changes, but what it already holds can still be restored. The restore steps are below.
What Synology warns can corrupt backup data
The same help page warns that modifying or deleting files directly in a backup destination will corrupt the stored backup data and cause unexpected behavior. Synology also says that Hyper Backup stores data in the .hbk format, which can only be read by Hyper Backup, Hyper Backup Explorer and Hyper Backup Vault, and that you should not rename the destination folder, because relinking to the task will then fail.
Running an integrity check yourself
Among the actions for a task, Synology lists Check backup integrity. It says the check lets you know whether the task can proceed and whether the data can be restored.
Scheduling integrity checks
Synology's Hyper Backup settings help describes the integrity check schedule, which has two parts:
- Check index structure: required. Synology says it ensures that backup and restoration can succeed.
- Check data: optional. It ensures that the data can be restored. You can set a time limit; setting 0 minutes checks all the data. Its progress is written to the logs.
If an integrity check is scheduled at the same time as a backup, Synology says they run one after the other. The schedule cannot be modified from Control Panel, but it can be deleted there.
Restoring data from the task
Synology's Restoration help gives these routes:
- Restore (upper left) > Data, then select the task for a local repository, or choose to restore from existing repositories for an external one. An encrypted task needs its password or encryption key.
- Backup Explorer: select the task, pick a version from the timeline or calendar, then use Restore, Copy to, or Download for a single file. Synology notes that Copy to and Download do not keep the original privileges, and that Backup Explorer is only for multi-version tasks.
- The .hbk file: double-click it in File Station to open Hyper Backup Explorer, or right-click the
.hbkor.bkpifile and select Mount Hyper Backup destination to browse it through File Station or SAMBA/AFP. Unmount turns this off.
Two points from the same page matter after an integrity problem. Files that were modified during a backup are skipped on restoration. And with Hyper Backup on DSM 6.1 or later, you can partially restore files from previously damaged backup versions; the damaged files are skipped.
If you restore an entire system, Synology warns that the drives on the destination must have more capacity than the backed-up drives, and that all data on the destination will be overwritten and cannot be recovered.
Not the same as a suspended task
Synology describes a separate state, suspended. Its settings help says that if a task is interrupted and can be resumed, its status becomes suspended; if it cannot be resumed, it is cancelled. For a suspended task, previous versions cannot be deleted and the version in progress is incomplete, and you can choose Resume or Discard. Synology says a task suspended by something other than a person, such as a network disconnection or power outage, resumes on its schedule once the cause is gone. A restore-only task is different: it is the result of a failed integrity check, and it no longer backs up data.
The three help pages cited here do not describe a way to return a restore-only task to normal backups. A new data backup task is created from + > Data backup task.
Summary of what Synology says
- Restore-only follows a failed integrity check: no more backups, no version deletion.
- Never modify, delete or rename anything in the backup destination yourself.
- Restore through Restore > Data, Backup Explorer, or a mounted .hbk; on DSM 6.1 or later, damaged versions can be partially restored.
- Schedule integrity checks: index structure is required, data check is optional.
When to stop and get help
Before restoring an encrypted task, make sure you have its password or encryption key: Synology says losing them means the data is permanently lost. If the volume holding the backup has turned read-only, see volume read-only first.
Questions
What does restore-only mean in Synology Hyper Backup?
Synology says a task enters restore-only state when something wrong is found during the integrity check. Data in the task is not backed up anymore and existing backup versions cannot be deleted, but you can still restore from it.
Can I restore from a damaged Hyper Backup version?
Synology says that with Hyper Backup on DSM 6.1 or later you can partially restore files from previously damaged backup versions. The damaged files are skipped.
What corrupts Hyper Backup data?
Synology warns that modifying or deleting files directly in a backup destination corrupts the stored backup data and causes unexpected behavior. It also says not to rename the destination folder, or relinking fails.
Sources
Every fact on this page comes from the vendor documents below, opened on 2026-11-17.