SQL LiteSpeed Backup job failing intermittenly

SQLServerCentral is supported by Red Gate Software Ltd.

Popular Topics

Home

Members

Calendar

Who's On

Home » SQL Server 2005 » Backups » SQL LiteSpeed Backup job failing...

13 posts, Page 1 of 2

1 2 »»

SQL LiteSpeed Backup job failing intermittenly

Rate Topic

Display Mode

Topic Options

Author

Message

Erich Brinker

Posted Tuesday, November 17, 2009 8:23 AM

SSC Veteran

Group: General Forum Members
Last Login: Saturday, December 10, 2011 6:38 AM
Points: 215, Visits: 633

I was hoping someone else is getting the following error with Litespeed. We are getting the error 2 -4 times a day for full backups and t-log backups.

SLS Error: No Result XML returned from Engine. (Possible abend/termination...

We are running SQL 2005 Standard edition(SP3) on a 2003 sp1 x64 server. Servers have 16 gig of RAM and 13 has been given to SQL Server. This is a clustered environment 2 node active passive cluster.

Per the suggestions from Quest we have spaced out our jobs, and set the MaxTransfer Size parameter when running their extended stored procedure.

I have noticed that when we get errors with the backups we see a drop of around 200mb of RAM available on the server.

Any help would be appreciated
Thanks
Erich

Post #820108

jimk-524058

Posted Tuesday, November 24, 2009 1:07 PM

SSC Rookie

Group: General Forum Members
Last Login: Thursday, May 09, 2013 11:42 AM
Points: 47, Visits: 184

I'm getting this error now too.

Msg 50000, Sev 18, State 1: SLS Error: No Result XML returned from Engine. (Possible abend/termination) [SQLSTATE 42000]

It just started recently after a reboot of the box to swap out some questionable RAM. Latest OS updates were installed as well and the error started right after. Before the upgrade the backups ran without error.

My box is MS Windows Server 2003 R2, Standard x64 Edition Service Pack 2
Microsoft SQL Server 2005 Enterprise Edition (64-bit) on Windows NT 5.2 (Build 3790: Service Pack 2)

Post #824103

Erich Brinker

Posted Tuesday, November 24, 2009 1:12 PM

SSC Veteran

Group: General Forum Members
Last Login: Saturday, December 10, 2011 6:38 AM
Points: 215, Visits: 633

I will say this...We called quest and ended up changing our call to their extended procedure. We added verbose logging on failure to 1 of our servers that was having lots of problems, and now none of the backups have failed since we changed that setting.

Post #824110

Paul White

Posted Wednesday, November 25, 2009 12:11 AM

SSChampion

Group: General Forum Members
Last Login: Wednesday, May 08, 2013 10:33 AM
Points: 10,989, Visits: 10,529

These questions might be better asked of the Quest LiteSpeed support team BigGrin

You might also try The Quest Online Support Forums.

Often, these things come about when using a older version of LiteSpeed. Equally often, the cause can be traced to an update from Microsoft breaking something.

Paul

Paul White
SQL Server MVP
SQLblog.com
@SQL_Kiwi

Post #824325

EdVassie

Posted Wednesday, November 25, 2009 4:30 AM

SSCrazy

Group: General Forum Members
Last Login: Today @ 6:21 AM
Points: 2,621, Visits: 2,757

I have experienced similar problems when memory has been under perssure.

The OP said they have a 16GB box with 13GB allocated to SQL Server. This may be OK in the OP's environment, but typically allocating 12GB to SQL on a 16GB box is about the upper limit of what is safe.

Over allocating memory a small amount does not always cause SQL Server to run slowly, although large over allocation will affect SQL speed. However, lack of memory may affect other processes on the box that need to conmnect to SQL Server, such as SSIS and backup routines.

One troubleshooting tactic that is definitely worth doing in this situation is reducing the memory available to SQL by maybe 10%, and see if things become stable. If this does work, you can then increase the SQL memory in stages until things start breaking again, to prove that this is a memory starvation issue.

Author: SQL Server FineBuild 1-click install and best practice configuration of SQL Server 2012, 2008 R2, 2008 and 2005. 25 March 2013: now over 23,000 downloads.
Disclaimer: All information provided is a personal opinion that may not match reality.
Concept: "Pizza Apartheid" - the discrimination that separates those who earn enough in one day to buy a pizza if they want one, from those who can not.

Post #824419

Erich Brinker

Posted Wednesday, November 25, 2009 8:08 AM

SSC Veteran

Group: General Forum Members
Last Login: Saturday, December 10, 2011 6:38 AM
Points: 215, Visits: 633

Thanks guys! I appreciate the help.

I posted here because we didn't really get a quality answer from Quest Support, and I was hoping someone else might have experienced the same issue.

I will check the forum as you suggest. And I will look into the memory pressure, but this hasn't seemed like an issue to this point.

Thanks again for the help

Post #824611

Erich Brinker

Posted Wednesday, November 25, 2009 9:00 AM

SSC Veteran

Group: General Forum Members
Last Login: Saturday, December 10, 2011 6:38 AM
Points: 215, Visits: 633

I do have a follow up question on why you say 12 gb is normally the upper limit of what is safe. Can you tell me what that is based on?

I have sized at 13 based on watching the total and target server memory. I have not seen it get to anything less than 1.4 gb free memory.

I was just wondering if I am missing something.

Thanks

Post #824683

EdVassie

Posted Wednesday, November 25, 2009 9:32 AM

SSCrazy

Group: General Forum Members
Last Login: Today @ 6:21 AM
Points: 2,621, Visits: 2,757

Did you check the memory use when you are running backups and other batch processes? You need to set your max memory use to take these into account.

If you have done this and 13GB looks OK, then it probably is. Just remember that if extra software is added to the server (including Windows, SQL and anti-virus fixes) or you add lots of new batch tasks then you should review the SQL max memory limit to see if it is still OK.

Author: SQL Server FineBuild 1-click install and best practice configuration of SQL Server 2012, 2008 R2, 2008 and 2005. 25 March 2013: now over 23,000 downloads.
Disclaimer: All information provided is a personal opinion that may not match reality.
Concept: "Pizza Apartheid" - the discrimination that separates those who earn enough in one day to buy a pizza if they want one, from those who can not.

Post #824725

Erich Brinker

Posted Wednesday, November 25, 2009 9:39 AM

SSC Veteran

Group: General Forum Members
Last Login: Saturday, December 10, 2011 6:38 AM
Points: 215, Visits: 633

I have watched it during backups and while it does drop, it never goes below 1.4 gb available.

I was just wondering if I had missed something. Thanks again for your time

Post #824734

Paul White

Posted Wednesday, November 25, 2009 2:36 PM

SSChampion

Group: General Forum Members
Last Login: Wednesday, May 08, 2013 10:33 AM
Points: 10,989, Visits: 10,529

1-2GB free is plenty on a dedicated box. Don't worry about it.

See http://blogs.msdn.com/slavao/archive/2006/11/13/q-a-does-sql-server-always-respond-to-memory-pressure.aspx for more information.

Paul White
SQL Server MVP
SQLblog.com
@SQL_Kiwi

Post #824952

« Prev Topic | Next Topic »

13 posts, Page 1 of 2

1 2 »»

Permissions