Release Notes

Virtual Volume operations
25 Dell EMC SC Series and VMware vSphere Virtual Volumes Best Practices | 3161-BP-SC
6.2 Snapshots
Snapshots created through vSphere with the vSphere Web Client or PowerCLI result in SC Series array-
based snapshots of the type “Managed”. SC Series arrays support up to 16,000 snapshots depending on the
controller model. These snapshots will be maintained with no expiration on the array until they are deleted
through vSphere. Unmanaged snapshots of a Virtual Volume occur outside of vSphere. Examples would be
the creation of a snapshot using Snapshot Profile, Dell Storage Manager, or Dell PowerShell SDK.
Managed versus Unmanaged snapshots of a Data vVol
Note: Snapshots of virtual machines with Virtual Volumes is not supported if the virtual machines use VMFS
or RDMs for storage.
6.3 Renaming
Renaming a virtual machine will not automatically result in the renaming of its associated Virtual Volumes. If it
is desired that vVol names match the changed virtual machine name, migrate the virtual machine to a
different datastore. vSphere will automatically change the associated names during the migration process.
Optionally, migrate the virtual machine back to its original storage container to ensure storage policy
adherence.
6.4 Deletion
Much like the creation of Virtual Volumes, the deletion of Virtual Volumes occurs through virtual machine
operations. Powering off a virtual machine results in the unbinding and deletion of the Swap vVol. Deleting a
virtual machine from inventory instructs the SC Series array through the VASA Provider to delete respective
Config and Data vVols including any Data vVol snapshots which may exist.
Note: vVols cannot be deleted through Dell Storage Manager. Removal of a storage container through Dell
Storage Manager cannot occur until all child vVols have been removed from the storage container through
vSphere.