Virtual Volumes (vVols) Customers Software-Defined Storage Technology Partners

Automating vVols DR with Power CLI 6.5

One of my favorite updates in vSphere 6.5 is the support for array-based replication with Virtual Volumes (vVols). Now with VASA 3.0 storage vendors have the ability to configure array-based replication into their VASA providers allowing users to preconfigure VM Storage Policies that include replicating VMs for Disaster Recovery. Support for Array-based replication was by far biggest request we have seen from customers interested in using vVols See What’s new in Virtual Volumes 2.0 for a closer look at how this works.vvol-dr

So what happens when I want to actually failover to these replicated VMs? Well, for vSphere 6.5 there are two choices.  You can leverage the public API or you can use PowerCLI 6.5.  That’s right, new in PowerCLI 6.5 is the ability to manage vSphere policy-based storage. For detailed information and examples for managing vSphere Policy-Based Storage with PowerCLI check the VMware vSphere 6.5 Document Center.



Sample Scripts

A few examples of what you can now automate with PowerCLI are listed below:


Planned Failover Example

Below is an example of the sample script “invoking a planned failover on a replication group” and then “initiating reverse replication“. In this example I am using Nimble Storage but the PowerCLI cmdlets will work on any VASA 3.0 certified VASA Provider.  Be sure to check the VMware HCL for compatibility.



  • vSphere admin credentials


  • A VM in a vVols datastore configured with a VM storage policy containing replication


Disclaimer:  This is only an example.  It works great in my environment.  That doesn’t mean it will work in yours.  VMware supports PowerCLI but custom scripts like this are not supported.

Huge shoutout to Nimble Rockstar Julian Cates for helping me with this script.  I could not have done it without his expertise.

VM Failover with PowerCLI on Nimble Storage

In our VMworld 2016 session Julian Cates and I demonstrated a planned failover of a vVols VM.  If you haven’t already, be sure to check out Nimble’s implementation of Virtual Volumes on Nimble OS 3.  In this demo video you will see the following:

  • There is a VM on the source side called Barcelona Demo.
  • There is no replicated copy of this VM on the target side
  • The script kicks off.
  • The VM is removed from the source vCenter Inventory
  • The VM is brought online at the destination
  • Refreshing the view on the destination array shows that the previous replicas are now online volumes.

What about SRM?

So does this mean I can now use Site Recovery Manager (SRM) with vVols? Yes and no. Yes SRM 6.5 is the first version to offer support for Virtual Volumes but only using vSphere Replication.  vSphere 6.5 addresses the largest DR use case we see with automated DR via either public API or Power CLI. Will SRM support vVols for Array-Based Replication you ask?  Well I am not a Product Manager and have no official response to this question but I would definitely stay tuned for more info on that in a future release. 🙂


The long awaited vVols support for Array-Based Replication has made Virtual Volumes a real option for production workloads. Using PowerCLI organizations can now experience the true value of vVols and Storage Policy-Based Management with automated data protection and disaster recovery.


2 comments have been added so far

  1. Doesn’t it require a sync-spbmreplicationgroup in planned failover, in case it’s not fully synchronized before failover?

Leave a Reply

Your email address will not be published. Required fields are marked *