Shulou(Shulou.com)06/03 Report--

Problems of one kind or another are often encountered during the operation and maintenance of DFS, resulting in poor DFS replication, and some files cannot be copied synchronously. Here are 2 common problems and solutions.

1.DFS reported an error and failed to copy normally because of a sharing conflict.

First of all, we export the diagnostic results through our own diagnostic report. We can see the details of sharing conflicts in the report, and we can find out which files caused the sharing conflicts, as shown below:

On the way, we can see the affected folder and the file path. The solution is to manually copy the conflicting files to the DFS member server, or delete the conflicting files on other member servers, restart the dfs service after execution is complete, let the dfs server re-detect the replication relationship, and check whether the initialization replication log is generated, and then we generate a diagnostic report. You will find that the content of the sharing conflict has been resolved and the DFS replication status has returned to normal.

2.DFS replication encountered ESF encryption

When DFS encounters a file encrypted by ESF in the process of copying, an error log will appear, and the path and name of the file will be marked in the log. When this problem occurs, we need to find the file. At this time, the encrypted file will be displayed in green. We find the file, right-click its properties, select Advanced, and then open the details of step 3 in the following figure to see who encrypted the file. All we have to do is find the user and ask him to decrypt the file.

3. Use the command to query the hoarding files of DFSR. If there are hoarding files that indicate that the server data of the members of the replication group are not fully synchronized, then we need to check the log to see if there are any errors or whether the replication plan is inappropriate and needs to be adjusted.

Dfsrdiag backlog / rgname: name of replication group / rfname: name of replication folder / smem: sending member / rmem: receiving member

As can be seen from the figure above, there is no hoarding of files in the replication group of the test center, indicating that the data of the servers on both sides are the same, while 51174 files are hoarded in the electrical performance test, indicating that the data of the servers on both sides are not consistent. My hoarding is because my replication plan is set to work hours not to replicate, so there are so many hoarding files.

If you have encountered other problems during the operation and maintenance of DFS, you are welcome to share them.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.