Troubleshooting guide

Synology Restore to Different NAS: Why Files Are Missing After Restore

Category: Backup & Restore

You restored an offsite Hyper Backup vault to a different Synology NAS, but the restore finished and files that exist in the backup are absent from the target.

Check the restore scope and target path

Open Hyper Backup on the target NAS and review the restore job settings. Confirm you selected the correct backup version and that the restore scope includes the folders you expect. A common cause is restoring only a subset of shares. After the job, compare the top-level folder list on the target against the backup’s folder list in Hyper Backup Explorer. If entire shares are absent, the scope was too narrow; re-run the restore with the full scope.

Confirm the target share exists and has space

On the target NAS, verify each destination shared folder exists and is mounted. If a share was renamed or not created before restore, Hyper Backup may skip its contents without failing the job. Check Control Panel > Shared Folder and confirm the share names match the backup exactly. Also check Storage Manager for free space; a full volume can truncate the restore silently. If space is low, free capacity and restore again.

Run a verification test

Use Hyper Backup Explorer on a workstation to open the same backup version and note the file count and total size for one affected folder. Then compare that count and size on the target NAS. A mismatch confirms the restore gap rather than a display issue. Record both numbers before changing anything.

Rollback and recovery note

Before re-running, snapshot or rename the partially restored share so you can roll back if the second attempt overwrites good data. If the verification test still shows missing files after a full-scope restore with adequate space, the backup index may be incomplete; do not delete the vault. For a controlled diagnosis of this synology restore to different nas gap,

A Synology backup task and a restored sample folder

Ask for help.


Back to the service page · Ask about this exact symptom