SQL Database Error during backup

Something seems to be wrong with your SQL config... is this first time you have attempt it?

You are missing backup command.

1. Start NetWorker Remote Exec service with the same account and password used for running SQL services

2. if in cluster, check that physical nodes do not contain entry of virtual nodes

.
.
.
or... you need to reboot the sql server

No, this client is part of a scheduled backup that runs everyday and the problem as been coming since just two days back. When i ran a test backup with just this client, this error came up:

save: using `MSSQL:\' for `MSSQL:'
save: cannot stat MSSQL:\: Invalid argument
save: Could not stat MSSQL:: Invalid argument

The client has been restarted to see if that would perhaps fix the trouble, but still its showing.

Steve

I agree, I think you are missing the backup command - it trying to treat MSSQL as a flat file backup

Thank you all for your kind replies. Yes, i found that backup command was missing. I entered it in its field and restarted the backup. Now this error is coming up:
------------------------------------------------------------------------------------------------------------------------------
From nsrsqlsv.log:

[3336] 08/08/07 17:04:39 Start time Wed Aug 08 17:04:39 2007
[3336] 08/08/07 17:04:39 Computer Name: INGBTCPIC1MS410 User Name: NT AUTHORITY\SYSTEM (SYSTEM)
[3336] 08/08/07 17:04:39 System Version: 5.0 Build 2195 Service Pack 4
[3336] 08/08/07 17:04:39 Microsoft Data Access Component(MDAC) version: 2.71.9030.9
[3336] 08/08/07 17:04:39 Microsoft SQL Server version (from registry) : 8.00.194
[3336] 08/08/07 17:04:39 Local host has following SQL Server online:
[3336] 08/08/07 17:04:39 MSSQL server : INGBTCPIC1MS410
[3336] 08/08/07 17:04:39 Use Legato Networker Server : ingbtcpic1ms013.code1.emi.philips.com
[3336] 08/08/07 17:04:39 Legato Networker Server Version: NetWorker nw_7_3_2_jumbo.Build.399 Network Edition/123
[3336] 08/08/07 17:04:39 nsrexecd.exe Version: 7.1.2.Build.325
[3336] 08/08/07 17:04:39 nsrsqlsv.exe Version: 5.0.0.154 Supporting SQL 7.0, SQL 2000, and SQL 2005
[3336] 08/08/07 17:04:39 Command line:
[3336] 08/08/07 17:04:39 C:\Program Files\nsr\bin\nsrsqlsv.exe -s ingbtcpic1ms013.code1.emi.philips.com -g Test2 -LL -f - -m ingbtcpic1ms410.code1.emi.philips.com -l full -q -W 78 -N MSSQL: MSSQL:
[3336] 08/08/07 17:04:39 SQL Connection to INGBTCPIC1MS410 is created. SQL Server Version is 08.00.0818
NSR_BACKUP_LEVEL: full;
NSR_GROUP: Test2;
NSR_SAVESET_NAME: "MSSQL:";
NSR_SERVER: ingbtcpic1ms013.code1.emi.philips.com;
[3336] 08/08/07 17:04:41 Internal system error, please see nsr\applogs\xbsa.messages on the client system for reason.
[3336] 08/08/07 17:04:41 Processing Northwind failed, the item will be skipped.


[3336] 08/08/07 17:04:41 Internal system error, please see nsr\applogs\xbsa.messages on the client system for reason.
[3336] 08/08/07 17:04:41 Microsoft SQL Server Provider error:
[3336] 08/08/07 17:04:41 Processing master failed, the item will be skipped.


[3336] 08/08/07 17:04:41 Microsoft SQL Server Provider error:
[3336] 08/08/07 17:04:46 Write on 'Legato#4df234ac-5883-4a1e-84d9-f5dd1d406917' failed, status = 995. See the SQL Server error log for more details..
[3336] 08/08/07 17:04:46 BACKUP DATABASE is terminating abnormally..
[3336] 08/08/07 17:04:46 Write on 'Legato#4e1155b7-1d4c-4b96-806e-28892c435055' failed, status = 995. See the SQL Server error log for more details..
[3336] 08/08/07 17:04:46 BACKUP DATABASE is terminating abnormally..
[3336] 08/08/07 17:04:46 Internal system error, please see nsr\applogs\xbsa.messages on the client system for reason.
[3336] 08/08/07 17:04:46 Processing model failed, the item will be skipped.


[3336] 08/08/07 17:04:46 Internal system error, please see nsr\applogs\xbsa.messages on the client system for reason.
[3336] 08/08/07 17:04:46 Microsoft SQL Server Provider error:
[3336] 08/08/07 17:04:46 Write on 'Legato#a9fd8cac-5db9-4972-8fc5-4dc99e1a7c77' failed, status = 995. See the SQL Server error log for more details..
[3336] 08/08/07 17:04:46 BACKUP DATABASE is terminating abnormally..
[3336] 08/08/07 17:04:47 Processing msdb failed, the item will be skipped.


[3336] 08/08/07 17:04:47 Internal system error, please see nsr\applogs\xbsa.messages on the client system for reason.
[3336] 08/08/07 17:04:47 Processing pubs failed, the item will be skipped.


[3336] 08/08/07 17:04:47 Completion time Wed Aug 08 17:04:47 2007


From xbsa.messages:

XBSA-1.0.1 LNMs_2H_2005.Build.154 3336 Wed Aug 08 17:04:47 2007 _nwbsa_is_retryable_error: received a network error (Severity 5 Number 12): The feature "NetWorker Module for Microsoft SQL Server/9" is not properly enabled. for client ingbtcpic1ms410.code1.emi.philips.com.

From SQL Errrorlog:

2007-08-08 17:04:41.24 spid53 BackupMedium::ReportIoError: write failure on backup device 'Legato#4df234ac-5883-4a1e-84d9-f5dd1d406917'. Operating system error 995(The I/O operation has been aborted because of either a thread exit or an application request.).
2007-08-08 17:04:41.24 backup BACKUP failed to complete the command BACKUP database [Northwind] TO virtual_device='Legato#4df234ac-5883-4a1e-84d9-f5dd1d406917' WITH name='LegatoNWMSQL'
2007-08-08 17:04:41.24 spid53 Internal I/O request 0x43FC5C28: Op: Write, pBuffer: 0x01DC0200, Size: 512, Position: 0, UMS: Internal: 0x0, InternalHigh: 0x0, Offset: 0x0, OffsetHigh: 0x0, m_buf: 0x00000000, m_len: 0, m_actualBytes: 0, m_errcode: 995, BackupFile: Legato#4df234ac-5883-4a1e-84d9-f5dd1d406917
2007-08-08 17:04:41.32 spid53 BackupVirtualDeviceFile::RequestDurableMedia: Flush failure on backup device 'Legato#4df234ac-5883-4a1e-84d9-f5dd1d406917'. Operating system error 995(The I/O operation has been aborted because of either a thread exit or an application request.).
2007-08-08 17:04:41.46 spid54 BackupMedium::ReportIoError: write failure on backup device 'Legato#4e1155b7-1d4c-4b96-806e-28892c435055'. Operating system error 995(The I/O operation has been aborted because of either a thread exit or an application request.).
2007-08-08 17:04:41.46 backup BACKUP failed to complete the command BACKUP database [master] TO virtual_device='Legato#4e1155b7-1d4c-4b96-806e-28892c435055' WITH name='LegatoNWMSQL'
2007-08-08 17:04:41.46 spid54 Internal I/O request 0x44029C00: Op: Write, pBuffer: 0x01E00200, Size: 512, Position: 0, UMS: Internal: 0x4402FA70, InternalHigh: 0x44029CA0, Offset: 0x4402FAC0, OffsetHigh: 0x0, m_buf: 0x00000000, m_len: 0, m_actualBytes: 0, m_errcode: 995, BackupFile: Legato#4e1155b7-1d4c-4b96-806e-28892c435055
2007-08-08 17:04:41.60 spid54 BackupVirtualDeviceFile::RequestDurableMedia: Flush failure on backup device 'Legato#4e1155b7-1d4c-4b96-806e-28892c435055'. Operating system error 995(The I/O operation has been aborted because of either a thread exit or an application request.).
2007-08-08 17:04:46.64 spid53 BackupMedium::ReportIoError: write failure on backup device 'Legato#a9fd8cac-5db9-4972-8fc5-4dc99e1a7c77'. Operating system error 995(The I/O operation has been aborted because of either a thread exit or an application request.).
2007-08-08 17:04:46.64 backup BACKUP failed to complete the command BACKUP database [model] TO virtual_device='Legato#a9fd8cac-5db9-4972-8fc5-4dc99e1a7c77' WITH name='LegatoNWMSQL'
2007-08-08 17:04:46.64 spid53 Internal I/O request 0x43FC5C10: Op: Write, pBuffer: 0x01DC0200, Size: 512, Position: 0, UMS: Internal: 0x995F78, InternalHigh: 0x1, Offset: 0x995F88, OffsetHigh: 0x43FC4030, m_buf: 0x00000000, m_len: 0, m_actualBytes: 0, m_errcode: 995, BackupFile: Legato#a9fd8cac-5db9-4972-8fc5-4dc99e1a7c77
2007-08-08 17:04:46.73 spid53 BackupVirtualDeviceFile::RequestDurableMedia: Flush failure on backup device 'Legato#a9fd8cac-5db9-4972-8fc5-4dc99e1a7c77'. Operating system error 995(The I/O operation has been aborted because of either a thread exit or an application request.).
2007-08-08 17:04:46.86 spid54 BackupMedium::ReportIoError: write failure on backup device 'Legato#65c1aab7-9f25-4a12-8d1c-4b396dd24ddc'. Operating system error 995(The I/O operation has been aborted because of either a thread exit or an application request.).
2007-08-08 17:04:46.86 backup BACKUP failed to complete the command BACKUP database [msdb] TO virtual_device='Legato#65c1aab7-9f25-4a12-8d1c-4b396dd24ddc' WITH name='LegatoNWMSQL'
2007-08-08 17:04:46.86 spid54 Internal I/O request 0x44001C10: Op: Write, pBuffer: 0x01E00200, Size: 512, Position: 0, UMS: Internal: 0x0, InternalHigh: 0x0, Offset: 0x0, OffsetHigh: 0x0, m_buf: 0x00000000, m_len: 0, m_actualBytes: 0, m_errcode: 995, BackupFile: Legato#65c1aab7-9f25-4a12-8d1c-4b396dd24ddc
2007-08-08 17:04:47.01 spid54 BackupVirtualDeviceFile::RequestDurableMedia: Flush failure on backup device 'Legato#65c1aab7-9f25-4a12-8d1c-4b396dd24ddc'. Operating system error 995(The I/O operation has been aborted because of either a thread exit or an application request.).
2007-08-08 17:04:47.07 spid53 BackupMedium::ReportIoError: write failure on backup device 'Legato#7685c45b-1662-4350-a36e-cbadcc0eb1fc'. Operating system error 995(The I/O operation has been aborted because of either a thread exit or an application request.).
2007-08-08 17:04:47.07 backup BACKUP failed to complete the command BACKUP database [pubs] TO virtual_device='Legato#7685c45b-1662-4350-a36e-cbadcc0eb1fc' WITH name='LegatoNWMSQL'
2007-08-08 17:04:47.07 spid53 Internal I/O request 0x43FC5C08: Op: Write, pBuffer: 0x01E30200, Size: 512, Position: 0, UMS: Internal: 0x0, InternalHigh: 0x0, Offset: 0x995F78, OffsetHigh: 0x1, m_buf: 0x00000000, m_len: 0, m_actualBytes: 0, m_errcode: 995, BackupFile: Legato#7685c45b-1662-4350-a36e-cbadcc0eb1fc
2007-08-08 17:04:47.15 spid53 BackupVirtualDeviceFile::RequestDurableMedia: Flush failure on backup device 'Legato#7685c45b-1662-4350-a36e-cbadcc0eb1fc'. Operating system error 995(The I/O operation has been aborted because of either a thread exit or an application request.).


From daemon.log:

/07 17:04:41 Internal system error, please see nsr\applogs\xbsa.messages on the client system for reason.
* ingbtcpic1ms410.code1.emi.philips.com:MSSQL: [3336] 08/08/07 17:04:41 [3336] 08/08/07 17:04:41 [3336] 08/08/07 17:04:41 Microsoft SQL Server Provider error:
* ingbtcpic1ms410.code1.emi.philips.com:MSSQL: Processing master failed, the item will be skipped.
* ingbtcpic1ms410.code1.emi.philips.com:MSSQL:
* ingbtcpic1ms410.code1.emi.philips.com:MSSQL:
* ingbtcpic1ms410.code1.emi.philips.com:MSSQL: Microsoft SQL Server Provider error:
* ingbtcpic1ms410.code1.emi.philips.com:MSSQL: [3336] 08/08/07 17:04:46 Write on 'Legato#4df234ac-5883-4a1e-84d9-f5dd1d406917' failed, status = 995. See the SQL Server error log for more details..
* ingbtcpic1ms410.code1.emi.philips.com:MSSQL: [3336] 08/08/07 17:04:46 BACKUP DATABASE is terminating abnormally..
* ingbtcpic1ms410.code1.emi.philips.com:MSSQL: [3336] 08/08/07 17:04:46 Write on 'Legato#4e1155b7-1d4c-4b96-806e-28892c435055' failed, status = 995. See the SQL Server error log for more details..
* ingbtcpic1ms410.code1.emi.philips.com:MSSQL: [3336] 08/08/07 17:04:46 BACKUP DATABASE is terminating abnormally..
* ingbtcpic1ms410.code1.emi.philips.com:MSSQL: [3336] 08/08/07 17:04:46 Internal system error, please see nsr\applogs\xbsa.messages on the client system for reason.
* ingbtcpic1ms410.code1.emi.philips.com:MSSQL: [3336] 08/08/07 17:04:46 Processing model failed, the item will be skipped.
* ingbtcpic1ms410.code1.emi.philips.com:MSSQL:
* ingbtcpic1ms410.code1.emi.philips.com:MSSQL:
* ingbtcpic1ms410.code1.emi.philips.com:MSSQL: [3336] 08/08/07 17:04:46 Internal system error, please see nsr\applogs\xbsa.messages on the client system for reason.
* ingbtcpic1ms410.code1.emi.philips.com:MSSQL: [3336] 08/08/07 17:04:46 Microsoft SQL Server Provider error:
* ingbtcpic1ms410.code1.emi.philips.com:MSSQL: [3336] 08/08/07 17:04:46 Write on 'Legato#a9fd8cac-5db9-4972-8fc5-4dc99e1a7c77' failed, status = 995. See the SQL Server error log for more details..
* ingbtcpic1ms410.code1.emi.philips.com:MSSQL: [3336] 08/08/07 17:04:46 BACKUP DATABASE is terminating abnormally..
* ingbtcpic1ms410.code1.emi.philips.com:MSSQL: [3336] 08/08/07 17:04:47 Processing msdb failed, the item will be skipped.
* ingbtcpic1ms410.code1.emi.philips.com:MSSQL:
* ingbtcpic1ms410.code1.emi.philips.com:MSSQL:
* ingbtcpic1ms410.code1.emi.philips.com:MSSQL: [3336] 08/08/07 17:04:47 Internal system error, please see nsr\applogs\xbsa.messages on the client system for reason.
* ingbtcpic1ms410.code1.emi.philips.com:MSSQL: [3336] 08/08/07 17:04:47 Processing pubs failed, the item will be skipped.
* ingbtcpic1ms410.code1.emi.philips.com:MSSQL:
* ingbtcpic1ms410.code1.emi.philips.com:MSSQL:
ingbtcpic1ms410.code1.emi.philips.com: MSSQL: level=full, 0 KB 00:00:08, 5-file(s)-processed, 0-file(s)-succeeded
* ingbtcpic1ms410.code1.emi.philips.com:MSSQL: nsrsqlsv: COM Error. Code = 800a0cb3
* ingbtcpic1ms410.code1.emi.philips.com:MSSQL: nsrsqlsv: COM Error. Code = 800a0cb3
* ingbtcpic1ms410.code1.emi.philips.com:index uasm: error while saving D:\Legato\nsr\index\ingbtcpic1ms410.code1.emi.philips.com\db6\467d0000\467d3cd1.rec
* ingbtcpic1ms410.code1.emi.philips.com:index uasm: xdr flush failed
------------------------------------------------------------------------------------------------------------------------------

I have tried restarting the services, restarting the server but still these messages show up. Please advice.

Hi,

Try to take backup of SQL database with it's native backup utility.That will help you to isolate the issue with SQL server or Networker.

Regards
Narendra Yadav

If you initiate the Backup from the client do you get the same results? What does the xbsa.messages log file contain?

Did anything change 3 days prior? Meaning if the backup started failing two days from your original post then what changed the day before the failures? Network, patches, OS level, SQL level, etc?

Dana

XBSA error usually is seen when you have issue with alias (short name not on alias list) or even licensing (I would expect backup would then fail earlier too). I agree that having client initiated backup with some debug could be helpful, but this seems to fail immediately so I suspect something more trivial - something like resource corruption. I noticed that you have server on 7.3.2 b399 while client is 7.1.2. Any reason for 7.1.2? I would suggest to star with somewhat different approach:
a) update client to b399 too
b) delete client from server
c) restart server
d) create client again (use clientid too)
e) without any further modifications does it work now?

If this fails again, then let us know if this is some sort of cluster and also try debug client side backup.

Thank you for your replies.
The guys who are in charge of this server have formatted it and they are installing windows afresh. I will install the 7.3.2 b399 ver. of networker and trigger an sql backup and get back to you with the results. Thanks again.

and where download this module 7.3.2 b399 ?.......

From the XBSA Messages:

The feature "NetWorker Module for Microsoft SQL Server/9" is not properly enabled

Has this key expired? Or the auth code never entered?

Paul

It's not a module, but agent version and build... which is pretty much outdated now.