Failed to Verify the Connection to SQL Server

KB ID: 4190
Product: Veeam Backup for Microsoft Azure | 3.0 | 4.0
Published: 2021-09-29
Last Modified: 2022-08-10
Get weekly article updates
By subscribing, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.

Cheers for trusting us with the spot in your mailbox!

Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest

error icon

Oops! Something went wrong.

Please try again later.

Challenge

  • To back up a database, workers must be able to connect to the source SQL server.

    In case of consistent backup (using a staging server), the workers must connect to the staging server. Connection to the source server is not required as Microsoft Azure performs the copy from the source to the staging server.
  • To restore a database, workers must be able to connect to the target SQL server.

Cause

An error is reported when workers cannot reach SQL Servers. There can be different causes of such errors, for example:

  • Incorrect credentials used to log in to the server
  • Workers cannot reach the server due to networking issues

Solution

Incorrect credentials used to log in to the server

As the backup process is based on the BACPAC export, workers must connect using any SQL account to access the database.

  • For backup operations, the selected account must have access to all protected databases.
  • For restore operations, the account must have full access to the newly created (restored) databases.

 

Workers cannot reach the server due to networking issues

The virtual network where all Veeam Backup for Azure workers are running must be enabled in the SQL server firewall.

In case of the SQL Managed Instances, enable the public endpoint in the instance networking options and then configure the security group of the network where the SQL Managed Instance is connected.

If there are any other firewalls between Veeam Backup for Azure and the SQL Servers or SQL Managed Instances, they must be configured as well.

  • Connections to SQL Servers use port 1433.
  • Connection to SQL Managed Instances run on port 3342.
Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

Spelling error in text

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please try again later.

KB Feedback/Suggestion

This form is only for KB Feedback/Suggestions, if you need help with the software open a support case

By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Verify your email to continue your product download
We've sent a verification code to:
  • Incorrect verification code. Please try again.
An email with a verification code was just sent to
Didn't receive the code? Click to resend in sec
Didn't receive the code? Click to resend
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

error icon

Oops! Something went wrong.

Please try again later.