none
Domain Controller Replication

    Question

  • Hello Everyone...

    This is regarding the File replication Service. I have 2 DCs in our company. DC1 (RDKSVR)- Primary DC and DC2 (RDKSQL)- Additional DC.

    I have been handed over this network recently, so thought of verifying if things are working fine. I started doing DCDIAG on the servers and found some errors. The DCDIAG on Primary DC shows all test passed. The Event Viewer Shows the 

    "The File Replication Service has detected that the replica set "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)" is in JRNL_WRAP_ERROR. 
     
     Replica set name is    : "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)" 
     Replica root path is   : "c:\windows\sysvol\domain" 
     Replica root volume is : "\\.\C:" 
     A Replica set hits JRNL_WRAP_ERROR when the record that it is trying to read from the NTFS USN journal is not found.  This can occur because of one of the following reasons. 
     
     [1] Volume "\\.\C:" has been formatted. 
     [2] The NTFS USN journal on volume "\\.\C:" has been deleted. 
     [3] The NTFS USN journal on volume "\\.\C:" has been truncated. Chkdsk can truncate the journal if it finds corrupt entries at the end of the journal. 
     [4] File Replication Service was not running on this computer for a long time. 
     [5] File Replication Service could not keep up with the rate of Disk IO activity on "\\.\C:". 
     Setting the "Enable Journal Wrap Automatic Restore" registry parameter to 1 will cause the following recovery steps to be taken to automatically recover from this error state. 
     [1] At the first poll, which will occur in 5 minutes, this computer will be deleted from the replica set. If you do not want to wait 5 minutes, then run "net stop ntfrs" followed by "net start ntfrs" to restart the File Replication Service. 
     [2] At the poll following the deletion this computer will be re-added to the replica set. The re-addition will trigger a full tree sync for the replica set. 
     
    WARNING: During the recovery process data in the replica tree may be unavailable. You should reset the registry parameter described above to 0 to prevent automatic recovery from making the data unexpectedly unavailable if this error condition occurs again. 
     
    To change this registry parameter, run regedit. 
     
    Click on Start, Run and type regedit. 
     
    Expand HKEY_LOCAL_MACHINE. 
    Click down the key path: 
       "System\CurrentControlSet\Services\NtFrs\Parameters" 
    Double click on the value name 
       "Enable Journal Wrap Automatic Restore" 
    and update the value. 
     
    If the value name is not present you may add it with the New->DWORD Value function under the Edit Menu item. Type the value name exactly as shown above."

    On the Additional DC, DCDIAG shows the following.

    "Doing primary tests

       Testing server: RDK-two-towers\RDKSQL
          Starting test: Advertising
             ......................... RDKSQL passed test Advertising
          Starting test: FrsEvent
             There are warning or error events within the last 24 hours after the
             SYSVOL has been shared.  Failing SYSVOL replication problems may cause
             Group Policy problems.
             ......................... RDKSQL passed test FrsEvent
          Starting test: DFSREvent
             ......................... RDKSQL passed test DFSREvent
          Starting test: SysVolCheck
             ......................... RDKSQL passed test SysVolCheck
          Starting test: KccEvent
             ......................... RDKSQL passed test KccEvent
          Starting test: KnowsOfRoleHolders
             ......................... RDKSQL passed test KnowsOfRoleHolders
          Starting test: MachineAccount
             ......................... RDKSQL passed test MachineAccount
          Starting test: NCSecDesc
             ......................... RDKSQL passed test NCSecDesc
          Starting test: NetLogons
             ......................... RDKSQL passed test NetLogons
          Starting test: ObjectsReplicated
             ......................... RDKSQL passed test ObjectsReplicated
          Starting test: Replications
             ......................... RDKSQL passed test Replications
          Starting test: RidManager
             ......................... RDKSQL passed test RidManager
          Starting test: Services
             ......................... RDKSQL passed test Services
          Starting test: SystemLog
             ......................... RDKSQL passed test SystemLog
          Starting test: VerifyReferences
             ......................... RDKSQL passed test VerifyReferences

    "

    Event Viewer shows the following

    The File Replication Service is having trouble enabling replication from RDKSVR to RDKSQL for c:\windows\sysvol\domain using the DNS name rdksvr.rdk.local. FRS will keep retrying. 
     Following are some of the reasons you would see this warning. 
     
     [1] FRS can not correctly resolve the DNS name rdksvr.rdk.local from this computer. 
     [2] FRS is not running on rdksvr.rdk.local. 
     [3] The topology information in the Active Directory Domain Services for this replica has not yet replicated to all the Domain Controllers. 
     
     This event log message will appear once per connection, After the problem is fixed you will see another event log message indicating that the connection has been established.

    Could you guys please advise...

    Tuesday, September 22, 2015 11:48 AM

All replies

  • Also, would like to inform that when i create a policy or make a change in DNS, it does show up in the Additional DC. off late i ve been facing intermittent DNS resolution issue, when i do nslookup the fqdn of the server/pc does resolve the ip. but when i ping the fqdn it would ping sometime or might not, the ip always pings...

    Tuesday, September 22, 2015 5:40 PM
  • Hi, This question might not be related to HPC Pack. Please re-post in appropriate forum.

    Qiufang Shi

    Monday, September 28, 2015 8:36 PM