Question on DFS

Discussion in 'File Systems' started by Joshua Graham, Jul 12, 2004.

  1. I have 3 DC, 2 on a main site and 1 offsite connected through a WAN link. I
    just implemented DFS on our main File Server at the main site. I took a
    backup take and went to the Off-site server and restored the files to that
    server, about 60 gigs worth. I set up a DFS root and 3 DFS links and enabled
    replication to the off-site server. I was monitoring the status and then I
    saw this folder,NtFrs_PreExisting___See_EventLog and all the files that I
    restored were in that folder. I noticed that replication was going good
    because some files and folders from our main site were replicated to our
    off-site server, however, I did not want over 60 gigs of data going over my
    wan link. I moved the files that were in the
    NtFrs_PreExisting___See_EventLog to the folder that it was suppose to be in.
    I now see the FRS-Staging area filling up with data and I have not seen any
    files or folders replicate in about 24 hours or so. I have files in both of
    the staging areas and I do not know why I would have any on the Off-site
    staging area since all the files are older than the ones on my main file
    server.

    Today, I upgraded the main file server to 2003, however the offsite server
    is still Windows 2000. I check the status and it says OK and I installed
    Ultrasound and the status says okay, however, I am new to Ultrasound so I
    will have to learn as I go.

    Question: Did I do wrong when I moved the files from the
    NtFrs_PreExisting___See_EventLog to the folder that the files and folders
    were suppose to be in?
    Why is my Staging area filling up and no replication has taken place in
    about 24 hours.
    What am I doing wrong?

    Thanks in Advanced,

    Josh
    MCP, A+
     
    Joshua Graham, Jul 12, 2004
    #1
    1. Advertisements

  2. Joshua Graham

    Brian [MSFT] Guest

    Josh,
    It is normal to see existing file content on a newly-added DFS member get
    moved to the NtFrs_PreExisting folder. The reason this occurs is that the
    newly-added machine needs to sync from an already-existing DFS member. If
    the content you took from the main site had already been replicated between
    the two machines in the main site (so that MD5 checksum info existed for the
    replicated files), AND if either 1) the DFS had existed for 7+ days, or 2)
    you had fiddled with the "outlog change history in minutes" registry value
    on one of your main site DFS members, then the 60 gigs would not be sent
    over the wire. Instead, this content would be moved into the
    NtFrs_PreExisting folder and then moved back into the replicated folder one
    file at a time. This is called "prestaging" data and it is an admittedly
    complex process. If the required steps weren't followed, the 60 gigs would
    indeed flow over the WAN link.

    As for the second issue regarding staging space: there are guidelines/best
    practices regarding the proper staging space limit depending on the number
    of files and total size of replicated data. The default limit is 660MB; for
    60 gigs of data this probably isn't enough and performance will be hindered.

    A third thing to consider is upping the size of the NTFS change journal on
    your DFS members to prevent the dreaded "journal wrap error". FRS tracks
    filesystem changes by reading the change journal; the journal is a fixed
    size so if too many changes occur at once, FRS loses its spot on the journal
    and chokes. A larger journal helps lower this risk and the only cost is
    less disk space. As with staging space, there are guidelines for proper
    journal size too.

    You downloaded Ultrasound? With that download comes a troubleshooting
    document that should prove helpful. I would also suggest reading the FRS
    portion of the Branch Office Guide, available at
    http://www.microsoft.com/downloads/...F6-A8A8-40BB-9FA7-3A95C9540112&displaylang=en.

    --
    Brian [MSFT]

    Disclaimer: 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.
     
    Brian [MSFT], Jul 13, 2004
    #2
    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.