Building disaster-recovery solution using Azure Site Recovery (ASR) for VMware & Physical Servers (Part 2)

Transcription

1

2 Building disaster-recovery solution using Azure Site Recovery (ASR) for VMware & Physical Servers (Part 2) KR Kandavel Technical Solutions Professional Asia Azure Site Recovery Specialist Team Microsoft Corporation

3 Azure Site Recovery use case scenarios for DR (Part 1) 1. On-premise to On-premise DR (for Hyper-V and Virtual Machine Manager) 2. On-premise to On-premise DR (for Hyper-V, Virtual Machine Manager and SAN) 3. On-premise to Azure DR (for Hyper-V, and Virtual Machine Manager) 4. On-premise to Azure DR (for Hyper-V) Azure Site Recovery use case scenarios for DR (Part 2) 5. On-premise to On-premise DR (for VMware and Physical Servers) 6. On-premise to Service Provider DR (for VMware and Physical Servers) 7. On-premise to Azure DR (for VMware and Physical Servers) 8. On-premise to Azure Migration (for VMware, Hyper-V and Physical Servers) 9. Azure Site Recovery - FAQ, Pricing & Licensing Wrap up

4 Replication Replication SAN SAN Replication Hyper-V Hyper-V to Hyper-V (on-premises) Hyper-V Hyper-V Hyper-V to Hyper-V (on-premises) Hyper-V Hyper-V Microsoft Azure Hyper-V to Microsoft Azure Replication Replication VMware or physical VMware or physical to VMware (on-premises) VMware Microsoft VMware or physical Azure VMware or physical to Microsoft Azure

5 DR Scenario 5: On-premise to On-premise DR for VMware and Physical Servers

6 Microsoft Azure Site Recovery Download InMage Scout InMage Scout Replication and orchestration channel: InMage Replication InMage Scout VMware/ Physical Primary site Recovery site VMware

7

8 Download InMage Scout Microsoft Azure Site Recovery Download InMage Scout Source: VMware vsphere VMs and physical servers Contoso primary location (On-premises or service provider) Process Server InMage Scout data channel Config Server Master Target Target: VMware vsphere VMs Contoso secondary location (On-premises or service provider) Process Server Used for caching, compression and encryption Config Server Used for centralized management of InMage Scout Master Target Used as a repository and for retention

9 Primary Site Scout Roles (PS & UA) Servers (Physical/VM) Mobility Agent Discovery of production server OS & configuration (physical & virtual) Continuous capture of changing data blocks (CDP) Continuous transfer of captured blocks to Process Server cache Application detection and Server In-line compression of incoming CDP data on behalf of production servers Caching of compressed CDP data and resiliency to WAN outages or QoS problems Bandwidth throttling of replication traffic to a Master Target Encryption of replication traffic Capture of each production server & volume level change rate status

10 DR Site Scout Roles (CS & MT) Server Replication and recovery policies stored in its DB Web-based UI with extensive graphs, reports, and UI/ /SNMP alerts User management Management dashboard, monitoring pie-charts, real-time granular RPO Target VMWare VM Downloading data from Process Server and writing to DR VM disks for multiple prod servers (on behalf of all the powered off DR VMs) Copying older data from DR VM disks into a journal to allow pointin-time recovery Cataloguing the application consistency and recovery points Virtual snapshots to allow file and folder recovery at any point in time Recovery and cloning of DR VMs for failover as well as DR drills N-tier application recovery Inter application recovery sequencing Network adaptation of DR VMs to the recovery IP subnet/vlan

11 Primary server discovery: Administrator provides details of vsphere environment, with or without vcenter and select VMs and their disks, for protection. Provide target vsphere information, select a particular Process Server, retention values and target datastore on the secondary site. Advanced replication settings: Granular replication controls for retention, folder structure, compression, encryption, resource pools and provisioning. Rich monitoring: Deep insight into protection of the infrastructure, including protected workloads, and InMage component health. Detailed views of protection, including RPO, recovery windows, and consistency points.

12 Simple recovery wizard: Select VMs that have been protected, and select the recovery point. This could be the latest consistent point, the very latest crash consistent point, or an older point. Then perform a readiness check to ensure VM can be recovered successfully. VM configuration: If needed, modify VM settings, such as adding CPUs, memory, or changing network configuration. Orchestrated recovery: Granular options to ensure VMs start in a particular Recovery Order. Recovery can be triggered now, or set for later. Multiple VMs can be recovered in batches.

13 Scout Primary Server Discovery

14 Scout Replication Settings

15 Scout Replication Advanced Settings

16 Scout Monitoring Protected Servers

17 Scout VM Recovery

18 Scout VM and Network Configuration

19 Scout VM Recovery Sequencing

20 InMage Scout - OS & application support Windows (32/64-bit) 2003 & variations (releases/sps) 2008 & variations 2008 R2 & variations R2 Linux (32/64-bit) RHEL 4.x, 5.x, 6.x CentOS 4.x, 5.x, 6.x OEL 5.x, 6.x SLES 10x, 11x Supported popular applications: MS stack Exchange, SQL Server, File Server, SharePoint, Dynamics NAV DBs Oracle, MySQL, DB2 All other apps are supported via a combination of File System (FS) consistency on Windows/Linux and application native consistency mechanisms if any exist (for example, a custom application could use ext3 FS to store its files and have hot backup APIs which can be used to provide application level consistency).

21 Demo On-premise to On-premise DR for VMware and Physical Server

22

23 Source: VMware vsphere VMs and physical servers Contoso primary location (On-premises or service provider) Source: VMware vsphere VMs and physical servers Fabrikam primary location (On-premises or service provider) Process Server Used for caching, compression and encryption Process Server Process Server Config Server Used for centralized management of InMage Scout Microsoft Azure Site Recovery InMage Scout data channel Config Server Master Target Config Server Master Target Master Target Used as a repository and for retention Contoso Fabrikam Orchestration Orchestration Hosting Service Provider RX Server RX Server Used for multi-tenant management in Azure

24

25 Microsoft Azure Site Recovery Microsoft Azure Site Recovery Download InMage Scout Replication channel: InMage Scout Orchestration and replication InMage Scout 2015 VMware Physical Primary site Recovery site VMware Primary site VMware Physical

26 Source: VMware vsphere VMs and physical servers Contoso primary location (On-premises or service provider) Process Server Microsoft Azure Site Recovery Config Server Master Target Contoso Orchestration Source: VMware vsphere VMs and physical servers Fabrikam primary location (On-premises or service provider) Process Server InMage Scout data channel Config Server Master Target Fabrikam Azure Site Recovery Orchestration Microsoft Azure Process Server Used for caching, compression and encryption Config Server Used for centralized management of InMage Scout Master Target Used as a repository and for retention RX Server Used for multi-tenant management in Azure

27

28

29 MA migrates Windows Physical, Virtual and AWS workloads into Azure, irrespective of underlying hardware and storage MA provides a web based portal with 3 levels of tenancy for self-service and SI partner driven migrations MMA performs guest level application discovery and enforces consistency across all VMs in a multi-tier application MMA performs end-to-end Recovery Orchestration such as network and endpoint adaptation and recovery sequencing

30 Sign-Up Preview announced via Azure homepage, Blogs Accept Preview Terms on landing page Request for MMA Portal Sign-Up, bits & documentation access Subscribe Get an Azure Subscription Bandwidth S2S VPN or NAT IP for Cloud Gateway Sign-up response e- mail with follow up instructions Provision Download S/W and set up 2 Management VMs in Azure Subscription Download S/W and set up 1 Management VM on-premise

31 Physical, Virtual, AWS Application Discovery (SharePoint) Windows 2008 R2 and above Discover Protect Select Azure Subscription Replication Settings Map Storage Account Select Servers and Recovery Order VM and Network Settings Specify End Points Cut-over

32 VMware Physical Other Compute Storage Networks Process Server Master Target Config. Server MMA Multi-tenant Portal VMware Physical Other Master Target Config. Server Compute Storage Networks Process Server Microsoft Azure

33

34 Yes. ASR converts VHDX to VHD for failover. On failback, VM continues to use VHDX. The OS partition has to be less than 127G. Azure supports 32 data disks each of up to 1TB. So about 31 TB VM can be supported. ASR supports all the Operating systems supported in Azure, which includes most flavors of Windows and Linux

35 What about network bandwidth? ASR supports working with WAN Optimizer Riverbed as well as Express route. Import Export integration coming in CY15. Yes you can use the network throttling on the host MARS (Microsoft Azure Recovery Services) agent to control how much network bandwidth is used for replication. Yes. You can use Express Route to send your replication traffic in a secure and fast manner. However its not mandatory. See here Its not mandatory to have S2S VPN we work over simple internet connectivity also. However if you have S2S we also work with that. A detailed blog on DR to Azure networking is available here How do you connect to VMs post failover to Azure? You should enable RDP for your VMs On Premises. Then post failover if you have a S2S VPN connection you can connect to them in the same way. Or if you want to access them over internet we have a script available with ASR integration with Azure automation to enable RDP endpoint.

36 Yes. Using ASR Azure Automation integration uses PowerShell scripting Yes. Using Site to Site VPN you can connect failed over Application in Azure back to On-Premise components. ASR is designed for Public Cloud DR. Therefore in steady state we replicate changes to storage with no running VMs and no charges for any Azure IAAS VMs. On failover ASR automatically creates IAAS VMs and IAAS charges are made only for the period VMs run in Azure. Please set your SAN Policy as ON inside Guest On Premise and then Azure will retain the drive letters. See here

37 What Recovery Time Objective (RTO) ASR supports? ASR supports minutes of RTO which is industry standard. Actual failover time depends on type of VMs. Best way to measure is run TFO and use ASR Job reports to view where time is spent as ASR provides time taken for each activity. What Recovery Point Objective (RPO) ASR supports? ASR supports near sync RPO for Azure target. Actual RPO depends upon the data change rate and available bandwidth to send this data to Azure. Yes you can failback to on-premises. Is there a tool to help me plan capacity Yes we have an excel sheet as well as Capacity Planner tool. As a customer you can protect hundreds/thousands of VMs for DR to Azure. However within a recovery plan we support a maximum of 50 VMs. As customers use Recovery plans for Applications and have different recovery plans for different applications. Each Azure subscription comes with a set of limits on cores etc. Use TFOs to validate if you need to increase the default values.

38

39

40 * Prices are Level A, annual ** At recovery, Azure IaaS capacity is guaranteed to be available at Azure datacenter of customer s choice. Customer will pay for actual IaaS usage separately if VM running in Azure. InMage Scout is included with the ASR per VM license starting August 1, 2014 ASR is sold per number of VMs protected depending on the recovery site destination: Included capabilities: Orchestrati on Replication to Azure (100GB/VM included) Guaranteed IaaS Availability EA Level A Recover to customer site Replicate and recover to an on-premises secondary site or a hoster site. $140 / VM Recover to Azure Replicate and recover to Azure as the recovery site. $475 / VM

41 1. Azure Site Recovery: 1 VM or 2. Azure Backup: 100GB $475 or $140 $248 New! $388 Promo ASR 1VM (1 year) + 100GB Azure Backup (1 year) Includes access to InMage Scout What the annual subscription promo means Two ways to frame for customers: Compared to the replication to Azure option, the promo provides a discount + Backup at no additional cost Compared to site-to-site + Backup, the promo provides Azure as a recovery site at no additional cost Offer validity period : Oct 1, 2014 ~ June 30, 2015 * Prices are Level A, annual Any overage is billed at the metered rate Available by EA / EAS only Separate from Azure commitment spend ** At recovery, Azure IaaS capacity is guaranteed to be available at Azure datacenter of customer s choice. Customer will pay for your actual IaaS usage separately if VM running in Azure.

42

43 Replication Replication SAN SAN Replication Hyper-V Hyper-V to Hyper-V (on-premises) Hyper-V Hyper-V Hyper-V to Hyper-V (on-premises) Hyper-V Hyper-V Microsoft Azure Hyper-V to Microsoft Azure Replication Replication VMware or Physical VMware or Physical to VMware (on-premises) VMware Microsoft VMware or Physical Azure VMware or Physical to Microsoft Azure

44 Hyper-V (2012 or 2012 R2) Hyper-V (2012 or 2012 R2) Inbox Hyper-V Replica Today Hyper-V (2012 R2) Microsoft Azure Inbox Hyper-V Replica Today Hyper-V (2012 or 2012 R2) Hyper-V (2012 or 2012 R2) SAN replication Today (Preview) Hyper-V (2008 or 2008 R2) Hyper-V or Azure InMage Scout Future VMware or physical Microsoft Azure InMage Scout Future VMware or physical Hyper-V (2012 R2) InMage Scout Future

45

46

47

48 Session Evaluation

49