Why is Hyper Backup skipping backups with a timeout waiting for integrity check message?

Applies to: Hyper Backup tasks on DSM 7.x, including supported DSM 7.3 systems, reporting the specific timeout waiting for integrity check message.

Check and resolve

1. Open the failed task's log and confirm the exact timeout message. Note the scheduled backup time, integrity-check start/end times and whether a check is still active.
2. Open the task's schedule settings. Compare the backup window with the integrity-check window and allow the check to finish before the next backup starts. Choose timings based on measured duration, rather than assuming a short quiet period is enough.

   

3. If checks regularly take longer than three hours, review the destination's health, available space and observed read/write performance. Check whether the delay is new or follows a larger repository or more retained versions.
4. Distinguish the backup-data check from the index-structure check. A time limit can restrict the data portion, while the index is still checked each time. Use the available settings with the recovery policy in mind.
5. After the current check finishes, run one backup and watch its log. Confirm that a completed new recovery version appears.
6. Keep the revised schedules under observation for the next automatic cycle. A manual success does not prove that the scheduled overlap has been resolved.

Check the result

The integrity check and the next scheduled backup both finish without the timeout. Restore a small test file to a separate location to confirm recovery works.

Need help?

Submit Ticket if the destination appears unhealthy or the check no longer progresses. Include task timings, log messages and destination type, with credentials removed.