Windows 2003 FRS

Discussion in 'File Systems' started by John Winslet, Aug 9, 2004.

  1. John Winslet

    John Winslet Guest

    Hi

    We have 2 servers running Windows 2003 Server. Originally
    there was 1 w2k3 server and the second was added later.
    The second additional server had the wrong date set when
    it was added to Active Directory and the event logs gave
    FRS errors about it being too far into the future. In fact
    the date was around 6 months in the future.
    To stop this annoying error appearing the the event logs I
    made the FRS service manual and stopped it.

    Today the date has come where it should be able to sync,
    so I have made the service automatic and started it. The
    event logs said about a 'journal wrap' because I kept the
    service stopped for so long. I added the 'Enable Journal
    Wrap Automatic Restore' with a value of 1 which fixed this
    and the FRS looked to be working ok - the event logs for
    FRS were clear.

    Now the 2nd server has the SYSVOL share, but nothing is
    sync'd. There is also no NETLOGON share.
    I have checked the RCP connections by viewing the other
    servers event log from each other.

    I have installed FRSDiag.exe. When I run the test on the
    2nd server it shows errors from the debug dir, something
    about 'Send Penalty', also when run against 1st server it
    tells me that junction points are missing in the sysvol
    which I understand is in SYSVOL\SYSVOL\mydomain.com and
    SYSVOL\Staging Area\mydomain.com.

    Any Ideas would be much apprecaited. Sorry the info's a
    bit sketchy but I dont know what to try!
     
    John Winslet, Aug 9, 2004
    #1
    1. Advertisements

  2. Enabling automatic journal wrap recovery might not be the safest thing
    to do. When FRS performs a journal wrap recovery be it initiated
    manually or automatically, it will move all content into a folder in
    the replica root that holds "preexisting" content. As the recovering
    member syncs with one of its partners, the files will gradually move
    back out from this preexisting folder into the main replica. After
    the process completes, leftovers in the preexisting folder should be
    looked at to see if they are needed. If they're needed, they should
    be merged or copied over any files that were restored as the result of
    the recovery process.

    As you can see, the danger with automatic recovery is the files
    "disappear" for some time. If the machine is unable to contact a
    partner to sync with, there could be significant problems as the files
    will remain "gone" for a lenghty period.

    A better solution is to use Ultrasound or at least Sonar to monitor
    FRS replicas. They can detect when journal wraps happen and alert you
    to take action. Admins can perform the D2 process at a time that is
    safe.

    Now to fix your current problems, you need to fix your junction points
    for SYSVOL. Use the following KBs.

    http://support.microsoft.com/?id=186750

    http://support.microsoft.com/?id=205524


    --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.
     
    Richard Chinn [MSFT], Aug 9, 2004
    #2
    1. Advertisements

  3. John Winslet

    John Winslet Guest

    Hi, Thanks for the info. I did try to use the linkd
    utility to re-link the junction points but i cannot do
    this. The source directory needs to be empty to create
    junction points and they currently have all the policies
    and scripts in. I cannot lose these!!
     
    John Winslet, Aug 10, 2004
    #3
  4. If you don't fix things up right with the junction point and get FRS
    running, you risk getting your two DCs SYSVOLs out of sync with each
    other. This can cause all sorts of problems.

    If possible, take a backup of the system and try to fix things up
    using the KB articles as a guide. Once you have the junction set up,
    and your SYSVOL all sorted out on the original machine, you can work
    on getting FRS replicating properly with your new DC.

    --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.
     
    Richard Chinn [MSFT], Aug 11, 2004
    #4
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.