Post reply

Log-Shipping Failed

  • September 6, 2012 at 9:05 pm

    #263828

    Hi,

    We have a log-shipping set up on the production server for reporting purpose.

    Unknowingly, I have set up a backup strategy which also includes trans-log backups.

    So, my log-shipping failed. (Restoration job on the second server failed.)

    Is there any way I can get back the secondary database on Server2.

    Secondary Database is in (StandBy mode/Readonly)

    Can anyone help me getting back my secondary server database back?

    (I will be getting a daily full back up at 12AM and Tran-log backup for every hour)

    Thankyou

  • September 7, 2012 at 1:53 am

    #1534908

    Follow these steps

    • stop all LS jobs for this database
    • take a differential backup on the primary
    • restore differential to the secondary
    • enable and start LS backup job on primary
    • enable and start LS copy job on secondary
    • enable and start LS restore job on secondary
    • check for success

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

    "Ya can't make an omelette without breaking just a few eggs" 😉

  • September 7, 2012 at 2:30 am

    #1534921

    Do you still have the full set of transaction log backups you took? If you do have a set of backups, between the manual ones and the ones that Log Shipping took, with the log sequence intact, you can manually restore them onto the secondary. Log shipping will then carry on as normal (but make sure you've disabled that extra log backup job!)

  • September 7, 2012 at 2:55 am

    #1534932

    HI, I already disabled all other backup jobs.

    though I have the tran-backup set, I think its all messed up now.

    I see only way is to diable the respective jobs and reset the log-shipping again by resoting the new full backup.

    Thanks

  • September 7, 2012 at 2:59 am

    #1534937

    rohaandba (9/7/2012)

    I see only way is to diable the respective jobs and reset the log-shipping again by resoting the new full backup.

    Thanks

    Did you even bother to read my post above???

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

    "Ya can't make an omelette without breaking just a few eggs" 😉

  • September 7, 2012 at 3:15 am

    #1534947

    rohaandba (9/7/2012)

    HI, I already disabled all other backup jobs.

    though I have the tran-backup set, I think its all messed up now.

    I see only way is to diable the respective jobs and reset the log-shipping again by resoting the new full backup.

    Thanks

    No, its not all messed up now! Did you read and digest either mine or Perry's posts; both of which will get you back on track?

    If you have the entire set of transaction log backups, at the most superficial level, sorting them into chronological order and restoring them (WITH NORECOVERY) will get you back to where you need to be. Alternatively you can follow Perry's suggestion which will work just as well.

    How can it be 'all messed up'? Its a logical thing; provided you have the full sequence of log backups, regardless of which job/process/person executed them, you can restore to a point where automated log-shipping can pick back up.

  • September 7, 2012 at 3:29 am

    #1534957

    MissTippsInOz (9/7/2012)

    rohaandba (9/7/2012)

    HI, I already disabled all other backup jobs.

    though I have the tran-backup set, I think its all messed up now.

    I see only way is to diable the respective jobs and reset the log-shipping again by resoting the new full backup.

    Thanks

    No, its not all messed up now! Did you read and digest either mine or Perry's posts; both of which will get you back on track?

    If you have the entire set of transaction log backups, at the most superficial level, sorting them into chronological order and restoring them (WITH NORECOVERY) will get you back to where you need to be. Alternatively you can follow Perry's suggestion which will work just as well.

    How can it be 'all messed up'? Its a logical thing; provided you have the full sequence of log backups, regardless of which job/process/person executed them, you can restore to a point where automated log-shipping can pick back up.

    To add to this and more importantly, ensure you stop any other log backup jobs on this database or you'll be back in the exact same situation!!!!!

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

    "Ya can't make an omelette without breaking just a few eggs" 😉

  • September 7, 2012 at 8:15 am

    #1535080

    Thanks Guys for your detail step by step guidance.

    It worked great. My secondary database is up now.

    I was panic, Thanks for all the help.

  • September 7, 2012 at 9:25 am

    #1535132

    rohaandba (9/7/2012)

    Thanks Guys for your detail step by step guidance.

    It worked great. My secondary database is up now.

    I was panic, Thanks for all the help.

    You were given two solutions which one did you follow???????

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

    "Ya can't make an omelette without breaking just a few eggs" 😉

  • September 7, 2012 at 10:41 am

    #1535173

    As suggested, I just followed your step by step process taking a differential backup and restoring on secondary.

    Thank You.

Viewing 10 posts - 1 through 9 (of 9 total)

You must be logged in to reply to this topic. Login to reply