Post reply

Logshipping secondary server is out of sync and LSRestore job failing

  • June 3, 2015 at 11:40 pm

    #297440

    I checked the server and found that LS restore job failing and Backup and copy jobs running fine without any issue. and also observed that Copy folder the trn file existing on secondary server. i try to restore trn file im getting the error. and observed that last log backup file that it restored at the secondary database on May2nd,2015.

    Can anyone help me and give me suggestions please? its urgent.

    2015-06-02 12:25:00.72*** Error: The log in this backup set begins at LSN 761571000000022500001, which is too recent to apply to the database. An earlier log backup that includes LSN 721381000002384200001 can be restored.

    From Restore job histort details below.

    Message

    2015-06-02 12:25:00.72*** Error: The file '\\xx\xx\_20150530104503.trn' is too recent to apply to the secondary database 'database'.(Microsoft.SqlServer.Management.LogShipping) ***

    2015-06-02 12:25:00.72*** Error: The log in this backup set begins at LSN 761571000000022500001, which is too recent to apply to the database. An earlier log backup that includes LSN 721381000002384200001 can be restored.

    RESTORE LOG is terminating abnormally.(.Net SqlClient Data Provider) ***

    2015-06-02 12:25:00.73Searching for an older log backup file. Secondary Database: 'database'

    2015-06-02 12:25:00.73*** Error: Could not find a log backup file that could be applied to secondary database 'database'.(Microsoft.SqlServer.Management.LogShipping) ***

    2015-06-02 12:25:00.74Deleting old log backup files. Primary Database: 'database'

    Thanks in advance!!

    Thanks & Regards,

    DBA

    SQL server DBA

  • June 4, 2015 at 1:02 am

    #1802888

    Unless you have the log backups back to May 2nd 2015 then you'll need to restore a new full backup.

  • June 4, 2015 at 3:35 am

    #1802921

    See if this will help: http://www.brentozar.com/archive/2014/09/log-shipping-magic-using-differential-backup-delayed-secondary/

  • June 4, 2015 at 5:09 am

    #1802940

    Database admin(DBA) (6/3/2015)

    I checked the server and found that LS restore job failing and Backup and copy jobs running fine without any issue. and also observed that Copy folder the trn file existing on secondary server. i try to restore trn file im getting the error. and observed that last log backup file that it restored at the secondary database on May2nd,2015.

    Can anyone help me and give me suggestions please? its urgent.

    2015-06-02 12:25:00.72*** Error: The log in this backup set begins at LSN 761571000000022500001, which is too recent to apply to the database. An earlier log backup that includes LSN 721381000002384200001 can be restored.

    From Restore job histort details below.

    Message

    2015-06-02 12:25:00.72*** Error: The file '\\xx\xx\_20150530104503.trn' is too recent to apply to the secondary database 'database'.(Microsoft.SqlServer.Management.LogShipping) ***

    2015-06-02 12:25:00.72*** Error: The log in this backup set begins at LSN 761571000000022500001, which is too recent to apply to the database. An earlier log backup that includes LSN 721381000002384200001 can be restored.

    RESTORE LOG is terminating abnormally.(.Net SqlClient Data Provider) ***

    2015-06-02 12:25:00.73Searching for an older log backup file. Secondary Database: 'database'

    2015-06-02 12:25:00.73*** Error: Could not find a log backup file that could be applied to secondary database 'database'.(Microsoft.SqlServer.Management.LogShipping) ***

    2015-06-02 12:25:00.74Deleting old log backup files. Primary Database: 'database'

    Thanks in advance!!

    Thanks & Regards,

    DBA

    Check whether a full backup has occurred on the primary since the LS plan started failing, do that using this query against the primary and then the secondary

    select DB_NAME(database_id), differential_base_lsn, differential_base_time

    from sys.master_files

    where database_id = db_id('SQL_Overview') and type_desc = 'ROWS'

    group by DB_NAME(database_id), differential_base_lsn, differential_base_time

    if the base LSNs match then take a differential backup on the primary and restore it to the secondary.

    If they don't match then a full re initialisation will be needed

    Also inspect the restore job to find out why the LS plan broke in the first place

    -----------------------------------------------------------------------------------------------------------

    "Ya can't make an omelette without breaking just a few eggs" 😉

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply