I have released a new version of the VMware/Pure PowerShell module which can be automatically installed from the PowerShell Gallery.
Pure Storage PowerShell VMware Module
Updates in this release are focused on VVols. Creating VVol snapshots, copying them, creating new disks from them, retrieving them etc.
I wrote a blog post below on using some of the new cmdlets:
PowerCLI and VVols Part V: Array Snapshots and VVols
Continue reading 220.127.116.11 Release of the Pure Storage VMware PowerShell Module
A few months back I was reviewing our VMware training for our field (and after some direct feedback) realized it wasn’t really doing what our field needed. It was too nuts and bolts technical–which isn’t really what was needed by the masses. There was more of a desire to understand the value of the VMware product, the value of the integration and the value that we as Pure can bring to it.
The ones that wanted/needed more technical training could get that as needed.
In short, what they wanted to be able to do was have the “I’m staffing a booth at a conference and someone asks me about vRealize Orchestrator”. Not being an expert in the product, how to do I quickly understand the value, so I know if I am chasing the right product/solution and I should inquire further.
There are so many options out there, the “why” sometimes can be the most important question. Continue reading VMware & Pure Integration Training Videos
I see a fair amount of requests around how to do different things with VMware PowerCLI and the Pure Storage PowerShell SDK. How do I correlate a VMFS to a volume? How do I create a new VMFS? How do I expand? Etc.
To help our customers I have written a module that includes a lot of the common operations people might need to “connect” PowerCLI to our PowerShell SDK.
The module is called Cody.PureStorage.FlashArray.VMware. Continue reading Pure Storage and VMware PowerShell Module
One of the first technical benefits users can enjoy around VVols is the use of snapshotting. Snapshots created through VMware of VMs have always been a point of contention which as severely limited their usability (see a post I did around the performance impact of them here).
With VVols, when you right-click on a VM and choose take snapshot, VMware does not create the performance-impacting delta VMDK files that were traditionally used, but instead VMware entirely offloads this process to the array. So the array creates the snapshots and VMware just tracks them.
But since VMs are now a collection of individual volumes on the array (a VVol is just an array volume) you can also snapshot and restore individual virtual disks as well directly on the array.
So what does all of this mean?
Continue reading Virtual Volumes and Array Snapshots Part I: Managed Snapshots
An increasingly common use case for Active-Active replication in vSphere environments is vSphere Metro Storage Cluster (vMSC) which I wrote about in this paper recently:
This overviews how a stretched vSphere cluster interacts with the active-active replication we offer on the FlashArray called ActiveCluster. Continue reading Tech Preview: vCenter Site Recovery Manager with ActiveCluster
I recently did a VMUG webcast on VVols and there were a ton of questions and unfortunately I ran out of time and could not answer a lot of them. I felt bad about that, so I decided to follow up. I was going to send out emails to the people who asked, but figured it was simpler and more useful to others to just put them all here.
See the VMUG VVol webinar here:
You can get my slides here.
Would VVols replace the requirements for RDM’s?
Answer: Maybe. It depends on why you are using RDMs. If it is simply to allow sharing or overwriting between physical and virtual. VVols will replace RDMs. If it is to make it easier to restore from array snapshots, VVols will replace them. If it is for Microsoft Failover Clustering, VVols are not supported with that yet. You still need RDMs. Though VMware is supposed to be adding support for this in the next release. See this post for more info. Continue reading VVol VMUG Webinar Q&A Follow Up
Ok finally! I had this finished awhile ago, but I wrote it using our version 2.0 plugin–so I couldn’t post it until the plugin was certified by VMware. That plugin version is now certified and posted on the VMware Solution Exchange (see my post here).
Moving forward, we will likely be posting new workflows in various packages (working on an ActiveCluster one now), instead of including them directly in our plugin. This will make it easier to update them and add to them, without also having to generate an entire new plugin version.
So first, download and install the v2 FlashArray plugin for vRO and then install my workflow package for VVol on the VMware Solutions Exchange:
Continue reading vRealize Orchestrator VVol Workflow Package
In Purity 5.0 Pure Storage released support for Active/Active replication on the FlashArray. This provides the ability to present the same storage volume simultaneously from two different FlashArrays.
For a good overview, check out this video:
Continue reading Setting Up FlashArray Active/Active Replication (ActiveCluster)
This is a blog post I have been waiting to write for a long time. We at Pure Storage are pleased to announce that vSphere Virtual Volume support on the FlashArray is officially GA!
The FlashArray now supports running VVols in Purity 5.0.0 and later. The cool thing about the FlashArray is the flexibility of the Purity Operating Environment–so VVols are supported on all FA 400 models (405, 420, and 450), //M models (m10, m20, m50, m70) and FlashArray//X. Continue reading Announcing Pure Storage FlashArray VVol GA
One of the most strategic benefits of Virtual Volumes is how it opens up your data mobility. Because there is no more VMDK encapsulation, VVols are just block volumes with whatever file system your guest OS in the VM puts on it. So a VVol is really just a volume hosting NTFS, or XFS or whatever. So if a target can read that file system, it can use that VVol. It does not have to be a VMware VM.
Let me start out with: YES our VVols deployment will be GA VERY soon. I am sorry (but not really) for continuing to tease VVols here.
This is one of the reasons we do not treat VVols on the FlashArray any differently than any other volume–because they aren’t different! So there is no reason you can’t move the data around. So why block it??
Some possibilities this function opens us:
- Take a RDM and make it a VVol
- Take a VVol and present it to an older VMware environment as a RDM
- Take a VVol and present it, or a copy of it, to a physical server.
- On the FlashArray we are also introducing something called CloudSnap, which will let you take snapshots of volumes (aka VVols) and send them to NFS, or S3 to be brought up as a EBS volume for an EC2 instance.
Continue reading VVol Data Mobility: Data from Virtual to Physical