Replication Job and network remapping

[lvfranz]

Hi, I have notice some trouble with network remapping in replication job.
I haven't done all test, but I see that if I create a job and set network remapping immediately, replicated vm gets the correct network configuration.
If I forget to set network remapping on the job, replicate the vm, and then set remapping option on the job, the vm continue not to get the remapped network.
I have tried deleting the replicated vm, and starting the job and also in this case, vm still doesn't get the correct network.

[Andreas Neufert]

2 things need to be in place in order to get the Re-IP working.
1) A Failover is started of a Windows VM, then we change the target replica VM at failover times.
2) Failover need to be happening with Network connected (if you choose to failover without network connection enabled, then we do not set the different IP).

If you want to test it in a save way, you can create a dummy non connected network switch on the replica target ESXi host and use it as mapped network.
Let the Replication job run.

If you then failover while production VM is running, the ReIP works but the network card is connected to the dummy network switch that is not connected to your production network.
Then after test change the network mapping to what you want to use at failover (or disable it).

Or maybe test with a test VM.

I have done this Re-IP change many times throughout the years at different versions after replication job was already present. It worked without issues. It could be a bug as well, but please test the above, then decide to open a support ticket if it is still not working.

[lvfranz]

I didn't doing Re-IP but Network remapping.
I have two vcenter both with dvswitch configured. All dvPortGroup defined on production dvSwitch are present also on the DR dvSwitch.
I need that all replicated VM get the same dvPortGroup as source.
If I leeave replication job without "Network Remapping" flagged option, all replicated vm has "Not Connected" NIC. (I think since dvportgroup has different id between dvswitch)
If I set "Network remapping" option, i get vm with network remapped only if option is present before first replication; if I set the option AFTER first replication, replicated vm has "Not connected" NIC.

[lvfranz]

I have done more test and confirm that if I create a replica job and set "Network Remap" immediately at job creation, network remap occurs.
If I try to create a replica job without setting "Network Remap", start the replica, and then I try to edit job and set "Network remap" option, this doesn't occurs.
I try to delete the replica vm and restart job without result.