Question about NtFrs_PreExisting___See_EventLog and new deployments.

Discussion in 'File Systems' started by Francis Ouellet, Aug 17, 2004.

  1. Hi,

    We recently decided to use FRS to replicate the content of our file
    server to our DRP site. Both sites are now connected with a 10MBps link.
    Boths site have DCs and are replicating fine. The DFS root is located on
    one of the DCs in the main site where we will begin replication from.

    The configuration is the following:

    Site: Montreal
    root dfs: \\ntdomain\sfmontreal (Windows 2003)

    root target: \\ntdomain\sfmontreal\profiles (Windows 2000 Server, SP4)
    Links: \\sfmontreal\profiles (this is the master, where I want to
    replicate from. (Windows 2000 Server, SP4)
    \\huc-gen-fs-01\profiles (located in the remote site, an empty share)
    (Windows 2000 Server, SP4)

    I enabled replication between those two links (hub and spoke). The is
    roughly 10GBs of data on the \\sfmontreal\profiles share. I took a long
    time for anything to happen and then errors started to appear:


    Event ID: 13544 on SFMONTREAL
    The File Replication Service cannot replicate h:\profiles because it
    overlaps the replicating directory h:\profiles.

    Event ID: 13552 on SFMONTREAL
    The File Replication Service is unable to add this computer to the
    following replica set:

    This could be caused by a number of problems such as:
    -- an invalid root path,
    -- a missing directory,
    -- a missing disk volume,
    -- a file system on the volume that does not support NTFS 5.0

    The information below may help to resolve the problem:
    Computer DNS name is ""
    Replica set member name is "{4E971C45-5F8C-47E4-935F-88AE3309B4F0}"
    Replica set root path is "h:\profiles"
    Replica staging directory path is "d:\frs-staging"
    Replica working directory path is "c:\winnt\ntfrs\jet"
    Windows error status code is ERROR_BAD_COMMAND
    FRS error status code is FrsErrorResourceInUse

    Other event log messages may also help determine the problem. Correct
    the problem and the service will attempt to restart replication
    automatically at a later time.

    Event ID: 13520

    The File Replication Service moved the preexisting files in h:\profiles
    to h:\profiles\NtFrs_PreExisting___See_EventLog.

    The File Replication Service may delete the files in
    h:\profiles\NtFrs_PreExisting___See_EventLog at any time. Files can be
    saved from deletion by copying them out of
    h:\profiles\NtFrs_PreExisting___See_EventLog. Copying the files into
    h:\profiles may lead to name conflicts if the files already exist on
    some other replicating partner.

    In some cases, the File Replication Service may copy a file from
    h:\profiles\NtFrs_PreExisting___See_EventLog into h:\profiles instead of
    replicating the file from some other replicating partner.

    Space can be recovered at any time by deleting the files in


    Then all the files in the \\sfmontreal\profiles share were moved into
    the NtFrs_PreExisting___See_EventLog. folder under H:\profiles.

    I always thought that this pre-staging folder was used when both dfs
    links had files in them. In my scenario this is not the case since I'm
    populating a brand new server using frs. Is there anything I need to
    look at before enabling FRS? I caused a bit of downtime for some users
    since all the files were moved from the root share.

    Any help greatly appreciated.

    Francis Ouellet
    Francis Ouellet, Aug 17, 2004
    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.