Commvault IntelliSnap technology with VMware and the FlashArray

This is a post that is somewhat a long time coming as I did the work for this jeez basically in August 2015, but never got around to actually writing a blog post. Shame on me. Anyways, here it is!

Let us start with the requirements:

  • FlashArray 400 series or FlashArray//m
  • Purity v4.1.1 (or higher)
  • REST API: v1.4 (found in Purity v4.x and higher)
  • Fibre Channel or iSCSI Protocol
  • Commvault software version 10 service pack 12 or later with Commvault IntelliSnap software license

Some documentation links:

Pure Storage Community Commvault Page

FlashArray VMware & Commvault White Paper

Commvault VMware Setup

YouTube Demo Playlist

Continue reading “Commvault IntelliSnap technology with VMware and the FlashArray”

vRealize Orchestrator and Invoke a REST Host Workflow

Continuing my recent work on learning vRealize Orchestrator and ran into some funkiness with the “Invoke REST host” workflow, that I wanted to write down so I don’t forget how I fixed/worked around it (which I suppose is the impetus for basically every post I do). Anyways, I am working on a REST-based package for the FlashArray and I was using that workflow and had some trouble. Basically, any REST call I made through it to a REST host seemed to fail.

schema Continue reading “vRealize Orchestrator and Invoke a REST Host Workflow”

Site Recovery Manager and Raw Device Mappings (RDMs)

Somewhat surprisingly I have been getting a fair amount of questions in the past few months concerning VMware vCenter Site Recovery Manager and Raw Device Mappings (RDMs) and using this with Pure Storage. Common question is whether or not we support this (we do) but more commonly it is about how it works. There is a bit of a misunderstanding on how they differ or do not differ from VMFS management in SRM. So figured I would put a post out to explain this. Old topic somewhat, but worth reviewing for those newer SRM customers. Plus, I haven’t found a whole lot of on-point posts anywhere, so why not?

intro Continue reading “Site Recovery Manager and Raw Device Mappings (RDMs)”

VMFork, InstantClone, Project Fargo Oh My! Part 1: Walkthrough

One of the things in vSphere 6.0 that I really wanted to look at was the Instant Clone functionality that was included in the release. Instant Clone (AKA Project Fargo AKA VMFork) is the ability to essentially instantly create new virtual machines that are identical copies of a running parent VM by sharing the current memory and virtual disk files of that parent. The “forked” VMs are basically resumed copies of a stunned parent and the disk write/memory changes are committed down to delta VMDKs or delta memory pages while the children continue to read from any unchanged data in the parent VMDKs.

Fargo-poster

Plenty of other people have gone into more detail on this and the architecture, so instead of me re-writing all of this check out this post from Duncan Epping:

http://www.yellow-bricks.com/2014/10/07/project-fargo-aka-vmfork-what-is-it/

Or Google it.

Cool stuff. So I plan on doing a few different posts on this, tons of thoughts how this could be used, this first post though will focus on just simply setting it up. Continue reading “VMFork, InstantClone, Project Fargo Oh My! Part 1: Walkthrough”

VMware SRM and the PBM & PreCloneCheckCallback error

Quick post here. I recently updated my environment to vCenter 6.0 Update 1 and VMware Site Recovery Manager 6.1 and after my first attempted test failover (and subsequent ones) the test would always fail when it tried to power on the virtual machines. Some powered-on and some didn’t. The following errors appeared for about half of my VMs:

error

Continue reading “VMware SRM and the PBM & PreCloneCheckCallback error”

FlashArray and VMware documentation update for vSphere 6

I have completed updates for two of my main VMware vSphere documents for the Pure Storage FlashArray. These include the standard best practices document and the white paper explaining VAAI in detail and how it works on the FlashArray.

vmwarebpvaai

 

 

 

 

 

 

 

 

Best Practices Document Link

VAAI White Paper Link

The best practices document has mainly been updated with information that this blog has shown in the past couple of months. Notably:

  • vSphere 6 updates, support for Web Client Plugin versions, changes in virtual disk recommendations, in-guest UNMAP support, etc
  • VMFS UNMAP changes when it comes to best practice recommendations
  • vRealize Operations Management Pack
  • EFI-enabled VMs and Disk.DiskMaxIOSize

In the VAAI document, it is a similar update:

  • vSphere 6 changes, mainly focused on the thin virtual disk XCOPY enhancements
  • UNMAP changes, block counts, performance and in-guest support (EnableBlockDelete)

Both documents are also updated for FlashArray//m, but it is mainly a cosmetic change as nothing really changes for the VMware environment, no recommendations are changed. Of course the documents are also cleaned up and re-arranged to be more reader friendly with a semi-new format as well.

Important! If you have old versions of these documents, delete them! These get updated frequently (a few times a year at least) and these changes can be important. When needing to refer to the guides, please check back to the Pure Storage community for the latest version.

Enjoy! As always feedback on these documents is ALWAYS welcome.

 

UNMAP Block Count Behavior Change in ESXi 5.5 P3+

I recently was doing some troubleshooting for a customer that was using my UNMAP PowerCLI script and discovered a change in ESXi 5.5+ UNMAP. The issue was that the script was taking quite a while to complete. After some logic optimizations and increasing timeouts the script was sped up a bit and less timeout errors occurred, but a bunch of the UNMAP operations were still taking a lot longer than expected. Eventually we threw our hands up and said it was good enough. A bit more recently, I was testing a 3rd party UNMAP tool and ran into similar behavior so I dug into it a bit more and found some semi-unexpected changes in how UNMAP works, specifically the behavior when leveraging non-default block iteration counts. Continue reading “UNMAP Block Count Behavior Change in ESXi 5.5 P3+”

Changing an ESXi SATP Rule

One of the few hard requirements we make to configure best practices on ESXi for the FlashArray is to create a SATP rule. A SATP rule simply describes a certain configuration (mainly around multipathing) for a specific set of devices (usually devices from an array). For the FlashArray, this rule consists of making sure devices are using Round Robin and an I/O operations limit of 1.

esxcli storage nmp satp rule add -s VMW_SATP_ALUA -V PURE -M FlashArray -P “VMW_PSP_RR” -O iops=1 -e “FlashArray SATP Rule”

Continue reading “Changing an ESXi SATP Rule”

FlashArray //m and VMware Integration–What do you need to know?

Last week Pure Storage introduced the latest iteration in the FlashArray product line: the FlashArray //m. While Pure Storage has traditionally focused on software innovation from a technical standpoint, we decided that the only way to stay ahead of (and lead) the curve was to innovate in the hardware realm as well. Therefore, for the last few years, development on producing a hardware platform that could keep up with compute and storage speed and capacity leaps has been at full tilt. This produced the brand new FlashArray //m.

product--flash-array-m--front-bezel-angled-left--shadow2

Continue reading “FlashArray //m and VMware Integration–What do you need to know?”

Querying SRM for Protected VMs with PowerCLI

I was recently asked how to query SRM for protected VMs and I decided it would make a good quick blog post. There is a great post here on using PowerCLI with SRM, but it doesn’t show the information to return per virtual machine information by default. Needs a bit more.

All it returns is a SRM-based virtual machine ID which doesn’t relate to what a user is probably looking for (a virtual machine name). So it needs a few more simple steps. The following script which can be found on my GitHub page here that does the following things:

  1. Connects to a vCenter
  2. Connects to SRM
  3. Creates a log folder with a time stamp in the name
  4. Iterates through each Protection Group
  5. Logs every virtual machine in that protection group

Continue reading “Querying SRM for Protected VMs with PowerCLI”