Release Notes

Table 5. Known issues in Storage Manager 2020 R1 (continued)
Issue Functional area Description Workaround/Resolution
of the individual disks and the number of
snapshots of the VM.
DSM-14570 VMware 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.
Ignore the error message, and register
VASA Provider with a Storage Manager
Data Collector user with Administrator
privilege.
DSM-14149 VMware 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.
Reapply the new storage policy after
Storage vMotion has completed.
DSM-13316 VMware 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.
Unmount and then remount the datastore.
DSM-13042 VMware 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.
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 either sequential operations
or operations with interjected delays.
DSM-12732 VMware 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.
None
DSM-11417 VMware 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.
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 .
11