locked
log shipping got broken RRS feed

  • Question

  • Good Morning Experts, a quick question:

    I have log shipping set up. Junior dba took log backups and now log shipping got broken. How to fix this?


    Kiran

    Tuesday, November 6, 2018 12:09 AM

Answers

  • Hi,

    The manual log backup has caused a gap in the log chain. That's why log shipping got broken. The document will help you get a history of transaction log backup taken against the source database for all activity after that last applied backup. And you can restore all the log backups to the latest one against the target instance.If all these are done, you can re-enable the log shipping jobs on both servers.

    If you can't find the missing log backup, or the backup file is corrupted, then you'll have to reinitialise log shipping from a full backup.


    Best Regards
    Puzzle
    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com


    • Edited by Puzzle_Chen Tuesday, November 6, 2018 8:28 AM
    • Marked as answer by juniorkiran Friday, November 9, 2018 2:17 PM
    Tuesday, November 6, 2018 7:44 AM
  • disable all the JOb

    take a differentail backup followed with tran log bakcup

    copy to destination server secondary server

    resore them

    enable all job


    Ramesh Babu Vavilla MCTS,MSBI

    • Proposed as answer by Puzzle_Chen Friday, November 9, 2018 7:07 AM
    • Marked as answer by juniorkiran Saturday, December 22, 2018 11:44 PM
    Tuesday, November 6, 2018 4:35 PM

All replies

  • Hi Kiran,

    According to your description, my understanding is that log shipping broken due to log backup. If anything is misunderstood, please tell me.

    While you can perform any type of database backup without affecting the log chain, a transaction log backup outside of log shipping will cause a gap in the log chain. If you have any log backup job, please disable it. You can restart log shipping to fix this. Please refer to the documents from How to Restart Failed Log Shipping Quickly

    Best Regards
    Puzzle
    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com

    • Proposed as answer by Puzzle_Chen Friday, November 9, 2018 7:07 AM
    Tuesday, November 6, 2018 1:37 AM
  • The junior dba took manual log backups and log shipping got broken.

    Kiran

    Tuesday, November 6, 2018 7:05 AM
  • Puzzle,

    I did not understand the document. Could you please explain me in simple way. The junior dba took manual log backups and log shipping got broken.


    Kiran

    Tuesday, November 6, 2018 7:20 AM
  • Hi,

    The manual log backup has caused a gap in the log chain. That's why log shipping got broken. The document will help you get a history of transaction log backup taken against the source database for all activity after that last applied backup. And you can restore all the log backups to the latest one against the target instance.If all these are done, you can re-enable the log shipping jobs on both servers.

    If you can't find the missing log backup, or the backup file is corrupted, then you'll have to reinitialise log shipping from a full backup.


    Best Regards
    Puzzle
    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com


    • Edited by Puzzle_Chen Tuesday, November 6, 2018 8:28 AM
    • Marked as answer by juniorkiran Friday, November 9, 2018 2:17 PM
    Tuesday, November 6, 2018 7:44 AM
  • disable all the JOb

    take a differentail backup followed with tran log bakcup

    copy to destination server secondary server

    resore them

    enable all job


    Ramesh Babu Vavilla MCTS,MSBI

    • Proposed as answer by Puzzle_Chen Friday, November 9, 2018 7:07 AM
    • Marked as answer by juniorkiran Saturday, December 22, 2018 11:44 PM
    Tuesday, November 6, 2018 4:35 PM
  • Hi,

    Have you solved your problem? We’d suggest you mark the replies above as answers, so that it will be easier for other community members to find the useful ones.


    Best Regards
    Puzzle
    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com

    Friday, November 9, 2018 7:08 AM