Backup SQL with TLS-certificate

[Magz]

Hi

We have a Microsoft SQL 2022-server with a TLS-certificate attached to SQL-protocols. The certificate contains the public name of the SQL-service, which differs from the Windows servername.

To connect to the SQL-server with SQL-tools, we need to use the public name of the server, and that is working fine. Veeam on the other hand try to use the Windows servername to connect to SQL to do the application-processing. This is not successful since connections need to match the public name in the TLS-certificate.

Due to this, application processing is not working when we do the backupups.

Is there a way to make Veeam use the public name when it connects to SQL, or resolve this issue in any other way?

Regards
Magne

[PetrM]

Hi Magne,

There is no option to change the name used to connect to the SQL server. But could you please share the error message that you see and the support case ID?

Thanks!

[Magz]

Hi Petr

The error-message is: 8/10/2023 5:40:05 AM :: Failed to create VM recovery checkpoint (mode: Veeam application-aware processing) Details: Unable to perform application-aware processing because connection to the guest could not be established"

This was working fine before I installed the TLS-certificate.

I will create a supportcase next week.

[PetrM]

Hello,

Ok, let's wait for what support finds out. If the connectivity issue persists due to a certificate configuration, the only thing I can do is add your feature request to the list of improvements in next versions. So far, you can play with this tool to check connectivity to SQL server.

Thanks!