@Gostev - Thanks for your message. I am really confused with this one. You are saying that this patch is not for Server 2016, but one of the links you posted says it is:https://blogs.technet.microsoft.com/filecab/2017/01/30/windows-server-2016-data-deduplication-users-please-install-kb3216755/
Will Gries from MS on the comments says:I’m working with the team responsible for the Microsoft Update Catalog to get the answer to this question. Note however that it is possible to download and install the “Windows 10” version of the package on Windows Server 2016.
But then you also say that someone else from MS says the update is not meant for server. What a mess. We seem to have one MS team saying something and another something else!
It looks like we have three options available to us:
Go back to Windows 2012 R2 by downgrading our central B&R server with all the risks that entails. Leave the other servers as 2016, working as storage repositories with KB3216755
Install another Veeam B&R server and move all backup jobs to it and let that server manage all the backup jobs. Keep the other servers as 2016 servers working as storage repositories with KB3216755
Since KB3216755 is not meant for server, go back to Windows 2012 R2 by downgrading all our B&R servers with all the risks that entails.
All our copy job storage repositories use Windows deduplication, so we can't run Windows 2016 without KB3216755 due to the corruption issues, but if the fix is not for servers and it is causing issues with Veeam and SQL comms, I see the third option as being the only viable one. Downgrade everything and hope for the best.
Quite ironic that we upgraded to 2016 due to the added benefits around deduplication!