Error 14420 Sql
Contents |
Powered by Microsoft® Translator Wikis - Page Details First published by Praveen Rayan D'sa When: 4 Dec 2013 4:00 AM Last revision by Praveen
The Log Shipping Secondary Database Is Out Of Sync
Rayan D'sa When: 30 Nov 2014 7:04 AM Revisions: 13 Comments: log shipping issues in sql server 2008 r2 10 Options Subscribe to Article (RSS) Share this Engage! Wiki Ninjas Blog (Announcements) Wiki Ninjas on
Troubleshooting Log Shipping Issues
Twitter TechNet Wiki Discussion Forum Can You Improve This Article? Positively! Click Sign In to add the tip, solution, correction or comment that will help other https://support.microsoft.com/en-us/kb/2006312 users.Report inappropriate content using these instructions. Wiki > TechNet Articles > Log Shipping False Error Message - 14420 Log Shipping False Error Message - 14420 Article History Log Shipping False Error Message - 14420 Table of Contents ProblemInvestigationSolution Problem We recently migrated our SQL Server 2008 R2 and SAN storage to the new infrastructure, http://social.technet.microsoft.com/wiki/contents/articles/21575.log-shipping-false-error-message-14420.aspx I have log shipping setup on few databases and to retain all jobs I restored MSDB database on new server, post migration I synchronized primary and secondary servers, enabled all log shipping related jobs and entire process was successful, but few hours later Primary Server started generating alerts, error 14420:“The log shipping primary database [ServerName].[DatabaseName] has backup threshold of 60 minutes and has not performed a backup log operation for 120 minutes.” Investigation I started my investigation with sp_readeerorlog, I found lots of error messages as below. To confirm my log shipping status I checked Log backup, log copy and log restore jobs and all were running successfully, my last log backup was 15 min ago and it wassuccessfullyrestored on secondary server. On Primary Server Secondary Server Now I am pretty sure there is no problem with log shipping, but why the server generating alerts, on further investigation using following query on Primary server. Select * from msdb.
Tag: Error: 14420 Severity: 16 State: 1 SQL Server Log Shipping Common Errors or Failures November 3, 2014 SQLServerF1 Leave a comment Log Shipping in SQL Server is a very old and popular feature most widely http://www.sqlserverf1.com/tag/error-14420-severity-16-state-1/ used to mostly enable disaster-recovery solution for the application databases. SQL Server Log shipping allows us to automatically send transaction log backups from a primary database on a primary server instance to one or more secondary http://www.sql-server-performance.com/forum/threads/log-shipping-generating-error-14420.17824/ databases on separate secondary server instances. The transaction log backups are applied to each of the secondary databases individually. An optional third server instance, known as the monitor server, records the history and status of log shipping backup and restore operations and, optionally, raises alerts if these operations fail to occur as scheduled. Below are some of the common errors which may be raised during setup or configuration of Logshipping Error((An entry for primary server , primary database does not exist on this secondary. Register the primary first. (Microsoft SQL Server, Error: 32023)) - This error can occur, if there are any incorrect changes to the logshipping sql server 2008 configuration. Example: if you changed the path of backup share and updated the new share details in Logshipping configuration window, it may not take it into affect for copy and restore jobs, in such cases, it is better to use T-SQL instead like below exec master.dbo.sp_change_log_shipping_secondary_primary @primary_server = LS_PrimaryServerName, @Backup_source_directory= 'BackupSharePath' @primary_database = DBName, @file_retention_period =14420 Error: 14412, Severity: 16 The destination database TestDB is already part of a log shipping plan. This database TestDB is already log shipping. Error: 14424, Severity: 16 The database TestDB is already involved in log shipping. - These errors occur if you try to add a database to logshipping configuration using sp_add_log_shipping_database stored Procedure. - A database can be part of only one logshipping configuration. Verify existing log shipping configuration and alter or remove existing setup if it is not required. - If logshipping is already removed, then there may be remnants of previous log shipping configuration, so you need to cleanup log shipping metadata. Error: 14420, Severity: 16, State: 1 The log shipping destination is out of sync by minutes. Error: 14420, Severity: 16, State: 1 The log shipping primary database has backup threshold of minutes and has not performed a backup log operation for minutes. Check agent log and logshipping monitor
error 14420 Discussion in 'SQL Server Log Shipping' started by wjwagman, Mar 9, 2006. wjwagman New Member Greetings, I am running SQL Server 2000 SP4. I have log shipping configured and it appears to be working. We see changes to the primary propagated to the standby. The monitor is on the standby server. However the monitor is showing out of sync and when I look at the sql server logs on the standby server the message pair The log shipping source (LOCAL).dbname has not been backed up for nnnn minutes Error: 14420, Severity 16, State:1 is generated once per minute and every 30 minutes, when the database is scheduled to be backed up the log indicates it was backed up. The Backup Delta, Copy Delta load delta are constantly incrementing rather than being reset to zero and the value for the copy delta is consistent with the number of minutes displayed in the above error. I have looked at KB articles 329133 and 810969. Based on KB article 329133 I guess it has something to do with my backup alert threshold. It is set to 90 minutes and 14420 is enabled. My backups are schduled every 30 minutes. KB article 810969 indicates that the workaround is to use windows authentication in the specify the log shipping monitor server information dialogue box, which I did. I am guessing these are merely informational messages but nevertheless, I don't understand what is happening and am hoping someone can explain it to me. Thanks. wjwagman, Mar 9, 2006 #2 satya Moderator May refer to the relevant topics: http://www.sql-server-performance.com/forum/topic.asp?TOPIC_ID=11421 http://www.sql-server-performance.com/forum/topic.asp?whichpage=-1&TOPIC_ID=5202&REPLY_ID=28629 Also refer to this Technet articlehttp://www.microsoft.com/technet/prodtechnol/sql/2000/reskit/part4/c1361.mspx on LS information and those errors. HTH Satya SKJ Contributing Editor & Forums Moderator http://www.SQL-Server-Performance.Com This posting is provided “AS IS†with no rights for the sake of knowledge sharing. satya, Mar 10, 2006 #2 (You must log in or sign up to reply here.) Share This Page Tweet Please click 'Forgot Your Password' to reset your password if this is your first