Can't connect Backup Pro on non-default port

john.vandajohn.vanda Posts: 6
edited December 14, 2010 4:22PM in SQL Backup Previous Versions
When SQL Server is not listening on port 1433 (we have listening on a non-default port enabled), we are unable to restore a backup file using backup pro, due to a connection timeout. When we change the MSSQLSERVICE port configuration for listening on port 1433 instead, and restart the sql service, we are able to restore files using SQL Backup Pro. This however is not ideal for us, as we prefer to keep port 1433 off. Please advise on if I'm doing something wrong in Backup Pro, or if there are any workarounds.

SQL BACKUP Pro Version 6.2.0.134
SQL Server 2008 Version 10.0.1600.22 (X64)
· Share on Twitter

Comments

  • peteypetey Posts: 2,358 New member
    The error indicates that the SQL Backup Agent service was unable to connect to the local SQL Server instance. Assuming that only the TCP/IP protocol has been enabled on the server side, your options are as follows:

    - enable the shared memory protocol
    Enable the shared memory protocol for both the server and client configuration.

    - change the default port
    Using the SQL Server client configuration utility, change the default port to which TCP/IP connections are made on the server.

    - use an alias
    Set up a TCP/IP alias using the SQL Server client configuration utilities. The alias needs to be identical to the SQL Server instance name, and map it to the correct port number.

    - add a SQL Backup registry key
    In the registry node HKLM\Software\Red Gate\SQL Backup\BackupSettingsGlobal\<instance name>, add a string value named SQLServerName. Enter the server name/IP address and the port number e.g. 127.0.0.1,1435

    The first 3 options are SQL Server options, and would affect other applications running on the server. The last option is a SQL Backup specific option.

    Thanks.
    Peter Yeoh
    SQL Backup Consultant Developer
    Associate, Yohz Software
    Beyond compression - SQL Backup goodies under the hood, updated for version 8
    · Share on Twitter
  • john.vandajohn.vanda Posts: 6
    Petey,
    Thanks for the tips. I went with the registry option and all is working well now on the non-standard port.

    --John
    · Share on Twitter
  • cgriffincgriffin Posts: 9
    Add a new SQL Server, then use SERVERNAME\INSTANCE,PORT to connect. You can then change the alias to just display the server name if you want your list to look clean.
    · Share on Twitter
Sign In or Register to comment.