Migrate applications to Azure CSP using Azure Site

  • Slides: 35
Download presentation
Migrate applications to Azure CSP using Azure Site Recovery Cloud Solution Provider

Migrate applications to Azure CSP using Azure Site Recovery Cloud Solution Provider

Migrate Applications to Azure Key Considerations Plan the Azure infrastructure Plan Replicate Test Migrate

Migrate Applications to Azure Key Considerations Plan the Azure infrastructure Plan Replicate Test Migrate Replicate data to Azure Test applications in Azure before migration Reduce downtime of production workload during migration

Migrations offering for CSP Partner Assessment Portfolio Assessment, TCO Analysis, Security Requirements. Application Dependency

Migrations offering for CSP Partner Assessment Portfolio Assessment, TCO Analysis, Security Requirements. Application Dependency Mapping Migrate Create Azure environment. Replicate via ASR, POC, Integrate applications and networks, User Acceptance Manage Billing, Support, Monitoring…

Migration assessment

Migration assessment

Migration Assessment Migration planning assessment set out to answer three questions 1 What are

Migration Assessment Migration planning assessment set out to answer three questions 1 What are ripe targets for lift and shift to Azure Iaa. S? 2 What are the costs and configuration to run the targets on Azure? $ 3 What are the ripe targets for migration

ASR Readiness Report Validation against ~20 checks to see if the target is ready

ASR Readiness Report Validation against ~20 checks to see if the target is ready for ASR migration and divides outcome into Success/Warning/Critical. Provides workaround for the machines that are identified with “Warning” Example checks: Disk’s performance requirement failed but can be achieved by striping data across several disks. Work around: Use P 30 and migrate to RAID 0 after migration • General Disk Requirements • Windows OS Requirements • Hypervisor Requirements • Disk Space Requirements Download detailed • analysis . NET Version Requirements • Boot Software Requirements • Linux System Requirements

Azure Site Recovery Architecture

Azure Site Recovery Architecture

Migrate VMware and Physical Servers to Azure Config Server Process Server OMS Site Recovery

Migrate VMware and Physical Servers to Azure Config Server Process Server OMS Site Recovery Source: VMware VMs & Physical Servers Process Server Data Channel Configuration Server Microsoft Azure Mobility Service

Deployment Planning

Deployment Planning

Deployment Planning • Estimate network bandwidth required for initial and delta replication • Identify

Deployment Planning • Estimate network bandwidth required for initial and delta replication • Identify Azure storage type (standard or premium) required for virtual machines • Estimate the total number of standard and premium storage accounts that need to be provisioned • Estimate the total number of Configuration and Process Servers that need to be deployed while protecting VMware workloads • Virtual machine eligibility assessment based on number of disks, size of the disks and IOPS • Profile the actual churn on the source virtual machine without any impact to the production workload

Deployment Planner Recap It is recommended to https: //aka. ms/storageuse a three character performance-checklist

Deployment Planner Recap It is recommended to https: //aka. ms/storageuse a three character performance-checklist prefix for storage account names for performance and scalability optimization Naming convention https: //aka. ms/guidance-namingconventions https: //aka. ms/azure-storage. SQL Server workload scalbility-performance Other high performance workloads https: //aka. ms/azure-storagescalbility-performance Storage scalability and https: //aka. ms/azure-storageperformance scalbility-performance

Migrate VMware and Physical Servers to Azure Config Server Process Server OMS Site Recovery

Migrate VMware and Physical Servers to Azure Config Server Process Server OMS Site Recovery Source: VMware VMs & Physical Servers Process Server Data Channel Configuration Server Microsoft Azure Mobility Service

Deployment Steps 1 Prepare on-premises infrastructure 2 Replicate Application 3 Manage Recovery Plan Always

Deployment Steps 1 Prepare on-premises infrastructure 2 Replicate Application 3 Manage Recovery Plan Always perform a Test Failover to validate Perform Failover to recover application in Azure

Networking considerations : Optimizing replication Traffic • Process Server • Up to 10 Gbps

Networking considerations : Optimizing replication Traffic • Process Server • Up to 10 Gbps network • Riverbed

ASR with Express. Route Azure Public Services (Storage) Customer Datacenter Partner Edge Customer Connectivity

ASR with Express. Route Azure Public Services (Storage) Customer Datacenter Partner Edge Customer Connectivity Site Recovery replication traffic (Pubic Peering) Connectivity to Iaa. S Virtual Network post failover (Private Peering) Azure Edge Azure Compute

ASR with Riverbed Data Reduction Average: 72. 1% Peak: 99. 7% 3. 6 x

ASR with Riverbed Data Reduction Average: 72. 1% Peak: 99. 7% 3. 6 x capacity increase LAN Throughput Total: 95. 4 GB WAN Throughput Total: 26. 6 GB Source: Microsoft and Riverbed whitepaper: https: //gallery. technet. microsoft. com/Optimizing-Azure-Recovery-8 da 50893

Networking More details

Networking More details

Azure Support for Azure Platforms Classic and Azure Resource Manager (ARM) Storage Standard and

Azure Support for Azure Platforms Classic and Azure Resource Manager (ARM) Storage Standard and Premium Storage Encryption at rest Linux Distributions Red Hat Enterprise Linux Cent. OS Oracle Enterprise Linux SUSE Linux Enterprise Server For the latest list refer to the ASR support matrix.

Migrate Hyper-V to Azure Hyper-V Server Source: Hyper-V VMs Microsoft Azure Recovery Services Agent

Migrate Hyper-V to Azure Hyper-V Server Source: Hyper-V VMs Microsoft Azure Recovery Services Agent OMS Site Recovery Data Channel Microsoft Azure

Migration using Site recovery Value Props Migrate from multiple environments VMware, Hyper-V, physical, Azure

Migration using Site recovery Value Props Migrate from multiple environments VMware, Hyper-V, physical, Azure and Amazon Web Services Migrate any workloads Support for both Linux and Windows workloads No-impact migration testing When replicating workloads into Azure, execute tests to ensure readiness

Migration using Site recovery Value Props Move applications with near-zero downtime Move a single

Migration using Site recovery Value Props Move applications with near-zero downtime Move a single application or an entire datacenter to the cloud with minimal impact to production users No Licensing Fee No Site Recovery charges for Migration (first 31 days) HUB (Hybrid Use Benefit) Move Windows Server licenses covered under Software Assurance to Azure

HUB support through Power. Shell PS C: Usersbsiva> Login-Azure. Rm. Account Environment : Azure.

HUB support through Power. Shell PS C: Usersbsiva> Login-Azure. Rm. Account Environment : Azure. Cloud Account : bsiva@microsoft. com Tenant. Id : xxxx-xxxx-xxxxxxxx Subscription. Id : xxxx-xxxx-xxxxxxxx Subscription. Name : ASR PM team subscription 5 Current. Storage. Account : PS C: Usersbsiva> Select-Azure. Rm. Subscription -Subscription. Name "DR Hybrid Application Scenarios" Environment : Azure. Cloud Account : bsiva@microsoft. com Tenant. Id : xxxx-xxxx-xxxxxxxx Subscription. Id : xxxx-xxxx-xxxxxxxx Subscription. Name : DR Hybrid Application Scenarios Current. Storage. Account : PS C: Usersbsiva> $vault = Get-Azure. Rm. Recovery. Services. Vault -Name "Contoso-Recovery. Vault" PS C: Usersbsiva> Set-Azure. Rm. Site. Recovery. Vault. Settings -ARSVault $vault Resource. Name Resource. Group. Name Resource. Namespace Resouce. Type ------ ----------------- -----Contoso-Recovery. Vault Contoso-Recovery Microsoft. Recovery. Services vaults PS C: Usersbsiva> $fabrics = Get-Azure. Rm. Site. Recovery. Fabric PS C: Usersbsiva> $Protection. Container = Get-Azure. Rm. Site. Recovery. Protection. Container -Fabric $fabrics[0] PS C: Usersbsiva> $Protected. Item = Get-Azure. Rm. Site. Recovery. Replication. Protected. Item -Friendly. Name "Contoso-Eng. Wiki. DB" -Protection. Container $Protection. Container

HUB support through Power. Shell (contd. ) PS C: Usersbsiva> Set-Azure. Rm. Site. Recovery.

HUB support through Power. Shell (contd. ) PS C: Usersbsiva> Set-Azure. Rm. Site. Recovery. Replication. Protected. Item -Replication. Protected. Item $Protected. Item -License. Type Windows. Server Name : xxxx-xxxx-xxxxxxxx ID : /Subscriptions/xxxx-xxxx-xxxxxxxx/resource. Groups/Contoso-Recovery/providers/Microsoft. Recovery. Services/vaults/Contoso-Recovery. Vault/repl ication. Jobs/xxxx-xxxx-xxxxxxxx Type : Job. Type : Update. Vm. Properties Display. Name : Update the virtual machine Client. Request. Id : xxxx-xxxx-xxxxxxxx-2016 -10 -05 10: 20: 04 Z-P Activity. Id: xxxx-xxxx-xxxxxxxx State : In. Progress State. Description : In. Progress Start. Time : 10/5/2016 3: 50: 07 PM End. Time : Target. Object. Id : xxxx-xxxx-xxxxxxxx Target. Object. Type : Protection. Entity Target. Object. Name : Contoso-Eng. Wiki. DB Allowed. Actions : Tasks : {Update the virtual machine properties} Errors : {} PS C: Usersbsiva> Get-Azure. Rm. Site. Recovery. Job -Name "xxxx-xxxx-xxxxxxxx" Name : xxxx-xxxx-xxxxxxxx ID : /Subscriptions/xxxx-xxxx-xxxxxxxx/resource. Groups/Contoso-Recovery/providers/Microsoft. Recovery. Services/vaults/Contoso-Recovery. Vault/repl ication. Jobs/xxxx-xxxx-xxxxxxxx Type : Job. Type : Update. Vm. Properties Display. Name : Update the virtual machine Client. Request. Id : xxxx-xxxx-xxxxxxxx-2016 -10 -05 10: 20: 04 Z-P Activity. Id: xxxx-xxxx-xxxxxxxx State : Succeeded State. Description : Completed Start. Time : 10/5/2016 3: 50: 07 PM End. Time : 10/5/2016 3: 50: 12 PM Target. Object. Id : xxxx-xxxx-xxxxxxxx Target. Object. Type : Protection. Entity Target. Object. Name : Contoso-Eng. Wiki. DB Allowed. Actions : Tasks : {Update the virtual machine properties} Errors : {} PS C: Usersbsiva>

VMware UEFI Migration Azure does not support virtual machines running a UEFI / Generation

VMware UEFI Migration Azure does not support virtual machines running a UEFI / Generation 2 firmware. Site Recovery cannot directly migrate a virtual machine from VMware to Azure Iaa. S, when that virtual machine is using UEFI firmware Option 1: Convert the VMware VM from UEFI to BIOS firmware and use Site Recovery to migrate a BIOS virtual machine from VMware to Azure Iaa. S Option 2: Migrate the VMware VM from UEFI to a Generation 2 Hyper-V virtual machine and use Site Recovery to migrate the virtual machine from the Hyper-V host to Azure Iaa. S Option 3: Use an external vendor tool or manual process that can convert and migrate the virtual machines between formats in VMware and Azure Iaa. S

Application DR with ASR DR DB Tier ion h Orc rat est Azure Site

Application DR with ASR DR DB Tier ion h Orc rat est Azure Site Recovery DR Or ch est rat ion ASR Replication Azure Storage App Tier ASR Replication Web Tier Active Directory ASR Replication Primary Site Azure

Application DR with ASR DR DB Tier tion Azure Site Recovery Orc tra hes

Application DR with ASR DR DB Tier tion Azure Site Recovery Orc tra hes DR Or ch est rat ion Iaa. S VM SQL Availability Group App Tier ASR Replication Azure Storage AD & ASR Replication Iaa. S VM Web Tier Active Directory Primary Site Azure

Compliance and Certification Defend against Human Errors Protection from Malware and Ransomware Business continuing

Compliance and Certification Defend against Human Errors Protection from Malware and Ransomware Business continuing during regional outages

“Optimally protect your cloud data” • • • Linux SQL Server Premium Storage Virtual

“Optimally protect your cloud data” • • • Linux SQL Server Premium Storage Virtual Machines • • No backup infrastructure Self Service Backup/Restore Application consistent VHD and VM config backup Simplified Management and monitoring

Key Considerations Compliance DR drill restore application own business decisions no production impact

Key Considerations Compliance DR drill restore application own business decisions no production impact

Challenges with current approach High Operational cost Not all applications can support this High

Challenges with current approach High Operational cost Not all applications can support this High RTO No application consistency High operation Cost Only data replication – no application management

üNo DR infrastructure üAutomated protection and replication üBest in class RPO and RTO üNo-impact

üNo DR infrastructure üAutomated protection and replication üBest in class RPO and RTO üNo-impact DR Drill üOrchestrated recovery plans for application DR üFailback support

Next steps • Want to become a CSP partner? Join CSP today. • Want

Next steps • Want to become a CSP partner? Join CSP today. • Want to learn more about Azure in CSP? Read here.

© 2017 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are

© 2017 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U. S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.