Release Notes

Table 35. Known VMware Issues in Storage Manager 2019 R1 (continued)

Issue Description

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 .

Notes and Limitations

This section contains important notes and limitations for this release of Storage Manager.

Limitations in Unisphere

The following features are not currently available in Unisphere for Storage Manager 2019 R1.

• Chargeback

• Disaster recovery

• FluidFS management

• Live Volume and Live Migrate

• Managed servers

• Replication

• PS Series Group management

• VVols

Workaround for Performing a Planned Failover of LiveVolumes

in SRM 8.2

SRM 8.2 fails to send the ReverseReplication command to the Dell Storage Replication Adapter (SRA) during the planned failover of

LiveVolumes.

To resolve this issue, perform the following steps on the Windows servers that are running SRM 8.2 at both sites:

1. On the Windows server that is running SRM 8.2, open the vmware-dr.xml file in a text editor.

The default location of the vmware-dr.xml file is C:\Program Files\VMware\VMware vCenter Site Recovery

Manager\config\vmware-dr.xml.

2. Search for the XML tag <storage> in the file.

3. Add the following entry between the XML tags <storage> </storage> :

<forcePrepareAndReverseReplicationForNoopDevices>true</

forcePrepareAndReverseReplicationForNoopDevices>

4. Save the changes to the vmware-dr.xml file.

5. Restart the SRM services on the Windows server.