Solved

Issues with a domain controller running in a DR environment

Posted on 2013-12-17
21
1,314 Views
Last Modified: 2014-01-14
Hi

We replicate our environment to a DR site every night using Veeam backup and replication 7 patch 1. 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.
0
Comment
Question by:wsc-it
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 9
  • 3
  • 3
  • +3
21 Comments
 
LVL 57

Expert Comment

by:Mike Kline
ID: 39725627
So the DC in the DR site is a replica of the DC in primary?   Does that mean it is an exact copy?   Just trying to get a feel for what you have setup there.

Thanks

Mike
0
 

Author Comment

by:wsc-it
ID: 39725630
Yes it is a replica, Which is created using Veeam and is supported.

I am not replicating the DC2 however as it is a physical box.
0
 
LVL 57

Expert Comment

by:Mike Kline
ID: 39725636
Ok I won't blow smoke never used this scenario.  I'd just have another DC and have it replicate normally.  If Primary goes down then DC2 is still there and working.

It will be interesting to see the ideas.

Thanks

Mike
0
Portable, direct connect server access

The ATEN CV211 connects a laptop directly to any server allowing you instant access to perform data maintenance and local operations, for quick troubleshooting, updating, service and repair.

 
LVL 3

Expert Comment

by:WiReDWolf
ID: 39725641
Is the subnet the same?  This sounds like a DNS issue.  If on the same subnet, possibly an ARP Cache issue or a change in IP address?  For instance, the DNS client ooking for a DNS server at an address that currently doesn't exist.
0
 

Author Comment

by:wsc-it
ID: 39725648
Sorry, I do have that scenario running

two DCs, one virtual, one physical, in production running fine

BUT part of our Disaster Recovery plan is to have all virtual machines replicated to our DR site every night, then in event of DR test, or disaster you can fire them up and use them

So, Im replicating DC1 only, each night using Veeam, but upon boot i am plagued with issues.
0
 

Author Comment

by:wsc-it
ID: 39725652
Yes the subnet / network infrastructure is also replicated at the DR site, so all IP addressing etc remains the same, just in an isolated network obviously.
0
 
LVL 3

Expert Comment

by:WiReDWolf
ID: 39725659
Probably a stupid question but where is the GC?
0
 

Author Comment

by:wsc-it
ID: 39725660
I believe both the DCs are a GC
0
 
LVL 10

Expert Comment

by:Korbus
ID: 39725685
I'm confused.  How does the virtual test machine run on an isolated network?  Doesn't it need the physical DC to performe some roles?

You could test:  How does the virtual machine run in the production environment WITHOUT the physcial DC connected?  Do you get the same problems as in your test environment?
0
 

Author Comment

by:wsc-it
ID: 39725686
We have two DCs in our prod environment, One is virtual, one is physical, called DC1 (virtual) and DC2 (Physical) Now they replicate between each other fine and everything works fine.

Now, nightly, we use Veeam to perform a backup replication to another ESX server at a remote site on an isolated network.
0
 
LVL 10

Expert Comment

by:Korbus
ID: 39725692
So, does DC2 (physical), or a virtual copy of it, exist at the remote test site?

Perhaps I am misinterpreting replication...  do you mean the whole server using virtualization, or just active director replication?
0
 

Author Comment

by:wsc-it
ID: 39725698
Using virtualization replication, for DR use only.

No DC2 does not exist at remote site.
0
 
LVL 37

Expert Comment

by:Mahesh
ID: 39726083
What is the OS version of both domain controllers ?

Mahesh
0
 
LVL 5

Expert Comment

by:Steve M
ID: 39726816
I have a lot of questions to try to get a better idea of your environment...

When DC1 is brought online on the isolated DR network, does it retain the same IP address?
Does DC1 also run DNS services or is there another DNS server on that isolated network?
Do all the PC's on that isolated network point to the correct DNS server?
Does the DC1 point to the correct DNS server?
Is the isolated Network the same network address/subnets as your production?
0
 
LVL 5

Accepted Solution

by:
Steve M earned 500 total points
ID: 39726877
Something else you should know is who has the FSMO roles in your domain.  I suspect that the replicated DC should have all these roles, but here's how you check..

on your production domain (any domain member pc/server):
Command Prompt, type the following and hit enter> NetDOM /query FSMO

The results should be something like this:
Schema master               dc1.yourdomain.com
Domain naming master        dc1.yourdomain.com
PDC                         dc1.yourdomain.com
RID pool manager            dc1.yourdomain.com
Infrastructure master       dc1.yourdomain.com
The command completed successfully.

As I said, I'd expect that all these roles should be on the replicated dc (DC1), if not you should likely consider moving them off the physical DC over to the virtual DC.

./Steve
0
 
LVL 3

Expert Comment

by:WiReDWolf
ID: 39727716
The other aspect is one I know very little about which would be how the networking on the ESXi 5.5 is configured.  A VLAN configuration assigned to the physical NIC's could interfere, or a misconfigured vSwitch.  Or the NIC assigned to the DC is in on the Management Switch and not on the same vSwitch.  

On the replicated DC in the virtual offsite environment do you still have Internet access?  Once the DC finally boots and lets you get to a desktop can you hit google or any other websites?  Can it also see any replicated virtualized workstations on the same ESXi host?

I can practically guarantee the issue is related to DNS but without hands-on I can't quite see the answer, unfortunately.
0
 

Assisted Solution

by:wsc-it
wsc-it earned 0 total points
ID: 39766596
I resolved this myself thank you, Had to force seize of the fsmo roles on the DR site, and all is well
0
 

Author Comment

by:wsc-it
ID: 39768893
I've requested that this question be closed as follows:

Accepted answer: 0 points for wsc-it's comment #a39766596

for the following reason:

I was able to resolve this myself.
0
 
LVL 37

Expert Comment

by:Mahesh
ID: 39767249
If you could share exact issue ad resolution you done for knowledge sharing, it will be great

Mahesh
0
 
LVL 5

Expert Comment

by:Steve M
ID: 39768894
Did I not help find this resolution on my post "ID: 39726877" when I said "Something else you should know is who has the FSMO roles in your domain. I suspect that the replicated DC should have all these roles"?

/Steve
0
 

Author Closing Comment

by:wsc-it
ID: 39778788
I was able to resolve this myself, as above
0

Featured Post

Comprehensive Backup Solutions for Microsoft

Acronis protects the complete Microsoft technology stack: Windows Server, Windows PC, laptop and Surface data; Microsoft business applications; Microsoft Hyper-V; Azure VMs; Microsoft Windows Server 2016; Microsoft Exchange 2016 and SQL Server 2016.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Always backup Domain, SYSVOL etc.using processes according to Microsoft Best Practices. This is meant as a disaster recovery process for small environments that did not implement backup processes and did not run a secondary domain controller that ne…
I was prompted to write this article after the recent World-Wide Ransomware outbreak. For years now, System Administrators around the world have used the excuse of "Waiting a Bit" before applying Security Patch Updates. This type of reasoning to me …
This Micro Tutorial hows how you can integrate  Mac OSX to a Windows Active Directory Domain. Apple has made it easy to allow users to bind their macs to a windows domain with relative ease. The following video show how to bind OSX Mavericks to …
Are you ready to implement Active Directory best practices without reading 300+ pages? You're in luck. In this webinar hosted by Skyport Systems, you gain insight into Microsoft's latest comprehensive guide, with tips on the best and easiest way…

691 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question