We are trying to discontinue the use of TLS 1.0 and move to TLS 1.2 for tighter security. I have all SQL Servers patched to the newest levels. SQL backups work fine on TLS 1.0 machines, but machines that have TLS 1.0 disabled (thereby using TLS 1.2 instead), fail with the message

From the many forum posts I read, it seems that everyone is sticking with TLS 1.0, which is not the greatest idea. Does Veeam B&R not work properly with TLS 1.2? Do I just need to update SQL Server provider(s) on the Veeam B&R server? What is the proper way to do this? I want to do this safely without breaking communications to older machines still using TLS 1.0.

I have run into this same issue on my VM's and the above suggestion by VanillaMastermind did the trick. However, I am now having the issue with a physical server, does anyone know the correct place in the registry to mitigate this problem, as "HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Backup and Replication\" does not exist on systems managed by the Veeam Agent. I have done some research and came up blank.

In case anyone else was struggling with this, even after applying the suggested registry key:
I was getting the SSL error on VMs that were running SQL Server after having disabled TLS 1.0 throughout our domain, so I tried creating the UseSqlNativeClientProvider registry key under Veeam Backup and Replication - since it's a VM backup, that's the expected place, right? Well, it didn't help. So I took a look at the Veeam Endpoint Backup and noticed a bunch of info about our backup server recorded in there and figured I might as well try creating the UseSqlNativeClientProvider key in there. Success! No more SSL error.