• Call us: +1 (800) 622-0083
  • FIX: Log shipping failed due to broken/ damaged tansaction log backup

/
    • FIX: Log shipping failed due to broken/ damaged tansaction log backup.

       
      Log shipping has failed due to incomplete/ damaged transaction log backup.
      This issue occurred also when there is lack of free space on drive where backups are placed???(no logical explanation).

      For some reason transaction log backup was saved with errors (damaged) and then transfered to the destination server. 
      Result is - log shipping has failed.

      I've prepared a 6 step guide how to repair log shipping:

       
      1. Create Full Backup of source database (mine was placed '\\sharedstorage\XYZ\XYZ_backup.bak')
      2. Disable Restore and copy jobs on destination server.
      3. Restore database with:
       
      restore database XYZ from disk ='\\sharedstorage\XYZ\XYZ_backup.bak'
      with replace, norecovery;
       
      1. If destination database should be in standby mode go to step 5; else go to step 6
       
      1. Restore next transaction log backup and set database to standby (transaction log backups are working on source):
      restore log XYZ from disk ='\\sharedstorage\XYZ\XYZ_.trn'
      with standby= 'F:\Microsoft SQL Server\MSSQL.1\MSSQL\Backup\UNDO_standby_file.BAK'
       
      *note if full backup takes too long or is old and we are trying to restore transaction log backup which is not the correct one error will be generated. If backup is older error will be transaction log xxxx is to early. And if backup is newer the error will be transaction log is too recent.
       
      1. Enable Restore and copy jobs on destination server.
      2. Done.