Kill a long running Backup

  • What is the best way to kill a process ?  

    I have a Backup running across the Network that was setup and started via Maintenance plans.  It was just a test run and I think it may run all day!!!    What is the best way to kill it ????

  • OK.  ..   so I killed the process.....

    I went into the activity monitor and got the SPID for the T-SQL backup job step and issued a 'kill spid'

    now the .bak file on the destination server is still incrementing as if the backup is still running and the process on the source server is in 'rollback' it has been this way for a couple of hours..

    any ideas on what I did wrong and how to kill this backup????????

  • If its in rollback, you did successfully kill it.  SQL is basically "undoing" what it had done so far, and it will probably take roughly the same amount of time that you allowed it to run before killing it. 

    Steve

  • Kill 53 with statusonly     returns:

    SPID 53: transaction rollback in progress. Estimated rollback completion: 100%. Estimated time remaining: 0 seconds.

    It's been in this state ever since I issued the Kill.   I guess what concerns me most is that on the destination Server..  the .bak file keeps getting bigger and bigger..   I guess it's really not rolling back??  

  • Try to kill sqlmaint .exe from windows task manager.

Viewing 5 posts - 1 through 4 (of 4 total)

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