Azure文件同步 - 服务器2019 - Cloud Tiering无法处理重复数据删除卷 [英] Azure File Sync - Server 2019 - Cloud Tiering not working on Deduplication Volume

查看:87
本文介绍了Azure文件同步 - 服务器2019 - Cloud Tiering无法处理重复数据删除卷的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我们有一个运行带有GUI的Server 2019 Standard和Azure File Sync Agent版本6.1的文件服务器。数据驱动器设置为启用重复数据删除,并且包含Azure文件共享,并在同步组服务器端点
设置中启用了云分层。 

We have a file server running Server 2019 Standard with GUI and the Azure File Sync Agent version 6.1. The data drive is set with deduplication enabled and it contains an Azure File Share with the Cloud Tiering enabled in the sync group server end point settings. 

服务器位于已从启用了重复数据删除和Azure文件同步的Server 2012 R2升级,但升级前未启用云分层。

The server was in place upgraded from Server 2012 R2 with deduplication and Azure File Sync enabled, but cloud tiering not turned on before the upgrade.

升级完成后,云分层设置为保持90%的免费驱动并缓存超过1天未被访问或修改的所有内容,但似乎没有发生分层。 

After the upgrade was complete Cloud Tiering was set to keep 90% of the drive free and cache everything that's not been accessed or modified in more than 1 day but no tiering appears to be happening. 

文件同步代理日志事件6004显示所有文件都是由于不重新支持的重新分析点而被跳过。

The file sync agent log event 6004 is showing that all files are being skipped due to unsupported reparse point.

有关如何在不禁用重复数据删除和重新注释卷的情况下进行分层工作的任何建议?

Any suggestions on how to get tiering working without disabling deduplication and re-inflating the volume?

推荐答案

您目前使用的是哪种特定的Sync Agent版本?
What specific Sync Agent version are you currently using ?


这篇关于Azure文件同步 - 服务器2019 - Cloud Tiering无法处理重复数据删除卷的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

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