问题

存储利用率

b
Userlevel 1
徽章 +2
你好，

我已经打开了驻留在AHV上的一些文件服务器的Windows Dedup，但是降低存储并未反映在Prism上。关于为什么有什么想法吗？

我希望我可以运行AHV的容量缩放，但是上次我打开它时，我收到了以下警报：

请勿复制保护域xxxxxxx，该XXXXXX包括从存储容器中重复数据删除的实体，这些实体已启用到单个节点远程站点xxxxxxxx。（xxx表示省略的字段）
    \r\n
    \r\nI have turned on Windows Dedup for some of my file servers that reside on AHV, however the storage reduction is not reflected on Prism. Any thoughts as to why?
    \r\n
    \r\nI wish I could run the Capacity Dedup from AHV however the last time that I turned it on I received the following alert:
    \r\n
    \r\nDo not replicate protection domain XXXXXXX comprising entities from the storage container that have deduplication enabled to a single node remote site XXXXXXX. (XXX denote omitted field)","quoteUsername":"Brado-Mski","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
    该主题已关闭以供评论

    2个答复

    e
    Userlevel 1
    徽章 +1
    我认为Windows不会直接擦除已删除的文件“来自Dedupe或其他删除”，因此存储层将始终看到这些已删除文件的使用块。
    我不知道AHV，但是我认为您必须使用Sdelete或其他工具零填充已删除的块，以让存储层知道这些块不再使用这些块，以便它可以收回其使用的空间。
    \r\ni do not know about AHV, but i think you have to zero-fill the deleted blocks using sdelete or other tools to let the storage layer know these blocks are not used anymore so it can reclaim its used space.","quoteUsername":"eng_asfour","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
    ddubuque
    UserLevel 3
    徽章 +10
    因此，Nutanix将利用新写作，而不是现有的范围来利用能力固定。一种技巧是使用称为VDISK MANIPULATER的工具来指纹识别现有数据。这将使存储认为这是新的写作，并将其删除。我建议与支持交谈。他们会很乐意协助。

    该链接讨论了指纹过程。

    https://portal.nutanix.com/#/page/docs/details?targetId = advanced-admin-aos-v59:sto-vdisk-manipulator-t.html

    另一个替代方法是创建一个具有容量DEDUPE的新容器，并将VM迁移到新容器。牢记整体能力。两者都会产生额外的I/O，我已经完成了两者，这有帮助。
    大卫·杜比克（David Dubuque）||BKD ||Nutanix NTC 2019和2020 ||Nutanix技术咨询委员会成员||https://darklinkrising.com
    \r\n
    \r\nThis link talks about the fingerprinting process.
    \r\n
    \r\nhttps:\/\/portal.nutanix.com\/#\/page\/docs\/details?targetId=Advanced-Admin-AOS-v59:sto-vdisk-manipulator-t.html
    \r\n
    \r\nAnother alternative is to create a new container with capacity dedupe and migrate the VM to the new container. Keeping your overall capacity in mind. Both will generate additional I\/O I've done both and it helps.","quoteUsername":"ddubuque","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
    条款和条件
    Learn more about our cookies.<\/a>","cookiepolicy.button":"Accept cookies","cookiepolicy.button.deny":"Deny all","cookiepolicy.link":"Cookie settings","cookiepolicy.modal.title":"Cookie settings","cookiepolicy.modal.content":"We use 3 different kinds of cookies. You can choose which cookies you want to accept. We need basic cookies to make this site work, therefore these are the minimum you can select. Learn more about our cookies.<\/a>","cookiepolicy.modal.level1":"Basic
    Functional","cookiepolicy.modal.level2":"Normal
    Functional + analytics","cookiepolicy.modal.level3":"Complete
    Functional + analytics + social media + embedded videos"}}}">
    Baidu