locked
Migrating Mirroring instance to new server. RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    We are migrating Principle and Mirror SQL servers to newer version (2008 to 2016). New server and hardware in place along with SQL server. Now, we are in process of migrating databases from old version to newer. Can anyone please help what are the steps required to migrate Principle and Mirror databases to latest servers?

    Old server : Server A (Principle) and Server B (Mirror)

    New server: Server C( Principle) and Server D(Mirror).

    Wednesday, April 29, 2020 6:05 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

     Hi Chickoo79,

    It seems your situation involves server upgrades and migration to other locations. You may need to consider acceptable downtime and then choose the order in which to perform the upgrade and migration. Or you have installed SQL Server 2016 on the new server. After migrating the SQL server on the old server to the new server then reconfigure the database Mirroring or Always On availability group.

    Best Regards,
    Cris

    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.

    • Marked as answer by Chickoo79 Thursday, April 30, 2020 2:06 PM
    Thursday, April 30, 2020 7:47 AM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    I assume you want to migrate  to Always ON am I right?

    https://techcommunity.microsoft.com/t5/sql-server/migration-guide-migrating-to-alwayson-availability-groups-from/ba-p/384100

    Best Regards,Uri Dimant SQL Server MVP, http://sqlblog.com/blogs/uri_dimant/

    MS SQL optimization: MS SQL Development and Optimization
    MS SQL Consulting: Large scale of database and data cleansing
    Remote DBA Services: Improves MS SQL Database Performance
    SQL Server Integration Services: Business Intelligence

    Thursday, April 30, 2020 4:26 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    You have a MS official document for this.

    Upgrading Mirrored Instances.

    I would suggest for AG since mirroring in later editions would not be supported

    Cheers,

    Shashank

    Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it

    My TechNet Wiki Articles
    MVP

    Thursday, April 30, 2020 7:07 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

     Hi Chickoo79,

    It seems your situation involves server upgrades and migration to other locations. You may need to consider acceptable downtime and then choose the order in which to perform the upgrade and migration. Or you have installed SQL Server 2016 on the new server. After migrating the SQL server on the old server to the new server then reconfigure the database Mirroring or Always On availability group.

    Best Regards,
    Cris

    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.

    • Marked as answer by Chickoo79 Thursday, April 30, 2020 2:06 PM
    Thursday, April 30, 2020 7:47 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Thanks all for your response. I suggested Always On but client preferred to have Mirror instance. So, we are migrating mirroring instance from 2008 R2 to 2016. I understand migrating of mirroring instance involve the steps as below. Correct me if i am wrong.

    1) Stop the application on old servers.

    2) Issue a full backup backup from Old Servers.

    2) Restore Full backup on new Principle instance.

    3) Issue a full and TX log backup from new Principle instance.

    4) Restore Full and TX log on Mirror instance with No Recovery option.

    5) Configure Database mirroring

    6) Make sure Database Mirroring has been started successfully and fully synchronized.

    Thursday, April 30, 2020 2:17 PM