In place 2012 to 2104 upgrade and log shipping

  • GOing to do in place upgrade from 2012 to 2014.  Currently have log shipping.  I believe it is supposed to survive the upgrade but was going to try following plan.

    1.Stop log shipping backup at 10 PM
    2.Restore last file backed up to read only node
    3.Upgrade primary server to 2014.
    4.upgrade read only node to 2014
    Start log shipping back up

  • tcronin 95651 - Monday, July 17, 2017 8:14 AM

    GOing to do in place upgrade from 2012 to 2014.  Currently have log shipping.  I believe it is supposed to survive the upgrade but was going to try following plan.

    1.Stop log shipping backup at 10 PM
    2.Restore last file backed up to read only node
    3.Upgrade primary server to 2014.
    4.upgrade read only node to 2014
    Start log shipping back up

    A) I have advised my clients against doing in-place upgrades since, well, forever.

    B) I am pretty sure that if you have Standby mode enabled on secondary this will fail.

    C) Even without that I would be prepared to redo your log shipping.

    Best,
    Kevin G. Boles
    SQL Server Consultant
    SQL MVP 2007-2012
    TheSQLGuru on googles mail service

  • not a choice with this one so will have to wing it.

  • tcronin 95651 - Monday, July 17, 2017 9:47 AM

    not a choice with this one so will have to wing it.

    Good luck. I sure hope this isn't a critical production system. That's a bad phrase to be using if it is. Should it be, I would most definitely be setting up a test environment to know for certain how it is going to play out.

    Best,
    Kevin G. Boles
    SQL Server Consultant
    SQL MVP 2007-2012
    TheSQLGuru on googles mail service

  • I'd be prepared to script out everything and ready to re-set Log Shipping.

    Make sure you have  backups of all logins and linked servers, as well as user dbs.

  • TheSQLGuru - Monday, July 17, 2017 11:34 AM

    I would most definitely be setting up a test environment to know for certain how it is going to play out.

    This, x100

    ------------------------------------------------------------------------------------------------Standing in the gap between Consultant and ContractorKevin3NFDallasDBAs.com/BlogWhy is my SQL Log File HUGE?!?![/url]The future of the DBA role...[/url]SQL Security Model in Plain English[/url]

  • tcronin 95651 - Monday, July 17, 2017 8:14 AM

    GOing to do in place upgrade from 2012 to 2014.  Currently have log shipping.  I believe it is supposed to survive the upgrade but was going to try following plan.

    1.Stop log shipping backup at 10 PM
    2.Restore last file backed up to read only node
    3.Upgrade primary server to 2014.
    4.upgrade read only node to 2014
    Start log shipping back up

    Use rolling upgrades, Sequence should be

    • Stop log shipping backup on primary at 10 PM
    • stop copy and restore jobs on secondary(s)
    • manually run copy then restore jobs on secondary(s), which will restore any remaining backups up to secondary node(s)
    • switch secondary(s) to restoring mode
    • upgrade secondary node(s) to 2014
    • Upgrade primary server to 2014
    • switch secondary(s) to read only mode
    • Start log shipping jobs up

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

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

Viewing 7 posts - 1 through 6 (of 6 total)

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