Backup continues to try to execute...

Greetings
I've inherited a SQL server recently at work, and in trying to clean up
the maintenance plan and back ups I've discovered that every night
there is a backup job for the transactions for two particular databases
that attempts to run, but is misconfigured and fails. Weird thing is
there isn't a backup job in Enterprise Manager. My maintenance plan,
the only maintenance plan, executes fine and backs up those particular
databases and their transaction logs fine. I'm just trying to find
this phantom backup job that is misconfigured and filling up my event
logs. Any help you can provide is appreciated.
moterSQL Server Profiler is your friend
<motert@.gmail.com> wrote in message
news:1152453296.717787.45300@.m73g2000cwd.googlegroups.com...
> Greetings
> I've inherited a SQL server recently at work, and in trying to clean up
> the maintenance plan and back ups I've discovered that every night
> there is a backup job for the transactions for two particular databases
> that attempts to run, but is misconfigured and fails. Weird thing is
> there isn't a backup job in Enterprise Manager. My maintenance plan,
> the only maintenance plan, executes fine and backs up those particular
> databases and their transaction logs fine. I'm just trying to find
> this phantom backup job that is misconfigured and filling up my event
> logs. Any help you can provide is appreciated.
> moter
>|||I looked through the Profiler, but could not find any events that
watched backups. I know the job is executing, I just can't find it in
Enterprise Manager to delete it. It doesn't display in the Backups
section and is not a part of my maintenance plan. It's a phantom
backup job from some where.
Any other ideas?
Uri Dimant wrote:[vbcol=seagreen]
> SQL Server Profiler is your friend
>
> <motert@.gmail.com> wrote in message
> news:1152453296.717787.45300@.m73g2000cwd.googlegroups.com...|||The backup command can be executed by anyone. Agent isn't the only scheduler
on the market. Even
Windows comes with a built-in scheduler. Use Profiler to capture the BACKUP
command and see what the
application name is. Might help you to narrow things down a bit.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
<motert@.gmail.com> wrote in message news:1152456107.316846.79550@.75g2000cwc.googlegroups.com
..
>I looked through the Profiler, but could not find any events that
> watched backups. I know the job is executing, I just can't find it in
> Enterprise Manager to delete it. It doesn't display in the Backups
> section and is not a part of my maintenance plan. It's a phantom
> backup job from some where.
> Any other ideas?
>
> Uri Dimant wrote:
>|||motert@.gmail.com wrote:
> I looked through the Profiler, but could not find any events that
> watched backups. I know the job is executing, I just can't find it in
> Enterprise Manager to delete it. It doesn't display in the Backups
> section and is not a part of my maintenance plan. It's a phantom
> backup job from some where.
> Any other ideas?
>
The output of sp_who2 includes a column for the application name. If
this is running from an Agent job, it will indicate that in this field.
You could also KILL the process that is running the backup, and then see
which Agent job fails.
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Thanks to all who have responded so far. I went all the way through
the Profiler and couldn't find where to select BACKUP as an event to
trace. I'll admidt I've never used it before so any basics will help.
I was able to find this though:
"SQL Server Scheduled Job 'database backup1' - Status: Failed - Invoked
on: 2006-07-09 22:00:01 - Message: The job failed. The Job was invoked
by Schedule 13 (Schedule 1). The last step to run was step 1 (Step
1)."
Does that help narrow it down any?
Thanks again!
moter
Tracy McKibben wrote:
> motert@.gmail.com wrote:
> The output of sp_who2 includes a column for the application name. If
> this is running from an Agent job, it will indicate that in this field.
> You could also KILL the process that is running the backup, and then see
> which Agent job fails.
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com|||motert@.gmail.com wrote:
> Thanks to all who have responded so far. I went all the way through
> the Profiler and couldn't find where to select BACKUP as an event to
> trace. I'll admidt I've never used it before so any basics will help.
> I was able to find this though:
> "SQL Server Scheduled Job 'database backup1' - Status: Failed - Invoked
> on: 2006-07-09 22:00:01 - Message: The job failed. The Job was invoked
> by Schedule 13 (Schedule 1). The last step to run was step 1 (Step
> 1)."
> Does that help narrow it down any?
> Thanks again!
> moter
>
That gives you the name of the job right there in the error message.
"database backup1" is the name of the Agent job...
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||I found it. Typing it out led me there. Thanks everyone.
mot...@.gmail.com wrote:[vbcol=seagreen]
> Thanks to all who have responded so far. I went all the way through
> the Profiler and couldn't find where to select BACKUP as an event to
> trace. I'll admidt I've never used it before so any basics will help.
> I was able to find this though:
> "SQL Server Scheduled Job 'database backup1' - Status: Failed - Invoked
> on: 2006-07-09 22:00:01 - Message: The job failed. The Job was invoked
> by Schedule 13 (Schedule 1). The last step to run was step 1 (Step
> 1)."
> Does that help narrow it down any?
> Thanks again!
> moter
>
> Tracy McKibben wrote: