Comprehensive data protection for all workloads
Post Reply
c.medina.morales
Novice
Posts: 4
Liked: never
Joined: Sep 05, 2011 4:01 pm
Full Name: Carlos Medina
Contact:

After replication, VMs in "Public" network

Post by c.medina.morales »

All,

We are using replication jobs for moving VMs between two datacenters.
Replication job goes fine, however there is a problem when we start the VMs in the new datacenter.
Windows 2008 R2 is booting in the "public" network in the target datacenter when it was in the "domain" network in the source datacenter

What we are doing is just the following:
-Shutdown the VM in the source datacenter
-Power on the VM in the target datacenter

Anyone facing this before?
Thanks in advance

Carlos
Vitaliy S.
VP, Product Management
Posts: 27055
Liked: 2710 times
Joined: Mar 30, 2009 9:13 am
Full Name: Vitaliy Safarov
Contact:

Re: After replication, VMs in "Public" network

Post by Vitaliy S. »

Hi Carlos,

What type of NICs are you using for Windows Server 2008 R2? Are these the only VMs that are affected by this behavior?

Thank you!
c.medina.morales
Novice
Posts: 4
Liked: never
Joined: Sep 05, 2011 4:01 pm
Full Name: Carlos Medina
Contact:

Re: After replication, VMs in "Public" network

Post by c.medina.morales »

Hi Vitaliy

We are using VMXNET3.
We have all VMs in 2008 R2.

Regards

Carlos
Gostev
Chief Product Officer
Posts: 31460
Liked: 6648 times
Joined: Jan 01, 2006 1:01 am
Location: Baar, Switzerland
Contact:

Re: After replication, VMs in "Public" network

Post by Gostev »

Have you mapped source site networks to correct target site networks in the wizard while setting up the replication job?
dellock6
Veeam Software
Posts: 6137
Liked: 1928 times
Joined: Jul 26, 2009 3:39 pm
Full Name: Luca Dell'Oca
Location: Varese, Italy
Contact:

Re: After replication, VMs in "Public" network

Post by dellock6 »

Guys, have you ever looked at this problem?
http://kb.vmware.com/selfservice/micros ... Id=1020078
It's well known among vSphere admins, infact every template and Vm made with 2008 R2 "and" vmxnet3 needs a defined set of patches applied, in order to keep the cloned/replicated VM from creating everytime a new network.

Luca.
Luca Dell'Oca
Principal EMEA Cloud Architect @ Veeam Software

@dellock6
https://www.virtualtothecore.com/
vExpert 2011 -> 2022
Veeam VMCE #1
Vitaliy S.
VP, Product Management
Posts: 27055
Liked: 2710 times
Joined: Mar 30, 2009 9:13 am
Full Name: Vitaliy Safarov
Contact:

Re: After replication, VMs in "Public" network

Post by Vitaliy S. »

Yes, Luca, this is exactly what I was trying to check, though as far as I remember there were some hotfixes for this issue released by Microsoft.
dellock6
Veeam Software
Posts: 6137
Liked: 1928 times
Joined: Jul 26, 2009 3:39 pm
Full Name: Luca Dell'Oca
Location: Varese, Italy
Contact:

Re: After replication, VMs in "Public" network

Post by dellock6 »

What I found out in the past is that some of the required patches are not distributed into the regular windows update, at least it was what I saw in the past, and I finished up downloading and applying singles patches. Or better, install them into a template, so any new VM is already good to go :)

Luca.
Luca Dell'Oca
Principal EMEA Cloud Architect @ Veeam Software

@dellock6
https://www.virtualtothecore.com/
vExpert 2011 -> 2022
Veeam VMCE #1
c.medina.morales
Novice
Posts: 4
Liked: never
Joined: Sep 05, 2011 4:01 pm
Full Name: Carlos Medina
Contact:

Re: After replication, VMs in "Public" network

Post by c.medina.morales »

All

We finally found a workaround, than you for all the answers.
When running the replication job, the VMs that were being created had a different MAC address
So we are doing a manual step during the replication to change the MAC address so is not changing
Not sure if this is the way it should work, but the workaround has allowed us to fix the issue

Regards

Carlos
Vitaliy S.
VP, Product Management
Posts: 27055
Liked: 2710 times
Joined: Mar 30, 2009 9:13 am
Full Name: Vitaliy Safarov
Contact:

Re: After replication, VMs in "Public" network

Post by Vitaliy S. »

Carlos, do you use static or dynamic MAC addresses on the source site? What version of Veeam B&R are you using? Anyway, MAC address should be preserved starting from v6.x

BTW, you didn't answer what network adapters you use for production VMs. Can you please clarify?
Post Reply

Who is online

Users browsing this forum: No registered users and 238 guests