Azure Site Recovery DRaaS Technical Review Name Role Group 11/11/2018

Azure Site Recovery DRaaS Technical Review Name Role Group 11/11/2018
© 2012 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.

Agenda The Challenges of Business Continuity Azure Site Recovery
11/11/2018 Agenda The Challenges of Business Continuity Azure Site Recovery HSP Scenarios for VMware & Physical HSP Scenarios for Hyper-V Azure Pack integration Summary In this session, we’re going to look at a number of key areas around business continuity and disaster recovery. We’re going to start by taking a high level look at some of the common challenges organizations like you face when thinking about business continuity and disaster recovery, and then take a brief look at some of the solutions, provided by Microsoft, in market today, that can solve those challenges. From there, we’ll dive into a number of these areas in a little more depth, exploring some of the key features and capabilities that make them compelling in their own right – some built right into Windows Server, some provided via System Center, and others that utilize our powerful cloud capabilities in Microsoft Azure. All of these solutions demonstrate our integrated story, and how Microsoft can provide you with a compelling solution to meet your business continuity and disaster recovery needs. <next slide> © 2012 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.

Challenges Common business continuity & disaster recovery hurdles
11/11/2018 Challenges Common business continuity & disaster recovery hurdles © 2012 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.

11/11/2018 Business continuity challenges Data growth's impact on business continuity Business continuity Roadblock Protecting data and applications is complex Too much data—often with insufficient help protect Long data retention requirements Time-intensive media management Untested DR and decreasing recovery confidence IT teams have many challenges maintaining their business continuity capabilities. High data growth rates create numerous problems including the complex process of load balancing workloads between storage systems that are running out of capacity ─ a scenario that can lead to downtime if not corrected soon enough ─ but can also impact business continuity another way by severely impacting application performance. Business continuity is plagued by complicated processes, difficult to detect problems, and human errors. Organizations wanting to expand and improve their business continuity capabilities often discover they don’t have the means to do it with the solutions they have. They’d like to retain protected data longer, but either don't have sufficient disk capacity to store data copies or are using tapes, which require many hours of administrative oversight every week to manage properly. The bottom line is that overall confidence in their recovery abilities is low and getting lower each year as the amount of data and the cost of data protection increases. Costs scale with data size and number of VMs © 2012 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.

Business continuity challenges Bypassing the obstacles
11/11/2018 Business continuity challenges Bypassing the obstacles Business continuity Roadblock Roadblock Protecting data and applications is complex Automate, automate, automate Too much data—often with insufficient help protect Integrate solutions which scale with data and VMs Increase breadth and depth of help protect Long data retention requirements Time-intensive media management Eliminate media management Untested DR and decreasing recovery confidence Implement testable solutions So how do IT teams get beyond these obstacles to improved business continuity protection? Here are the game-changers they need: First, they need to automate as many business continuity solutions and processes as they can. Removing human errors from repetitive tasks makes business continuity more reliable as well as speeding up the effort. Automation brings new levels of efficiency that are needed to deal with data growth problems. Along with automation, they need better integration of primary data storage with secondary storage used for data protection – especially the automation and integration of off-site storage. The efficiencies gained from automation and integration give IT teams the ability to expand and improve business continuity protection for many more applications, systems, and virtual machines—not to mention circumventing the time-consuming manual processes that managing tapes demands. Many IT teams do not like to admit that they have not tested their recovery capabilities for far too long and they fear what would happen if they had to recover from a large scale disaster. New solutions for business continuity need to make it easier for IT teams to test their capabilities and find out what works and what needs improving. Costs scale with data size and number of VMs Achieve cost and operations stability © 2012 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.

Ensure business continuity and service delivery
11/11/2018 Protection that evolves with your IT IT solutions are not silos—your business continuity solutions shouldn’t be Physical Physical + Virtual Hybrid Cloud Cloud On-premises—built and managed infrastructure Cloud—flexible, remote infrastructure Microsoft provides solutions across all four scenarios Presentation Notes: Start the presentation with this slide to gauge where a prospect is in their journey to cloud adoption, what their long-term vision looks like and their timeline. This will open up a conversation on their current state, their desired future state, and impediments that stand in their way. As they explain their current state – ask them what products they currently use in their environment for backup, replication and disaster recovery. If the prospect shares their vision above, strive to match our ability to fuel that vision with our solution’s heterogeneity (including cloud). There will likely be one of two scenarios – 1.) Most likely scenario - they use multiple products for backup, replication and DR – perhaps even different products for differing infrastructure. 2.) They have an integrated solution for physical and virtual – but it doesn’t support cloud or offer DRaaS. If they have multiple products – the clear pitch is our heterogeneity and our ability to offer simplification with one solution – with the capabilities to support their future (cloud) needs, providing future validation to the “one solution” offering. If they have an integrated product and lack cloud capability – our angle is to highlight our cloud support, helping power their end-to-end vision, with less complexity. The key selling motion around heterogeneity, is solving a “three tense” problem – past, present and future. Regardless of what stage a customer is at today, a move to the next stage will require their team take on new challenges/problems – BC/DR just one of many. We reduce that problem set by having BC/DR be one less solution on the list to learn and manage. Since we connect all stages together with the capabilities of ASR and InMage, we address planned infrastructure as well as their former, which gives us a unique position in the market. EX: If the customer currently leverages physical infrastructure in combination with Vmware Virtual Machines (Stage 2) and wants to move assets to the cloud in the next 12 months (stage 3) the best way to position the solution to the prospect would be to highlight the current capabilities of ASR with InMage starting with their existing site to site needs. Focus on the solution’s near zero downtime or data loss, with the ability to move and protect assets in the private cloud and Azure. Unlike others - ASR with InMage has the capabilities they need today, with the ability to support their future vision, already built in. © 2013 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.

11/11/2018 Site Recovery As you can see, both Windows Server Backup, and more so, DPM offer some compelling capabilities for protection and recovery of key data within your environment, and through integration with Microsoft Azure Backup, allow organizations to embrace the cloud to unlock new protection scenarios. For customers looking for a more orchestrated solution for failover, that takes advantage of multiple geographical locations, and enables controlled failover between those sites, Microsoft Azure Site Recovery provides a compelling offering… © 2012 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.

11/11/2018 Microsoft Solutions Breadth & depth solutions for business continuity & disaster recovery Integration of WSB/DPM with Microsoft Azure Backup 5 Orchestrated Physical, Hyper-V & VMware VM Replication & Recovery using Azure Site Recovery, between on-premises locations, or between on-premises & Microsoft Azure 6 } Centralized backup with Data Protection Manager 4 Hyper-V Guest Clustering for app- level HA, i.e. SQL Server AlwaysOn FCI 2 Simplified help protect with Windows Server Backup 3 Firstly, when we think about our infrastructure fabric, features built into Windows Server, like Failover Clustering, ensure that in the event of a Hyper-V host failing, your virtual workloads running on top, will restart automatically on another available cluster node, without administrator intervention. <click> For additional levels of application-level protection, customers can create guest clusters i.e. clusters inside the virtual machines, that ensure if individual VMs fail, their partner guest cluster nodes take over, ensuring a higher level of availability at the application level. An example here would be a SQL Server AlwaysOn Failover Cluster Instance. For application and data protection, Windows Server Backup offers an inbox, small scale, simple protection solution for key applications, file and VM data. For more advanced, scalable, granular data and application protection, System Center Data Protection Manager provides a powerful solution for protection, across physical and virtual, with application-specific functionality built in, to protect Exchange, SQL Server, SharePoint, Hyper-V and more, all with a single agent. Both of these backup technologies now integrate with Microsoft Azure Backup – a Microsoft Azure-based service enabling customers to embrace the cloud as an offsite repository for backing up their key data, all seamlessly integrated into the respective UI’s of WSB and DPM. For customers looking to embrace a faster, VM-level failover between sites, Azure Site Recovery enables organizations to quickly and efficiently replicate their virtual machines to a secondary location, and build powerful recovery plans to orchestrate the failover to the second site, and back, in a controlled manner. In addition, with the recent acquisition of InMage, Microsoft has expanded it’s replication and recovery capabilities for Azure Site Recovery with support for replicating VMware vSphere-based VMs, or physical servers, to a secondary location running VMware vSphere. But what if you don’t have a second site of you own? Well, with new capabilities added to Microsoft Azure Site Recovery, combined with additional integrated capabilities provided by InMage, customers also also have the opportunity to replicate and recover their physical servers, Hyper-V, or VMware vSphere-based VMs into Microsoft Azure, taking advantage of Microsoft’s cloud scale, reliability and redundancy. What we have on the slide is just a taster of the capabilities that Microsoft can provide to help meet your business continuity and disaster recovery needs, so let’s take a look in more detail at each of these areas to understand a little more of how they work, and the advantages they can provide. <next slide> Hyper-V Failover Clustering for VM Resilience 1 © 2012 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.

Microsoft’s Disaster Recovery Stack
Inter net Infor mati on Servi ces (IIS) Apps SQL e.g. SQL AlwaysOn VM or Physical Server Replication with Hyper-V Replica or InMage Scout DR Orchestration with Microsoft Azure Site Recovery Storage Replication Compute Storage Networks Hyper-V, VMware or Physical

Azure Site Recovery One Solution for multiple infrastructures
11/11/2018 Azure Site Recovery One Solution for multiple infrastructures On-premises to On-premises help protect Protect to Azure Microsoft Azure Site Recovery Communication Channel Replication channel: Hyper-V Replica, SQL AlwaysOn, SAN Primary Site Windows Server Recovery Site Download Scout Replication channel: InMage Replication Physical/VMWare VMWare InMage Scout Communication and Replication Microsoft Azure Site Recovery VMWare/Physical InMage Scout Orchestration and Replication: Hyper-V Replica, SQL AlwaysOn Windows Server 2015 Primary Site Primary Site © 2012 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.

Azure Site Recovery One Solution for multiple infrastructures 1 2 3 4
11/11/2018 Azure Site Recovery One Solution for multiple infrastructures Hyper-V to Hyper-V (on-premises) 1 Hyper-V Replication Hyper-V to Hyper-V (on-premises) 2 Hyper-V Replication SAN Hyper-V to Microsoft Azure 3 Hyper-V Microsoft Azure Replication VMware/Physical to VMware (on-premises) 4 VMware/Physical VMware Replication VMware/Physical to Microsoft Azure 5 VMware/Physical Microsoft Azure Replication What are the different infrastructures that Azure Site Recovery can provide a solution for? Well firstly, for customers who have multiple sites, or work with a service provider as a secondary site, and Hyper-V is running on both sites, they can take advantage of Azure Site Recovery to orchestrate the replication and recovery between those sites. In that example, the engine of replication will be Hyper-V Replica, an inbox VM replication technology that’s built into Windows Server 2012 and 2012 R2. <click> For customers with an investment in SAN technology, that includes replication in the box, through integration with Hyper-V, System Center and Azure Site Recovery, customers can orchestrate the replication and recovery of their key workloads between those sites, this time, harnessing the power of the SAN, through asynchronous or synchronous replication, to transfer data between sites. For customers who don’t have a second site, and are running Hyper-V on their primary site, using Azure Site Recovery, customers can orchestrate the replication and recovery of their on-premises workloads, into the Microsoft Azure datacenters, enabling this as a target for failover in the event of a disaster. The engine of replication in this example is Hyper-V Replica. What about customers who don’t have Hyper-V within their datacenters? Well, as we mentioned at the start of the presentation, with the acquisition of InMage, under the umbrella of Azure Site Recovery, customers can orchestrate the replication and recovery of key workloads from physical, or VMware-based sites, over to a secondary site, running VMware also. This time, InMage Scout is providing the replication engine, and is transferring the data between the two on-premises locations. Finally, just like we saw earlier, where a customers without a secondary location, could use ASR to replicate and recover Hyper-V-based VMs into Azure, with the new InMage technologies, in the future, you will be able to replicate and recover VMware-based VMs into Microsoft Azure. Again, this will be powered by InMage Scout. <next slide> Protect important applications by coordinating the replication and recovery of private clouds across sites. Protect your applications to your own second site, a HSP’s site, or even use Microsoft Azure as your disaster recovery site © 2012 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.

11/11/2018 Service Provider Scenarios in Windows Server Hyper-V Environments © 2014 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.

Hosted Workloads to Second Site
11/11/2018 Hosted Workloads to Second Site for Windows Server Hyper-V DR Orchestration Microsoft Azure Site Recovery DR Orchestration System Center Virtual Machin e Manage r (SCVM M) & DRP SCVMM & DRP Source: Hyper-V Workloads Extensible Data Channel Target: Hyper-V Workloads HSP Data Center 1 HSP Data Center 2 © 2012 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.

Microsoft Azure Pack and CPS Integration (Future)
11/11/2018 Microsoft Azure Pack and CPS Integration (Future) DR Orchestration Microsoft Azure Site Recovery DR Orchestration Azure Pack, SCVMM & DRP Azure Pack, SCVMM & DRP Source: Hyper-V Workloads Data Channel Target: Hyper-V Workloads HSP Data Center 1 / CPS Stamp 1 HSP Data Center 2 / CPS Stamp 2 © 2012 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.

Microsoft Azure Pack Integration (Future)
DR as a Plan/Add-On property on VM clouds Service Management Datacenter Automation (SMA) runbooks To auto-create recovery site subscription when Tenant subscribes to DR on primary To help/disable DR help protect for all present and future created VMs in subscription Full integration of replica VMs with recovery site Azure Pack Tenants can manage (start/stop/console or desktop connect) failed over replica VMs on recovery site Azure Pack Replication and failover health monitoring through System Center Operations Manager (SCOM)

Hosted Workloads to Azure
11/11/2018 Hosted Workloads to Azure for Windows Server Hyper-V DR Orchestration Microsoft Azure Site Recovery DR Orchestration Azure Pack, SCVMM & DRP Source: Hyper-V Workloads Extensible Data Channel Target: Microsoft Azure HSP Data Center 1 Microsoft Azure Works with or without Azure pack © 2012 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.

Hosted Workloads to Azure – Tenant Isolation
TechReady 18 Hosted Workloads to Azure – Tenant Isolation 11/11/2018 Tenant 2 Tenant 1 Failover Microsoft Azure Pack Tenant 1 Subscription VM Replication Tenant 1 SCVMM SA1 Virtual Network HSP Billing Account Tenant 2 Subscription VM Replication Tenant 2 SA2 Virtual Network HSP Management Subscription ASR Vault DR Orchestration DRP HSP owns the billing of Azure subscriptions HSP creates management subscription in which ASR vault is created and HSP SCVMM is registered Tenants do no have access to management subscription Given managed DR focus, DR drills are triggered by HSP on behalf of tenants HSP creates new Azure subscription per tenant and makes tenant co-admin on it Tenant VM replicates to the Storage Account in subscription created for tenant During failover to Azure, VM instance comes up in Azure subscription created for tenant HSP Data Center Microsoft Azure © 2014 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.

Customer Workloads to HSP Cloud
11/11/2018 Customer Workloads to HSP Cloud for Windows Server Hyper-V DR Orchestration DR Orchestration Microsoft Azure Site Recovery SCVMM & DRP SCVMM & DRP Customer 1 DC Extensible Data Channel Target: Hyper-V Workloads SCVMM & DRP HSP Data Center Customer 2 DC © 2012 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.

Customer Workloads to Azure
11/11/2018 Customer Workloads to Azure for Windows Server Hyper-V DR Orchestration DR Orchestration Microsoft Azure Site Recovery SCVMM & DRP Customer 1 DC Extensible Data Channel Target: Microsoft Azure SCVMM & DRP Microsoft Azure Customer 2 DC © 2012 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.

Azure Site Recovery SDK
11/11/2018 Azure Site Recovery SDK ASR SDK now shipping as a component of Azure SDK Enables ASR integration with HSP management portals Provides single-pane of glass DR management for HSPs with homegrown management portals Scenarios enabled in v1 VM help protect and failover Recovery plan management Monitoring Design allows for interoperability with SCVMM and ASR from single script ASR SDK: REST API SDKs Windows PowerShell command-line tools © 2012 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.

Microsoft Azure Site Recovery
11/11/2018 Microsoft Azure Site Recovery How it works: Initial Configuration 1. Sign up Primary Site System Center Virtual Machine Manager 2. Create Recovery Vault 3. Deploy Provider 4. VMM Metadata pushed to Azure Site Recovery, outbound, over HTTPS System Center Virtual Machine Manager Secondary Site Firstly, you'll need an Azure account, so you’ll need to register with an appropriate Microsoft Account. Once completed…. <click> You create a Recovery Vault – this is a simple process that involves providing a name, and a location of where you want the vault to reside, choosing the geography which is most relevant to you and your business. From there, to register your on-premises Virtual Machine Manager servers in an Azure Site Recovery vault, you'll need to upload a management certificate (.cer) containing the public key to the vault. This management certificate should reside on each of your VMM servers. The SSL certificate can be self-signed, come from an enterprise CA, or any CA that is trusted by Microsoft. Once the certificate is imported into the Vault, you can deploy the provider, which is downloaded from the Azure portal. This should be installed on each of your VMM servers. The latest version of the Provider installation file is stored in the Azure Download Center. When you run the file on a VMM server the Provider is installed, and the VMM server is registered with the vault. Upon completion of this stage, metadata from the VMM server(s) is pushed to Azure Site Recovery, in order to orchestrate failover and recovery. After a server has been successfully registered its friendly name will be displayed on the **Resources** tab of the Servers page in the vault <next slide> © 2012 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.

11/11/2018 Microsoft Azure Site Recovery How it works: Configuring Protection & Map Networks Primary Site Active Directory (AD) System Center Virtual Machine Manager SQL 7. Configure Protection of Clouds LOB 5. On Primary Site, create VMM Clouds & add VMs 9. Map VM Networks from Primary to Secondary 8. Continuous Health Monitoring 6. On Secondary Site, create corresponding VMM DR Clouds System Center Virtual Machine Manager Secondary Site <click> You then need to create Clouds on the primary site. In VMM, a cloud is an object that is provisioned and managed on-premises by an organization. The cloud is deployed by using an organization’s own hardware to leverage the advantages of the cloud model. By using VMM, an organization can manage the cloud definition and can manage access to the cloud and the underlying physical resources. Clouds contain the VMs that will be protected by Azure Site Recovery. On the secondary site, you simply create clouds that map to those on primary, so for instance, if you had a cloud on primary called Test, you may create a cloud on secondary called Test_DR. These clouds will be mapped to one another at a later point. The user can then configure the key items within the Azure portal, from replication frequency, to additional recovery points and VSS integration. These settings ultimately determine the settings applied to Hyper-V Replica, which is on each Hyper-V host. From this point forward, Azure Site Recovery will monitor the VMM servers on your on-premises locations, but at this point, we have nothing configured for protection – only our clouds are configured. We then map our networks between the sites, which we can look at in a bit more detail. <next slide> © 2012 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.

11/11/2018 Microsoft Azure Site Recovery How it works: Configuring Protection of Clouds & Networks Virtual Machine Manager Clouds In VMM, a cloud presents an abstracted view of pooled resources, and can be accessed through self-service. Clouds are also a container object for Site Recovery, containing the VMs that you wish to help protect. Cloud Configuration Streamlined configuration of replication settings, including frequency, recovery points, VSS-snapshot integration, compression & initial replication. Map VM Networks Configure mapping between VM networks on source and target VMM servers to help make sure correct connectivity on failover. Where VMs use static IPs and primary & secondary sites have different IP ranges, Azure Site Recovery integrates with VMM to automatically inject a updated static IP address into the VM upon failover. As we said earlier, you then need to create Clouds on the primary site. <click> In VMM, a cloud is an object that is provisioned and managed on-premises by an organization. The cloud is deployed by using an organization’s own hardware to leverage the advantages of the cloud model. By using VMM, an organization can manage the cloud definition and can manage access to the cloud and the underlying physical resources. Clouds contain the VMs that will be protected by Azure Site Recovery. As you can see here, this cloud is configured for protection, and has a corresponding recovery cloud in the secondary site. We then adjust the relevant settings associated with the cloud, selecting a replication frequency, which could be every 30 seconds, 5 minutes or 15 minutes, whether we want additional recovery point, VSS integration for application consistent snapshots, whether we want to enable compression, and finally, how we want to perform the initial replication – immediately over the network, later, or via removable media. Finally, we configure out network mapping between VM networks on source and target VMM servers. Network mapping ensures that after failover, replica virtual machines are connected to appropriate networks, and to ensure that replica virtual machines are placed on hosts that can access the VM networks. You’ll see here that we simply select a network on our primary site, and select a network to map this to, in our secondary location. This assumes that you already have the correct IP addressing scheme configured on both sites – ASR simply ensures that the VMs connect to the correct network on failover. In addition, where VMs use statically assigned IPs and primary & secondary sites have different IP ranges, Azure Site Recovery integrates with VMM to automatically inject a new static IP address into the VM upon failover, by integrating with the VMM network pool construct. <next slide> © 2012 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.

11/11/2018 Microsoft Azure Site Recovery How it works: Finalizing Protection Primary Site 10. Enable VM help protect in VMM or in Azure Portal AD System Center Virtual Machine Manager SQL LOB 11. ASR selects suitable host that meets requirements & starts replication using the Hyper-V Replica Engine System Center Virtual Machine Manager Secondary Site AD SQL LOB Once the mapping is completed, it’s time to enable VM protection. This can be achieved through VMM, or through the Azure Portal. <click> Once enabled ASR performs all of the orchestration by selecting a suitable host on the recovery site which has necessary Storage, Memory and network connectivity for the VM to come up. This is what we mean by reliable recovery. We are not only replicating data to recovery site, using Hyper-V Replica but also ensuring that in case of failover, VMs come up successfully. <next slide> © 2012 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.

11/11/2018 Microsoft Azure Site Recovery How it works: Finalizing Protection Enable VM Protection Use Azure Portal, VMM GUI or PowerShell to help VM help protect within configured clouds. Sample PowerShell Script $cloud = Get-SCCloud -Name “CloudName” Get-SCVirtualMachine -Cloud $cloud | where {$_.IsDRProtectionRequired -eq $false} | Set-SCVirtualMachine –DRProtectionRequired $true -RecoveryPointObjective “TimeInSeconds” Replication Initiates Site Recovery automatically configures Hyper-V Replica for the selected VMs, between your protected and recovery clouds. To go into slightly more detail, as you can see, it’s very straightforward to enable a VM, within a protected cloud, to be configured for replication and recovery. You simply select the VM, and enable protection. The frequency cannot be changed, as it is set at a cloud level. <click> This configuration is fine for a few VMs, but if you have a larger number of VMs that you wish to enable protection for, you could utilize PowerShell to achieve that. This sample script takes a cloud name that you specify, and for all VMs in that cloud, checks whether they have protection enabled, and if not, enables DR protection, with the replication interval you specify. Once enabled, replication from primary to secondary site will begin, and within a short while, the VM will be listed as protected, and ready for failover. This replication, as we mentioned earlier, uses Hyper-V Replica, which we will now learn a little more about. <next slide> © 2012 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.

11/11/2018 Microsoft Azure Site Recovery Hyper-V Replica – Replication Engine Integrated Software-Based VM Replication VM replication capabilities built into Windows Server 2012 R2 Hyper-V. Configurable replication frequencies of 30 seconds, 5 minutes and 15 minutes. Secure replication across network using certificates. Flexible Solution, agnostic of network, server and storage hardware on either site No need for other virtual machine replication technologies, reducing costs. Automatic handling of live migration. Simple configuration and management – either through Hyper-V Manager, PowerShell, or with Azure Site Recovery Upon site failure, VMs can be started on secondary site Once replicated, changes replicated on chosen frequency Once Hyper-V Replica is enabled, VMs begin replication Primary Site Secondary Site Replicated Changes Initial Replica CSV on Block Storage SMB Share File Based Storage Windows Server 2012 introduced Hyper‑V Replica, a built-in feature that provides asynchronous replication of virtual machines for the purposes of business continuity and disaster recovery. In the event of failures (such as power failure, fire, or natural disaster) at the primary site, the administrator can manually fail over the production virtual machines to the Hyper‑V server at the recovery site. During failover, the virtual machines are brought back to a consistent point in time, and within minutes they can be accessed by the rest of the network with minimal impact to the business. Once the primary site comes back, the administrators can manually revert the virtual machines to the Hyper‑V server at the primary site. Hyper‑V Replica lets you replicate your Hyper‑V virtual machines over a network link from one Hyper‑V host at a primary site to another Hyper‑V host at a Replica site without reliance on storage arrays or other software replication technologies. The figure shows secure replication of virtual machines from different systems and clusters to a remote site over a WAN. Benefits of Hyper‑V Replica Hyper‑V Replica fills an important gap in the Windows Server Hyper‑V offering by providing an affordable in-box business continuity and disaster recovery solution. Failure recovery in minutes. In the event of an unplanned shutdown, Hyper‑V Replica can restore your system in just minutes. More secure replication across the network. Hyper‑V Replica tracks the write operations on the primary virtual machine and replicates these changes to the Replica server efficiently over a WAN. The network connection between the two servers uses the HTTP or HTTPS protocol and supports both integrated and certificate-based authentication. Connections configured to use integrated authentication are not encrypted; for an encrypted connection, you should choose certificate-based authentication. Hyper‑V Replica is closely integrated with Windows failover clustering and provides easier replication across different migration scenarios in the primary and Replica servers. Hyper‑V Replica doesn’t rely on storage arrays. Hyper‑V Replica doesn’t rely on other software replication technologies. Hyper‑V Replica automatically handles live migration. Configuration and management are simpler with Hyper‑V Replica: Integrated user interface (UI) with Hyper‑V Manager. Failover Cluster Manager snap-in for Microsoft Management Console (MMC). Extensible WMI interface. Windows PowerShell command-line interface scripting capability. Azure Site Recovery <next slide> © 2012 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.

11/11/2018 Microsoft Azure Site Recovery How it works: Recovery Plans Primary Site AD System Center Virtual Machine Manager SQL LOB 12. Create Recovery Plan System Center Virtual Machine Manager Secondary Site AD SQL LOB Once the VM’s have been replicated, and are fully protected, the user needs to create a Recovery Plan, which will help to coordinate the failover between sites. <next slide> © 2012 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.

11/11/2018 Microsoft Azure Site Recovery Orchestrated Recovery using Recovery Plans Orchestrated Steps for Recovery Recovery Plans help automate the orderly recovery in the event of a site outage at the primary datacenter. Recovery Plans consist of a series of groups that contain a list of protected virtual machines. The order the VMs failover is determined by the group they are within. VMs within a particular group failover in parallel Recovery plans typically model an application that needs to start up, or failover, in a particular order. Script Integration Scripts can be added, to run before or after a specific group in a recovery plan. Scripts could also allow integration with SQL Server AlwaysOn failover between sites. Manual Actions Manual actions can also be added, to run before or after a selected group. These require some form of physical interaction by a particular user before recovery plan continues. A recovery plan gathers virtual machines together into groups so that they can be processed as a single unit, and specifies the order in which groups should fail over. <click> Recovery plans consist of a series of steps, executed in a particular order. As you can see from the screenshot here, Recovery Plans consist of a series of groups, each with a user-defined number of virtual machines within those groups. Recovery Plans provide two key capabilities – sequencing (To ensure reliable failover) and parallelism (To reduce RTO). The order the VMs failover is determined by the group they are within. VMs within a particular group failover in parallel. You can use Recovery Plans to model a particular application, so tiers of that application failover, and start up, in a preferred manner. For instance, imagine a 3 tier application, with a database, app and web tier. The database tier should start first, as the app tier relies on this, then the app tier, and finally the web tier. Recovery Plans help to orchestrate this behavior. Scripts call also be integrated, to perform certain tasks whilst the Recovery Plan is being executed. In addition, these scripts could themselves trigger failover of assets that cannot be part of a Azure Site Recovery process, such as the failover of a SQL Server AlwaysOn Availability Group. If customers are using SQL Server’s own replication between sites, rather than Hyper-V Replica, with SQL Servers located in both primary and secondary sites, as part of the datacenter failover, a script could execute that handles failover of the SQL Server databases, at the SQL Server level, whilst the rest of the Recovery Plan focuses on failing over the VMs. Finally, manual actions can also be injected. These may involve someone physically performing some task before the recovery plan can continue. In this example, we’re asking the LOB app owner to check their application is functioning correctly, before allowing the rest of the Recovery Plan to execute. <next slide> © 2012 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.

11/11/2018 Microsoft Azure Site Recovery How it works: Executing Recovery Plans Primary Site System Center Virtual Machine Manager AD SQL LOB AD SQL LOB 13. Execute Recovery Plan 16. When Reverse Replication completes, a Planned Failover returns active VMs to Primary Site 15. When Primary Site is back online, implement a Reverse Replication 14. Site Recovery Orchestrates VMs starting on Secondary Site System Center Virtual Machine Manager Secondary Site AD SQL LOB AD SQL LOB <click> In the event of an outage, or even if we just want to test failover, we need to execute the recovery plan. The Recovery Plan runs in Microsoft Azure, and… Site Recovery starts the orchestrated failover of VMs in the secondary location. When the primary site is back online, the user can execute a reverse replication, and replication from secondary, back to primary will begin. Once completed, the user can initiate a planned failover, back to the primary site, without any data loss. <next slide> © 2012 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.

11/11/2018 Microsoft Azure Site Recovery Executing Recovery Plans Test Failover Useful to verify that your recovery plan and virtual machine failover strategy are working as expected. Simulates your failover and recovery mechanism into an isolated network(s), that you define, or that can be created automatically. Unplanned Failover Run an unplanned failover when a primary site experiences an unexpected incident, such as a power outage. Planned Failover Perform a complete failover and recovery of virtual machines in your recovery plans in a proactive, planned manner. Non-replicated changes are applied to the replica virtual machine with no data loss before bringing the VM online in the secondary site. When it comes to executing Recovery Plans, there are 3 ways they can be executed. Firstly, the user can run a test failover. <click> Running a test failover executes the recovery plan, brings workloads up on the secondary site, but in an isolated environment, whilst the primary site is still online. The ability to test failover ensures that recovery plans execute as expected, in the event of a disaster. You can have the test failover process automatically create new networks for VMs on the secondary site using Hyper-V Network Virtualization, or use existing ones that you’ve defined in advance. With an unplanned failover, this would be executed when the primary site has had an unexpected outage. When you execute an unplanned failover, you can attempt to shut down the VMs on the primary first, and replicate any final changes, but it’s most likely that in an unplanned scenario, you’ve lost the primary site already, and the main objective is to bring the secondary site online as quickly and efficiently as possible. Finally, we have the planned failover, where you’re executing failover in a proactive, planned manner. In this scenario, the VMs are cleanly shut down, their final delta changes since the last replication are replicated, and the VMs are failed over in a controlled and orchestrated manner. Now that we’ve heard about the process, let’s take a look at it in action with a demo. <next slide> © 2012 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.

11/11/2018 Demo Microsoft Azure Site Recovery Hyper-V <> Hyper-V (on-premises) Please access the DemoMate demonstration from: Inside, you will find a DemoMate and script. © 2012 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.

Orchestrated Disaster Recovery
11/11/2018 Orchestrated Disaster Recovery Between on-premises and/or service provider locations Microsoft Azure Site Recovery Communication Channel Replication channel: SAN Replication Primary Site Windows Server Recovery Site Similar to what we saw earlier, this time, instead of utilizing Hyper-V Replica as the replication engine between sites, customers can take advantage of the same rich ASR experience for orchestrating replication and recovery, only this time, the replication of important data will be provided by the existing storage investments. This replication could be asynchronous, or synchronous, depending on the customers’ needs. Let’s explore these additional capabilities, opened up by integration with SAN Replication, in a little more detail. <next slide> © 2012 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.

SAN Replication Harness the power of your SAN Investments 11/11/2018
Take advantage of SAN Replication capabilities provided by enterprise storage partners, across both FC & iSCSI storage Supports asynchronous replication for flexibility or synchronous replication for the lowest Recovery Point Objective (RPO)/Recovery Time Objective (RTO) Key Value Propositions Full Disaster Recovery orchestration for SAN storage Support for applications that require DR with shared storage, such as SQL Server, SharePoint, SAP etc. Integrated with Azure Site Recovery for streamlined, consistent experience. Integration Integration with SAN through SMI-S – SCVMM will discover and enumerate existing storage. SCVMM provides comprehensive SAN management capabilities within console. Microsoft Azure Site Recovery Communication & Orchestration Asynchronous or Synchronous SAN Replication SAN Storage SAN Storage © 2012 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.

SAN Replication | Storage Partners
11/11/2018 SAN Replication | Storage Partners Harness the power of your SAN Investments Partner Device EMC VMAX VNX & VNX/e NetApp FAS (8.2 C-MODE) HP 3PAR HDS VSP Fujitsu Eternus Dell Compellent Huawei OceanStor IBM XIV Supported on VMM 2012 R2 (with latest UR) Public Availability: Q2 FY15 © 2012 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.

SAN Replication | Replication Groups
11/11/2018 SAN Replication | Replication Groups Harness the power of your SAN Investments Replication Groups Achieve consistency for applications & workloads by grouping related LUNS into replication groups. SAN guarantees replication consistency across the arrays between sites. Replication groups are allocated to Clouds, which are used by Azure Site Recovery Azure Site Recovery Protection is configured at the Cloud level, but replication is by Replication Group Mapping between SANs on Primary & Secondary is configured through Azure Site Recovery Recovery Plans Enables orchestrated individual VM boot order to help make sure applications & workloads operate as expected. © 2012 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.

Orchestrated Disaster Recovery
11/11/2018 Orchestrated Disaster Recovery for Hyper-V VMs, between on-premises locations & Microsoft Azure Microsoft Azure Site Recovery Communication Channel Replication channel: Hyper-V Replica or SAN Replication Primary Site Windows Server Recovery Site Communication and Replication Microsoft Azure Site Recovery Primary Site Windows Server Key features include: Automated VM help protect and replication Remote health monitoring Customizable recovery plans No-impact recovery plan testing Orchestrated recovery when needed As mentioned earlier, with new capabilities added to Azure Site Recovery, customers now have the ability to replicate and recover their virtual workloads into Microsoft Azure datacenters, whilst gaining the same benefits we’ve learnt about earlier, from automated VM protection and replications, remote health monitoring of your key sites, customizable recovery plans for controlled failover, that can be tested, and failed over when required. <next slide> © 2012 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.

11/11/2018 Microsoft Azure Site Recovery Replication & Recovery into Microsoft Azure Consistent Experience Centralized view of replication & recovery between on-premises locations, & between on-premises & Microsoft Azure. Streamlined Configuration Only 1 additional installation step – installation of Site Recovery agent on Hyper-V Hosts Quickly set up help protect of on-premises clouds, with Microsoft Azure as a target. Support for Encryption of Data at Rest, along with flexible replication frequencies, additional recovery points & VSS-aware application consistent checkpoints. Network Mapping Enables the mapping of on-premises VM Networks into pre-created Microsoft Azure Virtual Networks To go one level deeper, what’s important here with the new capabilities for Azure Site Recovery, is that they are consistent with the existing capabilities. Customers can gain a single view for recovery between your own sites, and between your site and Azure, which makes management and control easy. <click> Only a single step differs when it comes to configuration when replicating to Azure – an additional agent needs to be deployed to the Hyper-V hosts, however this can be deployed via your regular deployment channels, and doesn’t require a reboot. Just as we saw earlier, the configuration is simple, and protection of clouds can be set up quickly, this time, specifying Azure as the target location for replication and recovery. Support for key features such as encryption of data at rest is provided as standard, helping you to meet your compliancy and regulatory requirements. In addition, features such as additional recovery points, and VSS-aware app consistent snapshots are all available. Replication frequencies can be every 30 seconds, 5 minutes, or 15 minutes. To ensure expected connectivity, the user can pre-create VM networks in Azure, and these can be mapped to on-premises networks, ensuring that when VMs failover in Azure, they connect to expected networks, and can communicate correctly. <next slide> © 2012 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.

11/11/2018 Microsoft Azure Site Recovery Replication & Recovery into Microsoft Azure Recovery Plans Automate the orderly recovery into Microsoft Azure, in the event of a site outage at the primary datacenter. Support for Manual Actions that require some form of human intervention during the implementation of the Recovery Plan. Shutdown of VMs upon implementation is in reverse order of recovery to help make sure zero data loss. Flexible Failover & Failback Options Support for Test, Unplanned & Planned Failover into Microsoft Azure. Can be used to provide compliance assurance without impacting production workloads, and also as a mechanism to migrate into Microsoft Azure for longer term usage. Streamlined process for failback into on-premises environment. When replicating and recovering into Azure, Recovery Plans still play an integral part. <click> As we saw earlier, they coordinate and control the failover of VMs into Azure, and also support manual actions being injected into the Recovery Plan. When replicating and recovering in Azure, customers still have support for test, planned and unplanned failover scenarios, which can be used to provide compliance assurance without impacting production workloads, and also as a mechanism to migrate into Microsoft Azure for longer term usage. Should the customer desire, once the on-premises location is back online after a failover, the workloads can be replicated, and failed back to on-premises. Let’s take a quick look at this through demonstration. <next slide> © 2012 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.

Demo Microsoft Azure Site Recovery
11/11/2018 Demo Microsoft Azure Site Recovery Hyper-V <> Azure Please access the DemoMate demonstration from: Inside, you will find a DemoMate and script. © 2012 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.

Service Provider Scenarios in VMware and Physical Environments
11/11/2018 Service Provider Scenarios in VMware and Physical Environments © 2014 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.

Heterogeneous Disaster Recovery
11/11/2018 Heterogeneous Disaster Recovery for VMware & Physical into Azure with ASR & InMage Scout Microsoft Azure Site Recovery Download InMage Scout Replication channel: InMage Scout Primary Site VMware/Physical Recovery Site Communication and Replication Microsoft Azure Site Recovery Primary Site VMware/Physical Using InMage Scout 2015 InMage Scout to Azure OS-based replication for flexibility Supports VMware vSphere & Physical Servers as the source of replication So what we’ve discussed there, is using InMage Scout to protect physical, or VMware vSphere-based workloads, to a secondary location on-premises, that’s also running VMware vSphere, however, with ASR and InMage Scout, we’re extending the capabilities to enable organizations to replicate and recover those physical, or VMware-based workloads on-premises into Microsoft Azure. With ASR, customers again can protect their existing investments in VMware vSphere, or in physical systems, but if they lack a second site, they can take advantage of Azure’s capacity, and replicate their workloads directly into Microsoft datacenters. In the event of a disaster, customers can failover, in a controlled and orchestrated manner, into Azure, and run their workloads utilizing the Azure IaaS capabilities. <next slide> Supports Microsoft Azure as target for replication & recovery Ideal for enterprises & service providers with existing VMware investments © 2012 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.

11/11/2018 Value Proposition Key strengths that InMage Scout brings to Azure Site Recovery Heterogeneous Replication – Scout helps protect physical & virtual environments, irrespective of underlying hardware Near-Zero RPO - lightweight mobility service on the primary servers to track & replicate data changes continuously in real-time N-tier Application Consistency - guest level app discovery & enforces consistency across all VMs in a multi-tier app Best-in-class RTO - end-to-end recovery orchestration such as network adaptation & sequencing to minimize site level RTO Maturity & Experience – customers, multiple patents & support for a wide range of different platforms …but what are some of the key value propositions that InMage brings to Azure Site Recovery? Well firstly, it’s support for heterogeneous environments. As we learnt earlier, ASR supports Microsoft-based environments, and relies on Hyper-V Replica as the replication engine to replicate data between on-premises locations, and between on-premises and Azure. With InMage however, things change considerably. InMage Scout works at the guest level, at the OS level, thus is agnostic of the underlying hardware platform. It could be a physical server, or a VMware virtual machine – either way, Scout handles the replication, and will orchestrate the recovery of workloads from one location, to another. <click> Scout also uses a very lightweight mobility service inside the source OS, known as the Data Tap, which tracks and replicates data changes continuously, in real time, sending them off to the local Process Server, which in turn, sends the data to the target site. It’s an extremely efficient process, and through the use of this architecture, means the impact to the workload itself is negligible. When replicating workloads, often, there are workloads that rely on one another. A 3 tier application for instance, may rely on all pieces of that application being in ‘sync’ with one another, both on the primary site, and after a failover on the recovery site. Thankfully, InMage Scout provides N-Tier app consistency. Applications can be automatically discovered, and InMage Scout will protect each of the key elements of the tiered application, and guarantees consistency across the tiers upon failover. You recovery time objective is a critical piece of your DR story. Fortunately, with InMage Scout, and it’s in-built orchestration capabilities, it’s easy to setup and ensure that your VMs and brought online in the correct sequence, but at the same time, Scout also enables you to adjust certain VM settings for the VMs that come up on the recovery site, for the highest levels of flexibility. Finally, InMage Scout joins the ASR family with a wealth of experience, maturity and large scale adoption. With a large number of patented technologies, and support for a large variety of platforms, from Windows to Linux, physical to virtual, InMage Scout and Azure Site Recovery provide an incredible combination to enable you to protect every workload within your environment. <next slide> © 2012 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.

Hosted Workloads to Second Site
11/11/2018 Hosted Workloads to Second Site for VMware vSphere-based VMs & Physical Servers Download InMage Scout Microsoft Azure Site Recovery Download InMage Scout Config Server RX Server Process Server Source: VMware vSphere VMs & Physical Servers Data Channel Master Target Target: VMware vSphere VMs HSP Data Center 1 HSP Data Center 2 Process Server – Used for Caching, Compression & Encryption Config Server – Used for Centralized Management Master Target – Used as a repository & for retention Mobility Service– Captures all data writes from memory RX Server – Used for multi-tenant management © 2012 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.

Hosted Workloads to Azure
11/11/2018 Hosted Workloads to Azure for VMware vSphere-based VMs & Physical Servers Microsoft Azure Site Recovery Customer 1 Process Server Customer 2 Data Channel Source: VMware vSphere VMs & Physical Servers Target: Microsoft Azure Microsoft Azure Process Server – Used for Caching, Compression & Encryption Config Server – Used for Centralized Management Master Target – Used as a repository & for retention Mobility Service– Captures all data writes from memory RX Server – Used for multi-tenant management © 2012 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.

Customer Workloads to HSP Cloud
11/11/2018 Customer Workloads to HSP Cloud for VMware vSphere-based VMs & Physical Servers Microsoft Azure Site Recovery Process Server Customer 1 Orchestration Source: VMware vSphere VMs & Physical Servers Customer 1 RX Server Customer 2 Data Channel Orchestration Process Server Source: VMware vSphere VMs & Physical Servers HSP Cloud Customer 2 Process Server – Used for Caching, Compression & Encryption Config Server – Used for Centralized Management Master Target – Used as a repository & for retention Mobility Service– Captures all data writes from memory RX Server – Used for multi-tenant management © 2012 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.

Customer Workloads to Azure
11/11/2018 Customer Workloads to Azure for VMware vSphere-based VMs & Physical Servers Microsoft Azure Site Recovery Process Server Customer 1 Source: VMware vSphere VMs & Physical Servers Customer 1 Customer 2 Data Channel Target: Microsoft Azure Process Server Source: VMware vSphere VMs & Physical Servers Microsoft Azure Microsoft Azure Customer 2 To go into a little more depth, in the future, we’ll be providing capability to enable VMware customers, and those with physical servers, to be able to replicate and recover their key workloads, from on-premises, into Microsoft Azure. This will again utilize the InMage capabilities, with InMage components existing both on-premises, and in Microsoft Azure, with customers being able to replicate into their respective Azure subscriptions, and make use of Azure IaaS as a failover target in the event of a disaster. In the example on the slide, you’ll see 2 customers, Contoso and Fabrikam, with on-premises resources. They have a number of vSphere hosts, but also a physical server. Through integration between ASR and InMage, these 2 customers will be able to independently replicate their key data into Azure, securely, with each having their own set of InMage components in Azure connecting back to their on-premises InMage components. ASR with InMage will orchestrate failover of the key workloads into Azure, should a disaster arise. This flexibility enables organizations to protect key vSphere workloads, to an enterprise-class public cloud, Azure, and gain a rich, granular level of control for the orchestration of failover. <next slide> Process Server – Used for Caching, Compression & Encryption Config Server – Used for Centralized Management Master Target – Used as a repository & for retention Mobility Service– Captures all data writes from memory RX Server – Used for multi-tenant management © 2012 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.

Azure Site Recovery | InMage Scout
11/11/2018 Azure Site Recovery | InMage Scout Streamlined Protection Primary Server Discovery Provide details of vSphere environment, with or without vCenter & select VMs and their disks, for help protect. 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 help protect of the infrastructure, including protected workloads, InMage component health, and more. Detailed views of help protect, including RPO, Recovery Windows, Consistency Points and more. So how does it work? Well, firstly, you provide the details of your target vSphere environment. This would be ESXi directly, or via vCenter. With appropriate credentials provided, you’ll see a list of VMs returned. You, as the admin, have the ability to select the appropriate VMs for protection, and additionally, select the VM disks that you would like to include, or exclude. <click> After providing the vSphere information for the target site, there’s a few more simple selections to make, such as the Process Server that will be used to collect the replication data from the Data Taps on the respective protected VMs. You can also provide information around retention size, drive, time scales and more. Finally, you’ll select a target datastore to store the VMs, in the recovery site. Admins also have additional granularity around retention, folder structure, compression, traffic encryption, resource pools and provisioning. Note, some of these settings are specific to a vSphere environment, demonstrating InMage’s integration points with VMware’s solutions. Once enabled, it’s important to keep an eye on what’s happening in the environment. Fortunately, Scout’s rich dashboard makes that easy, providing visual representation for important data, making it easy for the admin to understand the health of the overall infrastructure, key InMage components, and protected workloads. You’ll see detailed views for protection, including valuable Recovery Point Objective information, info on recovery windows, consistency points and much more. <next slide> © 2012 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.

Azure Site Recovery | InMage Scout
11/11/2018 Azure Site Recovery | InMage Scout Efficient Recovery 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 older. Readiness check is then performed to help make sure VM can be recovered successfully. VM Configuration VM settings can be modified, including additional CPUs, memory, or a change in network configuration. Orchestrated Recovery Granular options to help make sure VMs start in a particular Recovery Order. Recovery can be triggered now, or set for later. Multiple VMs can be recovered in batches. So that was protection, but what about recovery? Well, again, InMage Scout makes it easy. As you’ll see, in this simple wizard, simply select the VMs that have been protected, and choose a recovery point. You have the choice of selecting the latest consistent point, very latest crash consistent time, or a previous point in time. The readiness check is then performed, ensuring the VM can be recovered successfully based on your selected parameters. <click> As mentioned earlier, you have the opportunity to adjust the VM settings to reflect how you want the VM to look when it starts on the recovery site. This provides administrators with extra levels of flexibility, with the ability to adjust CPU, Memory and networking configurations… …and as you can see, you could switch to DHCP, change the static IP, attach to a different VM network etc. The recovery is then orchestrated. As you can see, you have the opportunity to adjust the order in which VMs start up, known as the recovery order, which is helpful when dependencies exist between different VMs. Think of a 3 tier app – you’d want your DB to start first, followed by an application tier, then a web front end. The recovery order helps to control this, and provides options to recovery now, or schedule for a later time, for added flexibility. <next slide> © 2012 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.

11/11/2018 Microsoft Azure Site Recovery VMware Replication – Architecture Integrated Software-Based VM Replication Powered-off recovery VMs are created identical to the protected VMs. The VMDKs are also created in the same size as the source VMDKs and attached to the Master Target. Continuous replication between the corresponding VM and Master Target VM. When replication is stopped, the recovery VMDKs are detached from the Master Target and are correctly assigned to the now powered on recovery VMs. Upon site failure, VMs can be started on secondary site Once replicated, changes replicated continuously Once Replication is started, VMs begin replication Primary Site Secondary Site Process Server Replicated Changes Initial Replica Master Target VMDK VMDK © 2012 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.

11/11/2018 Disaster Recovery For VMware Between on-premises and/or service provider locations Microsoft Azure Site Recovery Primary Site VMware/Physical Recovery Site Download InMage Scout Replication channel: InMage Scout © 2012 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.

ScoutCloud – Primary Server Discovery

ScoutCloud – Azure Target Discovery

ScoutCloud – Replication Settings

ScoutCloud – Monitoring

ScoutCloud – Migration Cut-over Settings

ScoutCloud – VM and Endpoint Configuration

ScoutCloud – Migration Cut-over

Azure Site Recovery One Solution for multiple infrastructures 1 2 3 4
11/11/2018 Azure Site Recovery One Solution for multiple infrastructures Hyper-V to Hyper-V (on-premises) 1 Hyper-V Replication Hyper-V to Hyper-V (on-premises) 2 Hyper-V Replication SAN Hyper-V to Microsoft Azure 3 Hyper-V Microsoft Azure Replication VMware/Physical to VMware (on-premises) 4 VMware/Physical VMware Replication VMware/Physical to Microsoft Azure 5 VMware/Physical Microsoft Azure Replication We’ve looked at all 5 scenarios that fall within ASR now, and hopefully what you’ve gleaned from this, is that there fantastic coverage for a wide range of different infrastructures. For a quick recap, for customers who have multiple sites, or work with a service provider as a secondary site, and Hyper-V is running on both sites, they can take advantage of Azure Site Recovery to orchestrate the replication and recovery between those sites. In that example, the engine of replication will be Hyper-V Replica, an inbox VM replication technology that’s built into Windows Server 2012 and 2012 R2. For customers with an investment in SAN technology, that includes replication in the box, through integration with Hyper-V, System Center and Azure Site Recovery, customers can orchestrate the replication and recovery of their key workloads between those sites, this time, harnessing the power of the SAN, through asynchronous or synchronous replication, to transfer data between sites. For customers who don’t have a second site, and are running Hyper-V on their primary site, using Azure Site Recovery, customers can orchestrate the replication and recovery of their on-premises workloads, into the Microsoft Azure datacenters, enabling this as a target for failover in the event of a disaster. The engine of replication in this example is Hyper-V Replica. What about customers who don’t have Hyper-V within their datacenters? Well, as we mentioned at the start of the presentation, with the acquisition of InMage, under the umbrella of Azure Site Recovery, customers can orchestrate the replication and recovery of key workloads from physical, or VMware-based sites, over to a secondary site, running VMware also. This time, InMage Scout is providing the replication engine, and is transferring the data between the two on-premises locations. Finally, just like we saw earlier, where a customers without a secondary location, could use ASR to replicate and recover Hyper-V-based VMs into Azure, with the new InMage technologies, in the future, you will be able to replicate and recover VMware-based VMs into Microsoft Azure. Again, this will be powered by InMage Scout. <next slide> Protect important applications by coordinating the replication and recovery of private clouds across sites. Protect your applications to your own second site, a HSP’s site, or even use Microsoft Azure as your disaster recovery site © 2012 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.

11/11/2018 Azure Site Recovery One Solution for multiple infrastructures | Positioning SOURCE HOST TARGET REPLICATION AVAILABILITY Hyper-V (2012 or 2012 R2) Inbox Hyper-V Replica Today Hyper-V (2012 R2) Microsoft Azure SAN Replication October (Preview) Hyper-V (2012) Future Hyper-V (2008 or 2008 R2) Hyper-V or Azure InMage Scout SOURCE HOST TARGET REPLICATION AVAILABILITY VMware or Physical VMware InMage Scout Today Microsoft Azure Future Hyper-V 2012 R2 So how do we position the different capabilities for different scenarios? Well, if we look at the table at the top, you’ll see, for customers and partners who are running Hyper-V, either as part of Windows Server 2012, or 2012 R2, and wish to replicate, and recover their key workloads to another on- premises location, also running Hyper-V, they can harness the power of ASR to orchestrate, monitor and manage the replication and recovery between those locations. This is harnessing the inbox Hyper-V Replica engine for the replication of data between the 2 sites. However, if a customer has an existing investment in a Storage Area Network, or SAN, many advanced SAN’s include replication capabilities. Some offer this as an included feature, whilst others offer a licensed add-on. Either way, if a customer has an existing investment in SAN replication, which replicates data between 2 identical SANs, between on-premises locations, with ASR in October, we’ll be able to harness this replication channel for replication and recovery of your data. Through engineering integration between System Center Virtual Machine Manager, Azure Site Recovery and our hardware partners, customers will be able to utilize their existing investments in SAN replication, configured and managed through SCVMM and ASR, to replicate, and recover key workloads between on-premises locations. For customers looking to utilize Microsoft Azure as a secondary location, as we learnt earlier, currently in preview is a capability of ASR to replicate and recover your on-premises, Hyper-V-based workloads, into Microsoft Azure. The general availability of this solution is October, but customers can access the preview up to that time. The replication engine to send data between your on-premises locations and Microsoft Azure, in this case, is Hyper-V Replica. Today, this capability is only available for use with Hyper-V in Windows Server 2012 R2, however going forward, the capabilities will be unlocked for customers utilizing Hyper-V in Windows Server 2012. But what about customers who are running older versions of Hyper-V, that shipped as part of Windows Server 2008, or 2008 R2, where Hyper-V Replica wasn’t a feature? Well, the flexibility that InMage technologies bring to the table will enable us, in the future, to unlock those capabilities to enable replication and recovery, again using ASR, but this time, for Hyper-V hosts that are running 2008 or 2008 R2, with either Azure, or another on- premises location as the target for replication and recovery. The top table refers explicitly for workloads running on a Microsoft platform, but what about workloads that currently run on VMware, or still in a physical environment? If we look in the bottom table, as we discussed earlier, with the new InMage technologies, specifically InMage Scout, customers can download the InMage components and use them to orchestrate, manage and monitor replication and recovery from a VMware vSphere or physical environment, into another vSphere environment on-premises. That is available today. However, going forward, in the future, we’ll be bringing to market additional capabilities that allow organizations to utilize ASR to replicate and recover existing VMware, or Physical workload, into Microsoft Azure, which is extremely powerful, and flexible for customers. © 2012 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.

Next Steps: Transform your Datacenter
11/11/2018 Next Steps: Transform your Datacenter Learn more about Microsoft Protection & Site Recovery capabilities Learn more about Windows Server Backup Learn more about Microsoft Azure Backup Learn more about System Center Data Protection Manager Learn more about Microsoft Azure Site Recovery Microsoft Azure Site Recovery Wiki Page Download Windows Server 2012 R2 Evaluation Download System Center 2012 R2 Evaluation © 2012 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.

© 2014 Microsoft Corporation. All rights reserved
© 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista 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.

Azure Site Recovery DRaaS Technical Review Name Role Group 11/11/2018

Similar presentations

Presentation on theme: "Azure Site Recovery DRaaS Technical Review Name Role Group 11/11/2018"— Presentation transcript:

Similar presentations

About project

Feedback

Log in

Auth with social network:

Azure Site Recovery DRaaS Technical Review Name Role Group 11/11/2018

Similar presentations

Presentation on theme: "Azure Site Recovery DRaaS Technical Review Name Role Group 11/11/2018"— Presentation transcript:

Similar presentations

About project

Feedback