Ghost backup job

SurinderSurinder Posts: 44 Bronze 2
edited September 23, 2010 1:28AM in SQL Backup Previous Versions
Hi,

We rescheduled our nightly backup job, which used to run just after midnight, to an earlier time.

The new rescheduled job runs fine, but for some reason the old job still kicks off. It doesn't do anything from what i can see.

How can i remove the unwanted jobs?

Thanks..
Surinder

Below is an snippet of the log.
09/21/2010 00:04:39,Backup,Unknown,Database backed up. Database: agrtempdb<c/> creation date(time): 2009/02/12(09:31:45)<c/> pages dumped: 1<c/> first LSN: 2085:35597:296<c/> last LSN: 2085:35670:1<c/> number of dump devices: 1<c/> device information: (FILE=1<c/> TYPE=VIRTUAL_DEVICE: {'{71C050B5-B082-48BA-A481-43BFD8657567}4'}). This is an informational message only. No user action is required.
09/21/2010 00:04:39,Backup,Unknown,Database backed up. Database: AgrProd<c/> creation date(time): 2009/02/12(07:54:55)<c/> pages dumped: 1<c/> first LSN: 23538:45175:87<c/> last LSN: 23538:45241:1<c/> number of dump devices: 1<c/> device information: (FILE=1<c/> TYPE=VIRTUAL_DEVICE: {'{71C050B5-B082-48BA-A481-43BFD8657567}3'}). This is an informational message only. No user action is required.
09/21/2010 00:04:39,Backup,Unknown,Database backed up. Database: msdb<c/> creation date(time): 2005/10/14(01:54:05)<c/> pages dumped: 1<c/> first LSN: 2028:16:48<c/> last LSN: 2028:48:1<c/> number of dump devices: 1<c/> device information: (FILE=1<c/> TYPE=VIRTUAL_DEVICE: {'{71C050B5-B082-48BA-A481-43BFD8657567}2'}). This is an informational message only. No user action is required.
09/21/2010 00:04:39,Backup,Unknown,Database backed up. Database: model<c/> creation date(time): 2003/04/08(09:13:36)<c/> pages dumped: 1<c/> first LSN: 109:288:34<c/> last LSN: 109:312:1<c/> number of dump devices: 1<c/> device information: (FILE=1<c/> TYPE=VIRTUAL_DEVICE: {'{71C050B5-B082-48BA-A481-43BFD8657567}1'}). This is an informational message only. No user action is required.
09/21/2010 00:04:39,Backup,Unknown,Database backed up. Database: master<c/> creation date(time): 2010/09/20(06:36:26)<c/> pages dumped: 1<c/> first LSN: 459:16:35<c/> last LSN: 459:40:1<c/> number of dump devices: 1<c/> device information: (FILE=1<c/> TYPE=VIRTUAL_DEVICE: {'{71C050B5-B082-48BA-A481-43BFD8657567}5'}). This is an informational message only. No user action is required.
09/21/2010 00:04:38,spid74,Unknown,I/O was resumed on database agrtempdb. No user action is required.
09/21/2010 00:04:38,spid75,Unknown,I/O was resumed on database master. No user action is required.
09/21/2010 00:04:38,spid73,Unknown,I/O was resumed on database AgrProd. No user action is required.
09/21/2010 00:04:38,spid76,Unknown,I/O was resumed on database msdb. No user action is required.
09/21/2010 00:04:38,spid71,Unknown,I/O was resumed on database model. No user action is required.
09/21/2010 00:04:38,spid75,Unknown,I/O is frozen on database master. No user action is required. However<c/> if I/O is not resumed promptly<c/> you could cancel the backup.
09/21/2010 00:04:38,spid74,Unknown,I/O is frozen on database agrtempdb. No user action is required. However<c/> if I/O is not resumed promptly<c/> you could cancel the backup.
09/21/2010 00:04:38,spid73,Unknown,I/O is frozen on database AgrProd. No user action is required. However<c/> if I/O is not resumed promptly<c/> you could cancel the backup.
09/21/2010 00:04:38,spid76,Unknown,I/O is frozen on database msdb. No user action is required. However<c/> if I/O is not resumed promptly<c/> you could cancel the backup.
09/21/2010 00:04:38,spid71,Unknown,I/O is frozen on database model. No user action is required. However<c/> if I/O is not resumed promptly<c/> you could cancel the backup.
09/21/2010 00:00:29,spid20s,Unknown,This instance of SQL Server has been using a process ID of 1704 since 20/09/2010 06:37:10 (local) 20/09/2010 05:37:10 (UTC). This is an informational message only; no user action is required.
09/20/2010 18:37:17,Backup,Unknown,Database backed up. Database: AgrProd<c/> creation date(time): 2009/02/12(07:54:55)<c/> pages dumped: 2674240<c/> first LSN: 23537:19366:300<c/> last LSN: 23537:22886:1<c/> number of dump devices: 1<c/> device information: (FILE=1<c/> TYPE=VIRTUAL_DEVICE: {'SQLBACKUP_011EC6CF-65CC-46A7-A47A-2F6288573DC9'}). This is an informational message only. No user action is required.
09/20/2010 18:30:11,Backup,Unknown,Database backed up. Database: msdb<c/> creation date(time): 2005/10/14(01:54:05)<c/> pages dumped: 2016<c/> first LSN: 2027:48:289<c/> last LSN: 2027:176:1<c/> number of dump devices: 1<c/> device information: (FILE=1<c/> TYPE=VIRTUAL_DEVICE: {'SQLBACKUP_2256A2C3-48BF-4ECB-A81A-2B561088A8C5'}). This is an informational message only. No user action is required.
09/20/2010 18:30:05,Backup,Unknown,Database backed up. Database: model<c/> creation date(time): 2003/04/08(09:13:36)<c/> pages dumped: 344<c/> first LSN: 109:240:37<c/> last LSN: 109:264:1<c/> number of dump devices: 1<c/> device information: (FILE=1<c/> TYPE=VIRTUAL_DEVICE: {'SQLBACKUP_EA2FCE36-1B0A-4BDD-BDA4-DE4807C77685'}). This is an informational message only. No user action is required.
09/20/2010 18:30:02,Backup,Unknown,Database backed up. Database: master<c/> creation date(time): 2010/09/20(06:36:26)<c/> pages dumped: 472<c/> first LSN: 458:368:50<c/> last LSN: 458:400:1<c/> number of dump devices: 1<c/> device information: (FILE=1<c/> TYPE=VIRTUAL_DEVICE: {'SQLBACKUP_8EBBF0DE-FFCB-4C77-934C-2AFDBC31B8DF'}). This is an informational message only. No user action is required.
Shin..
· Share on Twitter

Comments

  • peteypetey Posts: 2,358 New member
    All scheduled jobs using SQL Backup are maintained by the SQL Server Agent. SQL Backup itself does not have a scheduling component. Could you please use SQL Server Management Studio to check if the old job still exists as one of SQL Server Agent's scheduled jobs?

    Thanks.
    Peter Yeoh
    SQL Backup Consultant Developer
    Associate, Yohz Software
    Beyond compression - SQL Backup goodies under the hood, updated for version 8
    · Share on Twitter
Sign In or Register to comment.