FRS-Filesystem differs from Ultrasound

Discussion in 'Windows Small Business Server' started by pUmkInhEd, Apr 7, 2005.

  1. pUmkInhEd

    pUmkInhEd Guest

    I am running two DC's, Win2k3 SBS and Win 2k server. Both patched to current
    (though SBS server is not SP1, yet). I have 4 DFS links: SYSVOL, users
    shared folders and another directory called CorpDocs. CorpDocs and Users
    folders are links under a Root Target called Documents (visual below)

    -SYSVOL
    -Documents
    |--UserDocs (users shared folders)
    |--CorpDocs

    I've had FRS enabled on userdocs and corpdocs for some time though i had not
    switched any login scripts to reference the DFS root so nobody uses those
    Links at the moment. I was going to be settings some users up to test today,
    but browsing through the ultrasound interface I found some strangeness.

    About a month ago I moved some folders *using explorer on the sbs server*
    (from one link to another, ie moved an ex-employees folder from C:\users
    shared folders\username to C:\corpdocs\past employees\username) and the copy
    completed successfully with no errors.

    Now, in the details tab of Ultrasound (beside health tab) I've selected to
    Show: Files so I can browse the ReplicaTreeRoot. The reference server is my
    SBS server. In this view I can see my three DFS roots, SYSVOL, UserDocs and
    CorpDocs. Browsing through CorpDocs, I found some mysteriously named folders
    under 'Past Employees' named DC21, DC22, DC23... DC36. These folders do no
    appear on either filesystem (SBS or 2k servers) and they contain
    subdirectories, no files, the subdirectories appear again under username
    (visual below)

    CorpDocs
    |--Past Employees
    |--COrr
    |--Notifications (contains files)
    |--DC21
    |--Notifications (does not contain files)

    1) is this a problem or a known issue
    2) is this something I should be concerned about or indicative of a larger
    issue
    3) how do I fix it?

    I've searched MSKB and google but turned up no results.

    As always, any help is greatly appreciated.

    Thanks
    Brandon
     
    pUmkInhEd, Apr 7, 2005
    #1
    1. Advertisements

  2. pUmkInhEd

    Jerry zhao Guest

    Hi Brandon,

    Thanks for your posting.

    From the description, I understand that your issue is that you found many
    empty folders in the ultrasound. If I have misunderstood your issue, please
    let me know.

    The issue is around moving folder between replica set which is a known
    problem in FRS on W2k: For detailed information about this issue, please
    refer to the following Kb:

    Local File Move Operation Between FRS Replica Sets Is Not Replicated
    http://support.microsoft.com/default.aspx?scid=KB;EN-US;330567

    The DC* files/folders are names used by the Recycle Bin. So for FRS, the
    files were not deleted, but moved outside of the replica set. Then, those
    empty folders are produced. As for this reason, you can safely ignore this
    or perform the work around described in the KB.

    If you have any questions or concerns, please feel free to let me know.
    It's my pleasure to be of assistance.

    Best regards,

    Jerry Zhao (MSFT)

    Microsoft CSS Online Newsgroup Support

    Get Secure! - www.microsoft.com/security

    =====================================================
    When responding to posts, please "Reply to Group" via your newsreader so
    that others may learn and benefit from your issue.
    =====================================================
    This posting is provided "AS IS" with no warranties, and confers no rights.
     
    Jerry zhao, Apr 11, 2005
    #2
    1. Advertisements

  3. pUmkInhEd

    pUmkInhEd Guest

    Thanks Jerry, you hit the nail on the head. This precisely describes my
    issue, but the resolution does not fit my situation as there are no DC
    folders on either filesystem to delete/restore/move. From reading the KB
    that you suggested, I am seeing that the folder move did not cause any real
    damage other than these nagging entries in the JET db. The workaround to
    remove these entries would be as follows:
    Create folders locally on the Win 2k server, DC21, DC22, DC23... DC36 and
    delete them via explorer on another wkstn (ie create C:\Sharename\...\DC21
    and delete \\Win2kServer\Sharename\...\DC21)

    Does that sound right to you?
    Thanks again!
    Brandon
     
    pUmkInhEd, Apr 11, 2005
    #3
  4. pUmkInhEd

    Jerry zhao Guest

    Hi Brandon,

    Thanks for your response.

    Sorry for my delayed reply. I have discussed with other experts on this
    issue for potential risk if you try to perform the actions.

    Our suggestion is that you check the folders in the windows explore first,
    if the issue do not appears in the windows explore, you can safely ignore
    this issue.

    You still can try your action as we do not see any risk on it. However, we
    are not sure that it will work.

    If you have any thing new or you need further help, please feel free to let
    me know.

    Best regards,

    Jerry Zhao (MSFT)

    Microsoft CSS Online Newsgroup Support

    Get Secure! - www.microsoft.com/security

    =====================================================
    When responding to posts, please "Reply to Group" via your newsreader so
    that others may learn and benefit from your issue.
    =====================================================
    This posting is provided "AS IS" with no warranties, and confers no rights.
     
    Jerry zhao, Apr 13, 2005
    #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.