DFSR - This member is waiting for initial replication for replicated folder SYSVOL Share - How long should it take?

Question

Yesterday we were forced to perform a non-authoritative sync of the SYSVOL folder as replication had stopped because one of the DCs had been disconnected from it's replication partner for more than 60 days (caused by a unexpected shutdown and we did not
pick up on the fact replication had stopped until now).
I performed the non-authoritative sync of the SYSVOL folder and now the folder is in state 2
ReplicatedFolderName  ReplicationGroupName  State
SYSVOL Share          Domain System Volume  2
and has been for more than 12 hours.  The DFS replication health report, reports "This member is waiting for initial replication for replicated folder SYSVOL Share".
How long should it take and is there anyway to force it so that replication can resume?

Answer 1

I'm fairly sure it's not tombstoned.  Here is the DCDIAG output:
Directory Server Diagnosis
Performing initial setup:
   Trying to find home server...
   Home Server = RC-CURDC-02
   * Identified AD Forest. 
   Done gathering initial info.
Doing initial required tests
   Testing server: Default-First-Site-Name\RC-CURDC-02
      Starting test: Connectivity
         ......................... RC-CURDC-02 passed test Connectivity
Doing primary tests
   Testing server: Default-First-Site-Name\RC-CURDC-02
      Starting test: Advertising
         ......................... RC-CURDC-02 passed test Advertising
      Starting test: FrsEvent
         ......................... RC-CURDC-02 passed test FrsEvent
      Starting test: DFSREvent
         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. 
         ......................... RC-CURDC-02 passed test DFSREvent
      Starting test: SysVolCheck
         ......................... RC-CURDC-02 passed test SysVolCheck
      Starting test: KccEvent
         ......................... RC-CURDC-02 passed test KccEvent
      Starting test: KnowsOfRoleHolders
         ......................... RC-CURDC-02 passed test KnowsOfRoleHolders
      Starting test: MachineAccount
         ......................... RC-CURDC-02 passed test MachineAccount
      Starting test: NCSecDesc
         ......................... RC-CURDC-02 passed test NCSecDesc
      Starting test: NetLogons
         ......................... RC-CURDC-02 passed test NetLogons
      Starting test: ObjectsReplicated
         ......................... RC-CURDC-02 passed test ObjectsReplicated
      Starting test: Replications
         ......................... RC-CURDC-02 passed test Replications
      Starting test: RidManager
         ......................... RC-CURDC-02 passed test RidManager
      Starting test: Services
         ......................... RC-CURDC-02 passed test Services
      Starting test: SystemLog
         A warning event occurred.  EventID: 0x000003FC
            Time Generated: 06/12/2014   18:26:05
            Event String:
            Scope, 10.59.96.64, is 83 percent full with only 7 IP addresses remaining.
         A warning event occurred.  EventID: 0x000003FC
            Time Generated: 06/12/2014   18:26:05
            Event String:
            Scope, 10.59.98.0, is 95 percent full with only 5 IP addresses remaining.
         A warning event occurred.  EventID: 0x00000560
            Time Generated: 06/12/2014   18:26:05
            Event String:
            IP address range of scope 10.59.96.64 is 83 percent full with only 7 IP addresses available.
         A warning event occurred.  EventID: 0x00000560
            Time Generated: 06/12/2014   18:26:05
            Event String:
            IP address range of scope 10.59.98.0 is 95 percent full with only 5 IP addresses available.
         A warning event occurred.  EventID: 0x000016AF
            Time Generated: 06/12/2014   18:39:43
            Event String:
            During the past 4.23 hours there have been 95 connections to this Domain Controller from client machines whose IP addresses don't map to any of the existing sites in the enterprise. Those clients, therefore, have undefined
sites and may connect to any Domain Controller including those that are in far distant locations from the clients. A client's site is determined by the mapping of its subnet to one of the existing sites. To move the above clients to one of the sites, please
consider creating subnet object(s) covering the above IP addresses with mapping to one of the existing sites.  The names and IP addresses of the clients in question have been logged on this computer in the following log file '%SystemRoot%\debug\netlogon.log'
and, potentially, in the log file '%SystemRoot%\debug\netlogon.bak' created if the former log becomes full. The log(s) may contain additional unrelated debugging information. To filter out the needed information, please search for lines which contain text
'NO_CLIENT_SITE:'. The first word after this string is the client name and the second word is the client IP address. The maximum size of the log(s) is controlled by the following registry DWORD value 'HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters\LogFileMaxSize';
the default is 20000000 bytes.  The current maximum size is 20000000 bytes.  To set a different maximum size, create the above registry value and set the desired maximum size in bytes.
         ......................... RC-CURDC-02 passed test SystemLog
      Starting test: VerifyReferences
         ......................... RC-CURDC-02 passed test VerifyReferences
   Running partition tests on : curriculum
      Starting test: CheckSDRefDom
         ......................... curriculum passed test CheckSDRefDom
      Starting test: CrossRefValidation
         ......................... curriculum passed test CrossRefValidation
   Running partition tests on : Schema
      Starting test: CheckSDRefDom
         ......................... Schema passed test CheckSDRefDom
      Starting test: CrossRefValidation
         ......................... Schema passed test CrossRefValidation
   Running partition tests on : Configuration
      Starting test: CheckSDRefDom
         ......................... Configuration passed test CheckSDRefDom
      Starting test: CrossRefValidation
         ......................... Configuration passed test CrossRefValidation
   Running enterprise tests on : riddlesdown.local
      Starting test: LocatorCheck
         ......................... riddlesdown.local passed test LocatorCheck
      Starting test: Intersite
         ......................... riddlesdown.local passed test Intersite
Eveything is passing, except for the bits about the SystemLog and DFRS, all seems good to me.
Event 2213 is in the logs.  I will look and changing the MaxOfflineTimeInDays and see if that gets it going.