Release Notes

Table 35. Known VMware Issues in Storage Manager 2019 R1 (continued)
Issue Description
Workaround: None
DSM-14806 Migrate or Clone operations on virtual machines with snapshots might fail if not enough space
is available in the vVol datastore hosting the VM. The temporary space overhead that is
required by these operations depends on the size of the individual disks and the number of
snapshots of the VM.
Workaround:
1. Check if the vVol datastore (storage container) is nearing capacity.
2. Increase the size of the vVol datastore to sufficiently accommodate the overhead and then
retry the operation.
DSM-14570 If you attempt to register the VASA Provider with a DSM user with Reporter privilege, it
fails as expected. However, an incorrect error message Username or password is
incorrect is reported. The correct error should be user with Reporter privilege
is not allowed to register VASA provider.
Workaround: Ignore the error message, and register VASA Provider with a DSM user with
Administrator privilege.
DSM-14149 If you try to apply a new VM Storage Policy while Storage vMotion of a VM is in progress, the
compliance status of the VM goes to Out of Date.
Workaround: Reapply the new storage policy after Storage vMotion has completed.
DSM-13316 After increasing the storage container size in Dell Storage Manager, the vCenter user interface
shows the datastore with the new size. However, it still displays an error for insufficient space
when it tries to create a VM.
Workaround: Unmount and then remount the datastore.
DSM-13042 On rare occasions, if vVol operations (cloning and snapshots) are occurring on multiple VMs
concurrently using scripting that results in the eventual deletion of vVols, an attempt to delete
a vVol VM might result in vVols not being deleted. This scenario results in inefficient space
consumption and reduction in total vVols available for future use.
Workaround: Removal of the vVols is not a user-level corrective option. Contact technical
support for assistance. Avoid running concurrent vVol operations using scripting. Instead,
script sequential operations or operations with interjected delays.
DSM-12732 It is possible to create a storage container, and a subsequent vVol datastore using it, of a
logical size that exceeds the physical capacity of the storage array. The capacity values that
are displayed in vCenter for an oversubscribing container reflect the correct free or total
physical capacity values instead of the logical storage container values.
Workaround: None
DSM-11417 When high availability (HA) is configured, vVols are migrated from the active host to the
standby host when management network access to the active host is lost. This situation
is similar to VMFS, and is the expected behavior. However, if only the data network goes
down, VMFS datastores migrate to the standby host, but vVols do not fail over. VMCP is not
supported with vVols.
Workaround: No workarounds are available when the data network goes down, but the
management network stays up. However, if the management network to the active host goes
down, failover is triggered, regardless of the state of the data network .
20