• Skip to primary navigation
  • Skip to main content
  • Skip to primary sidebar

Yellow Bricks

by Duncan Epping

  • Home
  • Unexplored Territory Podcast
  • HA Deepdive
  • ESXTOP
  • Stickers/Shirts
  • Privacy Policy
  • About
  • Show Search
Hide Search

Datrium DVX goes GA

Duncan Epping · Jan 29, 2016 ·

I wrote an article about Datrium DVX when Datrium came out of stealth about 6 months ago. I am not going to rehash that as I think it was pretty clear around what Datrium DVX is. Datrium DVX is a combination of “host local data services” and network accessed storage capacity. This basically means that you utilize local flash resources for read caching (deduped before stored on the flash tier), writes will go directly to the “NetShelf” as Datrium calls it, which is basically your persistent layer. The write is compressed by the way before it is send to the NetShelf, and on theNetShelf itself there is a also a dedupe process that runs periodically to “collect garbage” and optimize the system for capacity.

I had a chat with the team from Datrium and we spoke about what was new with GA and stuff that I hadn’t covered yet in my previous article. Some of the facts from that call:

  • The DVX list price is $125,000. This includes a NetShelf D12X4 appliance and unlimited licenses for DVX Hyperdriver software on vSphere hosts
    • Servers and SSDs must be purchased and supported independently
    • There currently is a limit of 32 hosts connected to a NetShelf
    • With 32 hosts the expected aggregate is 1m IOPS
  • The NetShelf D12X4 appliance comes with 48TB raw, or 60TB – 180TB effective capacity at common deduplication and compression rates for Enterprise data (2x-6x)
    • Expected effective capacity on average is around 125TB
  • The NetShelf comes in an HA configuration with 2 controllers and mirrored NVRAM, no single point of failure
  • Datrium DVX takes up to 20% of the host CPU resources, but this is the most it will take and only when running at max speed, so typically CPU resources used will be much lower
  • Has “data locality”, meaning that when a VM is migrated between hosts than the cache will be read from the “source” host to the “destination” so that the “destination” warms up

I guess that says it all. Well there’s a bit around support for hypervisors and things like VVols and VAAI. Today Datrium only supports vSphere, and it wasn’t clear if and when other hypervisors would be supported. When it comes to VAAI it was mentioned that VAAI clones are fully supported as it stands today. On top of that Datrium is also working hard on enabling a VVol capable solution, they have joined the VVol program and are looking forward to release their VVol capable software, I am sure that when they do I will talk to them again.

A couple of things are missing in todays offering, which would definitely be nice to have, or in some cases even a must. Native replication and array based snapshots for instance. Today Datrium partners with Zerto, and of course VMware customers can use vSphere Replication for free. Snapshots rely on vSphere today, but there are plans to have them natively on the array at some point. Also, when you run out of capacity and you add a NetShelf, this will become a new mountpoint, it would be nice if this was scale-out, and the Datrium folks agreed but didn’t commit to anything (of course). Overall I think it is an interesting solution, and with 30 install sites for the beta I think it is safe to say that they will be a player to consider, but only time will tell.

Thanks guys for taking the time to brief me.

Virtual SAN, the leader in the hyper-converged market!

Duncan Epping · Jan 27, 2016 ·

I was just listening to the VMware earnings call, and needless to say that I was very excited hearing all the great news about Virtual SAN. When I talk to customers this is something that comes up every now and then, they want to know where we stand in the market. I figured I would share what was stated by Carl Eschenbach and Pat Gelsinger at the 2015 Q4 earnings call:

Summarizing a few other product areas, our hyper-converged offerings based on VMware Virtual SAN experienced significant traction. Specifically, our Virtual SAN business saw successes across a wide variety of industries, market segments, and geos. In Q4, total VSAN bookings grew nearly 200% year-over-year, and customer count has increased to over 3,000 versus over 1,000 a year ago. We are now well over $100 million annual run rate per total bookings.

With our next release of VSAN in Q1, we expect our momentum to build given the powerful new enterprise capabilities, the product brings to market. Taking into account, the hardware associated with running the Virtual SAN software and our current booking to run rate, we believe we are the industry leader in the hyper-converged offerings measured both by software and as an appliance.

And the best is yet to come… New version is around the corner, and I can’t wait for it to be released. Make sure to sign up for the launch events! (or attend one of the many VMUGs the upcoming months, I will personally be presenting in Newcastle, Johannesburg, Durban, Capetown and Den Bosch)

Rebuilding failed disk in VSAN versus legacy storage

Duncan Epping · Jan 26, 2016 ·

This is one of those questions that comes up every now and then, I have written about this before, but it never hurts to repeat some of it. The comment I got was around rebuild time of failed drives in VSAN, surely it takes longer than with a “legacy” storage system. The answer of course is: it depends (on many factors).

But what does it depend on? Well it depends on what exactly we are talking about, but in general I think the following applies:

With VSAN components (copies of objects, in other words copies of data) are placed across multiple hosts, multiple diskgroups and multiple disks. Basically if you have a cluster of lets say 8 hosts with 7 disks each and you have 200 VMs then the data of those 200 VMs will be spread across 8 hosts and 56 disks in total. If one of those 56 disks happens to fail then the data that was stored on that disk would need to be reprotected. That data is coming from the other 7 hosts which is potentially 49 disks in total. You may ask, why not 55 disks? Well because replica copies are never stored on the same hosts for resiliency purposes, look at the diagram below where a single object is split in to 2 data components and a witness, they are all located on different hosts!

We do not “mirror” disks, we mirror the data itself, and the data can and will be place anywhere. This means that when a failure has occurred of a disk within a diskgroup on a host all remaining disk groups / disk / hosts will be helping to rebuild the impacted data, which is 49 disks potentially. Note that not only will disks and hosts containing impacted objects help rebuilding the data, all 8 hosts and 55 disks will be able to receive the replica data!

Now compare this to a RAID set with a spare disk. In the case of a spare disk you have 1 disk which is receiving all the data that is being rebuild. That single disk can only take an X number of IOPS. Lets say it is a really fast disk and it can take 200 IOPS. Compare that to VSAN… Lets say you used really slow disks which only do 75 IOPS… Still that is (potentially) 49 disks x 75 IOPS for reads and 55 disks for writes.

That is the major difference, we don’t have a single drive as a designated hot spare (or should I say bottleneck?), we have the whole cluster as a hot spare! As such rebuild times when using similar drives should always be faster with VSAN compared to traditional storage. 

SMP-FT and (any type of) stretched storage support

Duncan Epping · Jan 19, 2016 ·

I had a question today around support for SMP-FT in an EMC VPLEX environment. It is well known that SMP-FT isn’t supported in a stretched VSAN environment, but what about other types of stretched storage? Is that a VSAN specific constraint? (Legacy) FT appears to be supported for VPLEX and other types of stretched storage?

SMP-FT is not supported in a vSphere Metro Storage Cluster environment either! This has not been qualified yet, I’ve requested the FT team to at least put it up on the roadmap and document max latency tolerated for these types of environments for SMP-FT just in case someone would want to use it in a campus situations for instance, despite the high bandwidth requirements for SMP-FT. Note that “legacy FT” can be used with vMSC environment, but not with VSAN. In order to use legacy FT (single vCPU) you will need to use an advanced VM setting: vm.uselegacyft. Make sure to set this setting when using FT in a stretched environment!

Disable VSAN site locality in low latency stretched cluster

Duncan Epping · Jan 15, 2016 ·

This week I was talking to a customer in Germany who had deployed a VSAN stretched cluster within a building. As it was all within a building (extremely low latency) and they preferred to have a very simple operational model they decided not to implement any type of VM/Host rules. By default when a stretched cluster is deployed in VSAN (and ROBO uses this workflow as well) then “site locality” is implemented for caching. This means that a VM will have its read cache on the host which holds the components in the site where it is located.

This is great of course and avoids incurring latency hit for reads. Now in some cases you may not desire this behaviour. For instance in the situation above where there is an extremely low latency connection between the different rooms in the same building. In this case as well because there are no VM/Host rules implemented a VM can freely roam around the cluster. Now when a VM moves between VSAN Fault Domains in this scenario the cache will need to be rewarmed as it only reads locally. Fortunately you can disable this behaviour easily through the advanced setting called DOMOwnerForceWarmCache:

[root@esxi-01:~] esxcfg-advcfg -g /VSAN/DOMOwnerForceWarmCache
Value of DOMOwnerForceWarmCache is 0
[root@esxi-01:~] esxcfg-advcfg -s 1 /VSAN/DOMOwnerForceWarmCache
Value of DOMOwnerForceWarmCache is 1

In a stretched environment you will see that this setting is set to 0 set it to 1 to disable this behaviour. In a ROBO environment VM migrations are uncommon, but if they do happen on a regular basis you may also want to look in to setting this setting.

  • « Go to Previous Page
  • Page 1
  • Interim pages omitted …
  • Page 117
  • Page 118
  • Page 119
  • Page 120
  • Page 121
  • Interim pages omitted …
  • Page 502
  • Go to Next Page »

Primary Sidebar

About the Author

Duncan Epping is a Chief Technologist and Distinguished Engineering Architect at Broadcom. Besides writing on Yellow-Bricks, Duncan is the co-author of the vSAN Deep Dive and the vSphere Clustering Deep Dive book series. Duncan is also the host of the Unexplored Territory Podcast.

Follow Us

  • X
  • Spotify
  • RSS Feed
  • LinkedIn

Recommended Book(s)

Also visit!

For the Dutch-speaking audience, make sure to visit RunNerd.nl to follow my running adventure, read shoe/gear/race reviews, and more!

Do you like Hardcore-Punk music? Follow my Spotify Playlist!

Do you like 80s music? I got you covered!

Copyright Yellow-Bricks.com © 2026 · Log in