October 30, 2007 at 2:36 pm
A scheduled backup job using LiteSpeed was hanging there. I stopped the job, run kill spid command. However, the spid still stayed there and I saw the message,
Killed/Rollback
using sp_who2 active.
I heard that whenever we use any third-party backup tool, we need to open two threads. We have to restart the SQL Server in order to remove the spid.
Could anyone be able to provide any reference about the above statement?
Many thanks in advance.
October 30, 2007 at 2:51 pm
Ouch! Sorry to hear it. We've had that happen twice with LiteSpeed x64 edition on SQL 2005 enterprise.
The only solution was to restart the instance. The hung rollback did not present an issue on the restart.
If you're in a highly-available situation like us, and can't restart the service at will, then you need to keep an eye on transaction logs if you are not in Simple recoverability mode. That hung backup may interfere with any further attempt to take log backups, and you cannot add grow a log file or add log files during a backup. The log will continue to fill until either you can restart the service and resume normal log backups or it runs out of room. You will need to look at the free space and the fill rate to project how much time you have left to restart the service.
Good luck,
-Eddie
Eddie Wuerch
MCM: SQL
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply