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 . 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 Replication Replication Replication SAN SAN Microsoft Hyper-V Hyper-V Hyper-V Hyper-V Hyper-V Azure Hyper-V to Hyper-V Hyper-V to Hyper-V Hyper-V to Microsoft Azure (on-premises) (on-premises) Replication Replication Microsoft VMware or physical VMware VMware or physical Azure VMware or physical to VMware or physical to VMware (on-premises) Microsoft Azure DR Scenario 5: On-premise to On-premise DR for VMware and Physical Servers Microsoft Azure Site Recovery Download InMage Scout InMage InMage Scout Scout Replication and orchestration channel: InMage Replication VMware/ Primary Recovery Physical site site VMware Download Microsoft Azure Download InMage Site Recovery InMage Scout Scout Config Server Process Server Master Source: VMware vSphere VMs InMage Target: VMware vSphere VMs and physical servers Scout data Target Contoso primary location channel Contoso secondary location (On-premises or service provider) (On-premises or service provider) Process Server – Used for caching, Config Server – Used for centralized Master Target – Used as a repository compression and encryption and for retention management of InMage Scout Primary Site Scout Roles (PS & UA) – Functions • Discovery of production server OS & configuration (physical @Prod Servers & virtual) (Physical/VM) • Continuous capture of changing data blocks (CDP) • Continuous transfer of captured blocks to Process Server cache Mobility Agent • Application detection and consistency • 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 @Process Server • Bandwidth throttling of replication traffic to a Master Target • Encryption of replication traffic • Capture of each production server & volume level change rate status DR Site Scout Roles (CS & MT) – Functions • Replication and recovery policies stored in its DB • Web-based UI with extensive graphs, reports, and UI/email/SNMP @Configuration alerts • User management Server • Management dashboard, monitoring pie-charts, real-time granular RPO display • 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 point- in-time recovery @Master Target • Cataloguing the application consistency and recovery points • Virtual snapshots to allow file and folder recovery at any point in VMWare VM 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 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. 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. Scout – Primary Server Discovery Scout – Replication Settings Scout – Replication Advanced Settings Scout – Monitoring Protected Servers Scout – VM Recovery Scout – VM and Network Configuration Scout – VM Recovery Sequencing InMage Scout - OS & application support . Windows (32/64-bit) . Linux (32/64-bit) . 2003 & variations (releases/SPs) . RHEL 4.x, 5.x, 6.x . 2008 & variations . CentOS 4.x, 5.x, 6.x . 2008 R2 & variations . OEL 5.x, 6.x . 2012 . SLES 10x, 11x . 2012 R2 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). Demo On-premise to On-premise DR for VMware and Physical Server Process Server Config Contoso Source: VMware vSphere VMs Orchestration Server and physical servers Contoso primary location Microsoft Azure Master Site Recovery Target (On-premises or service provider) RX Server Fabrikam InMage Config Scout data Server channel Process Master Orchestration Server Target Source: VMware vSphere VMs and physical servers Fabrikam primary location Hosting Service (On-premises or service provider) Provider Process Server – Used for Config Server – Used for Master Target – Used as RX Server – Used for caching, compression and centralized management of a repository and for multi-tenant encryption InMage Scout retention management in Azure Microsoft Azure Microsoft Azure Site Recovery Site Recovery Download InMage Scout Orchestration and replication InMage Scout Replication channel: 2015 InMage Scout VMware Primary Recovery VMware Primary VMware Physical site site site Physical Process Server Config Contoso Source: VMware vSphere VMs Orchestration Server and physical servers Contoso primary location Microsoft Azure Master Site Recovery Target (On-premises or service provider) Fabrikam Azure Site Recovery InMage Config Scout data Server channel Process Master Orchestration Server Target Source: VMware vSphere VMs and physical servers Fabrikam primary location Microsoft Azure (On-premises or service provider) Process Server – Used for Config Server – Used for Master Target – Used as RX Server – Used for caching, compression and centralized management of a repository and for multi-tenant encryption InMage Scout retention management in Azure . MA migrates Windows Physical, Virtual and MA provides a web based portal with 3 levels of AWS workloads into Azure, irrespective of tenancy for self-service and SI partner driven underlying hardware and storage migrations MMA performs guest level application discovery MMA performs end-to-end Recovery and enforces consistency across all VMs in a Orchestration such as network and endpoint multi-tier application adaptation and recovery sequencing Sign-Up Subscribe Provision • Preview • Get an Azure • Download S/W announced via Subscription and set up 2 Azure • Bandwidth Management homepage, • S2S VPN or VMs in Azure Blogs NAT IP for Subscription • Accept Preview Cloud Gateway • Download S/W Terms on • Sign-up and set up 1 landing page response e- Management • Request for mail with VM on-premise MMA Portal follow up Sign-Up, bits & instructions documentation access • Physical, Virtual, AWS Protect • Select Servers and • Application Discovery Recovery Order • Select Azure (SharePoint) • VM and Network Subscription • Windows 2008 R2 and Settings • Replication Settings above • Specify End Points • Map Storage Account Discover Cut-over http://azure.microsoft.com/en-us/features/migration-accelerator/ VMware Physical Other Master Config. Process Target Server Compute Storage Networks Server MMA Multi-tenant Portal Master Config. VMware Physical Other Target Server Process Microsoft Azure Compute Storage Networks Server . 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 . 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