Networker SQL Cluster client fails during creation

Question

Hi guys,  We have the below environment: Windows SQL Failover Cluster, 4 nodes, 4 instances without availability groups. Networker 19.4, Linux server.  I am trying to create a client from the management console, i am configuring the Virtual Node: sqlserver-cluster.domain.local, adding the physical hosts to remote access and at the next step the client creation is failing.  nsrsqlra.raw logs are below:  86373 1621253856 0 0 0 3528 14000 0 sql03.domain.local nsrnmsqlra NSR info 25 Start retrieving savesets 00 1621253976 1 0 0 3528 14000 0 sql03.domain.local nsrnmsqlra NSR notice 42 get_federated_savesets: No savesets found. 086378 1621253976 0 0 0 3528 14000 0 sql03.domain.local nsrnmsqlra NSR info 24 End retrieving savesets. 043708 1621254066 1 0 0 20964 5360 0 sql03.domain.local nsrnmsqlra NSR notice 14 Start time: %s 1 35 24 Mon May 3 15:21:06 202143621 1621254066 1 0 0 20964 5360 0 sql03.domain.local nsrnmsqlra NSR notice 35 Computer Name: %s User Name: %s 2 12 4 sql03 13 7 BackupUser37693 1621254067 0 0 0 20964 5360 0 sql03.domain.local nsrnmsqlra NSR info 57 SQL Connection to %s is created. SQL Server Version is %s 2 0 13 SQL\SQL15 0 10 15.00.200037953 1621254067 0 0 0 20964 5360 0 sql03.domain.local nsrnmsqlra NSR info 38 (%s)%d:query SQL server with %s failed 3 23 47 D:/views/nw/19.4/nsr/db_apps/bsmsql/sqlutil.cpp 1 5 17605 0 221 SELECT name FROM msdb.sys.availability_groups inner join msdb.sys.availability_group_listeners on availability_groups.group_id=availability_group_listeners.group_id where availability_group_listeners.dns_name='sqlserver-cluster'37693 1621254067 0 0 0 20964 5360 0 sql03.domain.local nsrnmsqlra NSR info 57 SQL Connection to %s is created. SQL Server Version is %s 2 0 9 SQL1\SQL16 0 10 15.00.200037953 1621254067 0 0 0 20964 5360 0 sql03.domain.local nsrnmsqlra NSR info 38 (%s)%d:query SQL server with %s failed 3 23 47 D:/views/nw/19.4/nsr/db_apps/bsmsql/sqlutil.cpp 1 5 17605 0 221 SELECT name FROM msdb.sys.availability_groups inner join msdb.sys.availability_group_listeners on availability_groups.group_id=availability_group_listeners.group_id where availability_group_listeners.dns_name='sqlserver-cluster'37693 1621254067 0 0 0 20964 5360 0 sql03.domain.local nsrnmsqlra NSR info 57 SQL Connection to %s is created. SQL Server Version is %s 2 0 9 SQL2\SQL21 0 10 15.00.200037953 1621254067 0 0 0 20964 5360 0 sql03.domain.local nsrnmsqlra NSR info 38 (%s)%d:query SQL server with %s failed 3 23 47 D:/views/nw/19.4/nsr/db_apps/bsmsql/sqlutil.cpp 1 5 17605 0 221 SELECT name FROM msdb.sys.availability_groups inner join msdb.sys.availability_group_listeners on availability_groups.group_id=availability_group_listeners.group_id where availability_group_listeners.dns_name='sqlserver-cluster'37693 1621254067 0 0 0 20964 5360 0 sql03.domain.local nsrnmsqlra NSR info 57 SQL Connection to %s is created. SQL Server Version is %s 2 0 9 SQL3\SQL31 0 10 15.00.200037953 1621254067 0 0 0 20964 5360 0 sql03.domain.local nsrnmsqlra NSR info 38 (%s)%d:query SQL server with %s failed 3 23 47 D:/views/nw/19.4/nsr/db_apps/bsmsql/sqlutil.cpp 1 5 17605 0 221 SELECT name FROM msdb.sys.availability_groups inner join msdb.sys.availability_group_listeners on availability_groups.group_id=availability_group_listeners.group_id where availability_group_listeners.dns_name='sqlserver-cluster' I have also added the physical nodes as clients to Networker. Is this an issue with permissions on the SQL Cluster? Permissions have been granted to BackupUser and Networker services are running with this account.  Any assistance is much appreciated.

Federal2004 · Accepted Answer

Thank you @crazyrov for all the tips. The issue was that the Networker client was not properly registered.

crazyrov · Answer

@Federal2004, you might have to create the client instance manually for Virtual instance to see what the issue. Make sure that the user that you are using for the configuration has sysdba privileges.

Federal2004 · Answer

@crazyrov thank you for the reply.

The user has system,sysadmin and dbcreator permissions.

Manually adding the client is failing as well.

The user is also Domain Admin and member of local administrators, backup and remote users.

crazyrov · Answer

@Federal2004, the only reason a manual client configuration will fail is because NetWorker wont be able to resolve a hostname of the client that you are adding. If that is the case you might have to do a hosts file entry for the cluster name on the NetWorker server. What is the error that you are seeing ?

Federal2004 · Answer

I created a client for the sql cluster manually, at global (2 of 2) i added all the nodes and *@*.

The backup command is: nsrsqlsv.

The backup is failing now with the error: Cannot run savefs: No error. Maybe i am missing the correct save sets here?

What should the saveset be? At the moment i have 5 SQL instances at the cluster.

Federal2004 · Answer

One more thing to add, during sql-cluster creation, i reached the step where i could not expand the database cluster and view the databases.

crazyrov · Answer

savefs is the probe job or initial connectivity check of a kind. So this means that there is an issue with communication between the backup server and active node.

NetWorker

Was this post helpful?