March 25, 2008 at 10:43 am
I am using SQL Litespeed tool for the restore of a database backup, can someone let me know how I can stop the restore as it looks like the restore is hung, Thanks!!
March 25, 2008 at 12:55 pm
I'm not familiar with Litespeed.
Does it use some sort of extended stored procedure, or does it run as a standalone program?
Assuming you know your backup is good, can you use task manager to manualyl kill litespeed and/or bounce SQL services to free it up?
The Redneck DBA
March 25, 2008 at 1:25 pm
It runs based on extended stored procs, without bounvcing the sql services can we stop the process? Thx.
March 25, 2008 at 1:53 pm
Not being a LiteSpeed guru I hesitate to suggest much. I'd look on Quest's support page. It may be a common problem with a simple solution.
Another thing you might do is look thru the Windows event logs. I used to use Idera SQL Safe, and sometimes errors would get logged there and nowhere else.
The Redneck DBA
March 25, 2008 at 3:19 pm
Is it using a connection to sql server. If so you can find out the spid by doing a sp_who2 and dbcc inputbuffer and kill the spid. I also am not familiar with litespeed but I would start there.
March 25, 2008 at 8:04 pm
Litespeed backup is compressed. When the backup is restored, it will be decompressed first then restored. Depends on the database size, it may take a while for the whole process. During the decompressing period, you will see the process is doing nothing (hanging).
You may terminate it by killing the process.
March 29, 2008 at 4:32 pm
I think you will not be able to stop without stopping sql service. you may try killing process id using tskill command thru DOS Command prompt
[font="Verdana"]--www.sqlvillage.com[/size][/font]
April 3, 2008 at 7:23 am
Hi MH,
I'm sorry you're having trouble with your restore. You can stop a hangin restore restore by either killing the spid that LiteSpeed is using or by ending the LiteSpeed process (sqllitespeed32.exe). You will not have to stop the SQL Server process at any point in time.
You can then restart the restore and if the problem persists you should contact Quest support. LiteSpeed is supported 24/7 and they'll be happy to help you.
Regards,
David Swanson
Quest Product Management
April 3, 2008 at 9:22 am
I remember there is a parameter showing the restore progress, like 10% something, when using xp_restore_database. I did not see it work when I used it.
David, do you know anything about this? Do you have an example to share how to use this parameter to see the restore progress?
Thanks,
Vivien
April 3, 2008 at 9:33 am
Hi Vivien,
The parameter is " @with = 'STATS = 10' ". Change the '10' to whatever oncrement you want reported. The progress var in the interface defaults to 10%.
I hope that helps.
-David
April 13, 2009 at 12:34 pm
If you forget to include stats in the restore stored procedure, you can use the LiteSpeed stored procedure xp_slsreadprogress 'database ' to retreive the percentage complete. This stored procedure will not work for native restores. Just like using stats in the restore, it doesn't seem to be completely accurate.
April 14, 2009 at 3:10 pm
Mh (3/25/2008)
I am using SQL Litespeed tool for the restore of a database backup, can someone let me know how I can stop the restore as it looks like the restore is hung, Thanks!!
Find the processes id and files it is using through handle.exe and then kill the handle that process id is making use of restoring backup file.
To get handle information, please execute handle.exe -p LiteSpeed32.exe
once you get the information, pick the handle information which is in hexadecimal format and this is followed immediately with a colon.
once you get the information, you can execute handle.exe -c hexadecimal value -P process name or id.
This will teriminate the restore processes rather than killing all the processes that are used by litespeed i.e backups etc if you kill the litespeed through task manager.
Viewing 12 posts - 1 through 11 (of 11 total)
You must be logged in to reply to this topic. Login to reply