Post reply

Log shipping from SQL Server 2017 to SQL Server 2012

  • December 27, 2019 at 4:56 am

    #3710636

    We have a primary server and seconday server both running SQL Server 2012 EE with log shipping configured. We are planning to move to SQL Server 2017 on a new physical primary server soon. Then at a later time we plan to move to SQL Server 2017 on our secondary server. This leads to two questions:

    1) Is it possible to log ship from a SQL Server 2017 database to a SQL Server 2012 database?

    2) Is it possible to restore a differiential backup file from the SQL Server 2012 Primary Database to the SQL Server 2017 database? Is it possible to restore the log backup files from the SQL Server 2012 Primary Database to the SQL Server 2017 database?

    Thanks in advance for any help provided.

     

  • December 27, 2019 at 12:20 pm

    #3710705

    1. No, we cannot downgrade.
    2.  Yes, you can from lower to higher version.

    Muthukkumaran Kaliyamoorthy
    https://www.sqlserverblogforum.com/

  • January 13, 2020 at 3:48 am

    #3714784

    1) Is it possible to log ship from a SQL Server 2017 database to a SQL Server 2012 database?

    No, you cannot restore a backup to a lower version. If you take the path of upgrading the primary, the secondary must be done at the same time.

    2) Is it possible to restore a differiential backup file from the SQL Server 2012 Primary Database to the SQL Server 2017 database? Is it possible to restore the log backup files from the SQL Server 2012 Primary Database to the SQL Server 2017 database?

    Yes, this is possible.

    What might be a better solution is to build your new 2017 servers (primary and secondary) and add them as log shipping secondaries to your 2012 primary. Then when you wish to cut over to 2017, the process would be:

    1. Recover the DB on your 2017 primary
    2. Point your application(s) at the 2017 primary.
    3. Remove log shipping configuration from both 2017 instances
    4. Configure log shipping from 2017 primary to 2017 secondary

    If at any point you need to rollback to using the 2012 primary, simply point your application(s) at the 2012 primary again. The databases should still be running like normal on your 2012 instances so getting the application back online would be that simple. there would obviously be cleanup tasks to reset the 2017 instances as secondaries to the 2012 primary for the next migration attempt, but this wouldn't impact end users once the app is pointing to 2012 again.

  • January 15, 2020 at 6:13 pm

    #3715733

    Is it possible to restore a differiential backup file from t http://rufushe SQL Server  http://uc browser2012 Primary Database to the SQL Server 2017 database? Is it possible to http://filezilla restore the log backup files from the SQL Server 2012 Primary Database to the SQL Server 2017 database?

    • This reply was modified 4 years, 3 months ago by  HATYRA.

  • January 15, 2020 at 10:49 pm

    #3715823

    HATYRA wrote:

    Is it possible to restore a differiential backup file from the SQL Server 2012 Primary Database to the SQL Server 2017 database?

    Is it possible to restore the log backup files from the SQL Server 2012 Primary Database to the SQL Server 2017 database?

    Yes to both. As long as the 2017 database has had the correct FULL backup restored for those DIFF and LOG backups and has been left in a RESTORING or STANDBY state.

Viewing 5 posts - 1 through 4 (of 4 total)

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