Networker SQL Backup Only Failing 1 Database

Question

Hey all, We are having an issue with one of our SQL servers, where every database except MSDB is successfully backing up. Whether using the scheduled backup jobs managed by our company's Infrastructure Team, or manually running the job from the client, all databases backup fine except MSDB. Our SQL team have done...SQL things, and passed it back saying it's a problem with the software or the OS. Environment ------------ SQL 2012 installed on Windows 2012 R2 Networker client 8.2.4 and NMM for SQL 8.23 Networker server 8.2.4 installed on Windows 2012 R2 Running manually from CMD on the client: nsrsqlsv -LL -s networker001.domain.local -g Site_SQL_Gold_G3 -m sqlserver001.domain.ads -o REQUESTED_LEVEL:level=full; -l full -q -W 78 -N MSSQL:msdb MSSQL:msdb 43708:(pid 5028):Start time: Wed Oct 17 11:43:23 2018 43621:(pid 5028):Computer Name: sqlserver001 User Name: domainadmin-username 38571:(pid 5028): Bad switch: -o 38562:(pid 5028): Unsupported savegrp option -o will be ignored 104810:(pid 5028):Detected application flag NSR_CONSISTENCY_CHECKS set to FALSE in NW resources for client sqlserver001.domain.ads nsr/db_apps/bsmsql/sqlutil.c(12387): SQL Server FILESTREAM Database called for d atabase 'msdb'            NSR_BACKUP_LEVEL: full;             NSR_CFI_USE_HINT: TRUE;            NSR_DIRECT_ACCESS: default;                    NSR_GROUP: Site_SQL_Gold_G3;                NSR_READ_SIZE: 4194304;             NSR_SAVESET_NAME: 'MSSQL:msdb';                   NSR_SERVER: networker001.domain.local; 142036:(pid 5028):Backup configured with maxtransfersize = 4194304 76677:(pid 5028): RPC send operation failed; peer = 10.176.56.1:8238, errno = An established connection was aborted by the software in your host machine. 38008:(pid 5028):Internal system error, please see nsr\applogs\xbsa.messages on the client system for reason. nsr/db_apps/bsmsql/sqlxbsacompforsave.cpp(965): Calling job completion attribute s for saveset: 1539773011 (-1) 53084:(pid 5028):Processing msdb failed, the item will be skipped. 29085:(pid 5028):Microsoft SQL Server Provider error: sqlserver001.domain.ads: MSSQL:msdb level=full, 0 KB 00:02:33,  1-file(s)-pro cessed, 0-file(s)-succeeded 38006:(pid 5028):Write on 'Legato#315783a9-4dc4-4c7f-b8d0-dd294a8c394a' failed: 995(The I/O operation has been aborted because of either a thread exit or an app lication request.). 38006:(pid 5028):A nonrecoverable I/O error occurred on file 'Legato#315783a9-4d c4-4c7f-b8d0-dd294a8c394a:' 995(The I/O operation has been aborted because of ei ther a thread exit or an application request.).. 38006:(pid 5028):BACKUP DATABASE is terminating abnormally.. Backup operation finished with error(s). Refer to the module backup log file for details. 43709:(pid 5028):Stop time: Wed Oct 17 11:46:06 2018 XBSA Logs XBSA-1.0.1 8.2.3.0.Build.1100 5028 Wed Oct 17 11:46:03 2018                   _nwbsa_senddata32: System detected error due to: sending a data buffer. Operation aborted XBSA-1.0.1 8.2.3.0.Build.1100 22224 Wed Oct 17 12:09:32 2018                   _nwbsa_senddata32: System detected error due to: sending a data buffer. Operation aborted XBSA-1.0.1 8.2.3.0.Build.1100 52008 Wed Oct 17 14:54:16 2018                   _nwbsa_senddata32: System detected error due to: sending a data buffer. Operation aborted NSRSQLSV Log 43708 1539773003 1 0 0 36452 5028 0 sqlserver001.domain.ads (pid5028) NSR notice 14 Start time: %s 1 35 25 Wed Oct 17 11:43:23 2018 43621 1539773003 1 0 0 36452 5028 0 sqlserver001.domain.ads (pid5028) NSR notice 35 Computer Name: %s     User Name: %s 2 12 10 SQLSERVER001 13 10 domainadmin-user 0 1539773004 1 0 0 36452 5028 0 sqlserver001.domain.ads (pid5028) NSR notice 18 System Version: %s 1 0 36 Microsoft Windows [Version 6.3.9600] 37975 1539773004 0 0 0 36452 5028 0 sqlserver001.domain.ads (pid5028) NSR info 49 Microsoft Data Access Component(MDAC) version: %s 1 0 14 6.3.9600.16384 37980 1539773004 0 0 0 36452 5028 0 sqlserver001.domain.ads (pid5028) NSR info 49 Microsoft SQL Server version (from registry) : %s 1 0 11 11.0.7001.0 29446 1539773004 0 0 0 36452 5028 0 sqlserver001.domain.ads (pid5028) NSR info 44 Local host has following SQL Server online:  0 37977 1539773004 0 0 0 36452 5028 0 sqlserver001.domain.ads (pid5028) NSR info 19 MSSQL server : %s 1 0 10 SQLSERVER001 37982 1539773008 0 0 0 36452 5028 0 sqlserver001.domain.ads (pid5028) NSR info 33 Use Legato Networker Server : %s 1 0 26 networker001.domain.local 37983 1539773008 0 0 0 36452 5028 0 sqlserver001.domain.ads (pid5028) NSR info 35 Legato Networker Server Version: %s 1 0 72 NetWorker 8.2.4.3.Build.1356 NetWorker Source Capacity Data Zone Enabler 107092 1539773008 1 5 0 36452 5028 0 sqlserver001.domain.ads (pid5028) NSR notice 75 Version information for %s: Original file name: %s Version: %s Comments: %s 4 23 51 C:\Program Files\EMC NetWorker
sr\bin
srexecd.exe 23 12 nsrexecd.exe 44 18 8.2.4.0.Build.1313 44 0 107092 1539773008 1 5 0 36452 5028 0 sqlserver001.domain.ads (pid5028) NSR notice 75 Version information for %s: Original file name: %s Version: %s Comments: %s 4 23 51 c:\Program Files\EMC NetWorker
sr\bin
srsqlsv.exe 23 12 nsrsqlsv.exe 44 12 8.2.3.0.1100 44 65 Supporting SQL 2005, SQL 2008, SQL 2008 R2, SQL 2012 and SQL 2014 43337 1539773008 0 0 0 36452 5028 0 sqlserver001.domain.ads (pid5028) NSR info 13 Command line: 0 43338 1539773008 0 0 0 36452 5028 0 sqlserver001.domain.ads (pid5028) NSR info 4   %s 1 0 176 nsrsqlsv -LL -s networker001.domain.local -g SITE_SQL_Gold_G3 -m Sqlserver001.domain.ads -o REQUESTED_LEVEL:level=full; -l full -q -W 78 -N MSSQL:msdb MSSQL:msdb 104810 1539773008 0 0 0 36452 5028 0 sqlserver001.domain.ads (pid5028) NSR info 89 Detected application flag NSR_CONSISTENCY_CHECKS set to %s in NW resources for client %s. 2 12 5 FALSE 12 26 Sqlserver001.domain.ads 37693 1539773009 0 0 0 36452 5028 0 sqlserver001.domain.ads (pid5028) NSR info 57 SQL Connection to %s is created. SQL Server Version is %s 2 0 10 SQLSERVER001 0 10 11.00.7462 0 1539773010 1 0 0 36452 5028 0 sqlserver001.domain.ads (pid5028) NSR notice 63 %s(%d): SQL Server FILESTREAM Database called for database '%s' 3 23 28 nsr/db_apps/bsmsql/sqlutil.c 1 5 12387 0 4 msdb 142036 1539773011 0 0 0 36452 5028 0 sqlserver001.domain.ads (pid5028) NSR info 25 Backup configured with %s 1 0 25 maxtransfersize = 4194304 38008 1539773163 5 0 0 36452 5028 0 sqlserver001.domain.ads (pid5028) NSR critical 2 %s 1 24 92 Internal system error, please see nsr\applogs\xbsa.messages on the client system for reason. 0 1539773163 1 0 0 36452 5028 0 sqlserver001.domain.ads (pid5028) NSR notice 62 %s(%d): Calling job completion attributes for saveset: %s (%d) 4 23 41 nsr/db_apps/bsmsql/sqlxbsacompforsave.cpp 1 3 965 0 10 1539773011 1 2 -1 53084 1539773163 5 0 0 36452 5028 0 sqlserver001.domain.ads (pid5028) NSR critical 47 Processing %s failed, the item will be skipped. 1 0 4 msdb 29085 1539773163 5 0 0 62720 5028 0 sqlserver001.domain.ads (pid5028) NSR critical 36 Microsoft SQL Server Provider error: 0 38006 1539773163 5 0 0 62720 5028 0 sqlserver001.domain.ads (pid5028) NSR critical 3 %s. 1 24 161 Write on 'Legato#315783a9-4dc4-4c7f-b8d0-dd294a8c394a' failed: 995(The I/O operation has been aborted because of either a thread exit or an application request.) 38006 1539773164 5 0 0 62720 5028 0 sqlserver001.domain.ads (pid5028) NSR critical 3 %s. 1 24 190 A nonrecoverable I/O error occurred on file 'Legato#315783a9-4dc4-4c7f-b8d0-dd294a8c394a:' 995(The I/O operation has been aborted because of either a thread exit or an application request.). 38006 1539773164 5 0 0 62720 5028 0 sqlserver001.domain.ads (pid5028) NSR critical 3 %s. 1 24 42 BACKUP DATABASE is terminating abnormally. 43709 1539773166 1 0 0 36452 5028 0 sqlserver001.domain.ads (pid5028) NSR notice 13 Stop time: %s 1 35 25 Wed Oct 17 11:46:06 2018

Claudette017 · Answer

These seem to suggest similar actions:

Review the underlying system error messages and SQL Server error messages preceding this one to identify the cause of the failure.
This may be due to a SQL Server virtual memory issue or limitation on the Windows client system.
Ensure that the backup and restore medium has sufficient space.
Correct any errors raised by third-party backup and restore software.

Hope this helps.

Mobdro

Ahmad Abuhasna · Answer

at first, you can check your SQL server instance if it is running without any issue, if yes check the event viewer if there is an error with the backup it will show in the application section, finally run Networker user for SQL and if it failed to connect it will though you the exact error.

NetWorker

Was this post helpful?