none
LSAlert job to informational

    Question

  • I have implemented logshipping and it is running with few issues. The SQL Server service account on our primary server runs under the local system account (network is a machine account), however we have created the backup folder in the secondary server because of our backup strategy and this lead us to create the sqlserver alert log error Executed as user: NT AUTHORITYNETWORK SERVICE. The log shipping primary database server.Database has backup threshold of 60 minutes and has not performed a backup log operation for 2295 minutes. Check agent log and logshipping monitor information. [SQLSTATE 42000] (Error 14420). The step failed. This also generates the event log error The log shipping primary database server.DatabaseName has backup threshold of 60 minutes and has not performed a backup log operation for 2295 minutes. Check agent log and logshipping monitor information. Is there a way to modify the event log so that the log becomes information because we know that the backup occurs during log shipping without any issues.
    Monday, April 29, 2013 2:35 PM

Answers

  • http://support.microsoft.com/kb/329133?wa=wsignin1.0

    Troubleshooting Error Message 14420

    By definition, message 14420 does not necessarily indicate a problem with log shipping. The message indicates that the difference between the last backed up file and current time on the monitor server is greater than the time that is set for the Backup Alert threshold.

    There are serveral reasons why the alert message is generated. The following list includes some of these reasons:
    1. The date or time (or both) on the monitor server is different from the date or time on the primary server. It is also possible that the system date or time was modified on the monitor or the primary server. This may also generate alert messages.
    2. When the monitor server is offline and then back online, the fields in the log_shipping_primaries table are not updated with the current values before the alert message job runs.
    3. The log shipping Copy job that is run on the primary server might not connect to the monitor server msdb database to update the fields in the log_shipping_primaries table. This may be the result of an authentication problem between the monitor server and the primary server.
    4. You may have set an incorrect value for the Backup Alert threshold. Ideally, you must set this value to at least three times the frequency of the backup job. If you change the frequency of the backup job after log shipping is configured and functional, you must update the value of theBackup Alert threshold accordingly.
    5. The backup job on the primary server is failing. In this case, check the job history for the backup job to see a reason for the failure.

    Srinivasan

    Monday, April 29, 2013 4:06 PM

All replies

  • http://support.microsoft.com/kb/329133?wa=wsignin1.0

    Troubleshooting Error Message 14420

    By definition, message 14420 does not necessarily indicate a problem with log shipping. The message indicates that the difference between the last backed up file and current time on the monitor server is greater than the time that is set for the Backup Alert threshold.

    There are serveral reasons why the alert message is generated. The following list includes some of these reasons:
    1. The date or time (or both) on the monitor server is different from the date or time on the primary server. It is also possible that the system date or time was modified on the monitor or the primary server. This may also generate alert messages.
    2. When the monitor server is offline and then back online, the fields in the log_shipping_primaries table are not updated with the current values before the alert message job runs.
    3. The log shipping Copy job that is run on the primary server might not connect to the monitor server msdb database to update the fields in the log_shipping_primaries table. This may be the result of an authentication problem between the monitor server and the primary server.
    4. You may have set an incorrect value for the Backup Alert threshold. Ideally, you must set this value to at least three times the frequency of the backup job. If you change the frequency of the backup job after log shipping is configured and functional, you must update the value of theBackup Alert threshold accordingly.
    5. The backup job on the primary server is failing. In this case, check the job history for the backup job to see a reason for the failure.

    Srinivasan

    Monday, April 29, 2013 4:06 PM
  • Hi

    Error 14420 and  14421  these are two generic alerts  for log shipping , please follow the log shipping prerequisites .

    1) check both  sql server agent services  must be same .

    2) shared folder should be access both ends either primary to DR , DR to primary and shared folder need to access specified account. 

    3) Check both server time whether its same or not 

    4)Finally check ls_backup , LS_copy and LS_restore time schedule

    Please refer  below link:

    @@http://msdn.microsoft.com/en-us/library/ms190640.aspx

    Wednesday, May 01, 2013 3:09 PM