我在全网格多用途复制组中设置了两台 2008r2 服务器。(01 和 02)。01 是源服务器。初始同步昨晚刚刚完成,有两个文件夹未出现在任何一台服务器上,但它们卡在从 02 推送到 01 的更改积压中。从 01 到 02 的积压很清晰,复制完美。
- 我尝试重新启动 02,但没有任何反应。
- 两个服务器的事件查看器都没有任何有用的信息。
- 我尝试创建并删除“batman”文件夹,希望这样可以清除它。但没成功。当我在 01 创建它时,它将其推送到 02。当我在 02 创建它时,它在积压中创建了一个冗余条目。
- 还有一些其他随机文件滞留在积压中。它们是不必要的,所以我只是从 01 中删除它们,这样它们就从积压中清除了。我希望对文件夹也做同样的事情……
我是否可以在其他地方查找这些文件夹卡住的原因?
编辑:
我还从 DFSR 调试日志中发现了这一点(这是昨晚初始同步完成时发生的):
20140513 23:27:39.254 2372 CSMG 6769 ContentSetManager::Initialize csId:{2D9CF1D7-50E2-4B3E-AC6B-3D60C6B026EB} csName:Art rootPath:E:\Art state:InitialSync(Sync) ptr:0000000000F83D50
20140513 23:27:39.254 2372 CSMG 5547 ContentSetManager::CheckContentSetState Updating content set record csId:{2D9CF1D7-50E2-4B3E-AC6B-3D60C6B026EB} csName:Art ghosted:0 readOnly:0 readOnlySince:16010101 00:00:00.000
20140513 23:27:39.254 2372 CSMG 5590 ContentSetManager::CheckContentSetState Content set csId:{2D9CF1D7-50E2-4B3E-AC6B-3D60C6B026EB} state:InitialSync(Cleanup)
20140513 23:27:39.395 2372 STAG 2594 Staging::ScanStagingDirectory Staging space usage is: 285794033664
20140513 23:27:39.395 2372 CSMG 2960 ContentSetManager::StartInitialSyncCleanup csId:{2D9CF1D7-50E2-4B3E-AC6B-3D60C6B026EB}
20140513 23:27:39.395 448 ISYN 153 InitialSyncCleanupTask::Run csId:{2D9CF1D7-50E2-4B3E-AC6B-3D60C6B026EB}
20140513 23:27:45.760 448 ISYN 453 InitialSyncCleanupTask::MoveOut Moving \\.\E:\Art\Artist Files\Christine\batman to pre-existing:0x9000000156B80 csId:{2D9CF1D7-50E2-4B3E-AC6B-3D60C6B026EB}
20140513 23:27:45.776 448 CSMG 547 ContentSetManager::DeleteChildren LDB Updating ID Record:
+ fid 0x1000000001DF2
+ usn 0x0
+ uidVisible 0
+ filtered 0
+ journalWrapped 0
+ slowRecoverCheck 0
+ pendingTombstone 1
+ internalUpdate 0
+ dirtyShutdownMismatch 0
+ meetInstallUpdate 0
+ meetReanimated 0
+ recUpdateTime 20140505 11:56:12.179 GMT
+ present 1
+ nameConflict 0
+ attributes 0x10
+ ghostedHeader 0
+ data 0
+ gvsn {BE36C74B-B5FC-4E8A-8735-039CF9FB3982}-v1264133
+ uid {BE36C74B-B5FC-4E8A-8735-039CF9FB3982}-v1264133
+ parent {29CFABC2-0180-41C7-A9CE-21DD92783892}-v6880183
+ fence Initial Sync (1)
+ clockDecrementedInDirtyShutdown 0
+ clock 20140501 00:01:02.367 GMT (0x1cf64d070b1522c)
+ createTime 20140124 09:37:42.441 GMT
+ csId {2D9CF1D7-50E2-4B3E-AC6B-3D60C6B026EB}
+ hash 00000000-00000000-00000000-00000000
+ similarity 00000000-00000000-00000000-00000000
+ name batman
+
20140513 23:27:45.776 448 LDBX 4435 Ldb::InsertWalkerJob Inserting dirWalkerJob:uid:{BE36C74B-B5FC-4E8A-8735-039CF9FB3982}-v1264133 moveType:MoveOut (2) at time:20140514 03:27:45.776
20140513 23:27:45.807 448 DIRW 647 DirWalkerTask::QueueMoveoutJob Queueing move-out uid:{BE36C74B-B5FC-4E8A-8735-039CF9FB3982}-v1264133 fid:0x1000000001DF2
20140513 23:27:45.807 2372 DIRW 317 DirWalkerTask::Run Start walking directory.
20140513 23:27:45.807 2372 DIRW 1373 DirWalkerTask::MoveoutStep Starting to process move-out job. uid:{BE36C74B-B5FC-4E8A-8735-039CF9FB3982}-v1264133
20140513 23:27:45.807 2372 DIRW 1398 DirWalkerTask::MoveoutStep Iterating children of uid: {BE36C74B-B5FC-4E8A-8735-039CF9FB3982}-v1264133
20140513 23:27:45.807 2372 DIRW 2764 DirWalkerTask::TombstoneOrDelete LDB Updating ID Record:
+ fid 0x1000000001DF2
+ usn 0x0
+ uidVisible 0
+ filtered 0
+ journalWrapped 0
+ slowRecoverCheck 0
+ pendingTombstone 0
+ internalUpdate 0
+ dirtyShutdownMismatch 0
+ meetInstallUpdate 0
+ meetReanimated 0
+ recUpdateTime 20140505 11:56:12.179 GMT
+ present 0
+ nameConflict 1
+ attributes 0x10
+ ghostedHeader 0
+ data 0
+ gvsn {BE36C74B-B5FC-4E8A-8735-039CF9FB3982}-v1376267
+ uid {BE36C74B-B5FC-4E8A-8735-039CF9FB3982}-v1264133
+ parent {29CFABC2-0180-41C7-A9CE-21DD92783892}-v6880183
+ fence Default (3)
+ clockDecrementedInDirtyShutdown 0
+ clock 20140514 03:27:45.776 GMT (0x1cf6f247911f746)
+ createTime 20140124 09:37:42.441 GMT
+ csId {2D9CF1D7-50E2-4B3E-AC6B-3D60C6B026EB}
+ hash 00000000-00000000-00000000-00000000
+ similarity 00000000-00000000-00000000-00000000
+ name batman
+
20140513 23:27:45.807 2372 DIRW 101 DirWalkerTask::Job::Finish MoveOut csId:{2D9CF1D7-50E2-4B3E-AC6B-3D60C6B026EB} uid:{BE36C74B-B5FC-4E8A-8735-039CF9FB3982}-v1264133
20140513 23:27:45.807 2372 DIRW 893 DirWalkerTask::RemoveJob Removing job type:2 uid:{BE36C74B-B5FC-4E8A-8735-039CF9FB3982}-v1264133
20140513 23:27:45.807 2372 LDBX 4472 Ldb::DeleteWalkerJob Deleting dirWalkerJob. uid:{BE36C74B-B5FC-4E8A-8735-039CF9FB3982}-v1264133
20140513 23:27:45.807 2372 DIRW 364 DirWalkerTask::Run Exit.
答案1
这是一个稍微陈旧的问题,但您是否探索过“暂存”和“冲突和已删除”文件夹?
您可能遇到这种情况的一种原因是这些文件夹中存在未得到正确解析的剩余文件或碎片。您可以清理这些位置以手动“重置”双方的同步。但是,我还会调查文件夹的来源并确保:
- 相关文件/文件夹未设置冲突的权限。
- 由于脚本或同步任务太旧或配置错误,另一台服务器或端点不会重复创建此文件夹。