FRS Issues - question before doing BurFlag D2

  • Thread starter Thread starter getkevin
  • Start date Start date
G

getkevin

Hello and thank you for reading.

I have a Win2000 SP4 AD setup with three DC's in the replica. I had a
power circuit issue yesterday and DC1 went down and when the server
booted, I noticed Journal errors in the FRS logs. FRS service starts
and runs just fine, it's just items in the NETLOGON (login scripts)
aren't syncing to DC1. I ran repadmin /showreps and all the neighbors
responded as successful so I think I am in good shape to begin fixing.

I've been reading many articles (including KB290762) trying to
identify when I should do D2 (non-authoritative) or the D4
(authoritative) re-initialization of the replica. DC1 is the guy
having trouble and is also holds the five FSMO roles. DC2 and DC3
have working FRS and are syncing just fine. Is there a way to
identify who is the replica master or has the authoritative copy of
the replica (forgive me if I have the jargon wrong)? It seems that if
the server in trouble is the authoritative server, you need the D4
option, otherwise using D2 will be fine. Or am I interpreting what I
am reading wrong and I should just try D2 first to update the local
copy? Thank you!

KW
 
Hello and thank you for reading.

I have a Win2000 SP4 AD setup with three DC's in the replica. I had a
power circuit issue yesterday and DC1 went down and when the server
booted, I noticed Journal errors in the FRS logs. FRS service starts
and runs just fine, it's just items in the NETLOGON (login scripts)
aren't syncing to DC1. I ran repadmin /showreps and all the neighbors
responded as successful so I think I am in good shape to begin fixing.

I've been reading many articles (including KB290762) trying to
identify when I should do D2 (non-authoritative) or the D4
(authoritative) re-initialization of the replica. DC1 is the guy
having trouble and is also holds the five FSMO roles. DC2 and DC3
have working FRS and are syncing just fine. Is there a way to
identify who is the replica master or has the authoritative copy of
the replica (forgive me if I have the jargon wrong)? It seems that if
the server in trouble is the authoritative server, you need the D4
option, otherwise using D2 will be fine. Or am I interpreting what I
am reading wrong and I should just try D2 first to update the local
copy? Thank you!

KW
Click to expand...
If you have a good working copy of your sysvol in your domain and you have
an upstream (Good replicating partner) then you want to do a
non-authoritative restore. Which is to say that another DC has a good copy
of the sysvol to provide back to this dc's sysvol.

If you were to do an authoritative restore then all data from the DC you set
as authoritative would overwrite the sysvol in all other dc's and this isn't
what you want in your situation.

So you want D2 - nonauthoritative mode restore

--
Paul Bergson
MVP - Directory Services
MCT, MCSE, MCSA, Security+, BS CSci
2003, 2000 (Early Achiever), NT

http://www.pbbergs.com

Please no e-mails, any questions should be posted in the NewsGroup
This posting is provided "AS IS" with no warranties, and confers no rights.
 
Thank you Paul, a firm answer from a trusted source, I couldn't ask
for more... but I will :)

How long should this process last taking into account the 5-10 minutes
or so needed to transfer ~500mb worth of data on NETLOGON?

Kevin
 
I can't imagine you sysvol is that large. I wouldn't think more than 5
minutes.

--
Paul Bergson
MVP - Directory Services
MCT, MCSE, MCSA, Security+, BS CSci
2003, 2000 (Early Achiever), NT

http://www.pbbergs.com

Please no e-mails, any questions should be posted in the NewsGroup
This posting is provided "AS IS" with no warranties, and confers no rights.
 
Yes it is that large unfortunately. There is about ~250mb tied up in
just the Policies folder and I have a Policies_NTFRS_xxxxxxxx that has
duplicate info. I will investigate this issue once I am done with
fixing the replication problem.

Thanks again.
 
those are morphed folders...

see:
http://www.microsoft.com/technet/pr...ry/maintain/opsguide/part1/adogd11.mspx#EEGAC
--

Cheers,
(HOPEFULLY THIS INFORMATION HELPS YOU!)

# Jorge de Almeida Pinto # MVP Windows Server - Directory Services

BLOG (WEB-BASED)--> http://blogs.dirteam.com/blogs/jorge/default.aspx
BLOG (RSS-FEEDS)--> http://blogs.dirteam.com/blogs/jorge/rss.aspx
------------------------------------------------------------------------------------------
* How to ask a question --> http://support.microsoft.com/?id=555375
------------------------------------------------------------------------------------------
* This posting is provided "AS IS" with no warranties and confers no rights!
* Always test before implementing!
------------------------------------------------------------------------------------------
#################################################
#################################################
------------------------------------------------------------------------------------------
Yes it is that large unfortunately. There is about ~250mb tied up in
just the Policies folder and I have a Policies_NTFRS_xxxxxxxx that has
duplicate info. I will investigate this issue once I am done with
fixing the replication problem.

Thanks again.
On Feb 15, 10:21 am, "Paul Bergson [MVP-DS]" <pbergson@allete_nospam.com>
wrote:
I can't imagine you sysvol is that large. I wouldn't think more than 5
minutes.
Click to expand...
Click to expand...
 
Good catch Jorge. I didn't pay enough attention to the last set of details.

I believe Jorge is right on. When this dc came back online it appeared that
the folders it had were named the same but not in sync with the other dc's
so it made a duplicate copy and replicated those out to the other dc's.

http://support.microsoft.com/kb/328492/


--
Paul Bergson
MVP - Directory Services
MCT, MCSE, MCSA, Security+, BS CSci
2003, 2000 (Early Achiever), NT

http://www.pbbergs.com

Please no e-mails, any questions should be posted in the NewsGroup
This posting is provided "AS IS" with no warranties, and confers no rights.

"Jorge de Almeida Pinto [MVP - DS]"
those are morphed folders...

see:
http://www.microsoft.com/technet/pr...ry/maintain/opsguide/part1/adogd11.mspx#EEGAC
--

Cheers,
(HOPEFULLY THIS INFORMATION HELPS YOU!)

# Jorge de Almeida Pinto # MVP Windows Server - Directory Services

BLOG (WEB-BASED)--> http://blogs.dirteam.com/blogs/jorge/default.aspx
BLOG (RSS-FEEDS)--> http://blogs.dirteam.com/blogs/jorge/rss.aspx
------------------------------------------------------------------------------------------
* How to ask a question --> http://support.microsoft.com/?id=555375
------------------------------------------------------------------------------------------
* This posting is provided "AS IS" with no warranties and confers no
rights!
* Always test before implementing!
------------------------------------------------------------------------------------------
#################################################
#################################################
------------------------------------------------------------------------------------------
Yes it is that large unfortunately. There is about ~250mb tied up in
just the Policies folder and I have a Policies_NTFRS_xxxxxxxx that has
duplicate info. I will investigate this issue once I am done with
fixing the replication problem.

Thanks again.
On Feb 15, 10:21 am, "Paul Bergson [MVP-DS]" <pbergson@allete_nospam.com>
wrote:
I can't imagine you sysvol is that large. I wouldn't think more than 5
minutes.
Click to expand...
Click to expand...
Click to expand...
 
Back
Top