locked
Recommended ways from On-Premise to Azure Migration for VM RRS feed

  • Question

  • What would be the recommended migration approach suggested for scenarios below

    (for each scenario, assuming that it contains SQL Server installed and entire box needs to be migrated on Azure so SQL Azure is not an option)

    1. On premise physical server hosting SQL Server instance.

    2. On premise virtual machine hosting SQL Servers instance.

    3. On premise virtual machine hosting SQL Servers with clustered configurations.

    I am aware that Azure site recovery could be an option however just was curious to post these machines as .vhd files, is it a mandate to generalize VMs before posting to Azure? If VM is generalized then what would happen to SQL users?


    Bhushan | Blog | LinkedIn | Twitter

    Thursday, August 11, 2016 5:57 PM

Answers

  • Hello Bhushan,

    Thank you for posting on the Azure forums!

    Below are the different migration options which you can look at which do not include migrating to Azure SQL or using Azure Site recovery but deals with migrating your SQL database from on-premise to an Azure VM.

    1- Use the Deploy a SQL Server Database to a Microsoft Azure VM wizard

    2- Perform on-premises backup using compression and manually copy the backup file into the Azure virtual machine
    3- Perform a backup to URL and restore into the Azure virtual machine from the URL
    4- Detach and then copy the data and log files to Azure blob storage and then attach to SQL Server in Azure VM from URL
    5- Convert on-premises physical machine to Hyper-V VHD, upload to Azure Blob storage, and then deploy as new VM using uploaded VHD
    6- Ship hard drive using Windows Import/Export Service
    7- If you have an AlwaysOn deployment on-premises, use the Add Azure Replica Wizard to create a replica in Azure and then failover, pointing users to the Azure database instance
    8- Use SQL Server transactional replication to configure the Azure SQL Server instance as a subscriber and then disable replication, pointing users to the Azure database instance.

    Please refer Migrate a SQL Server database to SQL Server in an Azure VM for a detailed explanation on the recommended migration methods.

    As you mentioned above the 5th option would suffice as well. Since this included migration of the entire database into a vhd file which is uploaded into Azure Storage, I don't think it should make any changes to the arrangement of data or the schema for your SQL database.

    Let me know if this helps.

    Regards,

    Loydon

    ________________________________________________________________________________________________________________
    When you see answers and helpful posts, please click Vote As Helpful, Propose As Answer, and/or Mark As Answer so that other customers can benefit from it.

    Friday, August 12, 2016 10:32 AM