November 4, 2013 at 1:34 pm
The nightly backup job on one of my SQL 2005 servers failed this past Saturday and Sunday night. I backup to our NAS on which I have a disk quota. The SQL error logs indicate an Out of Disk Space condition - which could be - but one of our storage admins also hinted that they may have caused a temporary outage on Saturday. So I don't know the true cause. In any event I have a SPID 55 spawned from the Sunday night's backup that was not killed when the SQL Agent job failed. I killed it this morning (7 hrs ago) but it is still in a KILLED/ROLLBACK status and has a huge 61962953 BACKUP THREAD wait that keeps incrementing, but the Physical IO counter remains unchanged. I need to get rid of this SPID so it doesn't interfere with tonight's backup. What are my options?
November 4, 2013 at 1:43 pm
The SPID has disappeared finally. I use Hyperbac on this server. I tried stopping the Hyperbac service but it did not respond normally. So I opened up Task Manager and killed the Hyperbac processes that were running. Moments later the backup SPID
finally went away. So it appears there was some hangup between SQL and Hyperbac.
I restarted the Hyperbac service. ....now we'll see what happens tonight.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply