Over the weekend, I saw this blog post about the disruptive XtremIO 2.4 –> 3.0 upgrade.
First of all, yes, it is accurate to call the XtremIO 2.4->3.0 upgrade a disruptive operation. When customers using XtremIO 2.4 migrate to 3.0, there are big changes, big improvements. Think 2x better performance. Think 2-4x higher utilization due to compression.
We continue to support 2.4, so if customers want to sit tight and avoid the upgrade, they are entitled to do exactly that – they will continue to enjoy all the XtremIO awesome they are loving. To get all the new goodies above (at no extra cost!) they will need to pull the data off, upgrade, and then bring the data back – and and our partners are always ready to help them do it.
All of the above is why so many customers are picking XtremIO, why Gartner put it here, and why it has become the fastest growing revenue storage product EVER.
But why is this particular upgrade disruptive? Why do disruptive storage events ever happen anymore?
Storage is persistent. This is patently obvious – but in general people don’t think through what this means (and why should they – they aren’t engineers!).
Anytime you touch two core parts of any persistence architecture: 1) layout structure layer or 2) metadata mapping layer – it means a disruptive migration to some degree.
BTW – it’s funny looking at some of the people who commented on the blog critically… who themselves as vendors are going through a huge disruptive event of their own! All the more reason to not listen to people who go negative, and trust those who disclose warts, and partner with you to work through them.
Disruptive upgrades affect ALL persistence architectures, all vendors at times. If you’re curious about the engineering reasons why (helpful to predict whether any future upgrade of any stack will likely be NDU or DU), as well as more on this particular XtremIO upgrade (and some more roadmap) read on!