SQL Server Performance

LogShip Error

Discussion in 'SQL Server 2005 Log Shipping' started by Fais, May 9, 2008.

  1. Fais New Member

    Hello Friends,
    I am seeing this error from the past two days .
    What exactly happened is when the full backup is taken at 10:00PM for the logshipped database 'A', all the log backup taken before 10:00 pm were successfully applied to the secondary database. But , the log backup taken by logshipping after 10:00 PM havent been applied by log shipping and it failed with the following error.
    *** Error: This log cannot be restored because a gap in the log chain was created. Use more recent data backups to bridge the gap.
    RESTORE LOG is terminating abnormally.(.Net SqlClient Data Provider) ***

    Note: The primary log shippned is also involved in replication. One of the member configured replication for this log shipped database a week ago.
    Anyone ideas.
  2. satya Moderator

    What kind of replication used on the primary server?
    The error clearly states that it is a mismatch of LSN due to the LOG TRUNCATION or NON LOGGED operations on the database which is involved in the log shipping.
  3. Fais New Member

    After deep investigation came to know that one of the member truncated the transaction log of the logshipped database, which caused this issue.
    Thanks for your help.

Share This Page