HP 3PAR Grow a Virtual Volume

One of the virtual volumes used in a Microsoft Failover Cluster was almost full (~43MB space left) therefore we needed to grow the virtual volume (VV) to prevent downtime or should I say minimise as some VMs were already in a paused state due to insufficient disk space.

The virtual volume in question was not part of a remote copy group, it exists purely for VMs that are to remain bound to a specific datacenter and never move between DCs.

To grow the virtual volume I used the growvv command while connected to the 3PAR CLI. It is also possible to grow a VV using the management console GUI.


Connect to the 3PAR using your SSH client of choice.

As you can see the command is very simple – we append the virtual volume name followed by a growth increment. In this instance the VV was expanded by an additional 1 terabyte. As all my volumes are thinly provisioned I don’t mind increasing the size by a decent amount.

A warning message is presented when you export a volume larger than 2TB, in this instance I confirmed my command and grew the volume.


To expand via the GUI is very easy. As stated above the volume is not in a remote copy group – if it had been then the process would be slightly different and I will cover this in a separate post.

Open the management console and browse to the virtual volume. Right click and choose to edit –

Edit Virtual Volume

You will see the Size field, all you have to do is alter the value in this field to grow the volume to your desired size.

Next Steps

Once the 3PAR had grown the VV (essentially this was instantaneous) I went to Microsoft Failover Cluster Manager to see which of my servers currently owned the disk. Once I found the owner I connected to it, opened disk management and extended the volume in Windows.

Check Failover Cluster Manager for Disk Owner

Free Space Showing

Right Click Extend Volume

01 Extend Volume Wizard

02 Extend Volume Wizard Select Disks

03 Completing the Extend Volume Wizard

Once the Windows finished extending the disk it displayed as a 2TB volume and the low space issue was resolved. As always the full help for the command is displayed below for reference.



Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.