Hi Pratik,

You need to have licenses to backup SQL, however to be sure you can check in NMSQL logs:

nsrsqlsv.exe (rendered) and XBSA messages. If there is anything related to the licenses then yes, you will need to apply them.

On the other hand that error 995 is kind of generic, so we will need to find some more clues to get to the root cause of the problem.

I think first step should be to render nsrsqlsv.raw and daemon.raw on the client side, and also check XBSA messages.

That should provide us with more information, and also the Application and System event logs on the SQl server.

Thank you.

Carlos

Hi Carlos,

I didn't find any such error which you mentioned in the event viewer. Also, i have changed the inactivity timeout to 0 from 30. Please let me know whether i should apply the licenses for even taking the test backup. I will be applying them once my test backup is successful.

Regards,

Pratik.

Hi Pratik,

We would need some further information, however my first question is, did you see anything on the application and/or system event logs?

Something like this?:

Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 18210
Date:  3/24/2009
Time:  4:04:37 PM
User:  NT AUTHORITY\SYSTEM
Computer: BG3WS028
Description:
BackupVirtualDeviceFile::RequestDurableMedia: Flush failure on backup device 'Legato#9bfefa18-046d-4a3c-ae2d-d017dbff3b8b'. Operating system error 995(The I/O operation has been aborted because of either a thread exit or an application request.).

If so please check out esg104108:

Cause

The error can occur due to several different reasons.

Using the lightweight pooling (fiber mode) SQL Server configuration option for a backup operation

Very large databases (VLDB) that take a long time to backup

Known Microsoft Virtual Device Interface (VDI) Issue

Resolution

Review the following steps to determine whether they address the issue or not:

1. What is the 'Inactivity Timeout' value for the Group? Is this set to 0? If not, try changing this to 0 and retry the backup.
2. Consider increasing the virtual memory and/or physical memory of the client.
3. Check if the latest fixes and patches have been applied to the MS SQL Server 2005 install.

This error is documented in Microsoft Knowledgebase Article: http://support.microsoft.com/kb/934396

"Error messages and an event may be logged when you use the Virtual Device Interface in SQL Server 2005 or in SQL Server 2000".

N.B.:-

In addition verify xbsa log for additional information

XBSA-1.0.1 rb_nmsql522.Build.23 8892 Wed Aug 31 11:03:48 2011 _nwbsa_is_retryable_error: received a network error (Severity 5 Number 12): The feature "NetWorker Module for Microsoft SQL Server" is not properly enabled

If there are sufficient SQL licenses and all SQL clients are connected and you still see the above message, most likely an instance of the SQL client used to backup flat files is using up an SQL license. Delete and re-add the client instance

Thank you.

Carlos.

Hi Carlos,

Please find the attached nsrsqlsv.raw and xbsa.messages log file. The xbsa messages file has entries regarding to licenses and hence i think it is mandatory to apply licenses.

Regards,

Pratik.