Re: SYSVol Replication - Multiple Locations
From: Richard Chinn [MSFT] (rchinn_at_online.microsoft.com)
Date: 02/07/05
- Next message: Arvind: "ADAM: Setup Application-Specific Directory"
- Previous message: Lennart Svenssson: "ERROR MESSAGE EVERY 5 MINUTES IN THE EVENT VIEWER"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 07 Feb 2005 00:04:50 -0800
Sysvol and AD are replicated via two different mechanisms. Sysvol is
replicated by FRS, so if you are having problems with Sysvol
replication, you need to look at FRS, not AD.
If you've started xcopying files around, you're 'helping the
replicator" which will actually make things worse. When you do manual
copies, FRS sees changes on several machines and attempts to transfer
the data. To get things running again, you need to wait for FRS to
settle down or take more drastic action like an authoritative (aka D4)
restore. If you've been doing several xcopies, then you may have to
do the D4.
You can disable the ntfrs service, but as you know, replication will
stop. You'd need to handle replication yourself and be sure to keep
sysvol and netlogon shared out. Sometimes this is a fair temporary
measure until you can get FRS running again.
You may want to try installing Ultrasound or Sonar to help monitor
replication once you get it running again. Its difficult to know what
caused your initial problems given that the system has been dealing
with xcopy "help."
--Richard
Please post FRS related questions to
microsoft.public.windows.server.dfs_frs and prefix the subject line
with "FRS:" to make it easier to spot. Note that FRS is used to
replicate SYSVOL on domain controllers and DFS root and link targets.
For additional FRS resources, please visit
http://www.microsoft.com/frs.
This posting is provided "AS IS" with no warranties, and confers no
rights.
On Fri, 28 Jan 2005 09:13:04 -0800, Allen Firouz
<AllenFirouz@discussions.microsoft.com> wrote:
>Matthew,
>
>Try setting the replication protocol to something that is less
>bandwidth-dependant, like SMTP. The slow connection could be causing a
>bottleneck that is causing replication problems. You can also run repadmin
>/replsummary from a command prompt to see the errors you are getting in
>replication. These links will give you more info:
>http://www.microsoft.com/resources/documentation/WindowsServ/2003/all/techref/en-us/Default.asp?url=/Resources/Documentation/windowsserv/2003/all/techref/en-us/W2K3TR_repto_how.asp
>http://www.microsoft.com/resources/documentation/WindowsServ/2003/standard/proddocs/en-us/Default.asp?url=/resources/documentation/WindowsServ/2003/standard/proddocs/en-us/sag_adintro_17.asp
>
>-Allen Firouz
>
>"Matthew Loraditch" wrote:
>
>> This is bit of a multifaceted question, We have 17 offices, each has their
>> own server, and our hq has 3 servers, all of the servers are DCs. We have
>> been having problems with sysvol replication to the net effect of new group
>> policies and logon scripts just not replicating. I have taken to copying the
>> policy folders myself by zipping them up and transporting the new policies
>> myself. The connection between the branches is dedicated 56k. Is there
>> anyway i can either disable the sysvol replication or would anyone have
>> recommendations as to a better AD structure or tricks with FRS? we will be
>> upgrading all the offices to 512k dedicated lines in November which should
>> hopefully put us back to normal but right now this is really becoming an
>> issue and I am at my wits end
>> ThanksMuch
>> Matthew Loraditch
>>
>>
>>
- Next message: Arvind: "ADAM: Setup Application-Specific Directory"
- Previous message: Lennart Svenssson: "ERROR MESSAGE EVERY 5 MINUTES IN THE EVENT VIEWER"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
