After a distributed portgroup is removed, it is possible the MSA may not be able to show the list of networks. Workaround: Restart the MSA service. (DRBC-7063)
Changes to per-network routing tables are not propagated to already deployed appliances. (DRBC-7586)
If the DRVA connection to the replication log disk is disrupted (iSCSI network failure or temporary datastore disconnection), it may lead to protected VMs becoming unresponsive until an internal network timeout is reached. The condition is transient and should resolve itself after a period of time. (DRBC-7046)
If the network between the DRVA and object cloud becomes disconnected for a prolonged period, it is possible replication may not be able to restart after the network issue has been resolved. To continue replication, restart the DRVA appliances manually. (JSDRAVS-111)
If the network between host(s) and the DRVA becomes unstable (establishing a connection randomly fails), it is possible the IO Filter daemon may hang. Workaround: To resume operation, migrate VMs from the affected host(s) and then restart the host(s). (DRBC-7296)
It is not possible to configure a proxy server for stateless appliance external communication. However, the MSA can be manually configured to reach external sites through a proxy. (DRBC-7794)
If the network between hosts and DRVA is momentarily disrupted, it is possible for slowdowns to occur on VMs protected using writeback mode. This is related to the default network configuration on the hosts. The condition is transient and should resolve itself after a period of time. (DRBC-7082)
Under some conditions the MSA will display an alert the DRVA is not accessible even though respective DRVA VMs are online and report IP through VMware tools. Workaround: Restart the MSA service. (DRBC-7950)
If the network communication between the MSA and vCenter is unstable during test failover, the MSA may not be able to clean up test VMs after TFO has been completed. Workaround: Manually delete the leftover test VMs. (DRBC-8177)
Foreground replication may become stuck if the DRVA internal network is down intermittently. Workaround: Restart the DRVA service. (DRBC-8351)