Shulou(Shulou.com)05/31 Report--

Today, I would like to talk to you about how to solve the problem of logshipping 14421. Many people may not know much about it. In order to make you understand better, the editor has summarized the following contents for you. I hope you can get something from this article.

1. Error message description Error: 14421:Server: The log shipping secondary database BOOK01\ sk.newshu has restore threshold of 45 minutes and is out of sync. No restore was performed for 48 minutes. Restored latency is 0 minutes. Check agent log and logshipping monitor information.

2. description of the phenomenon:

This message indicates that log shipping is out of sync when the restore threshold is exceeded. The restore threshold is the number of minutes allowed to wait between restore operations before generating a message.

3. Possible reasons:

This message does not necessarily indicate that there is a problem with log shipping. This message may indicate the following problems:

The restore job did not run.

Possible reasons for jobs not running include the SQL Server Agent service on the secondary server instance is not running, the job is disabled, or the job schedule has changed.

The restore job failed.

Possible reasons for job failure include invalid restore folder path, full disk, mismatch between the information of the monitoring server and the secondary or primary library, or any other reason that may cause the RESTORE statement to fail.

4. Problem solving:

First query the relevant views to verify

Query select * from log_shipping_monitor_primary on the main database

Query select * from log_shipping_monitor_secondary on the auxiliary library

You can view the information of last_copy_date and last_restored_date, and if it is found that it is not updated, it is really due to the fact that the information is not synchronized.

There is also a stored procedure that can synchronize the information of the monitoring server and the secondary server (primary service), which is sp_refresh_log_shipping_monitor, but I did not run it successfully.

Finally, after reconfiguring the log retransmission of the library and monitoring the server, the problem is solved.

5. Think:

To configure monitoring log shipping, you must add a monitoring server when log shipping is enabled. If you add a monitoring server later, you must first delete the log shipping configuration and then replace it with a new configuration that contains the monitoring server.

Other analytical data:

Ensure that the SQL Server agent service for the secondary server instance is running, while enabling the restore job for the secondary database and scheduling it to run at the appropriate frequency.

The restore job on the secondary server may fail. In this case, look at the job history of the restore job to find out why.

Log shipping restore jobs running on the secondary server instance may not be able to connect to the monitoring server instance to update the log_shipping_monitor_secondary table. This may be caused by authentication problems between the monitoring server instance and the secondary server instance.

The backup alert threshold may contain the wrong value. Ideally, set this value to at least three times the frequency of the restore job. If you change the frequency of restore jobs after you configure log shipping and make it work, you must update the value of the backup alert threshold accordingly.

When the monitoring server instance is offline and back online, the log_shipping_monitor_secondary table is not updated with the current value until the alert message job runs. Error 14421 may be raised when the restore job is successful but displays the message "No log backup files that can be applied to the secondary database". When this occurs, the restore time is not updated. In this case, the cause of the error may be a problem with the replication job.

To update the watch table with the latest data from the secondary database, run sp_refresh_log_shipping_monitor on the secondary server instance.

The date or time is incorrect on the secondary server instance or the monitoring server instance. This may also generate alert messages. The system date or time may have been modified on one of the server instances.

Note: the different time zones of the two server instances do not cause problems.

After reading the above, do you have any further understanding of how to solve the logshipping 14421 problem? If you want to know more knowledge or related content, please follow the industry information channel, thank you for your support.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.