This post is more than 5 years old
22 Posts
0
5333
July 16th, 2010 02:00
MSSQL backup: local backup succeeds, using nsrexecd fails
Hello list,
I've got a, rather strange, problem with backing up MSSQL databases on a MS cluster. Running this:
nsrsqlsv.exe -c client.local -m CLIENT.local -s backup.local -g Default -LL -t 1279270353 -l incr -q -W 78 -N MSSQL: MSSQL:
from the command line works. But started from nsrexecd fails? Error message:
43338 1279270858 1 0 0 3840 616 0 host.local (pid616) 4 %s 1 0 205 C:\Program Files\Legato\nsr\bin\nsrsqlsv.exe -c client.local -s backup.local -g Default -LL -m CLIENT.local -t 1279270843 -l incr -q -W 78 -N MSSQL: MSSQL:
29085 1279270868 5 0 0 3840 616 0 host.local (pid616) 36 Microsoft SQL Server Provider error: 0
38006 1279270868 5 0 0 3840 616 0 host.local (pid616) 3 %s. 1 24 69 Named Pipes Provider: Could not open a connection to SQL Server [2].
38006 1279270868 5 0 0 3840 616 0 host.local (pid616) 3 %s. 1 24 221 An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.
38006 1279270868 5 0 0 3840 616 0 host.local (pid616) 3 %s. 1 24 21 Login timeout expired
67945 1279270868 5 0 0 3840 616 0 host.local (pid616) 44 Cannot login to SQL Server Default Instance. 0
I've even started the command using runas as administrator, and that works fine.
Can anyone shed some light on the issue?
Some info:
MSSQL 2005
Windows 2003
NW client 7.6, LNMs_2008.Build.299
Backup server 7.6 on 2008R2
Many thanks, regards, Edgar Matzinger (using the account of a colleague).
BSequeira
30 Posts
0
July 16th, 2010 03:00
Hi,
My first troubleshooting step would be disabling User Account Control on the 2008 machine, and test the backup again (Requires Reboot).
That would probably work, but if you still have the same problem, check if Remote connectios are allowed on the SQL server.
Also check the remote user and password on your client configuration. These setting should match your SQL account.
Hope it helps.
Regards
Bruno
rovinabi
55 Posts
1
July 16th, 2010 16:00
This definitly looks like a authentication issue on the SQL application.
Just add any user in the sysadmin group to the remote user/password field of the client properties and try a backup. If it succeeds, then create a generic service account that can be used as a backup account. That shouls solve your problem.
HTH,
Rovin D'Souza.
jvdp2002
22 Posts
0
July 19th, 2010 02:00
Hello list,
I've "resolved" the issue by having nsrexecd running with my credentials. I've
added myself to the local backup users group and changed the nsrexecd service
to log in using my credentials, and restarted the service.
Many thanks, regards, Edgar.
jvdp2002
22 Posts
0
September 1st, 2010 04:00
Hello list,
I've switched to using NMM and there this issue does not reveal itself.
Regards, Edgar.