38006:(pid 13664):BACKUP DATABASE is terminating abnormally..
98519:(pid 13664): Unable to setup direct save with server system.domain.com: Client 'client.domain.com' is not properly configured on the NetWorker Server..
98519:(pid 13664): Unable to setup direct save with server system.domain.com: Client 'client.domain.com' is not properly configured on the NetWorker Server..
53084:(pid 13664):Processing model failed, the item will be skipped.
37994:(pid 13664):Backing up msdb...
4690:(pid 13664):BACKUP database [msdb] TO virtual_device='Legato#055546de-1000-4e05-b66b-252fb0058a87' WITH name=N'LegatoNWMSQL', description=N'MSSQL:'
98519:(pid 13664): Unable to setup direct save with server system.domain.com: Client 'client.domain.com' is not properly configured on the NetWorker Server..
38008:(pid 13664):Internal system error, please see nsr\applogs\xbsa.messages on the client system for reason.
29085:(pid 13664):Microsoft SQL Server Provider error:
38006:(pid 13664):Write on "Legato#055546de-1000-4e05-b66b-252fb0058a87" failed: 995(The I/O operation has been aborted because of either a thread exit or an application request.).
38006:(pid 13664):A nonrecoverable I/O error occurred on file "Legato#055546de-1000-4e05-b66b-252fb0058a87:" 995(The I/O operation has been aborted because of either a thread exit or an application request.)..
38006:(pid 13664):BACKUP DATABASE is terminating abnormally..
98519:(pid 13664): Unable to setup direct save with server system.domain.com: Client 'client.domain.com' is not properly configured on the NetWorker Server..
53084:(pid 13664):Processing msdb failed, the item will be skipped.
crazyrov
4 Operator
•
1.3K Posts
0
May 28th, 2015 03:00
you have to add the user "NT AUTHORITY\SYSTEM" sysadmin or you can put a user credentials that has sysadmin permission to the client configuration.
sokundu
1 Rookie
•
47 Posts
0
May 28th, 2015 04:00
Now I am getting this error message:
suppressed 4607 bytes of output.
38006:(pid 13664):BACKUP DATABASE is terminating abnormally..
98519:(pid 13664): Unable to setup direct save with server system.domain.com: Client 'client.domain.com' is not properly configured on the NetWorker Server..
98519:(pid 13664): Unable to setup direct save with server system.domain.com: Client 'client.domain.com' is not properly configured on the NetWorker Server..
53084:(pid 13664):Processing model failed, the item will be skipped.
37994:(pid 13664):Backing up msdb...
4690:(pid 13664):BACKUP database [msdb] TO virtual_device='Legato#055546de-1000-4e05-b66b-252fb0058a87' WITH name=N'LegatoNWMSQL', description=N'MSSQL:'
98519:(pid 13664): Unable to setup direct save with server system.domain.com: Client 'client.domain.com' is not properly configured on the NetWorker Server..
38008:(pid 13664):Internal system error, please see nsr\applogs\xbsa.messages on the client system for reason.
29085:(pid 13664):Microsoft SQL Server Provider error:
38006:(pid 13664):Write on "Legato#055546de-1000-4e05-b66b-252fb0058a87" failed: 995(The I/O operation has been aborted because of either a thread exit or an application request.).
38006:(pid 13664):A nonrecoverable I/O error occurred on file "Legato#055546de-1000-4e05-b66b-252fb0058a87:" 995(The I/O operation has been aborted because of either a thread exit or an application request.)..
38006:(pid 13664):BACKUP DATABASE is terminating abnormally..
98519:(pid 13664): Unable to setup direct save with server system.domain.com: Client 'client.domain.com' is not properly configured on the NetWorker Server..
53084:(pid 13664):Processing msdb failed, the item will be skipped.
client.domain.com: MSSQL: level=incr, 0 KB 00:00:01, 4-file(s)-processed, 0-file(s)-succeeded
43709:(pid 13664):Stop time: Thu May 28 12:02:31 2015
Backup operation finished with error(s). Refer to the module backup log file for details.
client.domain.com:MSSQL:: retried 2 times.
CarlosRojas
1.7K Posts
0
May 28th, 2015 05:00
Hi,
Make sure you add the following alias into the alias field of the client configuration:
QLEXWSESR001.na.ds.lexmark.com
Also check name resolution, it has to work forward and reverse DNS from server to client and vice versa.
Thank you,
Carlos
sokundu
1 Rookie
•
47 Posts
0
May 28th, 2015 06:00
Hi Carlos,
It is added in the alias field.And it is resolving forward and reverse DNS from server to client and vice versa.
new2prog2
79 Posts
0
May 28th, 2015 11:00
Hi Carlos,
What version of Networker S/w and NMM are you using ?
I am unable to reply to the post on Community but try running the below command on your networker server and retry the backups
nsraddadmin -u "host=CLIENTNAME”
Regards
Raghuram
CarlosRojas
1.7K Posts
0
June 1st, 2015 01:00
Hi sokundu
Have you checked the XBSA.messages file in /nsr/Applogs ?
Can you please run this command from NW server and attach the output?:
nsradmin -s QLEXWSESR001.na.ds.lexmark.com -p nsrexec
When you get to the nsradmin prompt, please run this command, and capture the output to share it here:
nsradmin>print type: nsrla
Thank you,
Carlos
sokundu
1 Rookie
•
47 Posts
0
June 9th, 2015 04:00
Hi Carlos
Please find the output of the command:
C:\Windows\system32>nsradmin -s QLEXWSESR001.na.ds.lexmark.com -p nsrexec
NetWorker administration program.
Use the "help" command for help.
nsradmin> print type: nsrla
type: NSRLA;
name: qlexwsesr001.na.ds.lexmark.com;
nsrmmd version: ;
nsrsnmd version: ;
NW instance info operations: ;
NW instance info file: ;
installed products: ;
auth methods: "0.0.0.0/0,nsrauth/oldauth";
max auth attempts: 8;
administrator: Administrators,
"group=Administrators,host=qlexwsesr001.na.ds.lexmark.com";
arch: Windows Server 2008;
kernel arch: AMD_X8664;
CPU type: AMD_X8664;
machine type: server;
OS: Windows Server 2008 6.0;
NetWorker version: 8.1.1.5.Build.306;
client OS type: Windows NT Server on Intel;
CPUs: 4;
MB used: 123475;
IP address: 157.184.229.89, 10.250.1.246;
nsradmin>