SQL Server Performance

help with log shipping tuf file

Discussion in 'SQL Server 2005 Log Shipping' started by avipenina, Nov 10, 2007.

  1. avipenina New Member

    Hi,
    i setup Log Shipping in my test environment.
    the log shipping works great, until i did some test.
    i did transaction backup of the log shipping database to different folder on the source server.
    now i see on the destination server in the folder where all the trn backup stays a file that the suffix is not trn but tuf,and i see that no restore happens at all.
    why is that?
    if i do log shipping and i mistake do log backup does it mean the the log shipping is broken and cannot be fixed?
    Thx
  2. satya Moderator

    Once you restore the full backup from Primary to secondary then continue loading the transaction logs in regular intervals without any interruption. There is no need to perform full backup again, as the Tlog backups are taking care of transactions on the database.

    The .tuf file is the Transaction Undo File, and is created when performing log shipping to a server in Standby mode.

Share This Page