I tend to write a lot about VMware VVols these days as I believe VMware’s new storage architecture has many benefits and VVols is the future of storage for vSphere. In this post I thought I would highlight and recap some of the posts that I did in 2017 related to VVols and you have many more VVols posts coming your way from me in 2018.
In January I gave an update on VVol adoption based on the data we collect from 3PAR arrays specific to VVols. I also showed how to find out which vendors support the new VVol replication feature introduced in vSphere 6.5.
- VVols by the numbers: an update on VVol adoption in the real world
- How to find out which storage vendors support VVol replication in vSphere 6.5
In March I provided an overview of current storage vendor support for VVols which continues to grow.
In April I wrote about some of the new PowerCLI cmdlets that were released that support BC/DR operations related to replicating VVols.
In June I wrote about why their were almost no VVols session at VMworld 2017 as VMware felt they had done enough to promote VVols and it was now on the partners to do so.
In August I wrote about resources to learn more about VVols replication.
In September I wrote about a new report that IDC released that highlighted the benefits of VVols. I also wrote on some of the enhancements that are in the upcoming vSphere release related to VVols. Finally I did a short post that highlighted an in-booth session that Pete Flecha from VMware did on VVols.
- New report from IDC highlights the many benefits of VMware VVols
- VVols enhancements coming in the next vSphere release
- The VVols Gospel according to Pete Flecha
In October I wrote about how VVols inmpacts the protocol choices people make in vSphere.
In November I gave a fresh update on VVols adoption.
And in December I rested, more to come very soon!
