Redundancy depth

Synology SHR-1 vs SHR-2: One or Two Drive Redundancy?

SHR-1 and SHR-2 answer different risk questions. SHR-1 normally protects against one member-drive failure, while SHR-2 is designed to tolerate two drive failures and therefore consumes more raw capacity. The right choice depends less on fear and more on bay count, drive size, rebuild exposure, restore requirements and whether the NAS has another current copy of the data.

See live products Use the selector

Quick answer

Buy redundancy where the failure window justifies it

Four or more large drives, long rebuild times and business-critical availability can make SHR-2 attractive. Smaller home arrays with strong external backup may get more usable capacity from SHR-1 while still maintaining one-drive tolerance.

Live Amazon products

Hardware relevant to this technical workflow

This Sprint 9F catalogue is intentionally focused on current and previous Synology Plus systems. Storage-repair pages can also read compatible third-party NAS hard-drive data from Cloudzat Storage Price Intelligence in read-only mode. Product cards support the decision; they never override current Synology compatibility or model-specific repair rules.

Checking the dedicated Synology technical catalogue…

Technical decision

Two-drive tolerance is not two backups

SHR-2 reduces array failure risk during a second drive event; it still cannot recover deleted files, stolen hardware, corrupted credentials or a site disaster.

Interactive technical tool

SHR-1 vs SHR-2 Risk Planner

Use this as a planning aid. It identifies capacity, redundancy, deployment or repair constraints, but it does not replace the current Synology model manual, DSM documentation or upstream application release notes.

Technical safety checklist

Four checks before changing a production NAS

Protect data before maintenance

A healthy RAID state is not a backup. Confirm an independent restorable copy before repairs, DSM upgrades, RAID migration or major container changes.

Change one layer at a time

Storage, DSM, networking and application changes should be separated so an unexpected result can be traced to one action rather than several.

Record the exact state

Write down model, DSM build, pool type, drive serials, ports, mapped folders and current application versions before modifying a production NAS.

Verify the result

A repair or upgrade is complete only after storage health, services, backups and representative restores behave as expected.

Define the failure promise correctly

Define the failure promise correctly is central to SHR-1 and SHR-2 Redundancy: SHR-1 normally tolerates one member failure while SHR-2 is designed for two, and that difference determines both usable capacity and degraded-state exposure. For SHR-1 and SHR-2 Redundancy, record the dual-failure redundancy path baseline before action. When checking define the failure promise correctly, compare the dual-failure redundancy path result with that earlier dual-failure redundancy path baseline.

A tested backup protects the dual-failure redundancy path workflow during define the failure promise correctly. For SHR-1 and SHR-2 Redundancy, recovery of the dual-failure redundancy path state matters more than speed.

SHR-2 needs enough drives

For SHR-1 and SHR-2 Redundancy, shr-2 needs enough drives matters because two-drive redundancy requires a larger array, so it is not an option for every two-bay or three-bay configuration. For SHR-1 and SHR-2 Redundancy, record the dual-failure redundancy path baseline before action. When checking shr-2 needs enough drives, compare the dual-failure redundancy path result with that earlier dual-failure redundancy path baseline.

Document the dual-failure redundancy path decision around shr-2 needs enough drives. In SHR-1 and SHR-2 Redundancy, record why the dual-failure redundancy path state changed and what outcome the dual-failure redundancy path procedure expects.

Large disks lengthen the conversation

Inside SHR-1 and SHR-2 Redundancy, the practical constraint is this: as member capacity grows, rebuild windows and the amount of data read during repair become more important operational considerations. For SHR-1 and SHR-2 Redundancy, record the dual-failure redundancy path baseline before action. When checking large disks lengthen the conversation, compare the dual-failure redundancy path result with that earlier dual-failure redundancy path baseline.

Keep large disks lengthen the conversation separate from other dual-failure redundancy path changes. On SHR-1 and SHR-2 Redundancy, isolating the dual-failure redundancy path work makes a failure in the dual-failure redundancy path path easier to identify.

Usable capacity is the visible tradeoff

The SHR-1 and SHR-2 Redundancy reason to study usable capacity is the visible tradeoff is straightforward: the second parity-equivalent protection layer consumes space that SHR-1 could otherwise expose to applications. For SHR-1 and SHR-2 Redundancy, record the dual-failure redundancy path baseline before action. When checking usable capacity is the visible tradeoff, compare the dual-failure redundancy path result with that earlier dual-failure redundancy path baseline.

Before buying hardware for usable capacity is the visible tradeoff, decide whether the dual-failure redundancy path target is capacity, redundancy or availability; verify the resulting dual-failure redundancy path outcome directly.

Backups change the economics

SHR-1 and SHR-2 Redundancy planning can fail here because a fast, tested restore path can justify accepting SHR-1 on workloads where availability during a second drive failure is less critical. For SHR-1 and SHR-2 Redundancy, record the dual-failure redundancy path baseline before action. When checking backups change the economics, compare the dual-failure redundancy path result with that earlier dual-failure redundancy path baseline.

In SHR-1 and SHR-2 Redundancy, make the dual-failure redundancy path step reversible. Back up the dual-failure redundancy path state; change one variable for backups change the economics; verify the dual-failure redundancy path result before continuing.

Business uptime can favor SHR-2

A safer SHR-1 and SHR-2 Redundancy interpretation starts with one fact: when restoring many terabytes from offsite backup would cause unacceptable downtime, deeper local redundancy may be worth the capacity cost. For SHR-1 and SHR-2 Redundancy, record the dual-failure redundancy path baseline before action. When checking business uptime can favor shr-2, compare the dual-failure redundancy path result with that earlier dual-failure redundancy path baseline.

If a tutorial conflicts with the dual-failure redundancy path behavior on SHR-1 and SHR-2 Redundancy, stop at business uptime can favor shr-2; follow the model-specific Synology instructions for the dual-failure redundancy path condition.

Mixed capacities still follow redundancy geometry

Mixed capacities still follow redundancy geometry is central to SHR-1 and SHR-2 Redundancy: SHR flexibility does not mean every unmatched region becomes usable under SHR-2; enough drives must exist to protect each capacity region against two failures. For SHR-1 and SHR-2 Redundancy, record the dual-failure redundancy path baseline before action. When checking mixed capacities still follow redundancy geometry, compare the dual-failure redundancy path result with that earlier dual-failure redundancy path baseline.

A tested backup protects the dual-failure redundancy path workflow during mixed capacities still follow redundancy geometry. For SHR-1 and SHR-2 Redundancy, recovery of the dual-failure redundancy path state matters more than speed.

Migration paths should be checked early

For SHR-1 and SHR-2 Redundancy, migration paths should be checked early matters because Synology supports changing SHR-1 to SHR-2 only under specific drive-count and pool conditions, so owners should not treat conversion as frictionless. For SHR-1 and SHR-2 Redundancy, record the dual-failure redundancy path baseline before action. When checking migration paths should be checked early, compare the dual-failure redundancy path result with that earlier dual-failure redundancy path baseline.

Document the dual-failure redundancy path decision around migration paths should be checked early. In SHR-1 and SHR-2 Redundancy, record why the dual-failure redundancy path state changed and what outcome the dual-failure redundancy path procedure expects.

Rebuild order deserves discipline

Inside SHR-1 and SHR-2 Redundancy, the practical constraint is this: after a failure, restore redundancy before starting optional capacity upgrades, package migrations or unrelated maintenance. For SHR-1 and SHR-2 Redundancy, record the dual-failure redundancy path baseline before action. When checking rebuild order deserves discipline, compare the dual-failure redundancy path result with that earlier dual-failure redundancy path baseline.

Keep rebuild order deserves discipline separate from other dual-failure redundancy path changes. On SHR-1 and SHR-2 Redundancy, isolating the dual-failure redundancy path work makes a failure in the dual-failure redundancy path path easier to identify.

Drive age correlation matters

The SHR-1 and SHR-2 Redundancy reason to study drive age correlation matters is straightforward: arrays populated with same-age drives from the same batch may experience clustered wear, making monitoring and replacement planning relevant to the redundancy decision. For SHR-1 and SHR-2 Redundancy, record the dual-failure redundancy path baseline before action. When checking drive age correlation matters, compare the dual-failure redundancy path result with that earlier dual-failure redundancy path baseline.

Before buying hardware for drive age correlation matters, decide whether the dual-failure redundancy path target is capacity, redundancy or availability; verify the resulting dual-failure redundancy path outcome directly.

Hot spare is a different mechanism

SHR-1 and SHR-2 Redundancy planning can fail here because a spare can shorten time to automatic repair on supported layouts, but it does not add the same steady-state fault-tolerance level as SHR-2. For SHR-1 and SHR-2 Redundancy, record the dual-failure redundancy path baseline before action. When checking hot spare is a different mechanism, compare the dual-failure redundancy path result with that earlier dual-failure redundancy path baseline.

In SHR-1 and SHR-2 Redundancy, make the dual-failure redundancy path step reversible. Back up the dual-failure redundancy path state; change one variable for hot spare is a different mechanism; verify the dual-failure redundancy path result before continuing.

Availability and backup remain separate controls

A safer SHR-1 and SHR-2 Redundancy interpretation starts with one fact: SHR-2 is best viewed as an availability feature inside the NAS, while backup is the recovery control that survives the NAS or site. For SHR-1 and SHR-2 Redundancy, record the dual-failure redundancy path baseline before action. When checking availability and backup remain separate controls, compare the dual-failure redundancy path result with that earlier dual-failure redundancy path baseline.

If a tutorial conflicts with the dual-failure redundancy path behavior on SHR-1 and SHR-2 Redundancy, stop at availability and backup remain separate controls; follow the model-specific Synology instructions for the dual-failure redundancy path condition.

Questions people ask

SHR-1 and SHR-2 Redundancy: common questions

How many drives does SHR-2 require?

SHR-2 requires at least four drives and the exact migration rules can require four or five depending on the existing SHR-1 layout.

For SHR-1 and SHR-2 Redundancy, "How many drives does SHR-2 require?" depends on the dual-failure redundancy path: check the exact DSM build for the dual-failure redundancy path, the NAS model, and the current dual-failure redundancy path state.

Does SHR-2 survive two failed drives?

Its purpose is two-drive fault tolerance when the pool is healthy and correctly configured.

For SHR-1 and SHR-2 Redundancy, "Does SHR-2 survive two failed drives?" depends on the dual-failure redundancy path: check the exact DSM build for the dual-failure redundancy path, the NAS model, and the current dual-failure redundancy path state.

Is SHR-2 always safer?

It provides deeper local redundancy, but safety also depends on backups, restore testing, power protection and correct administration.

For SHR-1 and SHR-2 Redundancy, "Is SHR-2 always safer?" depends on the dual-failure redundancy path: check the exact DSM build for the dual-failure redundancy path, the NAS model, and the current dual-failure redundancy path state.

Is SHR-2 worth it with four drives?

It can be, but two-drive tolerance on a four-drive array has a large usable-capacity cost. Compare downtime risk with backup quality.

For SHR-1 and SHR-2 Redundancy, "Is SHR-2 worth it with four drives?" depends on the dual-failure redundancy path: check the exact DSM build for the dual-failure redundancy path, the NAS model, and the current dual-failure redundancy path state.

Can I convert SHR-1 to SHR-2?

Synology supports this only for eligible configurations. Check the current Change RAID Type interface before purchasing drives.

For SHR-1 and SHR-2 Redundancy, "Can I convert SHR-1 to SHR-2?" depends on the dual-failure redundancy path: check the exact DSM build for the dual-failure redundancy path, the NAS model, and the current dual-failure redundancy path state.

Does SHR-2 replace a hot spare?

No. SHR-2 changes the active redundancy level; a hot spare is an unused drive reserved to start repair automatically on supported pools.

For SHR-1 and SHR-2 Redundancy, "Does SHR-2 replace a hot spare?" depends on the dual-failure redundancy path: check the exact DSM build for the dual-failure redundancy path, the NAS model, and the current dual-failure redundancy path state.

Does SHR-2 rebuild faster?

Not inherently. Repair duration depends on drive size, health, workload and hardware.

For SHR-1 and SHR-2 Redundancy, "Does SHR-2 rebuild faster?" depends on the dual-failure redundancy path: check the exact DSM build for the dual-failure redundancy path, the NAS model, and the current dual-failure redundancy path state.

Can SHR-2 use mixed drive sizes?

Yes within SHR rules, but two-drive protection imposes stricter capacity geometry than SHR-1.

For SHR-1 and SHR-2 Redundancy, "Can SHR-2 use mixed drive sizes?" depends on the dual-failure redundancy path: check the exact DSM build for the dual-failure redundancy path, the NAS model, and the current dual-failure redundancy path state.

Which is better for eight bays?

Eight-bay systems make SHR-2 more economically practical because the second redundancy drive consumes a smaller share of total bay count.

For SHR-1 and SHR-2 Redundancy, "Which is better for eight bays?" depends on the dual-failure redundancy path: check the exact DSM build for the dual-failure redundancy path, the NAS model, and the current dual-failure redundancy path state.

Should media libraries use SHR-2?

Decide from recoverability and downtime tolerance. Replaceable media with strong backup may not need the same local redundancy as unique business data.

For SHR-1 and SHR-2 Redundancy, "Should media libraries use SHR-2?" depends on the dual-failure redundancy path: check the exact DSM build for the dual-failure redundancy path, the NAS model, and the current dual-failure redundancy path state.

Official references and methodology

Verify the exact model, DSM build and application state

This SHR-1 and SHR-2 Redundancy guide uses primary documentation for the dual-failure redundancy path. Cloudzat evaluates the dual-failure redundancy path capacity, redundancy, deployment and recovery layers separately. Interactive dual-failure redundancy path results support planning; final dual-failure redundancy path changes need exact model guidance and current upstream documentation.

As an Amazon Associate, Cloudzat may earn from qualifying purchases. Prices, NAS models, drive compatibility, DSM behavior and upstream application requirements can change. Verify the exact DiskStation model, current DSM documentation and application release notes before changing storage pools, replacing drives, exposing network services or upgrading production containers.