Choose this when a direct-attached backup plus a genuinely independent off-site/cloud copy already protects the important devices, restores are tested, and shared network storage would add little day-to-day value.
HOME STORAGE · BACKUP · OWNERSHIP
A NAS can be a useful backup target. It is not automatically a complete backup plan.
Start with what must survive: the original data, at least one independent backup copy, the failure or loss events you care about, and a restore path you have actually tested. Only then compare bays, processors, apps, remote access or media features.
DECIDE THE DATA PLAN FIRST
Four bounded paths
The right storage product depends on the copies you already have and the failures you need to survive. Do not buy a multi-bay NAS merely because RAID sounds like backup.
Choose a basic network or directly attached target when the main gap is an automatic local second copy. Verify the backup software, filesystem/media support and restore workflow instead of assuming every storage box protects every endpoint.
Choose this when several household devices need a central backup target, shared files, snapshots/versioning or controlled expansion. Treat drive redundancy as availability/fault-tolerance evidence, not as the independent off-site copy.
Stop product comparison if the plan still has one physical location, one administrator account, no tested restore, unknown remote-access exposure or no independent copy that survives deletion, theft, fire or a compromised online system.
THE MOST IMPORTANT DISTINCTION
Redundancy, snapshots and backup solve different problems.
RAID/SHR is not the backup copy
Synology explicitly states that RAID, including SHR, is not a backup solution. Redundancy can keep some storage pools available through supported drive-failure scenarios, but the same enclosure, administrator, deletion event or site disaster can still affect the data. Verify the exact NAS model and supported RAID/SHR choices before using any capacity calculator.
Versioning can help—but keep an independent copy
Snapshots or versioned backups can make earlier states easier to recover when the exact model/filesystem/software supports them. They are one layer, not a reason to abandon an off-site or otherwise independently protected copy. CISA recommends offline encrypted backups and regular testing because accessible backups can also be targeted during ransomware incidents.
A successful job is not a successful restore
A backup dashboard saying “completed” is evidence that a task ran, not proof that the files you care about are usable. Include periodic test restores in the ownership routine and record what was restored, from which copy, on which software version and how long the manual process took.
EIGHT-LAYER OWNERSHIP CHECK
Research the whole backup path, not just the enclosure.
| Layer | What to verify | Why it matters |
|---|---|---|
| Data role | Is the NAS the original file location, a backup target, a replica, or more than one role? | If the only copy lives on the NAS, calling the NAS “the backup” hides the missing independent copy. |
| Bays + exact media support | Bay count, supported drive types/capacities, vendor compatibility list, filesystem and any model-specific RAID/SHR limits. | Usable capacity and expansion paths depend on the exact disks, array layout and model—not just the number printed on the drive labels. |
| Endpoint backup | Exact Windows, macOS, phone/tablet or other backup method; agent/app requirement; exclusions; encryption; retention and restore method. | “Works with Mac/PC” is too broad. Verify the current application and OS workflow you will actually use. |
| Snapshots + versions | Which volumes/folders can be snapshotted or versioned, retention behavior, and what restores are possible from that history. | Snapshots can reduce recovery friction, but support and isolation differ by model, filesystem and software version. |
| Independent/off-site copy | External drive, second site/NAS or supported cloud/object target; encryption/key ownership; whether the copy is continuously reachable. | A second location or appropriately isolated copy addresses failures that the same enclosure/site cannot. |
| Network + remote access | Ethernet speed, local-only option, remote-access method, exposed services, MFA/account controls, update policy and whether a vendor relay/cloud account is required. | Remote access changes the threat model. Do not expose management or storage services merely because the setup wizard offers it. |
| Power + shutdown | UPS compatibility, graceful-shutdown behavior and startup/recovery expectations for the exact NAS and UPS path. | Power-loss handling is part of storage ownership; it should be documented rather than inferred from the presence of a USB port. |
| Restore + lifecycle | Test restore, drive replacement, pool expansion/migration, OS/app update policy, export path and what happens if the enclosure itself fails. | A long-lived household archive needs an exit/recovery path, not just an easy first-day setup. |
3–5 CANDIDATE WORKSHEET
Eliminate candidates with unresolved protection gaps before comparing features.
For each candidate, save the exact product page, compatibility list, backup documentation, restore instructions and support/manual links. Preserve the model, operating-system/software version, market and verification date because backup features can change across hardware and releases.
| Evidence field | Candidate A | Candidate B | Candidate C | Candidate D / E |
|---|---|---|---|---|
| Exact NAS / appliance model | — | — | — | — |
| Bays + supported media list verified | Yes / No / unresolved | Yes / No / unresolved | Yes / No / unresolved | Yes / No / unresolved |
| Planned redundancy + usable-capacity basis | — | — | — | — |
| Windows/macOS/mobile backup path evidenced | — | — | — | — |
| Snapshot/versioning evidence | — | — | — | — |
| Independent/off-site copy target | — | — | — | — |
| Remote-access / account exposure understood | Yes / No / unresolved | Yes / No / unresolved | Yes / No / unresolved | Yes / No / unresolved |
| UPS + graceful shutdown evidenced | — | — | — | — |
| Test-restore method documented | — | — | — | — |
| Migration / enclosure-failure exit path | — | — | — | — |
| Official manual/support/backup evidence | — | — | — | — |
| All must-haves evidenced? | Yes / No / unresolved | Yes / No / unresolved | Yes / No / unresolved | Yes / No / unresolved |
SECURITY + OWNERSHIP BOUNDARIES
No storage layout guarantees recovery.
Lohabook does not claim that RAID, snapshots, an “immutable” feature, cloud replication or any particular NAS prevents ransomware or guarantees recovery. Keep administrator and remote-access exposure narrow, follow current vendor security/update guidance, protect recovery keys/credentials separately, maintain an independent copy appropriate to your risk model, and test restores. This page does not estimate retail price, drive reliability, throughput, household electricity cost, warranty coverage, local service availability or recovery time.
AUTHORITATIVE LINKS
Recheck exact model and software documentation before purchase
- CISA — #StopRansomware Guide
- Synology — What is Synology Hybrid RAID (SHR)?
- Synology — Hyper Backup
- QNAP — Backup and restoration
Backup software, supported drives, cloud targets, snapshot capabilities and remote-access options can change across hardware and software releases. Preserve exact model/version/source/verification context in your research notes.