Repair DFS

Discussion in 'File Systems' started by scotth, Oct 19, 2006.

  1. scotth

    scotth Guest

    I initially had two member servers (FS1 & FS2) both running 2003 R2 and each
    with an 800gb external array configured for DFS storage. The system was
    fully functional for several months until the array on FS2 died. The server
    itself never had any problems, just ntfs errors on the array which required
    wiping the data and rebuilding the array. When the array died, I turned off
    DFS referrals to FS2; users were always able to access the data on FS1. The
    array had been healthy for nearly a week so I decided to 'redo' DFS. The
    steps I performed are as follows...

    1) Recreate the folder structure for the file storage on FS2, using the same
    permissions as those on FS1
    2) Recreate the DFSRoots folder structure on FS2, using the same permissions
    as those of FS1
    3) Within DFS Management, under Replication hierarchy, Connections tab for
    each replication group, right-clicked FS2 and selected Enable.

    That was all performed on Friday afternoon. Now on Monday morning, none of
    the data has been replicated to FS2 and I have the following errors in the
    DFSR logs on each server:

    Erros on FS1:
    Event ID: 5016 (received for each shared folder)
    The DFS Replication service detected that the connection with partner
    FS2.GL.local for replication group gl.local\dfsroot\shared has been removed
    or disabled.

    Additional Information:
    Connection ID: 1DA6A6D7-3915-4AAE-93CA-8462574BF17F
    Replication Group ID: D436BAD4-A970-4138-9C51-7A74601B85DE

    For more information, see Help and Support Center at
    http://go.microsoft.com/fwlink/events.asp.

    Event ID: 5012
    The DFS Replication service failed to communicate with partner FS2 for
    replication group gl.local\dfsroot\gluser. The partner did not recognize the
    connection or the replication group configuration.

    Partner DNS Address: FS2.GL.local

    Optional data if available:
    Partner WINS Address: FS2
    Partner IP Address: 10.0.0.9


    The service will retry the connection periodically.

    Additional Information:
    Error: 9026 (The connection is invalid)
    Connection ID: B790425D-C29B-4F9A-9C30-C28ECCF2DC33
    Replication Group ID: 83FD592E-C7B6-47E0-8A22-C60D42C29BE1

    Event ID: 5014
    The DFS Replication service is stopping communication with partner FS2 for
    replication group gl.local\dfsroot\public due to an error. The service will
    retry the connection periodically.

    Additional Information:
    Error: 9033 (The request was cancelled by a shutdown)
    Connection ID: 18632AA3-5E43-47C6-8B9D-86AD70DCF926
    Replication Group ID: 222CC41E-5D46-426C-A06A-3BCA433FD8F1


    Errors on FS2:
    Event ID: 2104
    The DFS Replication service failed to recover from an internal database
    error on volume F:. Replication has been stopped for all replicated folders
    on this volume.

    Additional Information:
    Error: 9214 (Internal database error (-1086))
    Volume: C3D5FF43-53AB-11DB-AD08-001372532156
    Database: F:\System Volume Information\DFSR

    Event ID: 2004
    The DFS Replication service stopped replication on volume F:. This failure
    can occur because the disk is full, the disk is failing, or a quota limit has
    been reached. This can also occur if the DFS Replication service encountered
    errors while attempting to stage files for a replicated folder on this
    volume.

    Additional Information:
    Error: 9014 (Database failure)
    Volume: C3D5FF43-53AB-11DB-AD08-001372532156

    Event ID: 4004 (Received for each shared folder)
    The DFS Replication service stopped replication on the replicated folder at
    local path F:\FS\Active.

    Additional Information:
    Error: 9003 (The replication group is invalid)
    Additional context of the error: F:\FS\Active\
    Replicated Folder Name: Active
    Replicated Folder ID: 811D6F38-1CF8-4A63-AF1D-FC3E5A60CC6F
    Replication Group Name: gl.local\dfsroot\active
    Replication Group ID: D20CB345-8E3E-49B2-BA99-5EA092BCD122
    Member ID: 798C1DF4-8129-4971-B1EA-CFBA104B2D8F

    So my questions are...

    What did I do wrong and how do I fix it? (preferrably with little to no
    impact on end-users)

    Thanks.
    Scott
     
    scotth, Oct 19, 2006
    #1
    1. Advertisements

  2. I think that the problem here is that the volume label has changed because
    you rebuilt the array. If you have the data on both of your arrays, then
    you can just recreate the replication group and replicated folders.

    Thanks,

    Robert A Post, Jr [MSFT]
    Distributed File Service Replication Test
    This posting is provided "AS IS" with no warranties, and confers no rights.
     
    Robert A Post, Jr, Oct 20, 2006
    #2
    1. Advertisements

  3. scotth

    scotth Guest

    Thanks for the reply.
    Unfortuantely since the array was having problems, I had to completely wipe
    the array. Therefore there's no data on it at all. I did however give the
    array the same volume name.
     
    scotth, Oct 20, 2006
    #3
  4. The volume serial is what is of importance here and you can't specify that
    when formatting. You can find out what you serial is by running a dir
    command. It's at the top. This value would have changed on your array.
    The problem is that this serial is put in the DFSR database and I don't
    know of any way to recover a DFSR DB in this case.

    I'm pretty sure the only course of action is to rebuild the RG. Since they
    are external drives, you should be able to plug them into the same machine
    and "mirror" the data yourself, then rebuild the RG. It will take less
    time.

    Thanks,

    Robert A Post, Jr [MSFT]
    Distributed File Service Replication Test
    This posting is provided "AS IS" with no warranties, and confers no rights.
     
    Robert A Post, Jr, Oct 20, 2006
    #4
  5. scotth

    scotth Guest

    Oh, I understand now. That makes sense.

    Thanks.
     
    scotth, Oct 20, 2006
    #5
    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.