Perhaps this is because of complexities associated with opening a support case with Microsoft? There were a number of comments about this a few pages back. We don't mind doing this as long as this accelerates the resolution for our customers, even when the issue is outside of the Veeam code.tsightler wrote:I think the important thing to remember is that it's a Microsoft test "hotfix". I'm pretty amazed that Veeam support is the one sharing it to begin with as they can't really answer any detailed questions on how it works or what it does, only pass along the same information they already have (the same that has been posted in this forum).
In any case, we have good collaboration with the ReFS team and they are currently very engaged. The current fix seems to be solving the big part of the issue, so there's definitely some progress. More importantly, in most cases it makes the system stable enough to remove the need to migrate off of ReFS, so those customers can continue doing backups while ReFS team is looking at the remaining issue.
I will keep everyone posted on all material updates.
