Backup job running for hours---Urgent

[ram]

hi,
my Backup job, took a backup at 3.00am , backup went well, but this job is still running , now the time is 10.00am.
I tried to kill this job but it is still running.
Why my process still running after taking a backup also.
Can anyone suggest me, how i have to resolve this.

Thanks!

--Ram

[Gary Andrews]

Don't know why, but:

1. Maybe you could look to see if you have any blocked processes?
(meaning is the backup process being blocked?)
2. Do you have any LONG running queries? I don't know how, but
maybe they are interfereing with the backup.
3. Do you have any OPEN transactions which in ways unknown to
me could be interfereing with the backup?

Sorry, but my 2 cents does not go any further. I will read other
responses to your question in an attempt to further my knowledge.




------------
ram at 10/12/00 12:34:24 PM

hi,
my Backup job, took a backup at 3.00am , backup went well, but this job is still running , now the time is 10.00am.
I tried to kill this job but it is still running.
Why my process still running after taking a backup also.
Can anyone suggest me, how i have to resolve this.

Thanks!

--Ram

[Gurukiran]

My $0.02 :

1. You cannot kill this process because in all probablility, the backup job
is running under 'sa' account. An 'sa' cannot kill another 'sa' process!
It is safer to always run this under a different account, one with the
fixed database role 'db_backupoperator'.

2. You can get the spid of this process by running sp_who, and then running
"dbcc sqlperf(threads)" and then looking for the hanging process to see if
it is doing any I/O. You will have to run the DBCC a few times and watch
for any change in the I/O column for that process. If there isn't any
change, you can conclude that it is a dead process.

3. If it is indeed a dead process, stop and restart SQL Server. Unfortunate,
but there it is. If it still doing I/O, you can wait for it to finish. Be
warned that trying to restart SQL Server in the middle of a long running
process will result in long recovery times for the database.

After the first time a similar thing happend to me, I decided to run these jobs in non-sa accounts, simply because I at least have the choice of killing the process.

Good luck !




------------
Gary Andrews at 10/12/00 12:44:44 PM

Don't know why, but:

1. Maybe you could look to see if you have any blocked processes?
(meaning is the backup process being blocked?)
2. Do you have any LONG running queries? I don't know how, but
maybe they are interfereing with the backup.
3. Do you have any OPEN transactions which in ways unknown to
me could be interfereing with the backup?

Sorry, but my 2 cents does not go any further. I will read other
responses to your question in an attempt to further my knowledge.




------------
ram at 10/12/00 12:34:24 PM

hi,
my Backup job, took a backup at 3.00am , backup went well, but this job is still running , now the time is 10.00am.
I tried to kill this job but it is still running.
Why my process still running after taking a backup also.
Can anyone suggest me, how i have to resolve this.

Thanks!

--Ram