Tool AT-W19REV. 2026-A

RAID calculator for NAS: how much space is left, and what does the backup need?

In RAID 5, usable capacity is the sum of all drives minus one; in RAID 6, minus two; and in RAID 1, only one drive. Four 4 TB drives therefore give 12 TB in RAID 5; Windows and the NAS show about 10.9 TB of that, because they calculate in binary. The backup needs a target of its own, because RAID is not a backup. The RAID calculator gives you both, plus fault tolerance, rebuild time and transfer time.

  • free
  • no sign-up
  • runs in your browser

Enter your drives, read off capacity and backup needs

Calculator · RAID capacity and backup needs

The calculator gives the capacity after RAID, before the file system and system take their share. SHR and RAIDZ are approximations; what your NAS shows after setup is what counts.

Step 1Which drives are in the NAS?

Size in TB, as printed on the box. Different sizes each get a row of their own.

    Step 2Which RAID type?

    Not sure? The result shows the usual choice for your number of drives.

    Usable capacity

    —

    Please enter at least one drive.

    Rule of thumb

    RAID is not a backup. It keeps the NAS running when a drive fails. But deleted or encrypted files are gone from all drives at once, and it does not help against theft or a fault in the device either. That is why step 3 follows.

    Step 3How much storage does the backup need?

    Versions means: how many older states you can go back to. The preset is a usual plan for small businesses.

    Upload and download are given in your contract or in the result of the speed test. The calculation uses 80 % of them.

    Storage per backup target

    —

    Initial backup, full data volume

    Duration by transfer route
    Connectioncalculated withDuration

    Restore from the cloud

    —

    Indicative values, as of 13 November 2026. We source NAS devices, drives and backup targets through the hardware ordering service; the easiest way to send us the summary is to copy it into the contact form.

    Runs in your browser. Nothing is sent or stored.

    RAID is not a backup

    The sentence we hear most often during NAS checks: “The data is stored twice; it has RAID.” A RAID spreads the data across several drives so that the device survives the failure of one drive. It works in real time. That is exactly the catch, because every change lands on all drives immediately, including the wrong one.

    • Deleted or overwritten by mistake. The file is gone from all drives at once. It comes back only from an older version in the backup.
    • Ransomware. It encrypts whatever it can reach over the network, and the RAID dutifully writes the encrypted files to every drive.
    • Silent data errors. In storage systems with a combined 1.53 million drives, researchers found over 400,000 cases where data was no longer correct without any error message Bairavasundaram et al. 2008. A mirror simply mirrors such an error too.
    • The device itself. In an analysis of about 39,000 storage systems, only 20 to 55 per cent of failures were caused by drives, the rest by connections and controllers Jiang et al. 2008. Lightning, water and theft hit all drives at once anyway.
    • The second failure. Drives from the same delivery age together, and failures come in clusters Schroeder and Gibson 2007. If another drive fails during the rebuild, a RAID 5 is lost.

    A RAID therefore spares you the downtime when a drive dies. The backup protects against loss: a second device, several versions and a copy kept off-site, as the 3-2-1 rule describes. And it only counts once a restore has been rehearsed; how to do that is explained in the guide to the restore test. How quickly your business as a whole is working again after a failure is shown by the IT emergency check.

    RAID 0, 1, 5, 6, 10, SHR and RAIDZ compared

    The term RAID comes from a paper of 1988: many inexpensive drives combined instead of one large one Patterson et al. 1988. All levels rest on two techniques Chen et al. 1994. Striping makes things faster, redundancy protects against failures. Redundancy means either a mirror, where each drive carries everything, or parity: a checksum from which a missing drive can be recalculated. Mirrors cost more space, parity costs more time during the rebuild.

    RAID types, example of four 4 TB drives
    Typemin.Usable4 × 4 TBMay failUse
    Basic / JBOD1sum of all drives16 TB0A single drive, or drives chained one after another. If one fails, data is lost.
    RAID 02sum of all drives (some controllers: number × smallest)16 TB0Speed only. If one drive fails, everything is gone.
    RAID 12smallest drive4 TB3Two drives in a small NAS. Each carries all the data.
    RAID 53(number − 1) × smallest12 TB1Three to four smaller drives. Plenty of space, but no reserve during the rebuild.
    RAID 64(number − 2) × smallest8 TB2The rule from five drives, or with large drives.
    RAID 104(number ÷ 2) × smallest, even number8 TB1 to 2Databases and virtual machines: fast, short rebuild, half the space.
    SHR-11with mixed sizes roughly sum − largest driveapprox. 12 TB1Synology with drives of different sizes, protection like RAID 5.
    SHR-24layers with at least four drives, per layer − 2approx. 8 TB2Synology with drives of different sizes, protection like RAID 6.
    RAIDZ12approx. (number − 1) × smallestapprox. 12 TB1TrueNAS, Proxmox and other ZFS systems. Checksums detect silent errors.
    RAIDZ23approx. (number − 2) × smallestapprox. 8 TB2ZFS from five drives, or with large drives.
    RAIDZ34approx. (number − 3) × smallestapprox. 4 TB3Large ZFS groups where even two failures during the rebuild should be survivable.

    RAID 1 with four drives is a four-way mirror; two drives are usual. Capacity rules according to the Synology documentation and OpenZFS, as of 13 November 2026.

    DRIVE 1DRIVE 2DRIVE 3DRIVE 4RAID 0NO PROTECTIONRAID 1MIRRORRAID 51 PARITYRAID 62 PARITIESRAID 10MIRROR PAIRSA1A2A3A4B1B2B3B4C1C2C3C4AA COPYBB COPYCC COPYA1A2A3PB1B2PB3C1PC2C3A1A2PQB1PQB2PQC1C2A1A1 COPYA2A2 COPYB1B1 COPYB2B2 COPYC1C1 COPYC2C2 COPY

    Fig. 1 · Data (A1, B1 …), parity (P, Q, hatched) and mirror copy (dashed) on four drives.

    Mixed drive sizes: Synology SHR

    Classic RAID uses only as much of each drive as the smallest one has. With 2, 4, 4 and 8 TB in the device, RAID 5 turns that into 6 TB of usable space, and 10 TB lie idle. This happens more often than you might think: over the years a NAS is upgraded with whatever was cheap at the time.

    Synology Hybrid RAID (SHR) therefore divides the drives into layers. The bottom layer spans all drives as high as the smallest one reaches, the next spans the remaining ones, and so on. Each layer with at least two drives gets a parity. With the same drives, SHR-1 reaches 10 TB, with the same protection as RAID 5. With mixed sizes, the rough rule is: sum of all drives minus the largest.

    SHR-2 has two parities and uses only layers with at least four drives. In this example that leaves only 4 TB. Synology itself describes the capacity as “optimised by the system” and gives no formula; we calculate with the layer model and have checked the results against the Synology RAID calculator. It remains an approximation; what counts is Storage Manager after setup.

    L12 TBL1L24 TBL1L24 TBL1L2FREE8 TBL1 · 4 DRIVES · 1 PARITYL2 · 3 DRIVES · 1 PARITYFREE · NO PARTNERSHR-1: 10 TB USABLE · RAID 5: 6 TB

    ZFS: RAIDZ1 to RAIDZ3

    TrueNAS, Proxmox and other systems with ZFS combine drives into RAIDZ groups with one, two or three parities. OpenZFS expressly gives the capacity only approximately, as (number − parity) × drive size. How much is actually usable depends on the block size: three drives in RAIDZ1 with very small blocks use only half, so no more than a mirror. In addition, ZFS keeps one thirty-second of the pool free, about 3 %. 3 to 9 drives per group are recommended.

    The advantage of ZFS is checksums over all data. In tests with deliberately injected faults, ZFS caught a broad range of drive errors, but was much less well protected against errors in main memory Zhang et al. 2010. A ZFS server therefore belongs on hardware with ECC memory, and it too needs a backup.

    Why Windows shows less than is printed on the drive

    Drive manufacturers calculate in decimal: 1 TB is 10¹² bytes, so a trillion. Windows and most NAS devices calculate in binary with 2⁴⁰ bytes per unit, which is just over 1.0995 trillion. Correctly, this unit would be called TiB (tebibyte), but “TB” is often still what is displayed. A 4 TB drive therefore appears as 3.64 TB. Nothing is missing; the difference of about 9 per cent is purely a matter of conversion.

    From the raw value after RAID, real deductions then follow. Synology reserves about 10 GB on each drive for the system and swap, a Btrfs volume holds back 4 % for metadata, an ext4 volume 2 %. The calculator therefore gives the value after RAID in TB and in TiB; what Storage Manager finally shows is a few per cent lower still.

    Drive size and displayed size
    On the boxShown in Windows / NAS
    1 TB0.91 TiB
    2 TB1.82 TiB
    4 TB3.64 TiB
    8 TB7.28 TiB
    12 TB10.9 TiB
    16 TB14.6 TiB
    20 TB18.2 TiB
    24 TB21.8 TiB

    When a drive fails: rebuild and read errors

    The datasheet figure of a mean time to failure of 1 to 1.5 million hours corresponds to an annual failure rate of at most 0.88 per cent. In the field, usually 2 to 4 per cent of drives were replaced each year, in individual installations up to 13 per cent Schroeder and Gibson 2007. With 2 % to 4 % per drive, with four drives the probability that at least one fails within a year is 7.8 % to 15 %. Over five years it is 33 % to 56 %; you should therefore expect a rebuild.

    During a rebuild, the replacement drive is completely rewritten. We assume 50 to 150 MB/s for a NAS that is in use; this is based on experience, and the peak rate of a large NAS drive is around 285 MB/s at the outer edge according to the datasheet. While the rebuild is running, a RAID 5 has no reserve.

    Rebuild by drive size
    Driveat 150 MB/sat 50 MB/s
    4 TB7.4 hours22 hours
    8 TB15 hours44 hours
    16 TB30 hours3.7 days
    24 TB44 hours5.6 days

    The read error risk, calculated and put in context

    Datasheets state a maximum uncorrectable read error rate: for desktop and many NAS drives, fewer than 1 per 10¹⁴ bits read; for Pro and enterprise drives, 1 per 10¹⁵. 10¹⁴ bits are 12.5 TB. If the rebuild of a RAID 5 reads all the remaining drives, the probability of at least one error by this figure is 1 − e^(−gelesene Bit ÷ 10^14). A single sector error in this phase is enough for data loss Schroeder et al. 2010.

    RAID 5, read error during a rebuild according to the datasheet (full drives)
    Drivesreadat 1 per 10¹⁴at 1 per 10¹⁵
    3 × 4 TB8 TB47 %6,2 %
    4 × 4 TB12 TB62 %9,2 %
    4 × 8 TB24 TB85 %17 %
    4 × 12 TB36 TB94 %25 %
    6 × 16 TB80 TB100 %47 %

    These figures are an upper limit, not a prediction. The datasheet gives a maximum value, not a measured one. In the largest field study on the subject, only 3.45 per cent of 1.53 million drives developed such a sector error at all within 32 months Bairavasundaram et al. 2007. But the errors cluster: on drives that already have some, and on larger drives. For SSDs the figure is of no use at all, because read errors there were not related to the amount read Schroeder et al. 2016.

    The conclusion remains the same, though. RAID 5 can fail during the rebuild, and it was precisely this that gave rise to double-parity schemes Thomasian and Blaum 2009. Models based on field data predict 2 to 1500 times as many double failures as the usual “mean time to data loss” formula Elerath and Pecht 2009. That is why the calculator does not work out this formula at all, and why it recommends RAID 6 or SHR-2 from 8 TB per drive. There, a read error during the rebuild is corrected using the second parity.

    Which RAID type for how many drives?

    Our recommendation by number of drives
    DrivesUsual choiceReason
    1Basic / JBOD, SHR-1A single drive has no fault protection. Then only the backup to a second device counts.
    2RAID 1, SHR-1Two drives: RAID 1, or SHR-1 on Synology. Each drive carries all the data.
    3RAID 5, SHR-1, RAIDZ1Three drives: RAID 5, SHR-1 or RAIDZ1.
    4, under 8 TBRAID 5, SHR-1, RAIDZ1, RAID 6, SHR-2, RAIDZ2Four smaller drives: RAID 5 or SHR-1 for more space, RAID 6 or SHR-2 for a reserve during the rebuild.
    4, 8 TB or moreRAID 6, SHR-2, RAIDZ2, RAID 10Four drives of 8 TB or more: RAID 6, SHR-2 or RAIDZ2. Same space as RAID 10, but any two drives may fail.
    5 to 8RAID 6, SHR-2, RAIDZ2From five drives: RAID 6, SHR-2 or RAIDZ2.
    9 or moreRAID 6, SHR-2, RAIDZ2, RAIDZ3From nine drives: RAID 6 or SHR-2. OpenZFS recommends 3 to 9 drives per RAIDZ group; above that, two groups or RAIDZ3.

    Two habits reduce the risk regardless of RAID type. First, regular data scrubbing, which reads all sectors while redundancy is still there: over 60 per cent of the sector errors in the field study were found this way Bairavasundaram et al. 2007, and with RAID 6 too, safety depends on it Elerath and Schindler 2014. Second, a look at the SMART values. They do not reliably predict the failure of an individual drive Pinheiro et al. 2007, but a rising number of reallocated sectors is a strong warning sign Ma et al. 2015. We replace such a drive before it fails. If it has already happened and the NAS no longer responds, the guide Hard drive has failed helps with the first steps.

    How much storage the backup needs

    A backup is more than a copy. It keeps older states so that you can go back to the day before the file was overwritten or encrypted. Common programs back up everything on the first run and afterwards only what has changed. Retention is staggered, following the grandfather-father-son principle: many daily states for the last few weeks, plus weekly and monthly ones for the time before that.

    The calculator adds the changes between all retained states to the full backup. With the preset values, 2 TB of data and 1 per cent change per day with 14 daily, 4 weekly and 6 monthly versions, that comes to 21 states over 150 days and at most 5 TB per backup target. So that the target is at most 70 % full and leaves room for growth, it should hold 7.14 TB, so an 8 TB drive. Under the 3-2-1 rule there are two such targets, one of them off-site.

    The result is an upper limit. If the same file changes every day, the calculator still counts it anew every day. Compression and deduplication can save a lot, but how much depends strongly on method and data Meyer and Bolosky 2012. That is why no saving is preset; you can choose one if you know your data. In the long run, what counts is less the last percentage point than the independence of the copies from each other and that errors are noticed early Baker et al. 2006.

    Initial backup and restore: the underestimated time

    Duration for the full data volume (internet net 80 % of the booked rate)
    Connectioncalculated with1 TB4 TB
    USB 3 to external hard drive150 MB/s1.9 hours7.4 hours
    Network 1 Gbit/s100 MB/s2.8 hours11 hours
    Network 2.5 Gbit/s250 MB/s1.1 hours4.4 hours
    Network 10 Gbit/s500 MB/s34 minutes2.2 hours
    Upload 40 Mbit/s to the cloud4 MB/s2.9 days12 days
    Download 100 Mbit/s from the cloud10 MB/s28 hours4.6 days

    The table shows why a cloud-only backup often falls short with typical connections. The first transfer of 2 TB takes 5.8 days at 40 Mbit/s upload; the daily change afterwards is no problem. It becomes inconvenient in an emergency: bringing everything back takes 2.3 days at 100 Mbit/s, and your business stands still for that long. A second copy on site, for example on a second NAS or a USB drive, brings the same data back over the network at 1 Gbit/s in 5.6 hours. How fast your connection really is, the speed test measures.

    How to plan a NAS and backup

    1. Establish the data volume. What is on the server, NAS and workstations today, and how much is added each year? That determines drive size and backup target.
    2. Choose the RAID type by number of drives. Two drives as a mirror, three to four smaller ones as RAID 5 or SHR-1, from four large drives RAID 6 or SHR-2.
    3. Mix drives, but deliberately. Equal sizes make the best use of the space. If you upgrade, use Synology SHR and replace the smallest drive first.
    4. Switch on monitoring. E-mail notification for drive errors and a monthly data scrub. A warning nobody reads does not protect anything.
    5. Back up to a second device. With versions, and one copy off-site or disconnected from the network. For this the NAS needs a UPS, so that a power cut does not strike in the middle of a backup.
    6. Rehearse the restore. Once a year restore one file and one whole folder, and time it.

    Where the calculator stops

    • Capacity comes before the file system. SHR and RAIDZ are approximations; what the NAS shows after setup is what counts.
    • Risks as a range. Read errors by the datasheet are an upper limit, rebuild times a value based on experience. The tool deliberately does not calculate a probability of data loss.
    • Backup as an upper limit. Files changed several times are counted several times. The logs of your backup software show the real change rate.

    How we build, monitor and restore backups for businesses in an emergency is described under backup and disaster recovery. We source NAS devices and drives through the hardware ordering service and plan larger storage and servers under servers and virtualisation. If a drive has already failed and the data is missing, data recovery is the next step.

    What the research says

    The warnings in the calculator are not gut feelings. Six findings from journals and conferences support the most important decisions; the full list with review notes is further down.

    • Drives fail more often than the datasheet says. Instead of at most 0.88 per cent, usually 2 to 4 per cent were replaced each year in the field, and failures were clustered in time Schroeder and Gibson 2007. The calculator therefore gives the probability that a drive fails within a year.
    • Sector errors are rare, but dangerous at the wrong moment. 3.45 per cent of drives were affected within 32 months, more among large drives Bairavasundaram et al. 2007; a single one during a rebuild is enough for data loss Schroeder et al. 2010.
    • The usual reliability formula underestimates double failures. Models close to the field come to 2 to 1500 times more Elerath and Pecht 2009. That is why the calculator advises double parity for large drives Thomasian and Blaum 2009.
    • RAID 6 is not invulnerable either. Among a million drives, triple faults accounted for 80 per cent of RAID 6 failures, and reallocated sectors foreshadowed failures Ma et al. 2015.
    • SSDs fail less often, but misread more often. Depending on the model, 20 to 63 per cent had at least one uncorrectable read error Schroeder et al. 2016. An SSD NAS also needs redundancy and a backup.
    • Only checksums and old states help against silent errors. Over 400,000 cases of corrupted data without an error message Bairavasundaram et al. 2008 explain why versions in the backup are worth more than a second mirror.

    Using this tool from an AI assistant

    Assistants such as Claude or ChatGPT that speak the Model Context Protocol (MCP) can call this page’s calculation directly instead of rebuilding it. The server is public, needs no sign-in and stores nothing. The answer always includes the link to this page, the date of the data and the limits of the result.

    Endpoint
    https://aureum-tech.com/mcp
    Tool
    werkzeug_nas_raid_rechner
    Transport
    Streamable HTTP, read-only
    Inputs
    NameRequiredMeaning
    plattenyesSize of each drive in TB, as on the box (decimal), e.g. [4, 4, 4, 4] or mixed [8, 4, 4, 2].
    raidyesRAID type: basic = Basic / JBOD; raid0 = RAID 0; raid1 = RAID 1; raid5 = RAID 5; raid6 = RAID 6; raid10 = RAID 10; shr1 = SHR-1; shr2 = SHR-2; raidz1 = RAIDZ1; raidz2 = RAIDZ2; raidz3 = RAIDZ3.
    daten_tbnoOptional: amount of data to back up in TB. The backup need is calculated only with this value.
    aenderung_prozent_tagnoShare of the data in per cent that changes per day. Default 1.
    versionen_taeglichnoRetained daily versions. Default 14.
    versionen_woechentlichnoRetained weekly versions. Default 4.
    versionen_monatlichnoRetained monthly versions. Default 6.
    einsparfaktornoAssumption for compression and deduplication: 1 = no saving (cautious, default), 2 = half the space.
    kopiennoNumber of backup copies besides the original (3-2-1 rule: 2). Default 2.
    upload_mbitnoUpload speed of the internet connection in Mbit/s, for the initial cloud backup. Default 40.
    download_mbitnoDownload speed of the internet connection in Mbit/s, for restoring from the cloud. Default 100.

    Questions where an assistant should call it

    • “How much space do I have with four 8 TB drives in RAID 5, and what does Windows show of it?”
    • “Is SHR worthwhile with drives of 2, 4, 4 and 8 TB?”
    • “How big is the risk of a read error when rebuilding a RAID 5?”
    • “How much storage does the backup of 3 TB with 30 daily versions need, and how long does the first upload take?”

    How the connection works and what MCP can do in your own business is explained on the page about MCP integrations.

    Common questions about NAS, RAID and backup

    How much storage is left with RAID 5?

    With RAID 5, you get the sum of all drives minus one, calculated with the smallest drive. Four 4 TB drives give 12 TB, three drives 8 TB. Windows and most NAS devices show about 10.9 TB of that, because they calculate in binary. The file system and system partition take a few more per cent. One drive may fail; a second one must not fail during the rebuild.

    Why does Windows show less storage than is printed on the drive?

    Manufacturers calculate in decimal: 1 TB is 1,000,000,000,000 bytes. Windows calculates in binary, with 1,099,511,627,776 bytes per unit, but still writes TB. A 4 TB drive therefore appears as 3.64 TB, an 8 TB drive as 7.28 TB. Nothing is missing; the difference of about 9 per cent is purely a matter of conversion. The calculator gives both values.

    Is a RAID a backup?

    No. A RAID keeps the NAS running when a drive fails. But a file that is deleted, or encrypted by ransomware, is changed on all drives at once. It does not help against theft, lightning or a fault in the device either. For that you need a backup on a second device, with versions and a copy kept off-site.

    RAID 5 or RAID 6 with four drives?

    With drives under 8 TB, RAID 5 is acceptable and provides the capacity of one additional drive. From 8 TB, we advise RAID 6 or SHR-2: rebuilding an 8 TB drive takes 15 to 44 hours, and during that time RAID 5 has no reserve. According to the datasheet, the risk of a read error when rebuilding four 8 TB drives is 85 %; RAID 6 corrects it.

    What does Synology SHR offer with drives of different sizes?

    Classic RAID uses only as much of each drive as the smallest one has. With 2, 4, 4 and 8 TB, only 6 TB remain usable in RAID 5. SHR-1 divides the drives into layers and reaches 10 TB, with the same fault protection. SHR-2 needs four drives per layer and manages only 4 TB here. Synology describes the capacity as optimised by the system; our values agree with the Synology RAID calculator.

    How long does a RAID rebuild take?

    The replacement drive is completely rewritten. At 150 MB/s, that takes 7.4 hours for 4 TB and 30 hours for 16 TB. If the office keeps working, the rate can fall to 50 MB/s, and 16 TB takes 3.7 days. This range is based on experience; how fast your NAS is depends mainly on its processor and load.

    How much storage does my backup need?

    The first backup is as large as the data; after that only changes are added. With 2 TB of data, 1 per cent change per day and 21 retained versions over 150 days, the tool calculates at most 5 TB per backup target. With some headroom, the target should hold 7.14 TB, so an 8 TB drive. Under the 3-2-1 rule you need two such targets.

    Where does the NAS and RAID calculator stop?

    It calculates capacity according to the RAID rule, risks according to the datasheet and field data, and backup needs as an upper limit. SHR and RAIDZ are approximations. We work with you to determine which NAS suits your data, how to set up and test the backup, and what to do first after a failure, on site in the Vogtland or remotely.

    What the tool is based on

    The guide values and notes above are based on these 16 scientific papers. Each one has been checked via its DOI or the publisher’s page (most recently on 13 November 2026): it exists, it has not been retracted, and its findings still hold for this question today.

    1. Schroeder, B.; Gibson, G. A. (2007): Understanding disk failure rates: What does an MTTF of 1,000,000 hours mean to you?. ACM Transactions on Storage 3 (3), Art. 8

      Finding Replacement data from over 110,000 hard drives: in the field, usually 2 to 4 per cent of drives were replaced each year, in individual installations up to 13 per cent, while the datasheets lead one to expect at most 0.88 per cent. The intervals between failures are not independent but clearly correlated.

      In the tool The tool calculates with 2 to 4 per cent per drive per year and points out that a second failure often does not take long to follow.

    2. Pinheiro, E.; Weber, W.-D.; Barroso, L. A. (2007): Failure Trends in a Large Disk Drive Population. 5th USENIX Conference on File and Storage Technologies (FAST ’07), San Jose

      Finding Failure data from a very large drive population in data centres: some SMART values correlate strongly with failures, but are not enough to predict the failure of an individual drive reliably. Temperature and load played a smaller role than assumed.

      In the tool The page advises taking SMART warnings seriously but not relying on them: the backup remains necessary.

    3. Bairavasundaram, L. N.; Goodson, G. R.; Pasupathy, S.; Schindler, J. (2007): An analysis of latent sector errors in disk drives. Proceedings of ACM SIGMETRICS 2007, pp. 289–300

      Finding Of 1.53 million drives, 3.45 per cent developed sector errors within 32 months that only show up when reading. The share rises with drive size, errors cluster on drives that already have some, and over 60 per cent were discovered by regular checking (scrubbing).

      In the tool It puts the datasheet calculation for read errors in context and explains the recommendation to run the NAS's data scrub regularly.

    4. Schroeder, B.; Damouras, S.; Gill, P. (2010): Understanding latent sector errors and how to protect against them. ACM Transactions on Storage 6 (3), pp. 1–23

      Finding A single sector error can lead to data loss if it occurs during the rebuild of a RAID after a drive failure. The paper compares checking strategies (scrubbing) on field data and expects more such errors as drive size grows.

      In the tool This is the basis for the “read error during rebuild” calculation and for the recommendation of double parity with large drives.

    5. Bairavasundaram, L. N.; Arpaci-Dusseau, A. C.; Arpaci-Dusseau, R. H. et al. (2008): An analysis of data corruption in the storage stack. ACM Transactions on Storage 4 (3), pp. 1–28

      Finding In systems with a combined 1.53 million drives, over 400,000 cases of silent data corruption were found in 41 months. Inexpensive nearline drives were affected about ten times as often as enterprise drives, and the cases occurred in clusters.

      In the tool This supports the rule of thumb “RAID is not a backup”: a RAID mirrors corrupted data too; only older versions help.

    6. Jiang, W.; Hu, C.; Zhou, Y.; Kanevsky, A. (2008): Are disks the dominant contributor for storage failures? A comprehensive study of storage subsystem failure characteristics. ACM Transactions on Storage 4 (3), pp. 1–25

      Finding Logs of about 39,000 storage systems with 1.8 million drives over 44 months: drives caused only 20 to 55 per cent of failures, the rest came from connections and protocol layers. Failures occurred in bursts.

      In the tool That is why the page allows for the failure of the whole device: no RAID helps against a power supply, controller or enclosure.

    7. Schroeder, B.; Lagisetty, R.; Merchant, A. (2016): Flash Reliability in Production: The Expected and the Unexpected. 14th USENIX Conference on File and Storage Technologies (FAST ’16), pp. 67–80

      Finding Six years of field data from SSDs in data centres: SSDs are replaced less often than hard drives but have more uncorrectable read errors; depending on the model, 20 to 63 per cent had at least one. The UBER metric is not meaningful, because the errors were not related to the amount read.

      In the tool That is why the read error calculation applies only to hard drives, and SSDs in the NAS too need redundancy and a backup.

    8. Patterson, D. A.; Gibson, G.; Katz, R. H. (1988): A case for redundant arrays of inexpensive disks (RAID). Proceedings of the 1988 ACM SIGMOD International Conference on Management of Data, pp. 109–116

      Finding The foundational paper that coined the term RAID: many inexpensive drives combined instead of one large one, with five levels that weigh performance, cost and reliability differently.

      In the tool This is the starting point of the RAID table; the capacity rules of the classic levels go back to this classification.

    9. Chen, P. M.; Lee, E. K.; Gibson, G. A. et al. (1994): RAID: high-performance, reliable secondary storage. ACM Computing Surveys 26 (2), pp. 145–185

      Finding Overview of RAID levels 0 to 6 comparing performance, cost and reliability: striping brings speed, redundancy brings protection against failure.

      In the tool This underlies the capacity and fault tolerance columns of the RAID table and the diagram of drive layout.

    10. Thomasian, A.; Blaum, M. (2009): Higher reliability redundant disk arrays: Organization, operation, and coding. ACM Transactions on Storage 5 (3), pp. 1–59

      Finding RAID 5 survives one drive; but the rebuild can fail because of unreadable sectors. This led to double-parity schemes such as RAID 6. The paper also summarises studies on drive failures and the effect of scrubbing.

      In the tool Explains why the tool recommends RAID 6 or SHR-2 instead of RAID 5 from four large drives.

    11. Elerath, J.; Pecht, M. (2009): A Highly Accurate Method for Assessing Reliability of Redundant Arrays of Inexpensive Disks (RAID). IEEE Transactions on Computers 58 (3), pp. 289–299

      Finding A model with distributions from field data for failures, rebuild, read errors and scrubbing predicts 2 to 1500 times as many double failures as the usual MTTDL calculation and matched field data from RAID groups of 14 drives.

      In the tool That is why the tool does not calculate a “mean time to data loss”: this figure looks precise but underestimates the risk.

    12. Elerath, J. G.; Schindler, J. (2014): Beyond MTTDL: A Closed-Form RAID 6 Reliability Equation. ACM Transactions on Storage 10 (2), pp. 1–21

      Finding A formula for data loss in RAID 6 groups that models failures, rebuild, sector errors and scrubbing as time-dependent processes, supported by field data from tens of thousands of systems. It is considerably more accurate than the MTTDL equation.

      In the tool This supports the point that RAID 6 too depends on regular scrubbing: the page lists it as a fixed step.

    13. Ma, A.; Traylor, R.; Douglis, F. et al. (2015): RAIDShield: Characterizing, Monitoring, and Proactively Protecting Against Disk Failures. ACM Transactions on Storage 11 (4), pp. 1–28

      Finding About a million SATA drives over up to five years: drive failures noticeably weaken the protection of a RAID; in RAID 6 systems, triple faults accounted for 80 per cent of RAID failures. The number of reallocated sectors correlated strongly with impending failures.

      In the tool The page advises replacing drives with a rising number of reallocated sectors as a precaution instead of waiting for the failure.

    14. Zhang, Y.; Rajimwale, A.; Arpaci-Dusseau, A. C.; Arpaci-Dusseau, R. H. (2010): End-to-end Data Integrity for File Systems: A ZFS Case Study. 8th USENIX Conference on File and Storage Technologies (FAST ’10), San Jose

      Finding With deliberately injected faults, the paper shows that ZFS detects and handles a broad range of drive errors, but is much less well protected against errors in main memory.

      In the tool This puts RAIDZ in context: checksums help against silent drive errors, but replace neither ECC memory nor a backup.

    15. Meyer, D. T.; Bolosky, W. J. (2012): A study of practical deduplication. ACM Transactions on Storage 7 (4), pp. 1–20

      Finding File systems of 857 desktop computers: deduplication of whole files achieved about three quarters of the saving of the most elaborate block-level method, and 87 per cent for backup images. How much can be saved depends on method and data.

      In the tool That is why no saving is preset in the calculator: the factor is an assumption that you choose deliberately.

    16. Baker, M.; Shah, M.; Rosenthal, D. S. H. et al. (2006): A fresh look at the reliability of long-term digital storage. Proceedings of the 1st ACM SIGOPS/EuroSys European Conference on Computer Systems, pp. 221–234

      Finding Long-lived data is threatened not only by hardware and software but also by people and organisations. The most effective measures: find hidden errors quickly, automate repair and make the copies more independent of each other.

      In the tool This underlies the recommendation of several separate copies under 3-2-1, one of them off-site, and of regular restore tests.

    Standards, authorities and manufacturer data

    Mon–Fri 8:00–17:00

    Have you got your figures? Send us the copied result. We will suggest suitable devices and backup targets and set everything up so that the restore works in an emergency, in Rodewisch and throughout the Vogtland.

    +49 3744 4399760[email protected]

    Mon–Fri 8:00–17:00 · Straße der Jugend 5, 08228 Rodewisch

    Have your backup planned
    +49 3744 4399760Mon–Fri 8:00–17:00
    CallCallback

    PARTS LIST · SHEET 1/1

    What this page is made of

    Values measured at build time. With JavaScript, your browser measures them again live.

    ITEMPARTTYPESIZE
    01index.htmlDocument≈ 29 kB
    02styles.cssStylesheet≈ 20 kB
    03scripts.jsScript≈ 13 kB
    04archivo-variable.woff2Font≈ 58 kB
    05ibm-plex-mono.woff2Font≈ 30 kB
    06favicon.svgImage< 1 kB

    Advertising or analytics cookies: none. Without your consent, the page loads nothing from third-party servers apart from Cloudflare, our delivery service. Fonts, scripts and images are hosted by us. That is how we build your IT, too.

    OUTSIDE OFFICE HOURS

    Feel free to call anyway

    Our regular office hours are Monday to Friday, 8:00–17:00.

    In the evening and at weekends the number is forwarded to us, and often someone will pick up. We cannot promise that, though.

    If nobody answers, leave a short message on the voicemail: your name, your number and what it is about. We will call back as soon as we can, on the next working day at the latest.

    The call costs nothing. If someone has to start work straight away outside office hours, the surcharge in the price list applies.

    Call now+49 3744 4399760

    Prefer to write? Use the contact form or e-mail [email protected]. We will read it on the next working day.

    DIAGNOSIS · AT-K2

    What do you need help with?

    ↵ SELECTESC CLOSECALL: +49 3744 4399760

    Custom settings

    Which services may load?

    Strictly necessary

    The choice you make here and your settings for colour scheme and motion. These are kept as small entries on your device and are never sent to a server. They are needed for the site to work and therefore cannot be switched off.