BACKUP LOG failed - no reason given

Hello,
I have an agent job that backs up transaction logs of several databases,
referring a maintenance plan.
Recently, one of the backups began to fail sometimes - the one of the
largest database. The messages in the log are:
...
Log backed up: Database: OLAP, creation date(time): 2004/01/21(11:42:56),
first LSN: 4615:16:1, last LSN: 4617:16:1, number of dump devices: 1, device
information: (FILE=1, TYPE=DISK:
{'D:\MSSQL\MSSQL\BACKUP\OLAP_tlog_200501211015.TRN '}).
Log backed up: Database: RGRSQL, creation date(time): 2004/01/08(10:20:44),
first LSN: 50593:45:1, last LSN: 50614:57:1, number of dump devices: 1,
device information: (FILE=1, TYPE=DISK:
{'D:\MSSQL\MSSQL\BACKUP\RGRSQL_tlog_200501211015.T RN'}).
BACKUP failed to complete the command BACKUP LOG [VMFG] TO DISK =
N'D:\MSSQL\MSSQL\BACKUP\VMFG_tlog_200501211015.TRN ' WITH INIT , NOUNLOAD ,
NOSKIP , STATS = 10, NOFORMAT
MSKB article says to examine the previous errors in the log, but there are
none, neither in sql server log, nor in any event log of the machine.
And then on the next scheduled time, it succeeds. Then again fails. No
pattern.
Pretty much same thing is happening with the full database backup - same
database.
"CHECKDB found 0 allocation errors and 0 consistency errors in database
'VMFG'."
How to troubleshoot it? is there a way to make it to tell _why_ it failed?
thanks,
Vadim Rapp
Polyscience, Inc.
Is someone else trying to put your backup device onto tape while your trying
to write to it?
"Vadim Rapp" <vrapp@.nospam.polyscience.com> wrote in message
news:#6Hq$J#$EHA.2316@.TK2MSFTNGP15.phx.gbl...
> Hello,
> I have an agent job that backs up transaction logs of several databases,
> referring a maintenance plan.
> Recently, one of the backups began to fail sometimes - the one of the
> largest database. The messages in the log are:
> ...
> Log backed up: Database: OLAP, creation date(time): 2004/01/21(11:42:56),
> first LSN: 4615:16:1, last LSN: 4617:16:1, number of dump devices: 1,
device
> information: (FILE=1, TYPE=DISK:
> {'D:\MSSQL\MSSQL\BACKUP\OLAP_tlog_200501211015.TRN '}).
> Log backed up: Database: RGRSQL, creation date(time):
2004/01/08(10:20:44),
> first LSN: 50593:45:1, last LSN: 50614:57:1, number of dump devices: 1,
> device information: (FILE=1, TYPE=DISK:
> {'D:\MSSQL\MSSQL\BACKUP\RGRSQL_tlog_200501211015.T RN'}).
> BACKUP failed to complete the command BACKUP LOG [VMFG] TO DISK =
> N'D:\MSSQL\MSSQL\BACKUP\VMFG_tlog_200501211015.TRN ' WITH INIT , NOUNLOAD
,
> NOSKIP , STATS = 10, NOFORMAT
> MSKB article says to examine the previous errors in the log, but there are
> none, neither in sql server log, nor in any event log of the machine.
> And then on the next scheduled time, it succeeds. Then again fails. No
> pattern.
> Pretty much same thing is happening with the full database backup - same
> database.
> "CHECKDB found 0 allocation errors and 0 consistency errors in database
> 'VMFG'."
> How to troubleshoot it? is there a way to make it to tell _why_ it failed?
>
> thanks,
> Vadim Rapp
> Polyscience, Inc.
>
>
|||Hello Chris:
You wrote on Fri, 21 Jan 2005 11:09:20 -0800:
C> Is someone else trying to put your backup device onto tape while your
C> trying to write to it?
No.
Vadim