Log Shipping Plan fails (event: 208)

Hi,
We've been using logshipping successfully for over a year,
but recently we are experiencing more and more failures
relating to the Transaction Log Backup Job. We are
currently log shipping 30 databases from a W2K(SP4)
SQL2000(SP3) server to a W2K3 Server (SQL2000SP3).
The backup jobs aren't consistently failing, which is
making this harder to diagnose. If I manually run the jobs
from Enterprise Manager they work fine, and the only error
messages that i'm seeing are like the following:
EventID: 208
SQL Server Scheduled Job 'Transaction Log Backup Job for DB
Maintenance Plan 'Unity_Server1 Log Shipping''
(0x318A0055279BA840AABD24DA1BA5B440) - Status: Failed -
Invoked on: 2004-09-20 17:15:10 - Message: The job failed.
The Job was invoked by Schedule 59 (Schedule 1). The last
step to run was step 1 (Step 1).
There aren't any issues with disk space, and I don't think
this is a security issue, as the jobs aren't consistently
failing.
Hoping that someone has come across this issue before.
Thanks,
Martin
Martin,
I'm not too sure where this message originates from, but if it is the job,
then in the maintenance plan can you enable logging to the textfile and then
examine the resulting messages. I often just receive sqlmaint.exe failed
messages in the job, but in the textfile find out the real cause of the
problem.
Regards,
Paul Ibison
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Paul Ibison wrote:
> Martin,
> I'm not too sure where this message originates from, but if it is the job,
> then in the maintenance plan can you enable logging to the textfile and then
> examine the resulting messages.
This is interesting - when I examine the folder containing the
log-shipping logs - whenever a job fails there is no log created.
However, successful log-shipping jobs do create a log file. So not only
is the job failing to complete, but it's also failing to create a log of
the failure.
Looking at the job history shows a complete list of all the log-shipping
jobs with corresponding results (failed or successful).
Thanks
Martin
|||Martin,
in that case you could use profiler. Some things are
incompatible with backups - eg file management operations
such as the ALTER DATABASE statement with either the ADD
FILE or REMOVE FILE options; shrink database or shrink
file - this includes autoshrink operations.
HTH,
Paul Ibison
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
sql