NAS backup foundation
Synology Hyper Backup: Build a Backup You Can Actually Restore
Hyper Backup is one of the strongest reasons to use Synology, but a backup task is only useful when its scope, destination, retention and restoration behavior are understood. DSM 7.4 supports backups of system data, folders, files, LUNs, packages and configurations to several kinds of destinations. The dangerous mistake is to enable a nightly job, see a green status, and never test whether the repository contains the right data or whether another administrator could recover it after the NAS is gone.
Quick answer
Design the restore before scheduling the backup
Choose what must be recovered, select a destination outside the failure domain you are protecting against, enable a retention policy appropriate to change rate, use encryption where the destination should not see plaintext, schedule integrity checks, and perform sample restores. Hyper Backup can keep many versions and resume interrupted tasks, but no retention setting compensates for backing up the wrong folders.
Live Amazon products
Current hardware for this workflow
This Sprint 9E catalogue is intentionally small: it surfaces current and previous Synology systems relevant to photo, backup and remote-access ownership decisions, while compatible third-party NAS drives can be read from Cloudzat Storage Price Intelligence in read-only mode. Hardware cards support the workflow; they do not replace the application and recovery guidance on each page.
Owner decision
One task rarely protects every risk
Use separate tasks when destinations, recovery objectives or retention policies differ. A local USB copy can recover quickly from accidental deletion, while an offsite NAS or cloud target protects against loss of the building. The strongest design often combines them rather than forcing one repository to serve every purpose.
Interactive owner tool
Hyper Backup Strategy Planner
Use this as a planning aid. It identifies missing reliability layers and the simplest likely direction, but it does not replace current Synology, Immich, Backblaze, Google or Tailscale documentation for the exact service and software version.
Owner reliability checklist
Four checks before trusting the new workflow
Protect the original data
A photo or backup application is not the final safety layer. Know where originals live and keep an independent copy outside the primary NAS.
Design remote access by user role
Family photo access, private administrator access and public sharing do not need the same exposure or credentials.
Document recovery secrets
Encryption keys, cloud credentials, tailnet access and DSM accounts should remain recoverable even when the original NAS is unavailable.
Test before deleting the old copy
Migration and backup jobs are complete only after representative files restore, metadata looks correct and the next administrator can follow the procedure.
Define the recovery objective before the destination
Backup design starts with the failure you want to survive. Recovering one accidentally deleted document is different from rebuilding an entire NAS after theft or fire. Those scenarios may require different destinations, schedules and retention.
Write down the acceptable data-loss window and recovery time for the most important folders. That simple exercise makes it easier to decide whether nightly cloud backup is enough or whether a local fast copy and more frequent snapshot layer are also required.
Know what Hyper Backup can protect
DSM 7.4 documentation lists entire system data, folders, files, LUNs, packages and system configurations among supported sources, with destination options varying by task type. That breadth can simplify recovery because configuration and application data can be included alongside ordinary files.
Do not assume every package or special dataset is captured identically. Review the source selection screen and Synology limitations for the exact task. Critical application data may need an application-specific backup in addition to Hyper Backup.
Choose local, remote or cloud according to the threat model
Local shared folders and external devices can provide fast recovery and can be practical for large datasets. A remote Synology or rsync server moves the copy to another machine. Public cloud and S3-compatible destinations can move it outside the building.
A local USB disk is not a complete disaster-recovery strategy if it remains permanently attached beside the NAS. Likewise, a cloud copy may be too slow for a multi-terabyte emergency restore. Combining different destinations can give both speed and geographic separation.
Understand the Hyper Backup repository format
Multi-version tasks store data in Synology’s .hbk backup format, which is designed to be browsed and restored with Hyper Backup, Hyper Backup Explorer or Hyper Backup Vault. This is not the same as a simple mirror of ordinary folders.
The format enables versioning and deduplication, but it also means recovery procedures should be documented. An administrator who only knows how to mount the backup drive in Finder or Explorer may be surprised that the repository is not intended to be treated like a normal folder tree.
Retention should match how data changes
Hyper Backup can keep large numbers of versions and offers rotation strategies such as Smart Recycle and custom retention. More versions are not always better if the repository grows without regard to recovery value.
Keep dense recent versions when accidental edits are likely to be noticed quickly, then reduce frequency as backups age. Important legal or archival data may justify a different schedule from replaceable media. Separate tasks can keep those policies understandable.
Encryption protects the destination from reading your backup
Client-side encryption is useful when backups leave your physical control. Synology documents client-side data encryption and transfer encryption capabilities for Hyper Backup.
Protect the encryption password or key material outside the NAS. An encrypted backup with lost credentials is effectively a successful destruction of your own data. Recovery documentation should tell a trusted administrator where those secrets are stored.
Integrity checks are not optional ceremony
Hyper Backup supports backup-data and index integrity checking to detect corruption and improve restoration confidence. Schedule checks rather than waiting for an emergency to discover that the repository cannot be read.
Integrity checks consume time and I/O, so schedule them away from the busiest production windows. The inconvenience is small compared with finding corruption during the only restore that matters.
Interrupted tasks and overlapping schedules need attention
Synology notes that only one backup task for a source can run at a time and simultaneous jobs can queue. Backup and version deletion for the same task also do not run concurrently.
On a busy NAS, a schedule that looks reasonable on paper may create long queues after a network outage or slow initial run. Review task duration and move heavy jobs so backup, scrubbing, snapshots and media processing do not all compete for disks at the same hour.
Large first backups deserve a seeding plan
Synology documents an export workflow for large cloud backups where the initial version can be written to external storage and delivered to a provider when supported. Even without formal seeding, the first backup deserves separate planning because it may run much longer than incremental updates.
Estimate upload time from usable upstream bandwidth, not your ISP’s download headline. If the first copy would require many days, consider local or remote-NAS alternatives, provider seeding options or starting with the most critical folders.
Test file-level and whole-system recovery separately
A file restore proves that the repository can return individual data, but it does not necessarily prove that an entire NAS rebuild procedure is documented. If you depend on system backup, understand the supported restore path for the target model and DSM environment.
At minimum, restore a folder to an alternate location, open several files and record the steps. For business systems, run a periodic recovery exercise that another administrator can follow without relying on your memory.
Monitor storage growth and abnormal changes
Hyper Backup can track backup statistics and alert on abnormal storage usage. Sudden growth may indicate legitimate new data, but it can also expose a runaway application, unexpected duplicate set or ransomware-style file churn.
Treat backup monitoring as part of NAS monitoring. A repository that silently fills to capacity is not healthy merely because last night’s task succeeded before the final few gigabytes were consumed.
Use Hyper Backup as one layer in a broader resilience plan
Hyper Backup complements snapshots, RAID, endpoint backup and application-specific exports; it does not replace all of them. RAID keeps the NAS available through certain drive failures, snapshots give fast local rollback, and Hyper Backup creates separate recoverable copies.
The architecture is strongest when each layer addresses a different failure. If every protection mechanism depends on the same NAS chassis and the same administrator account, the system still has a large shared failure domain.
Questions people ask
Synology Hyper Backup questions
What can Hyper Backup back up?
Depending on the task, DSM 7.4 supports folders, files, packages, system configurations, LUNs and entire-system data.
Where can Hyper Backup send data?
Destinations include local storage, external devices, remote Synology or rsync servers and several public-cloud or S3-compatible services, with some differences for entire-system backup.
What is an .hbk file?
It is Synology’s backup repository format for multi-version backups and is intended to be read through Hyper Backup, Hyper Backup Explorer or Hyper Backup Vault.
How many versions can Hyper Backup keep?
Synology documents support for up to 65,535 versions with rotation policies, although a sensible retention plan should be based on recovery needs and storage capacity.
Does Hyper Backup encrypt backups?
It supports client-side encryption and transfer encryption. Keep recovery credentials somewhere independent from the NAS.
How often should I run integrity checks?
Use a regular schedule appropriate to the importance and size of the repository, and avoid overlapping them with the busiest NAS workloads.
Can two Hyper Backup tasks run at once?
Tasks using the same source can queue, and Synology documents limitations around simultaneous backup and version-deletion operations.
Should I back up to USB or cloud?
They solve different risks. USB can restore quickly; offsite cloud or remote NAS protects against loss of the building. Many strong designs use both.
Is RAID enough without Hyper Backup?
No. RAID mainly improves availability during certain drive failures and does not protect against accidental deletion, ransomware, theft or total NAS loss.
How do I know my backup works?
Perform restores. A successful status message is useful, but opening restored files and documenting recovery steps provides much stronger evidence.
Official references and methodology
Verify the exact service, data path and recovery plan
This guide uses Synology DSM 7.4 Hyper Backup specifications and task documentation and evaluates the product from a recovery perspective. It treats local copies, offsite copies, encryption, retention, integrity checking and restoration testing as distinct design choices instead of presenting one nightly task as a universal backup plan.
- Hyper Backup DSM 7.4 specifications
- Hyper Backup backup-task documentation
- Synology folders and packages backup guide
- Synology 3-2-1 guidance for Active Backup data
As an Amazon Associate, Cloudzat may earn from qualifying purchases. Prices, NAS models, DSM behavior, application versions and service documentation can change. Verify the exact Synology model and the current Synology, Immich, Backblaze, Google or Tailscale documentation before changing a production photo, backup or remote-access workflow.