February 29, 2016 at 12:03 am
Hi,
I have a backup job running on scheduled basis.
This native backup job is blocked by different backup which is taking 1 db backup to virual disk.
This instance has 10 databases. The job completed 4 database backup and after it is blocked on the other db. It continuously blocked. So killed the native backup job.
After that I noticed it continued some other database backups except the db which it was blocked.
Questions:
What will happen if we right click and stop the running backup job instead of killing the backup job spids. Is there any difference b/n killing and stopping the job?
When I killed the job spid how it continued the backup of other databases?
February 29, 2016 at 7:33 am
Without seeing the code that's calling the backups, it's hard to tell you why it continued after you killed the process. However, in terms of stopping the backups, there's no difference between stopping the job and killing the process. But, if the job is the one that continued running backups after you killed the process, then stopping the job will stop all those backups.
The real issue is, why do you have more than one backup process running against your databases? Do you have differential backups in addition to full and log backups? If so, be sure that you're using copy_only for secondary full backups or you could have problems restoring databases in the future since differentials are linked to the last backup unless you use copy_only.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
February 29, 2016 at 12:42 pm
We have only log backups for some databases no diff backups.
After killing the backup job, took the backup of remaining databases manually (except the db which is blocking). I don't think it will break the chain.
February 29, 2016 at 4:19 pm
No. Full backups and log backups can be mixed and matched as long as you have the log backups in order. Taking a full backup, in and of itself, never affects your log backup chain. It's only differentials that you have to worry about.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply