There are some new REST API’s for vVols objects in Pure Storage’s FlashArray REST API 2.14! Specifically operations for virtual-machines and virtual-machine-snapshots. I won’t lie, the hardest part for me was figuring out how to use REST 2.0 with the FlashArray. The change from using standard authentication to using Oauth2 for REST 2.0 took some time. I had a lot of fun playing around and learning about them and want to share that process!
Recently I was working through an issue that was reported by one of our Partners. I wanted to see if I could reproduce the issue and if it may have been an issue with vVols with Pure. What was the issue you ask? Essentially there was an issue reported that inconsistent behavior was seen with […]
VMware vSphere Virtual Volumes (vVols) and FlashArray based replication will now be supported with Site Recovery Manager (SRM) 8.3! Along with the ability to leverage the API calls for SPBM Failover and Reverse operations for vVols with PowerCLI or vRO, SRM will now support the SRM recovery workflows with vVols and array based replication.
One of the more confusing errors when getting started with implementing vSphere Virtual Volumes is the vSphere HA failed to create a configuration VVol for this Datastore. This error can be symptom of a larger connectivity and access issue with the VVol Storage Container, but more often the issue lies in vSphere HA attempting to […]
One of the common questions I’m asked with regards to VVols on Pure Storage is “Can I rename the Data Volume on the FlashArray? If I do, what happens?”. Now, why would you want to rename the volume on the array? When Virtual Volumes are provisioned on the FlashArray they are given a “hash” that […]