Replication issues with Offline DC

[Guest]

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

We have three DC's in a Windows 2000 child domain. One of these DC's is
located in a seperate site in South America. The remaining two DC's are
located at the same location in the United States.

Because of power issues in South America (they loose power at least once a
day) they want to power down their DC for 17 days while that division is away
from work during the Holidays.

What adverse effect if any will that have on replication or anything else
while the DC is down and also when it is brought back online after 17 days?

Thanks for your Help...

 

[Guest]

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

Gary,

Having been in a similar situation myself I can tell you that we encountered
numerous problems with DCs that were turned off for a substantial amount of
time. I've found it to be easier to demote the DC and to re-promote it at a
later point in time, but that's just my experience.

One thing to consider if you do move forward with simply allowing it to be
powered down - you want to make sure that none of the FSMO roles are held on
that server as that could cause SEVERE problems for you.

JHK

"Gary Watters" wrote:

> We have three DC's in a Windows 2000 child domain. One of these DC's is
> located in a seperate site in South America. The remaining two DC's are
> located at the same location in the United States.
>
> Because of power issues in South America (they loose power at least once a
> day) they want to power down their DC for 17 days while that division is away
> from work during the Holidays.
>
> What adverse effect if any will that have on replication or anything else
> while the DC is down and also when it is brought back online after 17 days?
>
> Thanks for your Help...

 

[Guest]

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

"Gary Watters" <Gary Watters@discussions.microsoft.com> wrote in message
news:2FBEA78E-6F79-47A5-B152-5690CB055C0A@microsoft.com...
> We have three DC's in a Windows 2000 child domain. One of these DC's is
> located in a seperate site in South America. The remaining two DC's are
> located at the same location in the United States.
>
> Because of power issues in South America (they loose power at least once a
> day) they want to power down their DC for 17 days while that division is
away
> from work during the Holidays.
>
> What adverse effect if any will that have on replication or anything else
> while the DC is down and also when it is brought back online after 17
days?

You will get errors in your event logs due to the failed
replication. This is only a warning and a mild nuisance.


17 days will not cause a permanent problem however
60+ days might.

ONE SERIOUS CONCERN: Disable any DNS scavenging
or ensure that the times are set to EXCEED the loss of
connectivity time. ( refresh + norefresh intervals > 17 days).

 

[Guest]

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

If the offline time is less than tombstoneLifetime, then you will be ok (but
get a lot of warnings and info in the event viewer). Consider demote it and
then promote it after the holidays.

Regards,
/Jimmy
--
Jimmy Andersson, Q Advice AB
Microsoft MVP - Directory Services
---------- www.qadvice.com ----------


"Gary Watters" <Gary Watters@discussions.microsoft.com> wrote in message
news:2FBEA78E-6F79-47A5-B152-5690CB055C0A@microsoft.com...
> We have three DC's in a Windows 2000 child domain. One of these DC's is
> located in a seperate site in South America. The remaining two DC's are
> located at the same location in the United States.
>
> Because of power issues in South America (they loose power at least once a
> day) they want to power down their DC for 17 days while that division is
> away
> from work during the Holidays.
>
> What adverse effect if any will that have on replication or anything else
> while the DC is down and also when it is brought back online after 17
> days?
>
> Thanks for your Help...