When you configure the system to use VMware vSphere Virtual Volumes, you might
encounter issues and limitations.
You can also search the VMware Knowledge Base information on the VMware website to verify
and troubleshoot your
Virtual Volume
configurations:
http://kb.vmware.com
Functions not supported in Virtual Volumes configurations
Virtual Volumes support cannot be
used in the following configurations:
- Metro Mirror
- Global Mirror
- HyperSwap systems
- SAS-attached hosts (VMware vSphere Virtual Volumes
restriction)
Deleting a virtual machine
After an attempt is made to delete a virtual machine (VM), the VM is marked as orphaned or
inaccessible on the VMware vSphere web
client. Virtual Volumes that are
associated with the virtual machine remain on the system.
This problem can occur in rare scenarios when the Spectrum Control Base Edition server cannot successfully complete
the deletion tasks on the system. Potential causes for this issue might be network connectivity
problems or scenarios where management CLI functions are intentionally limited, such as following a
tier-2 recovery.
To remove the VM and its associated
Virtual Volumes completely, follow these steps:
- Establish the cause of the issue and restore full communications between Spectrum Control Base Edition and your system.
- On the VMware vSphere web client,
remove the orphaned or inaccessible VM from your inventory.
- Reregister the virtual machine with your host.
- Right-click the virtual machine and select Delete from Disk to remove
the Virtual Volumes that are
associated with this virtual machine from the system.
VMs marked as inaccessible by the VMware vSphere web client
The command-line interface (CLI) was unavailable for an extended period, such as following a
Tier 2 recovery. VMs that were powered off before the event might be marked as inaccessible by the
VMware vSphere web client. These
virtual machines need to be removed from the inventory and reregistered.