From the knowledge base, the main checks and fixes for Hyper Backup failures or stalls are:
1. Check the storage pool and volume status
- On DSM 7 and above, go to Storage Manager → Storage and check whether any storage pool is degraded or currently performing operations such as adding drives, changing RAID type, or repairs. If so, wait until those operations finish or repair the degraded pool.
- Also check the volume status. If usage exceeds 90%, free up space. This may improve backup performance.
- On DSM 6.2 and below, the same idea applies, but the checks are on the Storage Pool and Volume pages.
Source: [10]
2. Run the checks recommended when a task changes to “Restore Only”
- Run a memory test three times on the source Synology system. If it fails, the memory may be defective.
- Check Log Center for any recent improper shutdowns and troubleshoot them if found.
- Run data scrubbing for the storage pool where the backup source or backup data (.hbk file) is located.
Source: [9]
3. If Hyper Backup is hung and cannot be deleted or edited
- One reported workaround was to de-install Hyper Backup, re-boot NAS, then re-install Hyper Backup, and re-link to previous backup.
- The report specifically says the reboot is the key step; otherwise corrupted history may remain and the task may stay frozen.
Source: [8]
4. If you are dealing with older Hyper Backup versions or crashes
- The release notes mention fixes for random backup failures, crashes with many subfolders, and failures related to enabling the package while a USB destination is being removed.
- These notes are from older Hyper Backup versions, so they may only apply to legacy DSM/package builds.
Source: [1]
If you want, I can also turn this into a short step-by-step troubleshooting checklist for your exact DSM version.
Sources used: [1], [8], [9], [10]