Symptoms:
If you first protect a VM in Array-Based Replication Protection Group(ARB), vSphere Replication Protection Group(VR), or vVols Protection Group and then attach the VM's NICs to a different network, SRM will continue using the network mapping related to the original VM configuration at the moment of protection.

VMware Site Recovery Manager 8.3.x
VMware Site Recovery Manager 8.1.x
VMware Site Recovery Manager 8.2.x

VM based protection groups(ARB, VR, and vVol) determines the target VMs network on the recovery site during the VM protection process by using site-wide network inventory mappings. The info is stored in SRM DB and used during failover to attach the recovered VMs to configured networks.
After the moment of protection, VMware Site Recovery Manager (SRM) continuously monitors for protected VMs location, inventory, and settings changes so to update its protection metadata.
That includes the automatic protection of new NIC devices, but if you reconfigure existing NIC to point to a different network, SRM will not react on this change and will continue to use the old network protection metadata.

Note: This issue is seen in VMware Site Recovery Manager 8.3 and earlier versions.

This issue is resolved in VMware Site Recovery Manager 8.3.1, available at VMware Download.


Workaround:
To workaround this issue, use one of the following:

• Override the used site-wide network mapping by configuring individual network mappings on affected VMs, see Configure Inventory Mappings for an Individual Virtual Machine in an Array-Based, vVols, or vSphere Replication Protection Group. 

• Remove the old NIC device and add a new one attached to the desired network. In this case SRM will automatically protect the new NIC device.

• Unprotect the whole VM and protected it again.