SQL intelligent policy for DB on non standard port

[albatroz19]

Hi,
i've configured a new backup for db sql that is configured on non his default port. It's a two node cluster failover, and backup fail with this error:

12-gen-2024 19.47.38 - Info dbclient (pid=13684) INF - Intelligent policy initiated by server <bckprimary09>
12-gen-2024 19.47.38 - Info dbclient (pid=13684) INF - Intelligent policy <SQL-INT_WIN_2W_TEST> is valid. The input file <C:\Program Files\Veritas\NetBackup\dbext\mssql\input.7868.10680.0112124.194737> has been parsed successfully
12-gen-2024 19.47.39 - Info dbclient (pid=13684) INF - <GRFDMS100MM001> is a Failover Cluster Instance. Using virtual name <GRFDMS100MM001.domain.local>
12-gen-2024 19.48.09 - Info dbclient (pid=13684) DBMS MSG - ODBC return code <-1>, SQL State <08001>, SQL Message <-1><[Microsoft][SQL Server Native Client 11.0]SQL Server Network Interfaces: Error Locating Server/Instance Specified [xFFFFFFFF]. >.
12-gen-2024 19.48.09 - Info dbclient (pid=13684) DBMS MSG - SQL Message <-1><[Microsoft][SQL Server Native Client 11.0]A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online.>
12-gen-2024 19.48.09 - Info dbclient (pid=13684) DBMS MSG - SQL Message <0><[Microsoft][SQL Server Native Client 11.0]Login timeout expired>
12-gen-2024 19.48.39 - Info dbclient (pid=13684) DBMS MSG - ODBC return code <-1>, SQL State <08001>, SQL Message <-1><[Microsoft][ODBC Driver 17 for SQL Server]SQL Server Network Interfaces: Error Locating Server/Instance Specified [xFFFFFFFF]. >.
12-gen-2024 19.48.39 - Info dbclient (pid=13684) DBMS MSG - SQL Message <-1><[Microsoft][ODBC Driver 17 for SQL Server]A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online.>
12-gen-2024 19.48.39 - Info dbclient (pid=13684) DBMS MSG - SQL Message <0><[Microsoft][ODBC Driver 17 for SQL Server]Login timeout expired>
12-gen-2024 19.50.50 - Info dbclient (pid=13684) DBMS MSG - ODBC return code <-1>, SQL State <08001>, SQL Message <17><[Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or access denied.>.
12-gen-2024 19.50.51 - Info dbclient (pid=13684) DBMS MSG - SQL Message <67><[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Connect()).>
12-gen-2024 19.50.51 - Info dbclient (pid=13684) ERR - Unable to login into SQL instance <GRFDMS100MM001.griffon.local\GRFDMS100MM001> as user <sa> using standard connection.
12-gen-2024 19.50.51 - Info dbclient (pid=13684) ERR - Internal error. See the dbclient log for more information.
12-gen-2024 19.50.51 - Info dbclient (pid=13684) INF - ODBC connection setup failed
12-gen-2024 19.50.51 - Info dbclient (pid=13684) USER - This object has not been initialized
12-gen-2024 19.50.52 - Error bpbrm (pid=22538) from client grfdms100mm001: ERR - exit status: <2>
12-gen-2024 19.50.52 - Error bpbrm (pid=22538) from client grfdms100mm001: ERR - bphdb exit status = 2: none of the requested files were backed up
12-gen-2024 19.50.52 - Info bphdb (pid=7868) done. status: 2: none of the requested files were backed up
12-gen-2024 19.50.52 - end writing
none of the requested files were backed up  (2)


Please someone has idea in order to resolve.

Thanks and Regards

[admin_bkp007]

Do you check everything about list compatibility? In console NBU/APPLICATION/SQL checked was set cluster instead of node ?

[X2]

Were you able to successfully register the instance from the NetBackup console > NetBackup Management > Applications > MS SQL > All instances ?

[albatroz19]

Hi,
@admin_bkp007: I've configured backup using cluster name instead of node and compatibility is ok. Client and primary have 10.0.0.1 version.

@X2: I'm able to register sql instance without issue.

I think the problem is on port. On cluster there are multiple sql instances and DBA admin setted a non standard port at each sql. If i try to backup via batch file, setting port (BROWSECLIENT=GRFDMS100MM001,10334) it goes ok, but i would use intelligent policy.

any suggest?

Thanks in advance for support.

[Nick_Morris]

Have you tried what is in this article https://www.veritas.com/support/en_US/article.100055176 ?

[albatroz19]

Hi Nick_Morris,
thanks, but just tried technote on veritas support, so asked here for further reference.

Best Regards,

[albatroz19 · Accepted solution]

Hi,
after many attempts, the problem was alias name on SQL connection manager.

We added alias, and the backup succeded.

Regards,