Cannot backup - Old killed backup still running

Question

Cannot backup - Old killed backup still running

terry999

SSCertifiable

Points: 5036
More actions
March 25, 2013 at 6:57 am

#291376

Hi
I have one DB that on a multi DB server that people cannot connect to. I'm not familar with the DB.
I THINK the problem was that an reindex or backup was ongoing when the Server was restarted.
If I try and backup the DB now I get this error:
System.Data.SqlClient.SqlError: Backup, file manipulation operations (such as ALTER DATABASE ADD FILE) and encryption changes on a database must be serialized. Reissue the statement after the current backup or file manipulation operation is completed. (Microsoft.SqlServer.Smo)
I can find 2 processes which have been killed: KILLED/ROLLBACK status=SUSPENDED. Both have wait time (ms) of a couple of days
kill 85 with statusonly
SPID 85: transaction rollback in progress. Estimated rollback completion: 0%. Estimated time remaining: 0 seconds.
How can I remove these so I may get the DB back up and working. Would a SQL restart work..
Thanks

Viewing 9 posts - 1 through 8 (of 8 total)

You must be logged in to reply to this topic. Login to reply

Gail Shaw SSC Guru Points: 1004504 More actions · Answer 1

Restart the SQL instance.

Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

terry999 SSCertifiable Points: 5036 More actions · Answer 2

Thanks for the Reply.

I really don't understand how this could have happened. These jobs are being rolled back from Friday/Sat morn. Its now mon.

I can select from tables in the DB but users cannot log into the App (of which I know nothing).

I will have to wait until people go home, just in case it takes a while to restart.

I have a backup but I guess I would be able to restore that while its in this state.

Gail Shaw SSC Guru Points: 1004504 More actions · Answer 3

You won't be able to drop or restore the database, just restart SQL. Shouldn't take any recovery time at all.

Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

SQL learner22 Default port Points: 1487 More actions · Answer 4

re-start backup may be a good idea if you can't restart the server(sql server) now or restart sql server and backup both when you can do that.

terry999 SSCertifiable Points: 5036 More actions · Answer 5

Long and short the whole server has been restarted, SQL started ok. these Backup processes have disappeared.

Thanks for your help.

It didn't take any time to restart.

paul.knibbs SSCoach Points: 15320 More actions · Answer 6

GilaMonster (3/25/2013)
You won't be able to drop or restore the database, just restart SQL. Shouldn't take any recovery time at all.

I think that's the first time I've ever seen you give the advice to just restart the server to fix the issue--is this sort of thing a known problem in SQL Server?

Gail Shaw SSC Guru Points: 1004504 More actions · Answer 7

Not a known issue in that there's a kb and a pile of documentation. I've seen it in person once, seen it on the forums since 3 or 4 times since. I don't know what causes it (and until I can repo on demand probably won't be able to figure it out), but a restart removes the rolling back backup with no long recovery required.

Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

raj acharya SSCrazy Points: 2805 More actions · Answer 8

we are facing same error as below....

not able to kill that process .................

Msg 3023, Level 16, State 2, Line 1

Backup, file manipulation operations (such as ALTER DATABASE ADD FILE) and encryption changes on a database must be serialized. Reissue the statement after the current backup or file manipulation operation is completed.

is there any solution except to restart sql server instance

Raj Acharya