Turning up Secondary GC

  • Thread starter Thread starter Joshua
  • Start date Start date
J

Joshua

Greetings,

I'm running a native Win2k domain with 2 domain
controllers and Exchange 2000. When I take down my DC that
has GC running on it I lose my exchange functionality due
to the GC coming off line. I'd like to prevent losing my
exchange functionality by turning up a second GC server. I
understand I'll have to turn up a 3rd DC to do this, but
I've found no documentation on this.

My couple questions are -

1.) Is this possible? Or even common practice?
2.) How long does the GC replication take? Will it still
be automatic?
3.) Am I taking the wrong path for a solution on this one?
Is there another method of solving this problem with
Exchange when GC goes down that I'm just overlooking?

Thank you in advance,
Joshua
 
If you only have one domain then the GC restriction does not apply if all
DCs are also GCs
 
Hi Richard,

With one single domain model, the GC restriction will not be applied.
BUT, if we have the child domain, will the GC restriction be applied ?

Thanks,
J.H
Richard McCall said:
If you only have one domain then the GC restriction does not apply if all
DCs are also GCs

--
Richard McCall [MSFT]

"This posting is provided "AS IS" with no warranties, and confers no
rights."
Joshua said:
Greetings,

I'm running a native Win2k domain with 2 domain
controllers and Exchange 2000. When I take down my DC that
has GC running on it I lose my exchange functionality due
to the GC coming off line. I'd like to prevent losing my
exchange functionality by turning up a second GC server. I
understand I'll have to turn up a 3rd DC to do this, but
I've found no documentation on this.

My couple questions are -

1.) Is this possible? Or even common practice?
2.) How long does the GC replication take? Will it still
be automatic?
3.) Am I taking the wrong path for a solution on this one?
Is there another method of solving this problem with
Exchange when GC goes down that I'm just overlooking?

Thank you in advance,
Joshua
Click to expand...
Click to expand...
 
The gc is not recommended to be on the same dc that holds the IF role for
one reason, and that is because if it is changes made to an object in
domainA that also exist in domainB will not be properly updated in domainA
(clear as mud <g>) For example, if "tom" belongs to domainA, but also
belongs to say, a security group in domainB as well, and changes are made to
that group in B, the change will not be properly noted in A becaue the IF
will not pick up the change if it is on the same dc as a gc. That's because
IF keeps its logs and periodicaly does a comparison with the gc logs to look
for differences (read new changes), and if it is on the same box as a gc,
then when gc is updated the IF log is also updated, so when it does it's
comparision (to look for changes/differences) it never sees any. Thus it
would never notify the dc's in A of the change since it didn't see any.
As noted, in a single domain, since all dc's have all the same info anyway,
it doesn't make a difference if all dc's are gc's or only some (or where the
IF role is).
In multi domain models (like yours with child) the importance of that
relationship between domains may, or may not, be important with regards to
IF and gc since we don't know about your network. But the recommendation
for multiple domain networks not to have a gc on the same box as the IF
would be true. (obiviously exception with single dc domains)

--
David Brandt
Microsoft Corporation

This posting is provided "AS IS" with no warranties, and confers no rights.
Please do not send e-mail directly to this alias. This alias is for
newsgroup purposes only.
J.H said:
Hi Richard,

With one single domain model, the GC restriction will not be applied.
BUT, if we have the child domain, will the GC restriction be applied ?

Thanks,
J.H
Richard McCall said:
If you only have one domain then the GC restriction does not apply if all
DCs are also GCs

--
Richard McCall [MSFT]

"This posting is provided "AS IS" with no warranties, and confers no
rights."
Joshua said:
Greetings,

I'm running a native Win2k domain with 2 domain
controllers and Exchange 2000. When I take down my DC that
has GC running on it I lose my exchange functionality due
to the GC coming off line. I'd like to prevent losing my
exchange functionality by turning up a second GC server. I
understand I'll have to turn up a 3rd DC to do this, but
I've found no documentation on this.

My couple questions are -

1.) Is this possible? Or even common practice?
2.) How long does the GC replication take? Will it still
be automatic?
3.) Am I taking the wrong path for a solution on this one?
Is there another method of solving this problem with
Exchange when GC goes down that I'm just overlooking?

Thank you in advance,
Joshua
Click to expand...
Click to expand...
Click to expand...
 
Back
Top