September 21, 2004 at 6:28 am
I have a backup that is running on my SQL 2000 server that i cannot find to stop running. it is set to append and to backup to an extra hard drive so therefore it just grows and grows until i have to delete the file.
I don't know who put the backup in place but they must have used a script because i cannot see it in the backup feature in sql, microsoft backup, or my veritas backupexec task scheduler.
i did a search in the registry also and could not find it.
any help would be greatly appreciated.
chris noffsinger
September 21, 2004 at 7:18 am
have you looked in the sql agent - jobs section - are there any jobs you don't recognise??
also this backup could have been added as a second step in one of the jobs.
check the backup file last modified date and see if this co-incides with any scheduled jobs.
MVDBA
September 21, 2004 at 7:18 am
also - set the file to read only - then see what complains!!
MVDBA
September 21, 2004 at 9:19 am
thank you for your help.
the read only thing is a good idea. but the erro shows up in my SQL error log.
the successful backup that i set up in enterprise manager and scheduled looks like this:
Database backed up: Database: Vendmax, creation date(time): 2003/01/13(07:44:56), pages dumped: 620531, first LSN: 127317:42:1, last LSN: 127317:56:1, number of dump devices: 1, device information: (FILE=2, TYPE=DISK: {'E:\backup.sql'}).
the backup that i want to get rid of looks like this. they look different in their syntax:
BACKUP failed to complete the command BACKUP DATABASE [Vendmax] TO DISK = N'E:\test.bak' WITH NOINIT , NOUNLOAD , NAME = N'Vendmax backup', NOSKIP , STATS = 10, NOFORMAT
i still cant seem to find it
September 21, 2004 at 10:07 am
There's a possibility that the job may have been started remotely by someone with backup rights. The next time the job runs, you could try running sp_who2 to see where the BACKUP command originates from.
SQL BAK Explorer - read SQL Server backup file details without SQL Server.
Supports backup files created with SQL Server 2005 up to SQL Server 2017.
September 21, 2004 at 10:09 am
you could try the following in your master,msdb database and vendmax databases
select sysobjects.name,syscoments.* from syscomments,sysobjects where syscomments.text like '%BACKUP DATABASE%' and sysobjects.id=syscomments.id
this will list all f the stored procedures that run a backup database.
you should also check all of the sql agent jobs and look at the properties of the steps of each job for the BACKUP DATABASE statement.
MVDBA
September 22, 2004 at 11:36 am
If the application is a third party application, I think I'd be checking it to see if they're trying to do your job.
Steve
September 22, 2004 at 1:34 pm
I've run into issues before where even if a job is deleted it remains in cache and still runs. I ran into a dba who told me a story that every night they would get a page and a e-mail about a job failing but they also could not find that job anywhere. Once they restarted SQL Server and thereby clearing the cache, the phantom job dissapeared.
Jason
September 22, 2004 at 3:05 pm
ok the job was definitly made using the command line script within SQL called BACKUP. it is not a third party app. the error actually shows up in enterprise manager in the erro log.
i have restarted a bunch of times but the job is still there somewhere.
thanks for all of your help
September 22, 2004 at 4:19 pm
Run profiler to determine "who" is executing the command. Might give you some clues as to where its coming from.
Steve
Viewing 10 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply