Solved

Domain Controller - DR design best practices

Posted on 2010-08-25
8
1,517 Views
Last Modified: 2012-05-10
Hello there;

OK So we are setting up a new environment for a Client and we want to make the best design plan possible.

DR_Project  
Site 1 (left):  Production environment   (2 DC )

AD1: DHCP, DNS, CG & Holds all 5 FSMO Roles

AD2: DHCP,DNS,CG

Site 2 (right): DR Site (1 DC)

AD: DHCP,DNS,CG

Required:

Best design plan for DHCP,DNS,CG,FSMO, domain design "i.e child domain"

After hours of reading I reached a conclusion that we don't really need to make any changes to  FSMO Roles & we don't need to have a child domain on the DR site.

- Both sites "Production and DR" can be on the same domain in one single forest.
- First domain controller will be hosting all Five FSMO roles and there is no need to transfer or  or seize it.

If AD one goes offline and no hope of getting it back online:

-  seize FSMO roles to AD2

If the hole production site goes offline and there is no hope of getting it back online:

-  seize FSMO roles to DR AD


- Split the DHCP pool between 3 servers

- Make DNS available on 1st DC and DR DC


My question is: what do you think about this setup ?

Thanks  
0
Comment
Question by:atigris
[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
  • 3
  • 2
  • 2
  • +1
8 Comments
 
LVL 10

Accepted Solution

by:
dhruvarajp earned 167 total points
ID: 33523296
i would say GOOD design .. let us have the different Active directory sites for both physical sites
configure replication interval as less as 15 minutes

and have then different subnets and configure DHCP servers for 80-20 rule
http://technet.microsoft.com/en-us/library/cc958936.aspx 

Dhruv
0
 
LVL 2

Author Comment

by:atigris
ID: 33524332
OK very good, How about DNS ? what is your though on that ? Thanks
0
 
LVL 10

Assisted Solution

by:Dextertronic
Dextertronic earned 166 total points
ID: 33527956
I use the same setup betwen our core prod site and our remote DR site.
I'm assuming you have two different subnets with associated AD sites.
Tested successfully including Exchange failover using Doubletake.
Straight forward and simple to support.
AD replication is pretty good for what it does.
 
 
0
Does Powershell have you tied up in knots?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 
LVL 1

Assisted Solution

by:perplexd
perplexd earned 167 total points
ID: 33539277
Child domains just add extra complexity. If you need different domain password policies, or you want completely separate administrators to be delegated control of a child company, then that might be of value, but otherwise it is complexity that doesn't buy any value.

I think your design looks good - KISS.
0
 
LVL 2

Author Comment

by:atigris
ID: 33567468
well,
- I could create 2 sites this way the  replication dose not have to be over the hole domain.
- each site on it's own subnet.
- NO need to use child domains.
- DHCP use 80-20 rule & use SuperScope to simplify DHCP administration.
- Primary and Secondary DNS server on the production site and one DNS on the DR site.
- NO need to change  FSMO roles - all roles can be on first created machine.
- All machines can be Global Catalog server.

 
0
 
LVL 2

Author Closing Comment

by:atigris
ID: 33567478
no complete answer was provided.
0
 
LVL 10

Expert Comment

by:dhruvarajp
ID: 33567494
about dns
you already have inclused a that in the ADC on the DR site
0
 
LVL 1

Expert Comment

by:perplexd
ID: 33583853
You only need superscopes if you have a multi-net.
http://technet.microsoft.com/en-us/library/cc757614(WS.10).aspx

Otherwise your plan looks good to me.

0

Featured Post

Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

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

Many businesses neglect disaster recovery and treat it as an after-thought. I can tell you first hand that data will be lost, hard drives die, servers will be hacked, and careless (or malicious) employees can ruin your data.
After seeing many questions for JRNL_WRAP_ERROR for replication failure, I thought it would be useful to write this article.
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles from a Windows Server 2008 domain controller to a Windows Server 2012 domain controlle…
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…

707 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