Restore recovered virtual machine will be disconnected.

[Tank13]

Dear, I use version 6.5 with 20 hosts with more than 300 VMs on site A that are replicating to site B in another region using vreplication. So long. However, due to semi-routine restore testing, this is the problem. When I restore VMs the interfaces are not recognized automatically and I make this manual every step of entering VM configurations, ie a lot of work. How can I automate?

Thiago

[rcporto]

So, what you mean with "interfaces are not recognized automatically"? You mean the virtual machine network adapter is not connected to a port group on remote site? The port group name are the same on both sites? Are you using just vSphere Replication to perform the failover or are you using Site Recovery Manager? Switches at Main and DR site are both same type (standard or distributed)?

[Tank13]

Hi Richard, thanks for your feedback.
What I mean is that when restoring the VM in Site B I need to manually make the choice of Distribuited SW and this leaves my recovery very slow. Unfortunately I do not use SRM. The switches are allocated on site A and site B. The name of the vDS in site A is (vDS-DATA-A) and in site B (vDS-DATA-B) This impacts for the VM to recognize which one used the site When do I do recovery

[diegodco31]

Hi

vSphere Replication disconnects virtual machine network adapters to prevent damage in the production network. After recovery, you must connect the virtual network adapters to the correct network.

Recover Virtual Machines with vSphere Replication

For your scenario the ideal would use SRM, with SRM you will be able to do the network mapping of the main site and DR. The tool itself will already connect the network to VMS ..

If this answer has helped you, please mark it as answered.