Azure文件同步 - 陷入待定 [英] Azure File Sync - Stuck at Pending

查看:62
本文介绍了Azure文件同步 - 陷入待定的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

您好,


我目前使用FS角色进行3节点群集设置,并在所有3个节点上安装了Azure Sync Agent。


目前我已设置2个同步组设置同步2个不同的端点。


其中一个端点按预期工作,同步更改和所有端点。


但是,另一个端点似乎没有同步并且现在过去3天仍处于"待定"状态。


我查看了日志和诊断信息,更改了节点但似乎没有工作。



有什么建议吗?


非常感谢

解决方案


如果您发现任何e,请查看您的活动日志并通知我rror消息或代码?





只是为了澄清:你有没有提到这个

文章





要确定文件未同步到Azure文件共享的原因,请在
HomeFilesAFS服务器上运行AFSDiag(说明在故障排除 
guide < span style ="font-size:10.0pt; font-family:'Verdana',sans-serif;颜色:#333333; background:white">
请发送输出文件(.zip文件)
AZCommunity [AT] microsoft.com
请在主题栏中注明"ATTN subm"。





附加信息:


原因是可以创建在
中包含"无效"字符的文件或文件夹名称。这导致初始同步失败。


无法通过REST API(Portal
或存储资源管理器)创建(也不能访问,也不重命名或删除)这些类型的文件名。但是可以通过SMB连接创建(和重命名)它们在Windows上。


解决方案,通过SMB在Windows上挂载文件共享,遍历整个层次结构,寻找
异常的名称(在我的情况下是字符\ u0081),重命名它们,然后同步将成功。



如果上述情况有所帮助或者您需要在这个问题上需要进一步的帮助,请告诉我们。


------------------------------------- -------------------------------------------------- ---


点击帮助您的帖子上的"标记为答案",这对其他社区成员有益。




Hello,

I currently have 3 node cluster setup using FS role and have installed Azure Sync Agent on all 3 nodes.

Currently I have setup 2 Sync Groups setup syncing 2 different endpoints.

One of the end points works as expected, syncing changes and all.

However, the other end point does not seems to sync and stays at 'Pending' status for past 3 days now.

I've looked at the logs and diagnostics, changed nodes but nothing seems to work.

Any suggestions?

Thank you so much

解决方案

Can you please check your event logs and let me know if you find any error message or code?


Just for clarification: Have you refer to this article.


To determine why the files are not syncing to the Azure File share, please run AFSDiag on the HomeFilesAFS sever (instructions are in the troubleshooting guide). Please send the output file (.zip file) to AZCommunity[AT]microsoft.com. Please mention "ATTN subm" in the subject field.


Additional information:

The cause is that it is possible to create file or folder names that have "invalid" characters in them. This caused the initial sync to fail.

These types of file names cannot be created (nor accessed nor renamed nor deleted) through the REST API (Portal or Storage Explorer). However they can be created (and renamed) through an SMB connection on Windows.

Solution, mount file share on Windows via SMB, walk through the entire hierarchy looking for names that are unusual (in my case it was the character \u0081), rename them, then sync will succeed.

Kindly let us know if the above helps or you need further assistance on this issue.

------------------------------------------------------------------------------------------

Do click on "Mark as Answer" on the post that helps you, this can be beneficial to other community members.



这篇关于Azure文件同步 - 陷入待定的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆