Replication Question

[nag9127]

I am adding a second domain controller to a site for the purpose of replication for disaster recovery purposes. I have several questions that my research has not provided clear answers. This is a relatively simple network with AD primarily housing user names, passwords, and network shared resources such as printers. These are the only domain controllers on the network, both running Windows Server 2003 in the same site. Should I just install AD on this second controller and let it replicate automatically with the first controller or would it be a better idea from a control point of view to generate the replicated data from a media backup? Don't consider network throughput to be a concern as I am sure the replication would be uneventful with respect to network overhead and bandwidth, and I will do this during closed hours. Also how should I manage DNS on the second controller from the standpoint of disaster recovery in the event of a problem with the first controller and also from the standpoint of the the initial replication? Should I make the second domain controller a global catalog server or just leave that designation to the first controller only? Thanks for any input!!!

 

[pagy]

Just dcpromo it and let replication occur. Add the DNS service (via add/remove windows components) to your new DC and, assuming your zones are AD integrated, the dns data will replicate as well. Your job will be done!!!!


As for the GC, what else do you have on the network? any exchange servers? how many users?

Paul
MCSE


"Two things are infinite: the universe and human stupidity; and I'm not sure about the the universe."
Albert Einstein

 

[nag9127]

Thanks for the post pagy....

My network is very simple, no exchange server, no web page server, just a domain controller and 2 database servers, all running Server 2003 SP2. The database servers are running SQL Server applications with data storage. About 35 users across two different applications, all running on the same site.

With respect to making the second controller a GCS, my goal is to be able to relatively routinely move from one domain controller to another in the event of a system failure on my existing domain controller.

Thanks for your input!

 

[pagy]

Making it a GC certainly won't hurt anything so yeah, go ahead and make it a GC.

Paul
MCSE


"Two things are infinite: the universe and human stupidity; and I'm not sure about the the universe."
Albert Einstein