Release Notes
Issue Description
• Changing a storage container’s Data Reduction proles might cause future fast cloned VMs to be
created with mismatched Data Reduction proles for the cong and data VVols.
• If a user applies a VM Storage Policy to the original VM, the same changes apply to the data VVols
of the fast clone VM and conversely.
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 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 suciently 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-14301 The Datastore Connectivity tab in the Storage Manager Data Collector user interface is blank when
viewing a datastore on a vCenter 6.0 server or an ESXi 6.0 host.
Workaround: Use the vCenter or ESXi 6.0 client to view connection information.
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 insucient space when it tries to
create a VM.
Workaround: Unmount and then remount the datastore.
DSM-13274 The Dell Storage Manager VASA Provider, whether using VASA1 or VASA2, can have only one vCenter
server registered to it at any time. You cannot register multiple vCenter servers to the Dell VASA
Provider at the same time. If you register a vCenter server to Dell Storage Manager and then register
the server to the Dell VASA Provider, you rst must unregister the server from the VASA Provider
before registering a dierent vCenter server to the Dell VASA Provider.
Workaround: If you try to register any vCenter server to the Dell VASA Provider, and the registration
fails, make sure that no other vCenter servers are registered to the Dell VASA Provider.
DSM-13042 Under rare circumstances, usually involving VVol operations (cloning and snapshots) on multiple VMs
concurrently using scripting and eventual deletion of VVols, an attempt to delete a VVol VM might
result in VVols not being deleted. This scenario results in inecient 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-12728 In rare occurrences, the space consumption information for a volume might be blank.
Workaround: Close and reopen your client.
Storage Manager 2018 R1 Release Notes 29