This can cause DFS Replication to continually retry replicating the files, causing holes in the version vector and possible performance problems. For example, if a user copies a 10 megabyte (MB) file onto server A (which is then at the hard limit) and another user copies a 5 MB file onto server B, when the next replication occurs, both servers will exceed the quota by 5 megabytes.
It's possible for individual members of a replication group to stay within a quota before replication, but exceed it when files are replicated.
No folders may exceed the quota before the quota is enabled. Screened files must not exist in any replicated folder before screening is enabled. The hidden DfsrPrivate folder must not be subject to quotas or file screens. The following are best practices for implementing file screens or quotas: In addition, DFS Replication has its own filter mechanism for files and folders that you can use to exclude certain files and file types from replication. However, the File Server Resource Manager (FSRM) file screening settings must match on both ends of the replication.
0 kommentar(er)
