log shipping error

I have successfully configured log shipping, and verified that the standby
server is being updated correctly.
There is one job named "Log Shipping Alert Job - Backup" which fails every
minute.
In the job history, it says:
'The job shipping source SERVERNAME.DATABASE has not backed up for 190
minutes. [SQLSTATE 42000] [Error 14420] The step failed.'
I guess that this can be disregarded, but supervisors get nervous about
errors, and suspect that the log shipping is not reliable.
How can I make this job succeed?
Thanks
Bill
It looks like the 'last_updated' field in 'log_shipping_primaries' in MSDB
isn't getting updated.
Whey would that be the case?
Thanks
Bill
"bill" <belgie@.datamti.com> wrote in message
news:e$lobJOeFHA.2128@.TK2MSFTNGP14.phx.gbl...
> I have successfully configured log shipping, and verified that the standby
> server is being updated correctly.
> There is one job named "Log Shipping Alert Job - Backup" which fails every
> minute.
> In the job history, it says:
> 'The job shipping source SERVERNAME.DATABASE has not backed up for 190
> minutes. [SQLSTATE 42000] [Error 14420] The step failed.'
> I guess that this can be disregarded, but supervisors get nervous about
> errors, and suspect that the log shipping is not reliable.
> How can I make this job succeed?
> Thanks
> Bill
>
>
|||Microsoft say:
"Thresholds
The DBA maintaining the SQL Server environment needs to know if log shipping becomes too far out of sync and/or may be failing. The two parameters to configure are: backup alert threshold and out of sync alert threshold. The alerts are triggered by error messages 14420 and 14421, respectively, and can be changed. After log shipping is installed, access the parameters by selecting the properties of the log shipping pair listed under the Log Shipping Monitor. "
Regards,
Milovan