I have installed version 5 yesterday. Again it looks great. I think version 4 was already a big breakthrough but this one is even bigger!
However I am having some difficulties understanding the "virtual labs".
We have two location with both their dedicated EMC SAN. Both location have a physical server (Win2003 Enterpise) with Veeam Backup installed.
We use both location as active-active, so we backup data on both sides. This means that the Domain Controller with the FSMO roles is at location A and that the Exchange 2010 server is on location B. This means that I can not use the Domain Controller with the FSMO roles because it is backupped at location A and the backup files are not accesible to the backup server at location B. Is there a workaround for this (something else than creating a mapped drive to the location B, and import the backup)?
So now I am trying to use the DC that is at location B (same location as the Exchange 2010 Server).
I have created an Application Group:
1 DomainController (has the DNS, Domain Controller and GC roles, not DHCP). Also this is not the DC that has the FSMO roles.
1 Exchange 2010 Server.
Both server are Windows 2008 R2 (English), and have fixed ip-addresses.The Domain Controller has ip-address 10.1.10.25/24, gateway is 10.1.10.1. The Exchange Server has ip-adress 10.1.10.150/24, same gateway.
I have created a Virtual Lab with a proxy appliance (Basic). Her are the settings:
Lab name: Exchange Recovery
ESX name: esxaureool07.roermond.lokaal
Pool name: Exchange Recovery
Folder name: Exchange Recovery
IP: <Obtain automatically>
DNS: <Obtain automatically>
Network configuration type: Basic
Isolated network: Exchange Recovery VLAN10
Masquerade IP: 10.255.0.0
Appliance IP: 10.1.1.1
VLAN10 --> Exchange Recovery VLAN10
I have created a job with the Virtual Lab and Application group included, No linked backup jobs.
When I start the job, the VMs are created in VirtualCenter and the first VM (in this case the DC) is powered on.
So far, so good. When I look at the console the DC is starting fine, but because the Network Adapter is new (Exchange Recovery VLAN10), it looks like Windows 2008 R2 is creating a new adapter and the ip settings are reset to DHCP. The DC gets an ip-adres 10.1.0.1 As you can imagine this causes problems. The heartbeat, ping and application tests work fine. The next server that starts is the Exchange 2010 Server, this one has exactly the same problem as the DC, it gets the ip-address 10.1.0.2, during first startup. Because of this problem the Exchange Information Store will not start.
Is this standard behaviour? any help will be appriciated.
Thank you in advance.