After houres of trying I'll get now the following Error Message:
Internal system error, please see nsr\applogs\xbsa.messages on the client system for reason
Microsoft SQL Server Provider error:
Write on "Legato#0dd02b74-1dc4-4617-93a6-0dd8e3ba4f50" failed: 995(failed to retrieve text for this error. Reason: 15105).
38006:(pid 4580):A nonrecoverable I/O error occurred on file "Legato#0dd02b74-1dc4-4617-93a6-0dd8e3ba4f50:" 995(failed to retrieve text for this error. Reason: 15105)..
38006:(pid 4580):BACKUP DATABASE is terminating abnormally..
53084:(pid 4580):Processing master failed, the item will be skipped.
38008:(pid 4580):Internal system error, please see nsr\applogs\xbsa.messages on the client system for reason.
29085:(pid 4580):Microsoft SQL Server Provider error:
38006:(pid 4580):Write on "Legato#5f0c9ca9-e459-40c7-a794-6c167db1dddd" failed: 995(failed to retrieve text for this error. Reason: 15105).
38006:(pid 4580):A nonrecoverable I/O error occurred on file "Legato#5f0c9ca9-e459-40c7-a794-6c167db1dddd:" 995(failed to retrieve text for this error. Reason: 15105)..
38006:(pid 4580):BACKUP DATABASE is terminating abnormally..
53084:(pid 4580):Processing model failed, the item will be skipped.
38008:(pid 4580):Internal system error, please see nsr\applogs\xbsa.messages on the client system for reason.
29085:(pid 4580):Microsoft SQL Server Provider error:
38006:(pid 4580):Write on "Legato#7a6f6e6c-bca3-4a37-a62f-3721358bf72c" failed: 995(failed to retrieve text for this error. Reason: 15105).
38006:(pid 4580):A nonrecoverable I/O error occurred on file "Legato#7a6f6e6c-bca3-4a37-a62f-3721358bf72c:" 995(failed to retrieve text for this error. Reason: 15105)..
38006:(pid 4580):BACKUP DATABASE is terminating abnormally..
53084:(pid 4580):Processing msdb failed, the item will be skipped.
43709:(pid 4580):Stop time: Tue Aug 06 11:10:04 2013
In the File xbsa.messages are the following Entries:
XBSA-1.0.1 nmm_241.Build.92 4580 Tue Aug 06 11:10:04 2013 _nwbsa_is_retryable_error: received a network error (Severity 0 Number -7): no matching devices for save of client `[DBServer]; check storage nodes, devices or pools
- The client must be a member of a snapshot group.
- If you have defined a new one and you sort the data, make sure that the group has also been added to the correct pool. I stumbled over this a lot.
In this case look at the "Monitoring" window. There should pop up a waiting message in the "Alerts" area, which will tell you which media NW is waiting for.
CarlosRojas
1.7K Posts
0
July 31st, 2013 05:00
Hi,
I suppose you have NW 8.0.x in client and server, correct?
Looks like there could be a bad configuration or connectivity issue.
Please check the nsrsqlsv.raw and let us know what you find in there.
Thank you,
Carlos
N4SQL
1 Rookie
•
5 Posts
0
July 31st, 2013 07:00
Hi CarlosRojas
Thats right, we use Networker Version 8.0.1 on the Servers and 8.0.1.4 on the Clients. NMM is like i said on Version 2.4.0.375.
I don't think that there are connectivity issues, because when i start the Backup from the client, it works without problems.
I looked into the nsrsqlsv.raw and saw following:
C:\Program Files\Legato\nsr\bin\nsrsqlsv.exe -C -X -k -s [NetworkerServer.subdomain.domain.ch] -g GRP_SQL_POL3_FULL_J -LL -m [SQLServer] -a device interface=data domain -b DATAG -l full -q -W 78 -N MSSQL: MSSQL:
common\apputil(353): Failed to get nsr attribute version for server [NetworkerServer.subdomain.domain.ch]
savemain.cpp(1764): Unable to identify NetWorker Server Version. Status: 0x0000000d\n Server: null
I'm still not sure what causing the Error. Perhabs it is a Version conflict ??
Grateful for any help
Cheers
CarlosRojas
1.7K Posts
0
August 1st, 2013 00:00
I don't think this has to be with the version at all.
Basically nsrsqlsv fails to get the correct resource information (Client-Group-Pool) from RES DB config on NW server.
Are you able to run file system backups for the SQL clients correctly?
Have you tried to upgrade NMM 2.4 to NMM 2.4 SP1?
Thank you,
Carlos
N4SQL
1 Rookie
•
5 Posts
0
August 5th, 2013 06:00
HI Again
Filesystem Backup works. I have to make it via NMM but it works.
I updated the NMM Client to NMM 2.4 SP1... but it still doesn't works for my SQL-Backups.
Everytime the same Faillure...
Thank you,
Michael
N4SQL
1 Rookie
•
5 Posts
0
August 6th, 2013 02:00
After houres of trying I'll get now the following Error Message:
Internal system error, please see nsr\applogs\xbsa.messages on the client system for reason
Microsoft SQL Server Provider error:
Write on "Legato#0dd02b74-1dc4-4617-93a6-0dd8e3ba4f50" failed: 995(failed to retrieve text for this error. Reason: 15105).
38006:(pid 4580):A nonrecoverable I/O error occurred on file "Legato#0dd02b74-1dc4-4617-93a6-0dd8e3ba4f50:" 995(failed to retrieve text for this error. Reason: 15105)..
38006:(pid 4580):BACKUP DATABASE is terminating abnormally..
53084:(pid 4580):Processing master failed, the item will be skipped.
38008:(pid 4580):Internal system error, please see nsr\applogs\xbsa.messages on the client system for reason.
29085:(pid 4580):Microsoft SQL Server Provider error:
38006:(pid 4580):Write on "Legato#5f0c9ca9-e459-40c7-a794-6c167db1dddd" failed: 995(failed to retrieve text for this error. Reason: 15105).
38006:(pid 4580):A nonrecoverable I/O error occurred on file "Legato#5f0c9ca9-e459-40c7-a794-6c167db1dddd:" 995(failed to retrieve text for this error. Reason: 15105)..
38006:(pid 4580):BACKUP DATABASE is terminating abnormally..
53084:(pid 4580):Processing model failed, the item will be skipped.
38008:(pid 4580):Internal system error, please see nsr\applogs\xbsa.messages on the client system for reason.
29085:(pid 4580):Microsoft SQL Server Provider error:
38006:(pid 4580):Write on "Legato#7a6f6e6c-bca3-4a37-a62f-3721358bf72c" failed: 995(failed to retrieve text for this error. Reason: 15105).
38006:(pid 4580):A nonrecoverable I/O error occurred on file "Legato#7a6f6e6c-bca3-4a37-a62f-3721358bf72c:" 995(failed to retrieve text for this error. Reason: 15105)..
38006:(pid 4580):BACKUP DATABASE is terminating abnormally..
53084:(pid 4580):Processing msdb failed, the item will be skipped.
s2001-db600: MSSQL: level=full, 0 KB 00:00:03, 8-file(s)-processed, 0-file(s)-succeeded
43709:(pid 4580):Stop time: Tue Aug 06 11:10:04 2013
In the File xbsa.messages are the following Entries:
XBSA-1.0.1 nmm_241.Build.92 4580 Tue Aug 06 11:10:04 2013 _nwbsa_is_retryable_error: received a network error (Severity 0 Number -7): no matching devices for save of client `[DBServer]; check storage nodes, devices or pools
Someone any ideas ?
bingo.1
2.4K Posts
0
August 6th, 2013 04:00
Several possibilities:
- The client must be a member of a snapshot group.
- If you have defined a new one and you sort the data, make sure that the group has also been added to the correct pool. I stumbled over this a lot.
In this case look at the "Monitoring" window. There should pop up a waiting message in the "Alerts" area, which will tell you which media NW is waiting for.
Nick_Dichkovski
2 Posts
1
August 21st, 2013 09:00
Hi Guys!
I've resolved the same problem 5 mins ago.
I have Networker 7.6.3 and NMM 2.4., but it seems that trouble isn't in the version of software.
Check the pool's settings - your group must be checked in pool properties. And the main thing - the field "Pool" in group properties must be blank.
First time I've started my group with selected pool in group properies, but when I cleared the "Pool" field, it started to work fine.
Good luck!
Regards, Nikita
N4SQL
1 Rookie
•
5 Posts
0
August 21st, 2013 23:00
HI Nikita
Thanks my problem was nearly the same.
I checked the DataDomain Backup Option under the Client properties in Register APPS & Modules in Section Deduplication.
Without this option the Backup runned without problems.
Cheers guys