Short answer: Hyper Backup copies Synology NAS data to a compatible destination such as another NAS, external storage or supported cloud service. A useful task needs a destination separate from the source appliance, defined data scope, schedule, retention, encryption-key custody, alerts and a successful restore test. RAID and local snapshots do not replace that copy.
This is the design and setup guide. Part 2 covers verification and restoration. See business Synology solutions for the broader storage architecture.
Choose the data and destination before the wizard
Inventory shared folders, supported package data, present volume, change rate, retention and accepted RPO/RTO. Size the destination for the first copy and future versions. A permanently attached USB drive or folder on the same appliance may not provide enough separation against appliance loss, theft or compromised administration.
Compare a second NAS, compatible cloud storage and external media by capacity, bandwidth, recovery time, cost and access. Name the owner of destination credentials and encryption keys. Check actual model and DSM support for the intended task type before promising whole-system or package recovery.
Create the task and version policy
In Hyper Backup, create a Data backup task and select the correct destination type. Choose the shared folders and supported package data, then provide only the destination access needed. Schedule the first large transfer around business traffic; use bandwidth controls if appropriate. Set retention from the business requirement rather than accepting an arbitrary version count that may fill storage.
If client-side encryption is enabled, store the key and password through controlled handover outside the source NAS. Enable integrity checks and failure notifications where supported, with a named responder. Synology’s multiversion .hbk repository uses its own format and is accessed through Hyper Backup, Explorer or Vault, not as an ordinary folder of files.
Pilot, verify and hand over
Run a representative first backup and inspect logs, destination size, duration and completion status. Edit a test file, run another version and confirm the earlier version is selectable. Test destination access using the recovery account, not only the task creator. A green status is not acceptance: restore sample data and record the result.
Assign recurring checks for failed jobs, near-full capacity, old versions and key custody. If moving the source or destination, follow Synology’s relink workflow; renaming the .hbk repository folder can break relinking.
Frequently asked questions
How does Hyper Backup differ from RAID and snapshots?
RAID tolerates specified drive failures; snapshots retain points in time on supported storage; Hyper Backup creates a copy at another destination. Combine them according to risk.
Must encryption keys be retained?
Yes. Losing the key or password for an encrypted repository can prevent restoration. Use a controlled custody process.
Is a completed first job enough?
No. Select prior versions and restore representative files or folders against the agreed recovery objectives.
Technical sources
Synology Hyper Backup; Synology: create backup tasks. UI and support vary by DSM, model and destination.
