A 3-2-1 NAS Backup Plan: USB Drive, Second NAS and Cloud

Build a practical 3-2-1 NAS backup plan with rotating offline USB drives, a remote second NAS or cloud, secure retention, encryption and real restore tests.

Quick Summary (TL;DR):
The safest practical home-NASPriceAliExpress price backup strategy keeps at least three copies of important data across independent storage, with one copy off-site. Start with the live NASAliExpress price, add a versioned backup to a rotating USB HDD that you disconnect, then back up to a second NASAliExpress price in another location or an appropriate cloud storage service. If you use all three destinations—USB, second NAS and cloud—you have four copies including the original, which is even better when configured correctly. Our recommended starting point is a daily versioned remote/cloud job plus an A/B USB rotation, with separate credentials, encryption, retention and actual restore tests. RAID and one-way file sync do not replace independent backups. Do not spend money on a second NAS before deciding whether it protects you from the same fire, burglary or administrator compromise as the first.

3-2-1 NAS Backup Plan: What the Numbers Actually Mean

The traditional 3-2-1 rule means three copies including the live original, on at least two storage media or independently protected storage systems, with one copy kept away from the primary location. The practical aim is separation of failure domains: a broken NAS, accidental deletion, ransomware and a house fire should not all destroy your recovery options at once.

CopyExample destinationWhat it protects againstRemaining weakness
1: Live dataPrimary NAS (RAID/ZFS/SHR as appropriate)One drive failure may be tolerated by the arrayDeletion, ransomware, theft and site damage
2: Local recovery copyUSB HDD rotated and unpluggedFast restore; offline copy resists network-based deletionIf stored in the same house, fire or theft
3: Off-site recovery copyCloud backup or genuinely remote second NASBuilding-level disaster; travel/lost deviceCloud credentials, Internet access, provider and retention
Optional 4thSecond remote NAS plus cloudExtra independence and recovery routesExtra cost, monitoring and complexity

Two NAS boxes in the same rack are not an off-site design. Similarly, two datasets on separate volumes inside one enclosure are not two independent backup devices. The classic wording of “two media types” is useful, but independence, retention and recoverability matter more than buying different connector types merely to tick a box.

For the mechanics of A/B rotation, see our USB enclosure guide. For external-drive sizing, see Best External Hard Drives for NAS Backups.

Choose the Right Architecture Before Buying More Hardware

PlanComponentsWho it suitsImportant compromise
Essential 3-2-1Primary NAS + two alternating USB drives; store one at another addressFamilies with modest data volumes and occasional manual rotationOff-site freshness depends on how often you rotate
Low-maintenance 3-2-1Primary NAS + rotated USB + automatic versioned cloud backupMost homes and small home labsRecurring cloud charges and first-seed time
NAS-to-NAS 3-2-1Primary NAS + rotated USB + second NAS at another propertyLarge datasets with available second sitePower, network and security at both sites
Four-copy hybridPrimary NAS + offline USB + remote second NAS + cloudIrreplaceable or high-value dataHighest administrative and equipment cost

Recommended default: a versioned off-site cloud backup for the irreplaceable folders, plus one or two offline USB drives for a fast local restore. Expand to a remote second NAS once cloud volume, restore speed or recurring cost makes that investment worthwhile. The cheapest safe design is one that you can keep operating for years, not an elaborate plan abandoned after a month.

Start by Deciding What You Cannot Afford to Lose

Do not automatically send the entire NAS to every target. Classify data by value and the time required to recreate it. A downloaded media library may be replaceable; family photos, tax records, work projects, encryption keys and home automation configuration often are not.

DataExample backup priorityLocal copyOff-site copy
Family photos, original video and documentsCriticalEvery day or after changesDaily or as soon as practical
Work files, source code, Home Assistant backupsCritical/highDailyDaily
PC images and app configurationsMedium/highWeekly or after changesWeekly/after major changes
Large media library with re-download sourcesVariableWeekly or monthlySelective or none, by choice
Caches, transcodes, scratch filesLowNormally excludeExclude

Write down a recovery point objective (RPO): how much recent work you are prepared to lose. A job that runs weekly creates up to a week of exposure. Then set a recovery time objective (RTO): how quickly you need those files back. A slow cloud-only 15TB restore may be acceptable for archived video, but not for a workstation needed tomorrow morning.

Worked Example: A Family NAS with 8TB of Used Space

Imagine a four-bay NAS holding 8TB of actual data: 2TB of irreplaceable photos and documents, 1TB of PC and application backups and 5TB of largely replaceable media. The example below is an illustrative plan, not a benchmark or a claim that every backup format will have the same size.

PRIMARY NAS — 8 TB of used data
  ├─ USB BACKUP A — selected 8 TB, versioned, disconnected
  ├─ USB BACKUP B — selected 8 TB, versioned, off-site rotation
  └─ CLOUD — critical 3 TB, versioned + encrypted

OPTIONAL: second NAS at another address
  └─ critical folders or full 8 TB, scheduled

USB A/B: weekly rotation
Cloud: every night
Restore test: monthly sample; quarterly simulated failure

This configuration keeps a current cloud copy of the hardest-to-replace 3TB and rotating local copies of the larger dataset. It uses three or four backup copies plus original data depending on which USB disks count at a given moment, exceeding the three-copy minimum. Keeping an additional off-site USB copy is valuable, but a drive that is only transported quarterly leaves an old recovery point for a building disaster.

Backup Target 1: A Rotating USB Hard Drive

USB is the simplest way to create an offline NAS copy. A large 3.5-inch desktop HDD or an independently selected SATA drive in a USB enclosure is usually sufficient. For a reliable rotation, buy two appropriately sized drives, label them NAS-BACKUP-A and NAS-BACKUP-B, and test the backup job with each drive independently.

  • Connect Drive A. Confirm its volume identity before starting; do not guess based on a drive-letter or changing mount path.
  • Run a versioned or incrementally retained backup of selected NAS folders, system/app settings and other required data.
  • Review the job report; verify the expected new snapshot and sample files.
  • Use the NAS interface to unmount/eject, wait for disk activity to stop, then power down/disconnect.
  • Store Drive A safely, ideally outside the home. Connect Drive B on the next rotation and repeat.

If the NAS backup tool cannot use alternating destinations without risk of overwriting or invalidating a backup history, create separate job configurations rather than forcing both disks into a single uncertain workflow. QNAP documents a specific HBS 3 same-label rotation approach, but it is a vendor procedure, not universal behaviour for all NAS systems; see the original documentation below.

Choose the drive from selected backed-up data plus retention and growth, not the raw sum of installed disks. For a 6TB dataset with versions and expected growth, an 8TB target may be tight; model historical changes before deciding whether 10TB, 12TB or more is appropriate.

Backup Target 2: A Second NAS — Preferably at Another Address

A second NAS makes sense when you have several terabytes to protect and want scheduled replication or a faster restore than your Internet download allows. It can be an older two-bay NAS, a compact new appliance, or a DIY server that reliably supports the chosen destination protocol.

  • Location: a family member’s house or another secure property gives meaningful site independence. A NAS beside the primary unit does not.
  • Disk space: provision for the selected datasets, their change rate, versions and expected growth, not just present-day file size.
  • Power: suitable UPS and safe shutdown to reduce corruption from local power events.
  • Network: reliable upload at the primary location and download at the destination, plus a private VPN or other strongly authenticated route.
  • Access: a dedicated backup account with only required destination privileges; protect the management UI separately.
  • Recoverability: document whether the destination holds ordinary files or a proprietary backup repository that requires a tool to extract.

For cross-brand configuration, see How to Back Up One NAS to Another: Synology, UGREEN and QNAP. That article covers the detailed destination service and restore setup; this guide concentrates on designing the whole protection plan.

Backup Target 3: Cloud Storage — What to Look For

Cloud storage provides geographic separation without a second building or appliance. Synology C2 Storage, S3-compatible object storage such as Backblaze B2, and other destinations supported by your NAS software are possible choices. However, a compatible storage API alone does not guarantee that every backup app supports encryption, retention or immutability in the same way.

  • Backup application support: confirm your NAS model/firmware and selected app support the exact cloud service or S3 endpoint.
  • True backup rather than plain sync: multiple historical recovery points must survive source deletion, corruption or encryption.
  • Client-side encryption: preferable for sensitive household documents when supported, with independently stored recovery key.
  • Versioning and immutable retention: assess application-level backup versions and provider-side Object Lock separately.
  • Fees: storage, API transactions, outgoing downloads, minimum-duration charges and any support or subscription requirements.
  • Restore path: test whether you can download and open the data on a replacement NAS or normal computer without the old NAS.

Backblaze documents B2 Object Lock, which can prevent protected object versions from being deleted before their retention date. Enabling an Object Lock-capable bucket is not by itself proof that your uploaded objects are locked: confirm default/per-object retention, permissions and a real non-destructive restore test. Locking objects can also increase stored data and cost when old versions cannot yet be deleted.

Do not confuse ordinary personal-computer backup subscriptions with a supported NAS cloud destination. Backblaze Personal Backup and Backblaze B2 are different products with different use cases and billing. No affiliate commission should be assumed merely because a cloud provider has a partner programme.

Local Backup Setup on Synology DSM: Hyper Backup

Synology Hyper Backup supports external devices, compatible remote destinations and various cloud services for folders and packages, with versioning, encryption and integrity checks. Its full-system backup has a narrower destination list than its folders-and-packages backup, so choose the correct job type before planning the storage target.

  • Open Hyper Backup and create a backup task appropriate to your data: folders/packages for a USB or supported cloud target.
  • Select Local folder & USB or the appropriate supported destination in the wizard; select the actual USB volume when using local external media.
  • Choose the folders and applications to protect. Include package data only where the selected backup mode supports it.
  • Enable a realistic schedule, notifications, encryption and backup rotation/version retention as appropriate. Store the encryption key outside the NAS.
  • Run the first backup, use the integrity-check facility, then restore a test folder to a separate location.
  • Safely eject the USB drive before unplugging it. Use another task for the cloud or remote NAS and check its restore path independently.

Hyper Backup’s multi-version repositories commonly use the .hbk format and need Hyper Backup or Hyper Backup Explorer for convenient recovery. That is not the same as a directly browsable copy of your files. Keep a tested recovery tool and account credentials accessible if the NAS is destroyed.

Local Backup Setup on QNAP: Hybrid Backup Sync 3

On QNAP QTS or QuTS hero, HBS 3 supports local, external, remote and cloud backup jobs. QNAP’s external backup instructions use Local NAS as the destination category even when the selected destination folder is on a plugged-in USB disk—a slightly unintuitive menu detail.

  • Connect the target HDD and verify that the NAS sees it as external storage with correct filesystem permissions.
  • In HBS 3 → Backup & Restore, create a new backup job and select the protected source folders.
  • Select Local NAS, then choose a destination directory on the external USB device.
  • Configure schedule, job rules and retention/version management. Confirm how deletions are handled.
  • Run the job and inspect reports. If QuDedup is enabled, know that backup contents may be stored as .qdff and require HBS or the QuDedup Extract Tool for recovery.
  • Set up remote/cloud backup as a separate job, schedule data-integrity checks and confirm they do not unexpectedly download huge amounts of data.

For a two-drive rotation, QNAP provides a dedicated HBS 3 procedure that prepares two external drives with the same label and expected folder path. Verify it applies to your firmware and use a genuine restore test before making it your only independent backup.

Local Backup Setup on UGREEN NASync: UGOS Pro

UGREEN UGOS Pro has a Sync & Backup app. Its support documentation describes external USB backup using Backup & Restore → Backup Between Storage Pools with the mounted USB volume as destination. The same documentation distinguishes backup modes from a mirror backup, which can propagate source deletion.

  • Mount and identify the external USB backup drive in UGOS Pro.
  • Open Sync & Backup → Backup & Restore; add a new task and choose Backup Between Storage Pools for a locally attached USB drive when your version offers that route.
  • Select the protected internal folders and the external target directory.
  • Prefer a backup mode with retained versions over a deletion-mirroring mode when accidental deletion and ransomware are key threats.
  • Choose an off-peak schedule, complete the first job and inspect the execution history.
  • For another NAS, UGREEN documents Back up this UGREEN NAS to an rsync or WebDAV server in current UGOS Pro versions; enable and secure the receiving service on the destination.

The above paths are based on the linked manufacturer guides and may vary with UGOS Pro updates. Do not assume the configuration-backup-to-UGREEN-account feature protects your file dataset; system-configuration backup and whole-NAS data backup are different things. For third-party cloud backup, verify the actual supported app/container and recovery workflow rather than assuming an S3 icon exists in every firmware build.

Backup Is Not the Same as Sync, Replication or RAID

MethodWhat happens after an accidental delete?Does it independently satisfy 3-2-1?
RAID 1/5/6, SHR or ZFS redundancyDeletion affects the live array; redundancy does not restore itNo
Two-way file syncDeletion may propagate to the other copyNo, not without durable version history and isolation
One-way mirrorDestination may delete a file to match the sourceNo, unless separately versioned and protected
Versioned backupOlder file versions may remain until retention expiresA valid copy if actually independent and restorable
Offline USB backupDetached disk cannot be remotely modifiedUseful independent copy; still consider off-site location
Immutable cloud backupLocked objects resist deletion within defined retentionStrong off-site copy if application and retention work as tested

Snapshots on the primary NAS are useful for quick rollback, but snapshots stored on the same device can disappear with an enclosure disaster or privileged compromise. Snapshots complement off-site and offline backups rather than replacing them.

Set Version Retention Before Your First Big Backup

A single copy of today’s data is a poor defence against ransomware that started encrypting files last week. Version retention should cover the time between a problem occurring and somebody noticing it. For families and home labs, a simple starting design could be daily points for a short window, weekly points for a few months and monthly archive points for longer periods—subject to capacity and tool support.

Backup destinationExample starting scheduleExample retention approachReview point
Cloud for critical filesNightlySeveral weeks daily + monthly historyMonitor growth and immutable retention expiry
Remote NASNightly or several times a weekVersioned backups with periodic monthly copiesValidate destination and credentials
USB A/BWeekly each rotation / after major changesTwo physically independent jobs or archivesKeep at least one detached
NAS configuration + app exportsAfter settings/major changesA few labelled recent working copiesConfirm restore dependencies

These are design examples, not universal recommended values. Retention based on calendar time can be invalid if a job fails silently. Set alerts for missed jobs and for a backup repository approaching capacity. Avoid “delete everything except the latest copy” even when storage gets tight.

How Much Capacity Do You Actually Need?

First measure protected data, then its monthly change rate and likely growth. A versioned backup is not the same size as a full copy multiplied by the number of versions: deduplication, compression, changed-block tracking and media file characteristics all matter. But neither should you assume deduplication will rescue an undersized disk.

EXAMPLE INPUTS (illustrative)
Selected dataset now:       6 TB
Expected annual growth:     1 TB
Changed/deleted data:       measure over 30–90 days
Historical retention:      weekly + monthly
Target free space:         include working headroom

Choose a target AFTER examining the backup tool estimate.
Do not assume a 6 TB USB disk will hold 6 TB of source data
plus versions, filesystem overhead and future growth.

File-system-reported “TB” versus “TiB” can confuse shopping comparisons, too: drive makers use decimal terabytes, while operating systems may report binary tebibytes. See 8TB vs 12TB vs 16TB vs 20TB NAS Drives: Cost per Usable Terabyte for drive-cost planning.

Upload Speed Can Make or Break the Cloud Plan

An initial multi-terabyte cloud backup may take days or weeks on a residential connection. As a theoretical minimum, 3TB over a constant 20Mb/s upload takes about 14 days before protocol overhead, throttling, daily usage or retransmissions. At 100Mb/s it still takes nearly three days. Incremental daily uploads are usually much smaller, but only if your changed-data rate fits within your upstream bandwidth.

Rough transfer time (seconds) = data bytes × 8 / available bits per second

3 TB decimal × 8 / 20 Mb/s ≈ 1,200,000 seconds
≈ 13.9 days at 100% sustained link utilisation

Actual transfer will often be slower.

Test actual sustained upload from your NAS to the selected cloud destination. Plan the first seed over a holiday or quiet period, and check whether your provider and backup tool offer supported physical-seed/import options. Never change DNS or expose a management port to the public Internet simply to make the backup faster.

Cloud Storage Costs: Estimate More Than £ per TB

A sensible ownership calculation covers the monthly stored logical/physical backup size, the number of retained versions, writes and API transactions, retrieval/download charges, early-delete or minimum-duration rules where applicable, and expected data growth. Currency, VAT and geography also matter. Prices and promotional tariffs change, so the example below deliberately avoids pretending a current provider tariff is permanent.

Annual cloud cost estimate =
  12 × monthly storage charge for retained backup footprint
+ expected transaction/API fees
+ likely restore/egress fees
+ optional backup software licence

Second-NAS ownership estimate =
  enclosure + HDDs/SSDs + UPS + networking
+ 24/7 power + replacement disks + admin time
+ off-site Internet service where needed

If you back up 3TB of irreplaceable data instead of all 15TB on the NAS, the ongoing bill and first-upload time may become far more manageable. On the other hand, a remote second NAS provides no magic savings if you have to purchase and power an entirely new appliance solely to keep one more copy.

Security: Keep Backup Credentials Separate

A backup is not independent if the same compromised account can destroy the primary files, USB repository, remote NAS and cloud object versions. Use dedicated service accounts, minimum permissions and separate multifactor authentication for cloud administration where available.

  • Store encryption passwords and recovery keys in a password manager with an independent emergency recovery path; an encrypted backup without its key is effectively lost.
  • Keep the remote NAS management interface off the public Internet. Prefer a site-to-site or trusted mesh VPN with firewall restrictions over directly forwarding administrative and rsync ports.
  • Restrict backup destinations so daily jobs can write what they need without broad administrator or delete permissions. Confirm the application remains compatible with these restrictions.
  • Enable retention protection or Object Lock where supported, and separately test that the lock applies to actual object versions rather than just the bucket setting.
  • Keep NAS firmware and backup apps updated, monitor authentication attempts and ensure your cloud account recovery does not depend solely on files stored on the failed NAS.

An unplugged USB HDD is one of the few defences that does not depend on perfect software permissions. That is why CISA recommends offline encrypted backups and regular integrity/recovery testing as part of ransomware resilience.

A Monthly Restore Test That Takes Minutes, Not a Full Disaster

A green “backup succeeded” notification only proves that a task reported success. It does not prove that the correct folders were included, encryption keys work or a clean replacement device can read the repository. Schedule a small, repeatable recovery exercise.

  • Choose one photo, one PDF, a directory tree and one application/configuration export. Record their expected names and approximate sizes.
  • Restore them from the USB backup into a temporary folder that is not the live source. Open the files.
  • Repeat from the off-site target without using a cached local copy. For cloud repositories, confirm a genuine remote read occurs.
  • Restore an older version of a deliberately modified test file to prove version retention works.
  • Verify access to the recovery key, account MFA/recovery codes, app installer and documented password manager emergency process.
  • Record the date, copy tested, elapsed time, result and any missing files. Correct errors immediately.

Quarterly or after a major change, perform a broader restore test into a spare NAS, VM or computer. A disaster recovery plan should include what to do when the original NAS, its configuration and all locally stored credentials are unavailable.

Disaster Recovery: Which Copy Should You Restore First?

FailureFirst recovery choiceWhy
One deleted documentVersioned local or cloud backupFastest targeted recovery
One NAS HDDPrice failed, array healthyRepair/rebuild array, verify backups firstDo not needlessly restore all data; rebuilding carries risk
Primary NAS chassis/electronics deadOffline USB into supported recovery tool or replacement NASUsually fastest for many TB
Ransomware reached live NASConfirmed clean immutable or detached copyAvoid restoring contaminated/encrypted versions
Fire, theft or flood at primary homeOff-site cloud or remote NASSame-site USB/second NAS may also be gone
Internet outageDisconnected local USB, if safeCloud-only restores unavailable during outage

When rebuilding after malware, isolate the compromised NAS, secure credentials and investigate how the attack entered before reconnecting backup targets. Restoring from a dated backup onto an insecure, still-compromised system can immediately re-infect it.

Common 3-2-1 Backup Mistakes

  • Counting RAID as backup: two mirrored HDDs do not preserve yesterday’s deleted photograph.
  • Leaving the USB copy attached all year: it remains vulnerable to malware, power damage and administrator mistakes.
  • Putting both NAS devices in the same room: replication does not solve physical-site disasters.
  • Using sync with deletion propagation: a mirrored copy may faithfully erase files that you wanted to recover.
  • Never testing recovery: proprietary repositories, missing keys and wrong folder selection are discovered too late.
  • Buying too little capacity: version pruning can silently reduce recovery options.
  • Giving all destinations the same admin password: one compromised account can expose all copies.
  • Forgetting apps and configurations: files alone may not rebuild containers, databases, Home Assistant, NAS users or network settings.

What Hardware Is Worth Buying First?

Make the first purchase that closes the largest recovery gap. For a family with no independent backup, two suitable external drives are often more useful than a premium six-bay NAS. If you already have offline disks but everything is stored at home, the next euro or pound may be better spent on an off-site cloud tier or keeping one drive at another address.

PriorityBuy only if neededDecision check
1Sufficient external HDD capacity / second rotation diskWill a complete restore fit with headroom and versions?
2Reliable USB SATA enclosure or powered external HDDDoes the exact NAS recognise and safely eject it?
3Cloud storage plan for irreplaceable foldersCan you restore it, and is long-term cost acceptable?
4Remote second NAS + compatible HDDsWill it sit at a different site and be maintained?
5UPS for primary/secondary siteDo protected backup jobs need graceful shutdown?

Browse our external HDD guide and our USB enclosure comparison before shopping. For readers assessing a second NAS, Best 2-Bay NAS for Home Backups explains the smaller-appliance route. No affiliate link is inserted here until its region, product and programme eligibility are verified.

A First-Weekend 3-2-1 Setup Checklist

  • Saturday morning: inventory important data and record RPO/RTO for family photos, documents and applications.
  • Saturday afternoon: connect a known-compatible USB drive, create the first versioned backup job and finish the baseline copy.
  • Saturday evening: restore example documents and photograph files; label, eject and disconnect the disk.
  • Sunday morning: configure an off-site cloud job for the critical folders, or a second NAS on a protected remote connection.
  • Sunday afternoon: enable notifications, record encryption recovery procedures, set retention and run a small off-site restore test.
  • Following week: prepare the second rotating USB disk; decide exactly where the disconnected drive will live.
  • Every month: review failed jobs, storage consumption and one restored old file.

The entire baseline copy of many terabytes may not finish over one weekend; that is normal. What matters is verifying each destination before you label the system “protected”.

Frequently Asked Questions

Do I need both a second NAS and cloud storage?

No. For basic 3-2-1, a primary NAS, an independent local backup and one off-site backup is enough in principle. The off-site copy can be either a remote NAS or cloud. Having both is an extra copy and extra complexity, not a requirement.

Does a USB disk left plugged into the NAS count as a backup?

Yes, if it contains restorable independent backup data, but it does not count as an offline backup while attached. A permanently connected target is more exposed to ransomware and shared power/site failures.

Is Btrfs or ZFS snapshotting enough?

No. Snapshots provide valuable fast rollback but are often stored in the same appliance or storage pool. Export backup versions to a separate target and maintain an off-site copy.

Can I restore Synology Hyper Backup or QNAP HBS data on a computer?

Often, with the correct vendor tool and supported backup format. Synology documents Hyper Backup Explorer for .hbk; QNAP documents the QuDedup Extract Tool for applicable .qdff repositories. Download the tool and test it while the NAS is healthy.

What is a good cloud backup frequency?

Choose it from your RPO and actual upload bandwidth. Nightly is a practical starting point for valuable family data. Workflows where hours of lost work are unacceptable may require more frequent jobs and tighter monitoring.

Is a second NAS over the Internet secure?

It can be, but not automatically. Restrict connections, use a private VPN where possible, dedicate low-privilege accounts, encrypt transport and monitor the receiving NAS. Never assume exposing an rsync or NAS administration port directly is safe.

What if the cloud provider is unavailable when disaster strikes?

That is a reason to keep a second local recovery route, such as a disconnected USB HDD or remote NAS. Availability and recoverability are different problems; the cloud copy provides geographical separation while local media may provide a quicker full restore.

The Bottom Line: Build Three Recoverable Copies, Then Prove It

The best 3-2-1 home-NAS backup plan is not the one with the most drives. It is the one where copies fail independently, versions survive accidental deletion, at least one recovery path is off-site and restores are regularly tested. Start with the original NAS, a removable A/B USB rotation and a scheduled remote NAS or cloud backup for your important files.

If you add both a remote second NAS and cloud, treat the result as a carefully managed fourth-copy architecture. It provides more choices after a failure, but only if the additional destinations have separate security, valid retention, sufficient capacity and a known restore procedure.

Continue the NAS Backup Series

Official Documentation and Further Reading

CONTINUE EXPLORING / NAS & HOME SERVERS

Read next

Practical guides related to this article.

Explore the topic →
HARDWARE DECISION GUIDEPlanning your next NAS upgrade?

Compare hardware, storage and software before buying.

Compare options →