Creating virtual lab for Exchange 2010

[Vitaliy S.]

Michael, If you don't want to have your IP address reset while using VMXNET 3 adapters, please apply Microsoft's patch to fix this issue. Thanks!

[Gostev]

Hi Michael, workaround should still be in-place - please provide logs to the support and we will investigate. Although the patch is more reliable resolution for sure. Thanks!

[mpozar]

Hi Gents,
Thanks for that. I've applied the Patch from Microsoft for Windows 2008 R2 SP1 and that has resolved my problem. I don't know why Veeam B&R 6 is not doing it's thing in regards to this issue.
I'll raise a support case as soon as I get the chance..

Have FUN!

Michael

[Gostev]

Hi Michael, yes please open a support case since I have confirmed that our built-in VMXNET3 workaround should still work after upgrade. Thanks!

[markholmes]

[merged]

Hi,

I'm currently testing replication in VEEAM (6.0.0.154).

The replication side is working fine, but when I failover I find the replica VM is missing it's IP information.

So far I have tested a Windows 2k8R2 and a Linux (Centos 5) VM, both with exactly the same result - the networking has been reset to the default (DHCP) rather than the static IP it should have.

I'm guessing I'm missing a simple setting somewhere...? Note:I'm not using the re-ip or network remapping features here, I want the replica to have exactly the same IP and use the same virtual network as the source.

I also have a support ticket open for this, but in case anyone has a quick answer...?

Regards,

Mark Holmes

[Vitaliy S.]

Mark, please review this topic for the resolution as it is also applies to your case.

[markholmes]

Hi Vitaliy,

This only applies to WIn 2008 R2 though, right? I'm having this issue with a Linux (CentOS) box as well..

Thanks,

Mark

[tsightler]

Most Linux distro's will likely also have a problem since the majority of them now use udev rules to bind the ethX interfaces to specific MAC addresses, or at least add the MAC to the interface configuration. Unless you are using static MAC addresses, the MAC addresses on the replica will be different from the source. There are other posts on the forum that describe workarounds to this issue for various distro's.

[markholmes]

I'm using static MAC addresses

[markholmes]

Scratch that - I'm not using static MAC, I can see that vCenter recognises the duplicate MAC and changes it.

How to work around this? Can I make a MAC static?

[dellock6]

Yes, you can edit mac address of the network adapter and set a fixed MAC address. It's in the properties of the virtual hardware.

Luca.

[markholmes]

Never noticed that before - I'll put in a static one now. Thanks Luca.

[stefanpeters]

I am currently creating this setup for a client also. And I noticed the IP address going wrong in the lab. I have manually changed the IP addresses to the correct ones and that works.

What is the best practive, fix the MAC address and / or use e1000 instead of vmxnet3?

Thanks
Stefan

[Cokovic]

Fixing the MAC address is not necessary for Windows based systems. Either use e1000, or install a patch provided by Microsoft if you are using Windows Server 2008 R2 (SP1) and VMXNET3. You will find the links in this thread.

[mbeckey]

[merged]

I am testing Veeam 6.1 to replicate VM guests to our DR site. Testing all other versions of 2003 and 2008 server the MAC address stays the same and the replica will power on with the production VM IP address as long as the prod VM is shutdown. With 2008 R2 SP1 the MAC address on the replica is being changed by VMware and a DHCP IP address is being grabbed. The test environment I am using is using VM hosts ESX 4.1 update 1 and just using the local disk on the hosts as the data stores. I have seen other posts on this topic but there doesn't seem to be any concrete resolutions.

One work around I did find is to manually change the mac address on the replica to what match the prod MAC address. I would not like to do this step if at all necessary.