Discussion Locked

Backup of Active Directory and Restore

0 helpful
9 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I'm a newbie to W2K and active directory and am doing a bit of research. In our network we will have multiple, (500+) W2K Servers, My question is this, as each new server is installed, at varying locations, the time for replication is steadily increasing as more and more 2K servers come online. Most of these servers are at remote sites with 128 kb frame connections. Is there a way to say backup a copy of Active directory from our corporate office to a CD maybe a week or a few days before a new remote server is installed and then ship the CD to the site and have AD pull the info from the CD, then replicate with the remaining servers. That way it would have a fairly recent copy of the database and possibly spend less time replicating? Is this even possible? If so, how would that be accomplished?

Thanks

9 replies

by cg it

500+ W2K hardware servers? The Topology for the domain would determine records replication to each DC in the domain. Active Directory Domains & Trusts would coordinate [allow]replication of AD across the network for the DC's. File replication is done at fairly regular intervals, [depends on what the admin set up for replication, usually couple times a day. Depends on the size and scope of the Domain] therefore making a copy of the record and storing it on CD wouldn't benefit you.

by timwalsh

Replication takes place between servers. There is no way to tell a server to pull info from a CD or any other media.

What does your AD architecture look like?

If you have multiple sites set up, you can schedule when a site replicates with another site. In your situation with the (relatively) slow links, you could schedule replication to occur during off hours. It looks like initial replication is your biggest bandwidth hog. At the very least schedule the initial replication (once a server is brought online) to take place during off-hours.

If all your servers are in a single site, or you have large numbers of servers within a site, you have more of a problem. Intra-site replication happens almost immediately once a change has occured. There is a configurable delay between the time a change takes place and the time it is replicated (default is 5 minutes).

Hope this helps.

by banyanman

Not quite sure of your setup, but if you have a vendor doing the install at the remote site, why not have the server shipped to your location first, making the build, getting initial replication, and then shipping out to the remote site, schedule the vendor, Then simply modify AD Sites and Services for the location/network change of the DC.

by jaystar

Install win2k server on a laptop, dc promo it, move it to the same site that the remote site will be installed to, and ship it to the remote site. When the new server comes on-line it will check for a server in it's site first to replicate from.when youmove the latop out of it's site after replication, the KCC will find it new partners.

Let me know if I can be of any more help.
Jay

This discussion is closed to new replies.