April 23, 2012 at 10:54 am
Hey everyone. Need some help here.
I am working with 64 bit install of SQL Server 2005 SP4. We use Quest Litespeed Backups 6.5.1 for compression on our backups.
On Friday, for no reason, our instance restarted. Nothing in the error logs for 2 hours prior to the restart of the instance other than backup success emails. The suddently, bam, restart. No warning. Nothing. Started looking at the even viewer and errors logs and noticed that over the course of the last week we have had 4 different instances of it happening. Again, no errors in the error logs. The only consistent thing that I see is that directly before each restart of the instance, I get the following message in the Event Logs:
SQLVDI: Loc=SignalAbort. Desc=Client initiates abort. ErrorCode=(0). Process=6964. Thread=6988. Client. Instance=. VD=Global\VDI_BE103E66-E1D8-4842-A6DA-4AD0AF351D4D_0_SQLVDIMemoryName_0.
I find some information that SQLVDI is related to 3rd party backups. I am opening a ticket to Quest software, but I wanted to know if anyone else has dealt with this issue and found it not related to 3rd party backups.
Thanks,
Fraggle
April 23, 2012 at 12:07 pm
From what I can see, it's a problem with Quest Lightspeed trying to compress backups. Not limited to SQL 2005, and seems to have started about version 5.0.1 of Lightspeed.
I see some people solving it by moving to a different backup package (HyperBac or RedGate).
At least one seems to have solved it by removing a server alias from Configuration Manager.
That's what I can see on it. Probably the same stuff you're finding.
- Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
Property of The Thread
"Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon
April 23, 2012 at 12:33 pm
Yup, pretty much.
Fraggle.
April 24, 2012 at 1:00 am
Have you enabled Litespeed logging this will provide more info?
Try checking the windows application and system logs for any potential restart errors
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
April 24, 2012 at 8:25 am
We have Litespeed set to "Verbose, cleanup on success" so I have stuff that Litespeed is looking into.
The event logs don't show any restart errors.
Fraggle.
April 24, 2012 at 8:29 am
Fraggle-805517 (4/24/2012)
We have Litespeed set to "Verbose, cleanup on success" so I have stuff that Litespeed is looking into.The event logs don't show any restart errors.
Fraggle.
a;; of the shutdown and startup info you see in the sql server log is echoed to the windows application log, are you saying that you are not seeing any of this?
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
April 25, 2012 at 7:41 am
a few questions ...
How much RAM on the Windows side ?
How much RAM is allocated to SQL Server ?
Are you using any startup trace flags ?
Are you using 'default' LiteSpeed backup parameters ?
I ask because we encountered these issues as well in the past and worked through them with LiteSpeed successfully.
RegardsRudy KomacsarSenior Database Administrator"Ave Caesar! - Morituri te salutamus."
April 25, 2012 at 9:32 am
rudy - Doctor "X" (4/25/2012)
a few questions ...How much RAM on the Windows side ?
How much RAM is allocated to SQL Server ?
Are you using any startup trace flags ?
Are you using 'default' LiteSpeed backup parameters ?
I ask because we encountered these issues as well in the past and worked through them with LiteSpeed successfully.
1) 72GB total machine memory
2) 68GB max server memory for SQL
3) Flags on startup - 1222, 2861, 3226, 3605
4) With one exception, everything is default. We set our standard compression rate at 5.
Additionally, the machine does have SSIS and Full Text Indexing.
Lastly, the database on the server does use CLR's pretty heavily to call 3rd party API's.
Fraggle.
April 25, 2012 at 9:35 am
Fraggle-805517 (4/25/2012)
rudy - Doctor "X" (4/25/2012)
a few questions ...How much RAM on the Windows side ?
How much RAM is allocated to SQL Server ?
Are you using any startup trace flags ?
Are you using 'default' LiteSpeed backup parameters ?
I ask because we encountered these issues as well in the past and worked through them with LiteSpeed successfully.
1) 72GB total machine memory
2) 68GB max server memory for SQL
3) Flags on startup - 1222, 2861, 3226, 3605
4) With one exception, everything is default. We set our standard compression rate at 5.
Additionally, the machine does have SSIS and Full Text Indexing.
Lastly, the database on the server does use CLR's pretty heavily to call 3rd party API's.
Fraggle.
with that little lot running i would consider lowering max server memory to around 62GB initially
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
April 25, 2012 at 10:59 am
Why?
Fraggle
April 28, 2012 at 11:37 am
hmmm ... I do not see anything that really jumps out at me ...
I did learn about those first 2 trace flags though ...
At this point I do not have any positive steps to add to assist with your issue other than to open up a case with MS and possibly Quest.
Sorry ...
RegardsRudy KomacsarSenior Database Administrator"Ave Caesar! - Morituri te salutamus."
Viewing 11 posts - 1 through 10 (of 10 total)
You must be logged in to reply to this topic. Login to reply