none
Windows Backup forcing DFSR to reinitialize replicated folders

    Question

  • Windows Backup forcing DFSR to reinitialize

     

    Ever since I did a baremetal restore on this Windows 2008 R2 machine participating in DFS-R (also a DC, but don’t think it’s related)  using Windows Backup, I’ve been noticing that every night when it does a backup, DFS Replication will try to reinitialize the replicated folders. But since the files are unchanged amoung the DFSR members, files aren’t actually copied over. It’s pretty much like the files pre-seeded, and the hashes are just compared again.

    Just wondering if anyone can help me stop this from happening. Thanks

    Here’s the sequence of event from logs:

    Evenid – 1102

    The DFS Replication service has temporarily stopped replication because another application is performing a backup or restore operation. Replication will resume after the backup or restore operation has finished.

    EventID – 1104

    The DFS Replication service successfully restarted replication after a backup or restore operation.

    EventID – 1206

    The DFS Replication service successfully contacted domain controller server01.unionvilleorthodontics.local to access configuration information.

    EvenID – 2107

    The DFS Replication detected the ASR instance key has changed on volume D:. Replication has been stopped for all replicated folders on this volume.

     

    Additional Information:

    Volume: 69319B3E-024D-11DF-BADD-0026B9615747

    ASR Instance key: 120e4966-0519-4f09-8abd-39626d3f734b

    EventID – 2108

    The DFS Replication service successfully recovered from the ASR instance key change on volume D:. Replication has resumed on replicated folders on this volume.

     

    Additional Information:

    Volume: 69319B3E-024D-11DF-BADD-0026B9615747

    EventID – 4102

    The DFS Replication service initialized the replicated folder at local path D:\Patterson Dental and is waiting to perform initial replication. The replicated folder will remain in this state until it has received replicated data, directly or indirectly, from the designated primary member.

     

    Additional Information:

    Replicated Folder Name: Patterson Dental

    Replicated Folder ID: 2AF89C1F-862A-489D-8C19-524330F65CB8

    Replication Group Name: unionvilleorthodontics.local\fileserver\patterson dental

    Replication Group ID: C6FD7DB8-6E37-4DF9-A0EB-9198CF9D038C

    Member ID: 98CC9E73-5E8B-45B7-A844-440869988799

     

     

    This is the debug log from DFSR that I think is relevant:

     

    20101220 03:30:26.856 144 DOWN 2833 AsyncRpcHandler::ProcessReceive Completion. connId:{31FB28B5-542F-4E33-9FD5-8F6320809BDF} csId:{00000000-0000-0000-0000-000000000000} reqType:AsyncPollRequest reqState:Completed status:0 ptr:000000000BDE8D30
    
    20101220 03:30:26.856 4260 INCO 8561 InConnection::InConnectionContentSetContext::Hibernate Hibernating: connId:{31FB28B5-542F-4E33-9FD5-8F6320809BDF} csId:{35C923AB-3499-406D-A5E3-D511A330DF57}
    
    20101220 03:30:26.856 4260 IINC 392 IInConnectionCreditManager::ReturnCredits [CREDIT] Credits have been returned. creditsToReturn:32 totalConnectionCreditsGranted:0 totalGlobalCreditsGranted:0 csId:{35C923AB-3499-406D-A5E3-D511A330DF57} csName:ParadigmV4 connId:{31FB28B5-542F-4E33-9FD5-8F6320809BDF} sessionTaskPtr:0000000026D32C70
    
    20101220 03:30:26.856 4260 INCO 7343 InConnection::RequestVvUp Requested upstream version vector. requestState:00000000024DE9A0 connId:{31FB28B5-542F-4E33-9FD5-8F6320809BDF} csId:{35C923AB-3499-406D-A5E3-D511A330DF57} csName:ParadigmV4 changeType:notify
    
    20101220 03:30:26.857 144 DOWN 2833 AsyncRpcHandler::ProcessReceive Completion. connId:{31FB28B5-542F-4E33-9FD5-8F6320809BDF} csId:{00000000-0000-0000-0000-000000000000} reqType:AsyncPollRequest reqState:Cancelled status:0 ptr:00000000104434A0
    
    20101220 03:30:26.857 144 DOWN 7153 BandwidthThrottler::PrepareForShutdown Repeated call to shutdown ignored. rgId:F9E673DF-E95F-4BC2-81FB-9F631768E0DE rgName:unionvilleorthodontics.local\fileserver\paradigmv4 connId:31FB28B5-542F-4E33-9FD5-8F6320809BDF ptr:000000000BF524F0
    
    20101220 03:30:26.857 144 DOWN 2833 AsyncRpcHandler::ProcessReceive Completion. connId:{31FB28B5-542F-4E33-9FD5-8F6320809BDF} csId:{35C923AB-3499-406D-A5E3-D511A330DF57} reqType:VvUpRequest reqState:Completed status:0 ptr:00000000024DE9A0
    
    20101220 03:30:26.924 5308 PDBX 5449 PdbManager::Initialize Database schema version: 13 current version: 13
    
    20101220 03:30:26.925 5308 PDBX 5528 PdbManager::Initialize ASR ID Change. Previous value:{00000000-0000-0000-0000-000000000000}, new value:{120E4966-0519-4F09-8ABD-39626D3F734B}. Begin non authoritative restore for volume:{69319B3E-024D-11DF-BADD-0026B9615747}
    
    20101220 03:30:26.954 5308 EVNT 1185 EventLog::Report Logging eventId:2107 parameterCount:3
    
    20101220 03:30:26.954 5308 EVNT 1205 EventLog::Report   eventId:2107 parameter1:69319B3E-024D-11DF-BADD-0026B9615747
    
    20101220 03:30:26.954 5308 EVNT 1205 EventLog::Report   eventId:2107 parameter2:D:
    
    20101220 03:30:26.954 5308 EVNT 1205 EventLog::Report   eventId:2107 parameter3:120e4966-0519-4f09-8abd-39626d3f734b
    
    20101220 03:30:26.954 5308 VLMG 544 [ERROR] BaseVolumeManager::RecreateDbOnError [DS] The database is not usable. Delete and recreate. volId:{69319B3E-024D-11DF-BADD-0026B9615747} volPath:\\.\D: volState:INITIALIZING Error:
    
    +	[Error:9014(0x2336) VolumeManager::InitializeDb volumemanager.cpp:6311 5308 C Database failure]
    
    +	[Error:9014(0x2336) BaseVolumeManager::InitializeDb volumemanager.cpp:396 5308 C Database failure]
    
    +	[Error:9014(0x2336) LdbManager::Initialize ldb.cpp:1074 5308 C Database failure]
    
    +	[Error:9220(0x2404) PdbManager::Initialize pdb.cpp:5592 5308 C The ASR instance key in the registry does not match the one stored in the database]
    
    +	[Error:9220(0x2404) PdbManager::Initialize pdb.cpp:5527 5308 C The ASR instance key in the registry does not match the one stored in the database]
    
    20101220 03:30:26.969 5308 PDBX 6185 ReadLastInstanceValue SOFTWARE\MICROSOFT\WINDOWS NT\CurrentVersion\ASR\RestoreSession\LastInstance value is "120e4966-0519-4f09-8abd-39626d3f734b"
    
    20101220 03:30:26.969 5308 PDBX 6252 PdbManager::GetAsrInstanceKey lastInstanceASR:120e4966-0519-4f09-8abd-39626d3f734b asrId:{120E4966-0519-4F09-8ABD-39626D3F734B}
    
    20101220 03:30:27.281 3380 INCO 2551 InConnection::OnEstablishedOutConnection Found inConnection whose partner is the one that has just established an outConnection. connId:{2BDD823E-5E3E-4015-ADD1-57214D328897} partnerId:{54202CC5-CF21-4046-B983-6079DDEBCD6B} 
    
    
    Wednesday, December 22, 2010 5:07 PM

All replies

  • Anyone familiar with this?
    Saturday, January 15, 2011 7:18 PM
  • I am having exactly the same issue with backup exec. did it get resolved?
    Monday, April 11, 2011 1:23 PM
  • Me too, on SBS 2008 when using the built-in Windows Server Backup.

    It seems to be related to Shadow Copy as the 2107 & 2108 events (closely followed by 4102 - 'The DFS Replication service initialized the replicated folder') are generated immediately after the Shadow Copy backup process starts...
    Thursday, May 19, 2011 6:11 PM
  • I've changed two things on the server and it seems to have cured the problem (DFSR has been running for 3 days without any new initial replications or 2107/2108 events):

    1. Disabled AV scanning (SEPM) on the DFSR Folder (all sites)
    2. Changed the DFSR replication schedule to 'No replication' while the backup is running (gave it an extra 30 mins either side to be safe).

    Not sure which of these fixed the problem but hope the info helps someone...


    UPDATE 6/6/11 - Ok ignore the above, still having the same problems... :(
    Monday, May 23, 2011 9:29 AM
  • I am having the exact same issue! Have you had any luck resolving this? Thanks!!
    • Proposed as answer by Cody Lewis Thursday, December 08, 2011 9:01 AM
    • Unproposed as answer by Cody Lewis Thursday, December 08, 2011 9:02 AM
    Tuesday, December 06, 2011 10:11 PM
  • After many hours of reading logs and testing I have discovered the solution!


    When the DFSR service is launched, it will detect the registry “HKLM\SOFTWARE\MICROSOFT\WINDOWS NT\CurrentVersion\ASR\RestoreSession\RestoredVolumes”, if this entry exists, DFSR knows a restore was once performed on the volume where the DFSR content resides, so DFSR will do an initial sync to confirm the local database is in a consistent state.


    Problem is, this key is not getting removed, so when DFSR is disabled for backup, then enabled again, it believes it has just been recovered from backup and should sync again.


    Remove the “RestoreSession” subkey under “HKLM\SOFTWARE\MICROSOFT\WINDOWS NT\CurrentVersion\ASR”.


    Problem solved!


    I hope this helps,

    Cody

    • Proposed as answer by Cody Lewis Thursday, December 08, 2011 9:03 AM
    Thursday, December 08, 2011 9:02 AM