SQL Server Performance

manual copy transaction log

Discussion in 'SQL Server Log Shipping' started by fudiu, Apr 13, 2005.

  1. fudiu New Member

    If for certain reason, one transaction log backup is corrupted after copying from primary server to secondary server. the error "The log in this backup set begins at LSN 33000000022600001, which is too late to apply to the database. An earlier log backup that includes LSN 33000000011800001 can be restored." is prompted.<br /><br />Is it possible to manually copy the lost transaction log backup to secondary server to let the restore job proceeds?<br /><br />Thx [<img src='/community/emoticons/emotion-5.gif' alt=';)' />]<br />
  2. anilksharma99 New Member

    This should not be a corrupted tran log backup, rather the restore has come to an out of sync state. I guess you might need to restore the FULL backup and then start the tran log process again.
  3. satya Moderator

    True and in order to restart the log shipping process you must restore the full backup from primary server to secondary server.

    Check whether any network issues persisting while copying the file and also check the log shipping restore interval.

    Satya SKJ
    This posting is provided “AS IS” with no rights for the sake of knowledge sharing.

Share This Page