What’s .NEXT? – Erasure Coding!

Up to now, Nutanix has used a concept known as “Replication Factor” or “RF” to provide storage layer data protection as opposed to older RAID technologies.

RF allows customers to configure either 2 or 3 copies of data depending on how critical the data is.

When using RF2, the usable capacity of RAW is 50% (RAW divide 2).

When using RF3, the usable capacity of RAW is 33% (RAW divide 3).

While these sound like large overheads, but in reality, they are comparable to traditional SAN/NAS deployments as explain in the two part post – Calculating Actual Usable capacity? It’s not as simple as you might think!

But enough on existing features, lets talk about an exciting new feature, Erasure coding!

Erasure coding (EC) is a technology which significantly increases the usable capacity in a Nutanix environment compared to RF2.

The overhead for EC depends on the cluster size but for clusters of 6 nodes or more it results in only a 1.25x overhead compared to 2x for RF2 and 3x for RF3.

For clusters of 3 to 4 nodes, the overhead is 1.5 and for clusters of 5 nodes 1.33.

The following shows a comparison between RF2 and EC for various cluster sizes.ErasureCodingAs you can see, the usable capacity is significantly increased when using Erasure Coding.

Now for more good news, in-line with Nutanix Uncompromisingly Simple philosophy, Erasure Coding can be enabled on existing Nutanix containers on the fly without downtime or the requirement to migrate data.

This means with a simple One-click upgrade to NOS 4.5, customers can get up to a 60% increase in usable capacity in addition to existing data reduction savings. e.g.: Compression.

So there you have it, more usable capacity for Nutanix customers with a non disruptive one click software upgrade…. (your welcome!).

For customers considering Nutanix, your cost per GB just dropped significantly!

Want more? Check out how to scale storage capacity separately from compute with Nutanix!

Related Articles:

1. Nutanix Erasure Coding (EC-X) Deep Dive

9 thoughts on “What’s .NEXT? – Erasure Coding!

    • Hi Andrew, new features will be available to existing customers dependant on licence edition (Starter/Pro/Ultimate). Acropolis is available now (and actually has been for a long time) and other features such as EC-X are coming in 4.1.3 if I’m not mistaken which is imminent.

      • So I can see where acropolis lands in the licenses editions (most of my customers have pro so this is good news). What I can’t find is where EC-X lands in the licensing. Is it pro and above too?

  1. Hi,

    Does this approach eliminate the local copy on disk, moved there post a vMotion and subsequent read, to ensure on-disk locality, as I’ve seen described in S Poitras’ Bible? If not, it seems like most disk reads in this model lose all the nice locality benefits and become network disk reads, more like VSAN?

    • Hi Brian, Erasure coding is performed on cold data to reduce the potential reduced performance. If data is read frequently it will remain local and wont qualify for EC-X. Hope that makes sense.

  2. Pingback: Erasure Coding in NOS 4.1.3 | Invisible Infrastructure

  3. Pingback: Newsletter: June 21, 2015 | Notes from MWhite

  4. Pingback: Newsletter: October 24, 2015 | Notes from MWhite

Leave a Reply to forbsyCancel reply