Upgrade HPE StoreVirtual VSA From V11.0 To V12.0 on HyperV 2012 R2 Cluster #SCVMM #VMM

7 Min. Read

Hello folks,

Finally! HPE released the updated version for Lefthand OS V12.0.
Why? Well there are some features that were announced a quite some time ago that we are waiting for, and which become available now.
LeftHand OS Version 12.0 includes the following enhancements:

Space Reclamation—Reclaim space on thinly and fully provisioned volumes used by Windows Server 2012 or later, and vSphere 5 or later.
StoreVirtual Multi-Path Extension Module (MEM) for vSphere—Provides data path optimization similar to StoreVirtual DSM for Microsoft MPIO.
New REST API for StoreVirtual—Enables automation and scripting of clusters, provisioning and volume management.
StoreVirtual VSA term license management—Enforces term licensing for StoreVirtual VSAs.
Support for Microsoft System Center Virtual Machine Manager 2012 R2. Awesome! Open-mouthed smile
Faster remote copy performance and system reboot times.

A few blogs ago, I showed you how to deploy HP StoreVirtual VSA V11.0 on Hyper-V 2021 R2 Cluster.

You can find the 3 part series below:

Part 1: here
Part 2: here
Part 3:

So make sure to read the previous posts before moving along with the upgrade process.

In today’s blog post, I will show you how to upgrade an existing HP StoreVirtual Infrastructure from V11.0 to V12.0.

HP recommends that you always upgrade to the latest versions of software for the HP StoreVirtual VSA including:
• Firmware
• LeftHand OS
• Centralized Management Console (CMC)
• StoreVirtual VSA
• HP StoreVirtual Command-line Interface (CLI)
• HP StoreVirtual DSM for MPIO
• Application Aware Snapshot Manager

Before we start upgrading the storage virtual Infrastructure, we need to plan first.

Upgrade Plan

1- Verify the StoreVirtual version you are currently running and the upgrade path to the new release.
2- Verify the health of the current storage VSA systems and management groups before you start the upgrade.
3- Validate the health of your Hyper-V Cluster (Test-Cluster).
4- If you are running iSCSI load balancing, verify that a VIP is configured on each cluster.
5- Plan for volume access and the impact the upgrade will have to iSCSI sessions.
6- Schedule maintenance window time for the upgrade.
7- Upgrade the HP StoreVirtual VSA Storage components.
8- Keep and save all log files for HP support if needed.
9- Test the StoreVirtual Infrastructure after the upgrade.

Assuming that you verified your existing StoreVirtual VSA Infrastructure including your Hyper-V cluster and everything is healthy!

HP VSA System:


Hyper-V Cluster 2012 R2:


We will move now to Point 7 according to the plan.

You must upgrade the HP StoreVirtual Storage components in the following order:
Step 1. Upgrade Centralized Management Console (CMC) including the Command-Line Interface (CLI).
Step 2. Upgrade StoreVirtual DSM for Microsoft Windows MPIO.
Step 3. Upgrade LeftHand OS (VSA) and Failover Manager (FOM).
Step 4. Upgrade remaining HP StoreVirtual Application Integration Solution Pack components such as System Center Virtual Machine Manager (SCVMM).

One important note to remember, do not make any configuration changes to the management groups in the Configuration Interface. Otherwise, the upgrade might fail.

To get the updated bits, you have two options:

Option 1. Using the Centralized Management Console (CMC), click Help→Preferences→Upgrades.



Option 2. Download the updated bits manually from HP StoreVirtual Portal here.

Step1. Upgrading the CMC and the CLI

The CMC and CLI can be upgraded independently of the LeftHand OS software and other HP StoreVirtual Storage components. Be aware that some patches may require an upgrade to the CMC before
installing the patch.

1. Ensure that you have Administrator privileges before starting the upgrade.
2. Launch the CMC installation.
3. Follow the instructions on the installation wizard to complete the upgrade.



The Command-line Interface (CLI) upgrade is straight forward as well, launch the installation and follow the instructions in the wizard.

1. Ensure that you have Administrator privileges before starting the upgrade.
2. Launch the CLI installation.
3. Follow the instructions on the installation wizard to complete the upgrade.




Step 2. Upgrading the StoreVirtual DSM for Microsoft Windows MPIO

1. Ensure that you have Administrator privileges before starting the upgrade.
2. Launch the HP StoreVirtual DSM for Microsoft MPIO Installer.
3. Follow the instructions on the installation wizard to complete the upgrade.
4. Repeat the steps below on each Hyper-V Cluster Node.


Step 3. Upgrading the LeftHand OS and Failover Manager

You can upgrade the storage systems and Failover Managers within a management group or upgrade all the storage systems in the Available Systems pool. When upgrading a management group, the system determines how many storage systems can be upgraded simultaneously while ensuring quorum and volume availability. When upgrading storage systems in the Available Systems list, all storage systems (HP StoreVirtual VSAs and HP StoreVirtual Failover Managers) are upgraded as well.

One important point to mention, if you are running the promotional 1TB license of StoreVirtual VSA or the license is expired, you cannot upgrade to V12 and you are permitted to install urgent patches only.



I am running the 10TB version in my demo so I am entitled to the upgrade Winking smile

1. Ensure that you have Administrator privileges before starting the upgrade.
2. The upgrade must be done through the Centralized Management Console (CMC) only and not through the standard setup.
3. Using the Centralized Management Console (CMC), click on Recommended Patches Available→Upgrades.
4. When you see an upgrade for a management group or for available systems, click Install or Continue next to the item you want to upgrade.



5. Click Install. This is an automated process where every node will be updated 1 at the time so that your volumes remain online (if you have quorum of course – majority of managers).




6. Save the upgrade information to a file, and click Export Information


A quick check proves that my VSA infrastructure is updated to V12.0 Open-mouthed smile.




Let’s now validate the new enhancements in LeftHand OS Version 12.0 for Windows Server 2012 R2 and System Center Virtual Machine Manager 2012 R2:

• Space Reclamation—Reclaim space on thinly and fully provisioned volumes used by Windows Server 2012 or later.
• Integrate HP StoreVirtual VSA v12.0 and SCVMM 2012 R2 using SMI-S

Enable Space Reclamation

Space reclamation is enabled manually at the Management Group level.  Right Click your Management Group and Select Enable Space Reclamation.


Next, you will receive a warning message that once upgraded, you cannot downgrade to previous versions of LeftHand OS that do not support space reclamation.


I suggest checking your Device and RAID status to ensure that everything is OK before Enable Space Reclamation. This is done by selecting your Cluster, followed by the Node and then selecting Storage.

As you can see my RAID Status is Normal.


Enter your Management Group name, in my case HYPERV-MGMT-GROUP1 and accept the disclaimer and Enable Space Reclamation.


Note: You need to make sure that you have at least 3GB of RAM on your VSA systems in order to enable space reclamation, however the recommended amount of memory is 4GB.


After enabling Space Reclamation on the LeftHand OS, please make sure to perform the following steps from the host Hyper-V server:
1. Perform a rescan of the disk devices from the host server to ensure that Space Reclamation is registered with the host server.
2. Run defragmentation on existing volumes from the host OS, to ensure that you are maximizing the available space to be reclaimed.

It is recommended to conduct this process during non-peak production times, as performance may be impacted. The following are the steps to rescan and defragment your CSV volume:



Space Reclamation Test

Space Reclamation provides the capability for the LeftHand OS to request freed space from thinly and fully provisioned volumes and make that space available for new data storage. Space in Virtual Machines may be freed up by deleting files, moving data from one volume to another, and other activities that change the space used in the cluster.

Space reclamation can be performed either on the Hyper-V Cluster Shared Volume after a Storage Migration has taken place or when files have been deleted from within the guest OS.

In this test I’m going to perform a copy of fixed VHDX with 12GB of ISO images to a thinly provisioned Cluster Shared Volume 40GB. Then I will delete the fixed VHDX to force UNMAP (Space Reclamation) to take effect, and watch the space consumed of the Size of the LUN on the VSA, It drops as the data I deleted is in the active part of the LUN. Pretty awesome Open-mouthed smile


After copying the fixed VHDX

  • Volume – 13.45GB consumed space
    • 40GB Thin Provisioned volume with Adaptive Optimization enabled


After deleting the fixed VHDX

  • Volume – 512MB consumed space
    • 40GB Thin Provisioned volume with Adaptive Optimization enabled


Monitoring Space Reclamation

HP have introduced some extra performance statistics to monitor space reclamation which includes:

  • IOPS Space Reclamation
  • Total Latency Space Reclamation (UNMAP)
  • Queue Depth Space Reclamation

These can be accessed by added to the Performance Monitor window so that you can verify the effect of space reclamation on your Store Virtual infrastructure.


Integrate HP StoreVirtual VSA V12.0 and SCVMM 2012 R2 using SMI-S

As I mentioned in the previous post Part 3, System Center Virtual Machine Manager 2012 R2 was not supported with HP VSA LeftHand OS V11.0, however things has been changed now with V12.0.

What are the requirements for the integration?

• Windows Server 2012 R2 Hyper-V hosts.
• SCVMM 2012 R2.
• If you are using Fibre Channel, this only supported using SCVMM Server 2012 R2.

SCVMM storage device discovery and registration

System Center Virtual Machine Manager and Windows PowerShell require an IP address of the storage SMI-S provider to discover, register, and interact with the storage device. Use the Virtual IP Address (VIP) of the cluster to ensure high availability and failover protection.

Open the Fabric workspace in VMM, browse to the Storage, then right click on Providers and select Add Storage Devices.

Select SAN and NAS devices discovered and managed by a SMI-S provider


The cluster virtual IP address of the VSA can be added as storage provider. When adding the Provider IP address make sure you use SSL encryption for the communication, default port (TCP 5989), and protocol SMI-S CIM-XML as showing in below screenshots:


Next, click Import the certificate.



After the provider has been added successfully, all clusters in your StoreVirtual management group will be listed in the Classification and Pools list. New volumes can be provisioned from the available storage pools, used by new virtual machines and presented to Hyper-V hosts that are managed by Virtual Machine Manager via iSCSI.


Click Finish.


And here you go HP VSA Storage Infrastructure completely managed by SCVMM 2012 R2. Fantastic! Open-mouthed smile


SCVMM rapid provisioning provides a method to quickly deploy new virtual machines on top of block storage devices without copying the virtual machines over the network. SCVMM requests a
copy of an existing LUN on the block storage device. The LeftHand OS uses SmartClone volumes for this scenario. SmartClone volumes are fully featured volumes that derive from a snapshot
configured as a clone point of an existing volume.


I hope this in depth article has been informative for you, and I would like to thank you for reading!

Until next time… Enjoy your day!



Windows Server Hyper-V DEMO03: Production Checkpoints

Microsoft Unveils New HyperV Containers Technology and Nano Server For The Next #WindowsServer #CloudOS


Let me know what you think, or ask a question...

The content of this website is copyrighted from being plagiarized!

You can copy from the 'Code Blocks' in 'Black' by selecting the Code.

Please send your feedback to the author using this form for any 'Code' you like.

Thank you for visiting!