Issues with replication of domain controller URGENT

[mblackmore]

Hi

We replicate our environment to a DR site every night. In order to do our DR testing perform a failover, do our testing, then undo failover. In the past this has worked well, but trying to do a test now and it is becomming a nightmare, spent two full days trying to resolve, Really need to get a DR test in before EOY

We have two domain controllers, 1 virtual which we replicate and 1 physical which we do not.

Primary site is ESX 4.1
DR Site is ESXi 5.5

Veeam is configured correctly for replications, checked with Veeam support.

The issues we are having is
1) when booting the DC from the replica, no clients can login, they get an error saying "there are not domain controllers available......" login to the DC and try load ADUC, get errors "naming information cannot be located because: The specified domain either does not exist or could not be contacted"

2) doing anything on this VM only takes a very long time, login takes 15 mins, things like my computer etc take upto a minute to load etc, other VMs running at the DR are runing at expected speed (DR server / Storage is of HIGH spec)

3) The network on the DC is classed as unidentified, not domain.

[Vitaliy S.]

Hi Michael,

What kind of network adapter is used on the source DC VM? BTW, is it a Windows Server 2008 R2 DC?

Thanks!