Known issues and limitations with Virtual Volumes

Edit online

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

Unsupported functions in Virtual Volume configurations

Virtual Volumes support cannot be used in the following configurations:
  • Metro Mirror
  • Global Mirror

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 IBM Spectrum® Connect 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:
  1. Establish the cause of the issue and restore full communications between IBM Spectrum Connect and your system.
  2. On the VMware vSphere web client, remove the orphaned or inaccessible VM from your inventory.
  3. Reregister the virtual machine with your host.
  4. 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

In cases where the command-line interface (CLI) is unavailable for an extended period of time, 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. If this occurs, these virtual machines must be removed from the inventory and reregistered.