New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update with newer Windows Server limitations #2482
Comments
Hi, Is this feature in any time will be available in win10? I think this will be a great thing happens to end users who don't have extra storage and resources to enhance their storage. Thanks |
Thanks for your dedication to our documentation. If we have been unable to review your issue in a timely manner, we sincerely apologize for the delayed response. We have captured the informtion you have provided for review. We are closing this issue for now, but if you feel that it's still a concern, please respond and let us know. If you determine another possible update to our documentation, please don't hesitate to reach out again. #please-close |
Please reopen. The documentation still refers to 2016 and 2012R2, despite there being 2 mainstream releases and multiple ASHCI releases since then, all with improvements. |
Hi @eponerine Thank you for your response! |
Thanks for the feedback. The addition of ReFS support that arrived in Windows Server 2019 has already been added to this article since this issue was opened. 64TB is still the maximum limit on a dedup'd volume. This article will still contain references to specific Windows Server releases (e.g. 2016 and 2012 R2) as it's a What's New article designed to capture those changes as a point in time. I have pushed a few minor changes that should be visible later today for clarity. |
#assign:dknappettmsft |
#please-close |
Support for XXXXX references updates in 2016 from 2012 R2. With the addition of deduplication + ReFS and multiple new OS's having come out, can we have official guidance on supported deployments.
For example - Support for Large Volumes - is there still a max limit of 64TB on a dedup'd volume?
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
The text was updated successfully, but these errors were encountered: