I get this from the daemon log on the client when I try to use the GUI - nsrexecd 215 Authentication Warning: The user's OS groups cannot be verified and will not be included in the credential. This means that remote hosts may not see the user as being a member of any OS groups. Domain: %s, User: %s. 2 0 7 MYDOMAIN 13 7 d.knapp.
It looks like an issue with ODBC driver. When googling for these SQl error you find several hits which may apply to your case, but SQL admin should be involved to trace those and verify them first.
I am the SQL admin as well. I tried running from the client, same errors. This was working for a while, then started getting these errors. I ran several full backups from the default group last week, then moved client to another group. They started failing then, although that may have been a coincidence. Runs from the default group no longer work either. When running from the server, it does not recognize the cluster name, even though the command is "nsrsqlsv - a virtualname-sql -R -v". The virtualname is correct. We get
savegrp: suppressed 1 lines of output. 29100:(pid 1376): Invalid SQL virtual server name virtuaname-sql 38563:(pid 1376): Invalid option -a
Do I need to create a client with the virtual name as well as the individual node names? I tried that but was not successful.
We have Power Edition. That is supposed to have two cluster connections with it, but it does not look like they are being used, although I cannot really tell. The license conformance summary does not mention them.
Well, as SQL admin you surprised me with -R as MS itself does not recommend that (it kills PIT restore). -v you can also skip. I believe you use GA module version. Try to get from support build 358. I use that one and had never problems with it (not that I imply there is a problem, but... you get an idea). In my case, almost all SQL machines are VMs, but I have one physical cluster. What I use as backup command is:
nsrsqlsv -c -a SQLCLUSTERNAME
For -c I use FQDN as I use always FQDN for client names in NW. -a is shortname of course representing SQL cluster name.
I do not use any special user for this backup as local system is authorized as SQL admin.
david_knapp
1 Rookie
•
122 Posts
0
October 21st, 2011 09:00
I get this from the daemon log on the client when I try to use the GUI - nsrexecd 215 Authentication Warning: The user's OS groups cannot be verified and will not be included in the credential. This means that remote hosts may not see the user as being a member of any OS groups. Domain: %s, User: %s. 2 0 7 MYDOMAIN 13 7 d.knapp.
david_knapp
1 Rookie
•
122 Posts
0
October 24th, 2011 06:00
Also, this in the monitor log:
52775 1319462562 5 0 0 3984 3948 0 servername.us.xxx.com (pid3948) 23 COM Error. Code = %08lx 1 1 11 -2147217887
ble1
4 Operator
•
14.4K Posts
0
October 24th, 2011 10:00
It looks like an issue with ODBC driver. When googling for these SQl error you find several hits which may apply to your case, but SQL admin should be involved to trace those and verify them first.
david_knapp
1 Rookie
•
122 Posts
0
October 24th, 2011 11:00
I am the SQL admin as well. I tried running from the client, same errors. This was working for a while, then started getting these errors. I ran several full backups from the default group last week, then moved client to another group. They started failing then, although that may have been a coincidence. Runs from the default group no longer work either. When running from the server, it does not recognize the cluster name, even though the command is "nsrsqlsv - a virtualname-sql -R -v". The virtualname is correct. We get
savegrp: suppressed 1 lines of output.
29100:(pid 1376): Invalid SQL virtual server name virtuaname-sql
38563:(pid 1376): Invalid option -a
Do I need to create a client with the virtual name as well as the individual node names? I tried that but was not successful.
We have Power Edition. That is supposed to have two cluster connections with it, but it does not look like they are being used, although I cannot really tell. The license conformance summary does not mention them.
ble1
4 Operator
•
14.4K Posts
0
October 24th, 2011 11:00
Well, as SQL admin you surprised me with -R as MS itself does not recommend that (it kills PIT restore). -v you can also skip. I believe you use GA module version. Try to get from support build 358. I use that one and had never problems with it (not that I imply there is a problem, but... you get an idea). In my case, almost all SQL machines are VMs, but I have one physical cluster. What I use as backup command is:
nsrsqlsv -c -a SQLCLUSTERNAME
For -c I use FQDN as I use always FQDN for client names in NW. -a is shortname of course representing SQL cluster name.
I do not use any special user for this backup as local system is authorized as SQL admin.