SyncToy在DFS上生成DFSR 4304事件

问题描述

SyncToy 2.0.100.0为同步到DFS共享的每个文件生成DFSR 4304事件。 DFS服务器是Server 2008 R2 Enterprise 64位。

DFSR事件4304说明：由于在文件上遇到一致的共享冲突，已多次阻止DFS复制服务复制文件。由于共享冲突，该服务无法暂存文件以进行复制。

这是一个已知的问题吗？我猜synctoy在同步过程中由于某种原因在短时间内保持对文件的锁定。 DFS服务器确实在重试DFS同步时受到性能影响，特别是当某些用户同步15,000个已更改的文件时。事件日志将在几小时内填满。同时，CPU使用率比正常情况提高了20％。

解决方案

SyncToy 2.0.100.0 Generates a DFSR 4304 Event for every file it synchronizes to a DFS share. DFS server is Server 2008 R2 Enterprise 64-bit.

DFSR Event 4304 Description:
The DFS Replication service has been repeatedly prevented from replicating a file due to consistent sharing violations encountered on the file. The service failed to stage a file for replication due to a sharing violation. 
 
Is this a known issue? I guess synctoy maintains a lock on the file for a short period for some reason during the synchronization process. The DFS servers really take a performance hit from the retrying of DFS synchronization, especially when some users synchronize 15,000 changed files. The event log will fill up in a matter of hours. Meanwhile, CPU usage is up 20% from normal.

解决方案

这篇关于SyncToy在DFS上生成DFSR 4304事件的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！