Migrating SQL Server 2012 To Azure Using Azure . - Microsoft

3y ago
45 Views
3 Downloads
1.18 MB
29 Pages
Last View : 1m ago
Last Download : 2m ago
Upload by : Macey Ridenour
Transcription

Migrating SQL Server 2012 toAzure Using Azure SiteRecovery (ASR)Migration of SQL Server 2012 to Azure using Azure Site Recovery (ASR)Microsoft Corp.1

MICROSOFT MAKES NO WARRANTIES, EXPRESS OR IMPLIED, IN THISDOCUMENT.Complying with all applicable copyright laws is the responsibility of the user. Withoutlimiting the rights under copyright, no part of this document may be reproduced, storedin or introduced into a retrieval system, or transmitted in any form or by any means(electronic, mechanical, photocopying, recording, or otherwise), or for any purpose,without the express written permission of Microsoft Corporation. Microsoft may havepatents, patent applications, trademarks, copyrights, or other intellectual property rightscovering subject matter in this document. Except as expressly provided in any writtenlicense agreement from Microsoft, our provision of this document does not give you anylicense to these patents, trademarks, copyrights, or other intellectual property. Thedescriptions of other companies’ products in this document, if any, are provided only asa convenience to you. Any such references should not be considered an endorsement orsupport by Microsoft. Microsoft cannot guarantee their accuracy, and the products maychange over time. Also, the descriptions are intended as brief highlights to aidunderstanding, rather than as thorough coverage. For authoritative descriptions of theseproducts, please consult their respective manufacturers. 2016 Microsoft Corporation.All rights reserved. Any use or distribution of these materials without expressauthorization of Microsoft Corp. is strictly prohibited. Microsoft and Windows are eitherregistered trademarks or trademarks of Microsoft Corporation in the United States and/orother countries. The names of actual companies and products mentioned herein may bethe trademarks of their respective owners.Migration of SQL Server 2012 to Azure using Azure Site Recovery (ASR)Microsoft Corp.2

Contents1.Introduction . 42.Target Audience . 43.Prerequisites . 44.Source Environment (on-premise) Setup . 55.Migrating SQL Server 2012 (Standalone) to Azure. 65.1. Deploy Mobility Services Agent & Replicate Workload to Azure . 65.2. Create a Recovery Plan for your workloads . 145.3. Initiate Failover & Validate Workload . 155.3.1. Test Failover . 155.3.2. Failover . 216.Next Steps . 287.Additional Resources . 288.Support . 29Migration of SQL Server 2012 to Azure using Azure Site Recovery (ASR)Microsoft Corp.3

1.IntroductionThis document is a detailed guide describing the steps for migrating on-premise SQLServer 2012 (Enterprise Edition) workloads to Microsoft Azure using Azure Site Recovery(ASR). It is only intended to be used as a reference guide by Managed Services Providers(MSPs) that are part of the MSP - Azure Cloud Migration Program. The goal is to helpMSPs familiarize themselves with the methodologies, processes and steps needed tomigrate on-premise SQL Server workloads by leveraging the capabilities of ASR servicesto migrate workloads to Azure.Although ASR was designed as a Business Continuity and Disaster Recovery (BCDR) tool,the same techniques can be applied for migrations because of its direct replicationcapabilities to Azure with minimal changes required to the on-premise infrastructure.Specifically, this document covers the migration of SQL Server 2012 (Enterprise Edition)to Azure.2.Target AudienceThis document is primarily intended for Azure Architects, Solution Specialists and SystemAdministrators who will be involved in the on-premise to Azure workload migrations. It isassumed that this audience understands the intricacies of Microsoft Azure and its coreservices and has deep insights into its customer’s on-premise workloads to successfullymigrate them to Azure. The document is NOT intended to be a primer or guide on SQLServer or ASR but rather a guide to migrating SQL Server workloads to Azure.3.PrerequisitesBefore we can get started with migrating SQL Server 2012 to Azure, all items listed belowmust be completed or complied with:1. The source Planning, Discovery, and Assessment (Business risk, Cloud SuitabilityEtc.) steps should be completed and the application/workload has been approved tobe migrated to Azure. 2. The Azure Network Planning should be completed. 3. The ASR Capacity Planning and source setup should be completed. Migration of SQL Server 2012 to Azure using Azure Site Recovery (ASR)Microsoft Corp.4

4. Typically, SQL Server installation will have a dependency on Active Directory (AD).Please ensure that your AD infrastructure is already migrated and/or availablein Azure.5. SQL Server Version(s) supported by ASR are: SQL Server 2014 Enterprise and Standard SQL Server 2012 Enterprise and Standard SQL Server 2008 R2 Enterprise and StandardPlease Note: This document showcases SQL Server 2012 (Enterprise Edition)version only. Other versions of supported SQL migrations will be similar, but itis recommended that partners understand the subtle differences to successfullymigrate to Azure.4.Source Environment (on-premise) SetupThis section covers the lab environment configuration that was used to test the migrationof a SQL Server 2012 Enterprise Server using ASR.1. We have a single Windows 2012 R2 Standard server (VM) running a local instance ofSQL Server.2. The Server is domain joined, has a Static IP address and DNS set to the on-premiseAD-DNS server.3. The SQL version is SQL Server 2012 Enterprise and the configuration mode is‘Standalone’ (Non-clustered and No High Availability(HA)).4. The VM has a single dynamic disk (VHD) attached with a base size of 100GB sharedacross the Operating System, SQL database(s) & Transactional logs.The document assumes that these migration procedures would be similar to othersupported versions of standalone SQL Server workloads, but have not been verified. It ishighly recommended that the Architects and System Administrators involved in themigration effort ensure that they are testing this in their version of the environment.Migration of SQL Server 2012 to Azure using Azure Site Recovery (ASR)Microsoft Corp.5

5.Migrating SQL Server 2012 (Standalone) to AzureMigrating an application to Azure is typically a phased approach that consists of thefollowing stages:I.II.III.Deploy Mobility Service Agent & Replicate the Workload: Using ASR, thesource workload is replicated to an Azure Recovery Vault. Once the initialreplication is complete, ASR constantly monitors the application in the source andreplicates the deltas to Azure on a regular basis.Test Failover: Once the initial replication is complete, a test failover will spin upAzure VMs and the application can be tested multiple times without affecting theproduction workload running in the source environment.Failover: After the application has been successfully tested and validated to yoursatisfaction using test failover process, you will initiate a failover of the applicationfrom the source to Azure and turn off the source VM(s).5.1.Deploy Mobility Services Agent & Replicate Workload toAzureThe first step in migrating SQL Server workloads to Azure is to Deploy the MobilityServices Agent and start replicating the workload using ASR. Once the initialreplication process is complete, ASR constantly monitors the application in the sourceand replicates the changes (deltas) to Azure as well. The section below shows the stepsto replicate SQL workload to Azure.1.Login to the Azure Portal. Under ‘All Resources’ search for the Recovery Vaultname, open it and click on Site Recovery.Note: This Recovery Vault should have been setup using the ASR Setup Guideprior to migrating workloads. Please refer to the ASR Setup Guide for moredetails.2.Click on Step 2: Replicate Application and then click on the Source blade toselect the below options and click OK. Source – On PremisesMigration of SQL Server 2012 to Azure using Azure Site Recovery (ASR)Microsoft Corp.6

Source location - Select the Configuration Server Machine type –oPhysical Machines – for migrating Physical or Hyper-V VM’soVirtual Machines – for migrating VMware VMs VCenter / VSphere Host – Select the VCenter host [Applies only if youselected virtual machines for Machine Type] Process Server – Select the Process server that you want to use forreplication. If you haven’t set up a separate or multiple process server(s), theconfiguration server will show up as defaultMigration of SQL Server 2012 to Azure using Azure Site Recovery (ASR)Microsoft Corp.7

3.Under Target choose the following properties and click OK: Subscription – The subscription to be used for migrations. Post Failover Resource Group – The Resource Group to be used forMigrations. (These should have been created as part of the migrationplanning process). Post Deployment failover model – Resource Manager. Storage Account – Choose the one(s) that were created for handlingmigrations during ASR Capacity Planning phase. Azure Network – Configure now for selected machines. Post Failover Azure Network - Choose the Azure VNET that was createdfor migrations during the Network planning phase. Subnet – Choose the correct subnet within the Azure VNET.Migration of SQL Server 2012 to Azure using Azure Site Recovery (ASR)Microsoft Corp.8

4.Based on the Machine Type chose earlier, the below section(s) will slightly change: If Machine Type Virtual Machines: In the Virtual Machines SelectVirtual Machines blade, select the SQL VM you want to migrate and clickOKMigration of SQL Server 2012 to Azure using Azure Site Recovery (ASR)Microsoft Corp.9

If Machine Type Physical Machines: In the Physical Machines SelectPhysical Machines blade, click on Physical Machine. Enter the ServerName, on-premise IP Address, select OS type and click OK. This willdiscover the on-premise server from and add it to the vault for protection.Continue this process to add more SQL servers to be replicated (ifrequired).5.Under Notifications you will see that the server is being discovered and if themobility services agent is NOT present, it will be installed on this server. Youcan always check the progress of this job under Your Recovery Vault Jobs SiteRecovery JobsMigration of SQL Server 2012 to Azure using Azure Site Recovery (ASR)Microsoft Corp.10

6.Once the job completes, you can see that newly discovered server in the AzurePortal.7.In Properties Configure Properties blade, either set default values or chooseproperties per VM. Account – Choose the appropriate account that has administrator rights tothe Servers being migrated Disks to replicate – From the dropdown, select the disks that you want toinclude in replication and uncheck the ones that are not required (Ex: Diskfor non-production (temp) data).8.In Replication settings Configure replication settings choose the appropriatepolicy and click OK with the default values. You can always modify the replication policy in Your Recovery Vault SiteRecovery Infrastructure Replication Policies (For VMware & PhysicalMigration of SQL Server 2012 to Azure using Azure Site Recovery (ASR)Microsoft Corp.11

Machines) Policy Name Edit Settings. Changes you apply will be usedfor machines that are already replicating as well as new machines.9.Now click on Enable Replication.Migration of SQL Server 2012 to Azure using Azure Site Recovery (ASR)Microsoft Corp.12

10. Track the replication progress by checking at Your Recovery Vault ReplicatedItems. Once the status of a Replicated Item (server) changes to Protected, itmeans the application/workload is ready for failover.Migration of SQL Server 2012 to Azure using Azure Site Recovery (ASR)Microsoft Corp.13

5.2.Create a Recovery Plan for your workloadsWe are now going to create a Recovery Plan in your Azure Vault. The usage ofRecovery Plans helps facilitate easier management and migration of multiple servers(that make your service/application) into Azure without having to deal with eachcomponent individually. Below are a couple of examples to provide additional contextand the steps below to create and configure a recovery plan.Examples: A Recovery Plan for ALL your SQL servers in your environment. This wayyou can migrate all SQL servers into Azure cutover at one. Enterprise applications are mostly multi-tier that are split into multipleServer roles. Like IIS Web applications are split into Web front end &back end database servers that can be included in the same recoveryplan &

Azure The first step in migrating SQL Server workloads to Azure is to Deploy the Mobility Services Agent and start replicating the workload using ASR. Once the initial replication process is complete, ASR constantly monitors the application in the source and replicates the changes (deltas) to Azure as well.

Related Documents:

Server 2005 , SQL Server 2008 , SQL Server 2008 R2 , SQL Server 2012 , SQL Server 2014 , SQL Server 2005 Express Edition , SQL Server 2008 Express SQL Server 2008 R2 Express , SQL Server 2012 Express , SQL Server 2014 Express .NET Framework 4.0, .NET Framework 2.0,

SQL Server 2005 SQL Server 2008 (New for V3.01) SQL Server 2008 R2 (New for V3.60) SQL Server 2012 (New for V3.80) SQL Server 2012 R2 (New for V3.95) SQL Server 2014 (New for V3.97) SQL Server 2016 (New for V3.98) SQL Server 2017 (New for V3.99) (Recommend Latest Service Pack) Note: SQL Server Express is supported for most situations. Contact .

MS SQL Server: MS SQL Server 2017, MS SQL Server 2016, MS SQL Server 2014, MS SQL Server 2012, MS SQL Server 2008 R2, 2008, 2008 (64 bit), 2008 Express, MS SQL Server 2005, 2005 (64 bit), 2005 Express, MS SQL Server 2000, 2000 (64 bit), 7.0 and mixed formats. To install the software, follow the steps: 1. Double-click Stellar Repair for MS SQL.exe.

4. To upgrade SQL Server 2008 SP3 Express to SQL Server 2012 SP2 Express, launch th e installer for SQL Server 2012 SP2 Express, and then follow the wizard. 5. Select the Upgrade from SQL Server 2005, SQL Server 2008 or SQL Server 2008R2 option under the Installation option. The Upgrade to SQL

Bitlocker Administration and Monitoring MBAM Anforderungen: Hardware: 4 CPUs 12 GB RAM 100 GB Disk OS: Windows Server 2008 R2 SP1 Windows Server 2012/R2 Windows Server 2016 SQL Server: SQL Server 2008 R2 SQL Server 2012 SP1 SQL Server 2012 SP2 SQL Server 2014 SQL Server 2014 SP1

4395 querying data with transact -sql (m20761) microsoft sql server 6552 querying microsoft sql server 2014 (m20461) microsoft sql server 1833 sql server performance tuning and optimization (m55144) microsoft sql server 4394 updating your skills to sql server 2016 (m10986) microsoft sql server

install the SQL Server Reporting Services 2019 or 2017 installation program. For more information, see Installing SQL Server Reporting Services for SQL Server 2019 and SQL Server 2017 To use the SQL Installer to install a full version of SQL Server software (for example, SQL Server 2019 Standard editio

Business Intelligence SQL Server 2012 as well as Standard Edition Servers and legacy Enterprise Edition Servers. How to license 1. License each individual server with a SQL server license 2. License each user or device accessing the server with a SQL Server CAL SQL Server 2012 CALs can be used to access any SQL Server database licensed per .