Create a DC for Disaster Recovery

G

Guest

Guest
Archived from groups: microsoft.public.win2000.active_directory (More info?)

I want to create a DC for Windows 2000 Active Directory service for disaster
recovery site, and I will perform the testing on the DR site as well.

How do I do it so the DC in the DR site will work fine?
 
G

Guest

Guest
Archived from groups: microsoft.public.win2000.active_directory (More info?)

There are a number of things that need to be configures on the DR DC to get
it working.

There are SIX AD functions (5 FSMO Roles & Global Cat) that an AD Domain
needs
a server/s to take care of as well as DNS. When one of the DCs
dies you will have to transfer/seize the roles it held to a remaining DC (in
this case the single DR DC).
Also be aware of other Network Server Services that you will/may have to
move/restore/re-create, such as IIS, DHCP, Certificate Server, License
Servers, etc.

Check out:
http://support.microsoft.com/default.aspx?scid=kb;en-us;257288&Product=win2000
http://support.microsoft.com/default.aspx?scid=kb;en-us;216498
http://support.microsoft.com/default.aspx?scid=kb;en-us;255504
http://support.microsoft.com/default.aspx?scid=kb;en-us;255690

Hope this helps,
--
Yor Suiris
Remove the kNOT to reply.
But it is best to share it with the group.

"Simon Li" <SimonLi@discussions.microsoft.com> wrote in message
news:E18AEF3B-1C6C-4EFE-BBFA-5C3CAB2263CC@microsoft.com...
>I want to create a DC for Windows 2000 Active Directory service for
>disaster
> recovery site, and I will perform the testing on the DR site as well.
>
> How do I do it so the DC in the DR site will work fine?
 
G

Guest

Guest
Archived from groups: microsoft.public.win2000.active_directory (More info?)

In addition to what Yor has provided, I'd like to add or expand on a couple
of things if I may.

The most important thing is DNS. This DR-site DC needs to be running DNS
(AD-Integrated is preferable) and pointing to itself and at least one other.
Depending on the site and speed of the links between this site and the main
site, you should also define a site and appropriate site link costs. You
may want to increase replication frequency. If you know that you will
fail-over to this DC in the event of a failure, you should manually add a
connection object between this DC and the current FSMO role holder. You
will want to ensure that this DC is up-to-date when things go wrong.

When you run testing there are a couple of things you should consider:

If you have legacy clients you *have* to seize the PDCe role ASAP. This
isn't a big deal however, as this is one of the most flexible roles -you can
bring the old one back up and there shouldn't be an issue; you can just
transfer it again.

You should only seize the FSMO roles if the original DC isn't able to be
restored. If you are going to restore it do that. The AD can get by
without the roles for a while. The only one that effects users is the PDCe,
and that not as much in pure NT5.x domains (although it still can
obviously). (My point about the PDCe above is the exception to this
statement on seizing).

If you run WINS, this box should be a WINS server and replication partner.

This DC has to be a GC.

Clients have to point to this DNS server (unless there are other DNS servers
available that are still online). If you're using a dedicated DR site it
might be worth have the DNS server as a third DNS server for all TCP/IP
clients in the main site or sites.

--

Paul Williams

http://www.msresource.net/
http://forums.msresource.net/

"Simon Li" <SimonLi@discussions.microsoft.com> wrote in message
news:E18AEF3B-1C6C-4EFE-BBFA-5C3CAB2263CC@microsoft.com...
I want to create a DC for Windows 2000 Active Directory service for disaster
recovery site, and I will perform the testing on the DR site as well.

How do I do it so the DC in the DR site will work fine?