Bring Secondary Log Shipping DB online WITHOUT .TUF file

  • So if you have a database out of sync with its primary and you have lost the .TUF and old log files. Is there a way to fix log shipping? spend the last 20 mins looking for an answer, my plan was to bring the secondary online, then do a full restore of a new bkacup of the primary. But of course im running into the

    RESTORE database [myDB]

    WITH RECOVERY

    results in

    Msg 3013, Level 16, State 1, Line 1

    RESTORE DATABASE is terminating abnormally.

    Msg 3441, Level 17, State 1, Line 1

    During startup of warm standby database 'myDB' (database ID 13), its standby file ('X:\Logs\myDB_20140723080008.tuf') was inaccessible to the RESTORE statement. The operating system error was '2(error not found)'. Diagnose the operating system error, correct the problem, and retry startup.

    Im guessing the solution is remove log shipping and set it up again?

  • Yes, just set it up again from scratch. It's probably going to be quicker.

  • 🙁

    thought so.

    thanks for the quick reply..

  • don't ever delete the TUF file, this will require a re initialisation of the LS plan

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

    "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