https://login.veeam.com/en/oauth?client_id=nXojRrypJ8&redirect_uri=https%3A%2F%2Fwww.veeam.com%2Fservices%2Fauthentication%2Fredirect_url&response_type=code&scope=profile&state=eyJmaW5hbFJlZGlyZWN0TG9jYXRpb24iOiJodHRwczovL3d3dy52ZWVhbS5jb20va2IxMjQ5IiwiaGFzaCI6ImFhMDY2MGQwLThiZDgtNGRkZi04MGI4LTI1OWZmYmI5Y2M1OCJ9
1-800-691-1991 | 9am - 8pm ET
EN

SureBackup SQL Script Verification

Challenge

 



Cause

Port 1433 is disabled on the SQL server or there is a firewall preventing port 1433 from being used to communicate with the SQL server.

Solution

The SQL Server Configuration Manager provides basic configuration management for SQL Server services, server protocols, client protocols and client aliases.

On the SQL Server Instance you will need to ensure the TCP/IP Protocols is listening on port 1433 for the TCP port. You may also need to list this port for the TCP Dynamic Ports.

If you have changed this port for some reason, you will need to deploy a custom script for the verification section in SureBackup. After performing the script change in production, please perform another backup job for verification.

More information

Confirm the status of this port by performing "netstat -ban" on the masqueraded SQL server, from the command prompt.

For information on deploying a custom script please review this Veeam article: 
http://www.veeam.com/KB1312

KB ID:
1249
Product:
Veeam Backup & Replication
Version:
5.x
Published:
2011-09-30
Last Modified:
2020-08-13
Please rate how helpful this article was to you:
5 out of 5 based on 1 ratings
Thank you for helping us improve!
An error occurred during voting. Please try again later.

Couldn't find what you were looking for?

Below you can submit an idea for a new knowledge base article.
Report a typo on this page:

Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!

Spelling error in text

Knowledge base content request
By submitting, you agree that your personal data will be managed by Veeam in accordance with the Privacy Policy.
Your report was sent to the responsible team. Our representative will contact you by email you provided.
We're working on it please try again later