Hi,

Do you see any error messages on the log, when the backup fails?

What is the ouput of the Daemon.raw, and messages file?

Bruno

savegrp: suppressed 2 lines of verbose output
38006 1266433825 5 0 0 5104 4324 0 sp-mdb1.xxx.com (pid4324) 3 %s. 1 24 42 BACKUP DATABASE is terminating abnormally.
53084 1266434127 5 0 0 4776 4324 0 sp-mdb1.xxx.com (pid4324) 47 Processing %s failed, the item will be skipped. 1 0 3 mdb
:  Backup operation finished with error(s). Refer to the module backup log file for details.

Applogs' Messeges,

36 Microsoft SQL Server Provider error: 0
38006 1266433668 5 0 0 1588 5864 0 xxx.com (pid5864) 3 %s. 1 24 161 Write on "Legato#4339f171-2d13-48fe-830a-0d2f89982bec" failed: 995(The I/O operation has been aborted because of either a thread exit or an application request.)
38006 1266433668 5 0 0 1588 5864 0 xxx.com (pid5864) 3 %s. 1 24 190 A nonrecoverable I/O error occurred on file "Legato#4339f171-2d13-48fe-830a-0d2f89982bec:" 995(The I/O operation has been aborted because of either a thread exit or an application request.).
38006 1266433668 5 0 0 1588 5864 0 xxx.com (pid5864) 3 %s. 1 24 42 BACKUP DATABASE is terminating abnormally.
38008 1266433668 5 0 0 2852 4608 0 xxx.com (pid4608) 2 %s 1 24 92 Internal system error, please see nsr\applogs\xbsa.messages on the client system for reason

Hi Again,

With regard to this error which can be seen intermittently for failing SQL backup this can occur for a number of reasons and it is recommended to review the following steps to determine whether they address the issue or not:

I Assume you are running SQL server 2005, please correct me if i am wrong.

a) 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.

b) Consider increasing the virtual memory and/or physical memory of the client.

c) 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

which states that application of the latest fixes and patches is recommended.

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

Hope it helps.

Regards,

Bruno

Thanks B Sequeira, What size of Physcal and Virtual Ram We need for the Sql Backups?

For Example, System Ram 48 gb, Sql Database 200 gb, What size ram must be reserved for this backup?

Thanks B Sequeira, What size of Physcal and Virtual Ram We need for the Sql Backups?

For Example, System Ram 48 gb, Sql Database 200 gb, What size ram must be reserved for this backup?

Hi BSequeira

Sql2005 is running on Windows2003

sql2008 is running on Windows 2008

There is both some problem..

We are not  running SQL 2008 in 2005 compatibility mode, The problem still existing..

Is there any other recommenditions on this topic?

Good

Please place the information that has the file xbsa.messages mssql server which is on the path program files \ legato \ nsr \ applogs.

Please also tell us if you have installed the SQL x64 or x86 and if you have windows 2008 R2

I hope these answers to the solution,

regards,