Failed Maintenance Plan

Please advice.
I run a SQL2k SP4 on WIN2K SP4.
I have a maintenance plan to backup the databases at 01:30AM. This has alway
s been succesfull.
Strangely it did the backup at 02:25PM with no entry in SQL Error Log and ca
using subsequent backups to fail as the files created had the 02:25 badge he
nce could not be deleted.
Please help as to what caused the maintenance plan to backup at 02:25 and wh
at to do to avoid it.
Thanks for your kind response.I posted a reply to this yesterday. Here's that text:
My guess is that it wasn't Main Plan that did the backup, someone else did i
t (or explicitly started the main
plan job, or scheduled the main plan job at that hour). If it was executed a
s a job, you can view the job
history under EM, Management, Jobs. In any event, each backup is written to
the eventlog and the errorlog
file.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"Timi" <anonymous@.discussions.microsoft.com> wrote in message
news:EA0A7329-EAA1-49B3-9DDB-1736B6F35A4C@.microsoft.com...
> Please advice.
> I run a SQL2k SP4 on WIN2K SP4.
> I have a maintenance plan to backup the databases at 01:30AM. This has alw
ays been succesfull.
> Strangely it did the backup at 02:25PM with no entry in SQL Error Log and causing
subsequent backups to fail
as the files created had the 02:25 badge hence could not be deleted.
> Please help as to what caused the maintenance plan to backup at 02:25 and
what to do to avoid it.
> Thanks for your kind response.
>|||Thanks for your response.
The maint plan was ran at 02:25AM as opposed to 01:30AM the scheduled time.|||can you check with your server guys if there was a problem
with the server which resulted in it being restarted on or
arounf 2:25 ?, but the best way of finding out is to check
the error log.
J

>--Original Message--
>Thanks for your response.
>The maint plan was ran at 02:25AM as opposed to 01:30AM
the scheduled time.
>.
>|||Agent does no run a job if it was down at the time it should have executed.
I doubt that this is the reason,
based on that. I bet a beer that someone started the job at that time.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"Julie" <anonymous@.discussions.microsoft.com> wrote in message news:13fdd01c41357$84085e80$
a301280a@.phx.gbl...
> can you check with your server guys if there was a problem
> with the server which resulted in it being restarted on or
> arounf 2:25 ?, but the best way of finding out is to check
> the error log.
> J
>
> the scheduled time.|||Bet a beer against you and your SQL Server knowledge, never ;)
Anyway your right but my sneaky plan was to get Timm to check the server, as
we both agree thats where the problem is, and who actually started it.|||:-)
<<as we both agree thats where the problem is, and who actually started it.>
>
Yep.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"Julie" <anonymous@.discussions.microsoft.com> wrote in message
news:D6CB3367-9F9F-4633-B7FE-3FBEBFFA8B74@.microsoft.com...
> Bet a beer against you and your SQL Server knowledge, never ;)
> Anyway your right but my sneaky plan was to get Timm to check the server, as we bo
th agree thats where the
problem is, and who actually started it.