UK’s trusted IT infrastructure partner since 2003
Servnet
ConfiguratorGet in Touch

RAID-TEC calculator

NetApp triple parity (triple erasure coding) — three drives of protection on WAFL. Set your drives below for live usable capacity, fault tolerance, IOPS, rebuild time and URE risk.

DataDistributed parity

1 · Choose a RAID level

Stripe & mirror
Single parity
Dual / triple parity
Nested
ZFS RAID-Z

NetApp triple parity (triple erasure coding) on WAFL.

2 · Configure drives

3 · Drive class

3.5" nearline SAS/SATA capacity HDD — indicative figures.

Advanced — read/write mix, URE rate
RAID-TEC · 14 × 16 TB
176 TB usable
of 224 TB raw · 78.57% efficiency
Fault tolerance3 drives
Write penalty×2
IOPS estR ≈2K · W ≈840 · mix ≈1K
Throughput estR ≈3K · W ≈3K MB/s
Rebuild / drive est≈ 55.6 h
URE on rebuild risk81.0%

With redundancy still remaining during a single-drive rebuild, a URE here is reconstructed (recoverable) — not data loss. Data loss requires a concurrent second failure. Figure shown is the chance of encountering a URE.

Capacity distribution78.57% usableUsable: 176 TB176Parity: 48 TB48Usable · 176 TBParity · 48 TB
Fault tolerance — parity per arrayDDDDDDDDDDDPPPDataParity3 drives
IOPS — back-end budget vs deliveredBack-end budget2KFront-end read2KFront-end write840Write penalty ×2 — each host write costs 2 back-end I/Os
URE risk during a single-drive rebuild0%25%50%75%100%81%data read during rebuild (358.4 TB →)URE 1 in 10^15

Calculated for planning. We don't publish prices — a 24-year UK reseller, Servnet confirms the exact drives, array and pricing on quote. IOPS, throughput & rebuild are indicative estimates.

Overview

What RAID-TEC is

RAID-TEC is NetApp’s triple-parity scheme (triple erasure coding): usable capacity is (n−3) × drive size and it survives any three drive failures. It is intended for large RAID groups of high-capacity drives, where long rebuild windows make a third parity worthwhile.

Like RAID-DP it runs on WAFL, so its write behaviour avoids the classic read-modify-write penalty. Triple parity lets you build wider RAID groups safely — keeping more capacity usable per group while retaining redundancy even mid-rebuild on drives that take a long time to reconstruct.

At a glance
Usable capacity(n − 3) × drive size
Minimum drives5
Fault tolerance3 drives
Write penaltyWAFL full-stripe (≈ not ×6)
Worked example
14 × 16 TB nearline HDD176 TB usable, survives 3

Fourteen 16 TB drives in RAID-TEC give 176 TB usable and tolerate any three failures — letting NetApp build wide, capacity-efficient groups on large drives while staying protected even during the long rebuilds those drives require.

Advantages

  • Survives any three drive failures
  • Enables wider, more efficient RAID groups on large drives
  • WAFL writes avoid the classic parity penalty
  • Two parities still protect data during a single-drive rebuild

Trade-offs

  • Three drives of capacity to parity
  • Vendor-specific (NetApp)
  • Only worthwhile on large drives / wide groups
  • Overkill for small groups

Best for

  • NetApp groups of large-capacity nearline drives
  • Wide RAID groups where rebuild windows are long
  • Maximum resilience on high-density NetApp shelves

Consider another level when

  • Small RAID groups (RAID-DP is enough)
  • Non-NetApp arrays (use RAID 6/60)
  • Latency-critical workloads
Level landscape — efficiency vs fault tolerance (typical)012325%50%75%100%drives survivedspace efficiency →RAID 0RAID 5RAID 50RAID-Z1RAID 6RAID 60RAID-Z2RAID-Z3RAID 10RAID 1

RAID-TEC — common questions

How is RAID-TEC usable capacity calculated?

Usable capacity is (number of drives − 3) × drive size, because three drives hold triple parity. Fourteen 16 TB drives give (14−3) × 16 = 176 TB usable.

When should I use RAID-TEC over RAID-DP?

On large RAID groups of high-capacity drives where a rebuild takes a long time. The third parity means two are still in reserve while one drive rebuilds, so a multi-failure event during the long window is survivable — and you can build wider groups safely.

Is RAID-TEC the same as RAIDZ3?

They are both triple-parity (survive three failures, (n−3) usable), but RAID-TEC is NetApp WAFL and RAIDZ3 is ZFS. The capacity maths is the same; the implementation, performance behaviour and overheads differ.