11.5 HP StoreVirtual Storage Release Notes

Running Register-SCStorageLogicalUnit on an array of LUNs causes the LUNs to be
assigned to multiple storage groups
A single LUN can belong to only one storage group. If the commandlet
Register-SCStorageLogicalUnit is run on an array of LUNs, then the
Get-SCStorageLogicalUnit on a particular volume will return an invalid configuration.
To fix this issue, perform the following steps:
1. Unregister the volumes using the command Unregister_SCStorageLogicalUnit.
2. Run the SCStorageLogicalUnit commandlet again on each individual volume.
Storage Migration does not delete the source storage; it is copied instead of moved
When migrating the storage of a virtual machine from one volume to another, the original storage
is not totally removed and will display in both locations.
Update-StorageProviderCache fails with a Timeout
If running the commandlet Update-StorageProviderCache -Discoverylevel Full
and more then one storage provider is registered, it results in the following error message:
Update-StorageProviderCache : Timeout.
To resolve this issue, run the update command and indicate the individual provider (for example,
Update-StorageProviderCache -Discoverylevel -Name 10.1.16.113 ). If you
have a lot of providers and run the update command without a specific provider indicated, the
command could take a long time to finish.
Storage Migration fails when a virtual machine is running on a Windows Server 2012 Hyper-V
host
Storage migration fails when a virtual machine is powered on and is hosted on a Windows Server
2012 Hyper-V host. The virtual machine is down after this failure with some of the files representing
the virtual machine still on the old volume, and some of the files representing the virtual machine
moved to the new volume. Currently there is no workaround.
NOTE: The problem is limited to Windows Server 2012 Hyper-V hosts.
Registered providers have a blank value in the Arrays column until a manual refresh is done
The Array column in the provider screen on SCVMM will initially be blank after provisioning a
storage provider. To resolve this issue do one of the following:
Refresh or rescan the provider.
Restart SCVMM.
Classification Available Capacity value is wrong but the Storage Pool Available Capacity value is
correct
This reporting error is due to an issue with the Microsoft SCVMM 2012 SP1, and will be fixed
with SCVMM 2012 R2. To determine the capacity remaining in the cluster, do one of the following:
View the Storage Pool Available Capacity field in SCVMM.
Correct the display on the Storage Pool by refreshing the provider on the provider tab.
View the Use Summary tab in the StoreVirtual CMC cluster category.
Workarounds 23