1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.
  2. You are viewing our forum as a guest. For full access please Register. WindowsBBS.com is completely free, paid for by advertisers and donations.

Resolved [Server2012 DFS Replication fails after power loss]

Discussion in 'Windows Server System' started by batsona, 2015/03/10.

  1. 2015/03/10
    batsona

    batsona Inactive Thread Starter

    Joined:
    2007/12/18
    Messages:
    131
    Likes Received:
    0
    Trophy Points:
    106
    Location:
    Maryland
    Computer Experience:
    Intermediate
    All; I have 2 servers (Server 2012 Storage edition) that replicate in one direction. The source-server (authoritative) lost power abruptly, and corrupted its JET database. Replication will now no longer stay running, *even after* I deleted all the replication objects & groups & bounced the DFS service -- I then re-created everything, but the error about the corrupt JET database remains.
    The fix says to use the "WMIC" console to restart replication / recover the JET database. Files should be backed up in case the conflict-resolution that occurs during DB recovery causes data-loss. My remote site has no backup system because the DFS system *IS* the backup system :) (which ain't workin' right now)
    I do'nt care to recover this 'database' can't I just delete it somehow, after killing all the replication objects/groups and 'start over'? Thanks!
     
  2. 2015/03/12
    batsona

    batsona Inactive Thread Starter

    Joined:
    2007/12/18
    Messages:
    131
    Likes Received:
    0
    Trophy Points:
    106
    Location:
    Maryland
    Computer Experience:
    Intermediate
    Does anyone know a good website where I can find some DFS experts? the fixes I'm trying are increasing in risk, and are becoming a 'shot-in-the-dark' without some sort of input. Microsoft wants $600 a pop for a tech support case...
     

  3. to hide this advert.

  4. 2015/03/15
    batsona

    batsona Inactive Thread Starter

    Joined:
    2007/12/18
    Messages:
    131
    Likes Received:
    0
    Trophy Points:
    106
    Location:
    Maryland
    Computer Experience:
    Intermediate
    I had to solve this myself. For what its worth, here it is:

    1.) Delete all replication groups

    2.) Stop the Distributed File System service

    3.) You un-hide the "System Volume Info" directory at the root of the drive that houses the Replicated Directory. Then give yourself full rights to it.

    4.) Go into "System Volume Info ", and rename the "DFSR" directory.

    5.) re-start Distributed File System service

    6.) re-create the Replication groups.
     

Share This Page