Read Hyper Backup Integrity Results Without Mistaking Partial Coverage for a Full Check
A successful integrity-check notification is useful evidence, but its meaning depends on the task settings and the amount of data checked. For a backup review, record the task name, destination and check time before deciding that the entire archive has been inspected.
Hyper Backup distinguishes the backup's index structure from its stored data. Synology documents an index review on each integrity run, with data checking selected separately. A time limit can restrict how much backup data is examined during that run. The log reports coverage, and later checks continue from earlier results.
Read the result alongside its settings
Open the task's integrity settings and note whether data checking is enabled and whether it has a time limit. Then inspect the log for the corresponding run. Keep the amount checked in this run separate from any cumulative progress shown. A message that a timed check finished should not be rewritten in an office checklist as every byte checked today.
For example, a useful review entry says that the index check completed and the data check covered a stated portion during the available window. Include the actual date and task identifier. Avoid combining the completion time from one destination with the coverage figure from another similarly named task.
Keep restoration as a separate acceptance step
An integrity result does not show that staff can find the required version, supply the necessary credentials and open the restored document in its application. Choose a non-sensitive sample from a relevant backup date and restore it to a separate location using the documented recovery workflow. Inspect the content that matters to the business.
If the integrity check reports corruption, preserve its exact message and the destination details before making changes. Do not remove older backup versions simply to make the next check faster. Retention determines which recovery dates remain available, so any change needs a recovery requirement, not just a shorter run time.
Sources: Synology documentation 1.