Release Notes

Table 5. Known issues in Storage Manager 2020 R1 (continued)
Issue Functional area Description Workaround/Resolution
DSM-16248 VMware On rare occasions, selecting Update
information in the Dell Storage
Manager Server view results in the
error java.net.SocketException:
Unexpected end of file from
server.
Despite the vCenter appearing to be
online and able to accept connections, the
vCenter must be restarted to reestablish
proper connectivity between Dell Storage
Manager and vCenter.
DSM-15879 VMware The Host Setup wizard for VMware does
not allow you to select an HBA on an ESXi
host that contains adapters that are not
VMware software iSCSI adapters. When
establishing an integrated environment
with Dell Storage Manager and VMware,
there are multiple options available for you
to import the VMware known inventory
into Dell Storage Manager for enhanced
management benefits. You can choose to
add hosts individually, or by creating and
registering from a vCenter server.
Although the option exists in the Storage
tab to create from vCenter server, the
preferred and more reliable method is to
use the Dell Storage Manager Server tab.
Select the Server folder and then Register
Server > Add VMware vCenter Server.
Then, select Auto Manage Storage
Centers to populate the Storage Center.
DSM-15803 VMware On rare occasions, when a vVol VM
is migrated from one vVol datastore to
another, a config or data vVol might
become orphaned on the original datastore.
This vVol counts against the total vVol
scale and takes up unnecessary space.
Contact technical support to handle the
removal of the VM.
DSM-15302 VMware If you attempt to delete a datastore which
is populated (not empty) using the Storage
Manager Client, an error occurs. A false
indicator of connectivity is represented by
a red X on the vCenter server.
Click the Update Information button in the
top-level menu.
DSM-15000 VMware A vVol VM snapshot with quiesce guest
file-system option fails.
Install the VMware Tools without the VSS
feature. For more information, see VMware
Knowledge Base article number 2069952.
DSM-14997 VMware When using sDRS with vVols, vCenter
incorrectly recommends migrating the VM
when both vVols are on the same Storage
Center.
Review the recommendations from
vCenter before taking action.
DSM-14891 VMware A fast clone VM shows history with the VM
from which it was created. Hence the data
vVols of this clone VM inherit the settings
of the data vVols of the original VM.
This shared history also has the following
consequences:
● Changing the Data Reduction profiles
for a storage container might cause
future fast cloned VMs to be created
with mismatched Data Reduction
profiles for the config 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.
None
DSM-14806 VMware 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
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.
10