Tech · PRACTICAL GUIDE
Synology Photos Files Restored but Albums and People Are Missing? Check the App Backup Before Reindexing
If the files are visible on a new Synology NAS but created albums, People, Subjects, Places, settings, or share links are missing, pause before reindexing. First prove whether your backup contains the Synology Photos application data, not only the photo folders, and protect both the old NAS and any new-NAS changes before a supported restore.

Do not delete, reset, uninstall, or reindex Synology Photos yet. Visible photo and video files prove that storage data arrived; they do not prove that the Synology Photos application database arrived. Preserve the old NAS and backup, protect anything added to the new NAS, then check whether the backup includes the Synology Photos application. A supported application restore may recover created albums, recognition results, settings, and share links, but it can overwrite the current Photos data and settings.
First, freeze the last good copy
Keep the old NAS available and unchanged if it still contains the correct albums or recognition data. Do not uninstall Synology Photos, delete its application data, remove user accounts, run a reset, or start a large reindex as a first response. Also stop adding or reorganizing photos on the new NAS until you have protected those changes separately. Synology states that restoring the Photos application overwrites the current application data and settings, so a restore performed without a safety copy can replace work created after the move.
Record what is missing before changing anything: test two or three created albums, a few named people, Subjects or Places results, at least one share link, and both Shared Space and each affected user's Personal Space. This symptom list becomes the verification checklist after recovery.
A file restore and a Photos application restore are different
Open the backup task or archive with the supported Synology backup tools and inspect what the task actually included. A folder-only backup of /photo or a user's Photos folder can return the original media files, but it is not evidence that the Photos application data was saved. In Synology's current help, selecting the Synology Photos application in Hyper Backup includes the media, created albums and folders, People, Subjects, and Places recognition results, package settings, and share links.
Treat that distinction as the main fork in the diagnosis. If the archive lists Synology Photos as an application, a supported application restore may exist. If the archive contains only folders, do not promise that albums, recognition labels, settings, or shares can be reconstructed from the files alone. Hyper Backup Explorer can help confirm archive contents, but browsing files is not the same as restoring the application database.
Check Personal Space with the original user identity
Log in as each original DSM user who owned a Personal Space instead of testing only with an administrator account. Shared Space and Personal Space can make the same files appear under different ownership and library contexts. Confirm that the relevant DSM accounts still exist and that you are viewing the same space that held the missing albums.
Synology's help warns that a deleted user's personal profile cannot be restored. If an original account was deleted or recreated with a different identity, stop before assuming that reindexing will reconnect its library. Preserve the old NAS and backup and ask Synology Support about the supported options for that exact source and destination combination.
Choose one supported recovery path
If the old NAS is still healthy and both models and DSM versions meet Synology's compatibility rules, review Migration Assistant first. It is the supported whole-device route designed to transfer packages, settings, and package data together. Do not start it merely because it appears in Package Center: confirm the source and destination requirements in Synology's current migration documentation and protect anything already created on the destination.
If a valid Hyper Backup snapshot includes the Synology Photos application, first back up the current state of the new NAS. Confirm that the destination volume is not smaller than the backed-up volume, the destination DSM and package combination is supported, and the required photo folders are present in the restore selection. Then use Hyper Backup's supported restore workflow for the application and its required data. Exact menu labels can vary by DSM and package version, so follow the current Synology screen for your installed versions rather than an old screenshot.
If you have only the media files, there is no supported application snapshot to restore, the original user profile is gone, or the source and destination are incompatible, stop treating recovery as guaranteed. Keep the media safe, keep the old NAS or archive untouched, and open a Synology Support case before rebuilding. Reindexing can create a new library from files; it is not proof that old created albums, face names, share links, or user associations will return.
Protect against the overwrite trap
A Photos application restore is not a merge button. Synology says the restore overwrites current data and settings. Before starting, export or back up photos uploaded since the migration, record new album or share work, and keep a recoverable copy of the current destination state. If you cannot explain which copy is authoritative and how to roll back, do not run the restore yet.
Do not restore repeatedly to see what happens. Use one documented source snapshot, one supported path, and a written pre-restore checklist. Confirm available space, package support, DSM compatibility, and user accounts first. A general Hyper Backup job marked successful confirms that the job ran; it does not confirm that every Photos-specific object was included or that the restored library passes your checks.
How to know the recovery is complete
After the supported migration or restore finishes, sign in as every affected user and compare the same samples you recorded at the start. Open several created albums, check a few named people and recognition categories, test Subjects and Places where they previously existed, open at least one share link, and download random original files rather than relying on thumbnails. Check Shared Space and each relevant Personal Space separately.
Do not retire or wipe the old NAS after the first successful login. Keep the last known-good source until the new system has completed indexing and the sample checks pass. Also verify that photos added on the new NAS before the restore were preserved through your separate safety copy and that the library did not create obvious duplicates.
Stop conditions and the safe failure path
Stop and preserve evidence if the backup does not list Synology Photos as an application, the destination volume is smaller, the DSM or package combination is unsupported, the original user's profile was deleted, or restoring would overwrite unprotected new data. Also stop if the restore completes but the same albums and recognition data remain missing.
Keep the old NAS powered off but available when practical, retain the original archive, save Hyper Backup logs and screenshots of the missing items, and contact Synology Support with the source model, destination model, DSM versions, Synology Photos versions, backup method, affected user accounts, and exact tests that failed. Avoid database edits and unofficial scripts while a supported recovery path may still be possible.
