4. Turn on…. Calm restored ….

8. Application within DC failure DC location failure Loss of access from / to your office location

14. Inbox replication Application agnostic Storage agnostic

17. DR Orchestration Extensible Data Channel (Hyper-V Replica) Azure Site Recovery

21. Names of the service providers MS are endorsing, along with log’s to be added.

22. What DR failover goals must be meet Do you need to support all DC operations or only certain applications Do you need to meet data sovereignty requirements Is it important the location of your data is exactly known What amount of data loss is acceptable (replication interval) Do you want to build and maintain your own recovery SoP’s or take a managed solution

23. Great option if you already have more than one location (DC) Low cost – primary costs are MS ASR fee Potentially complex creation of recovery plans and failover process Great if you do not have a second location (DC) Very simple initial setup and maintenance Costs are lower than many other in market DR solutions Potential data sovereignty considerations (if no Azure DC’s are in region) Potentially complex creation of recovery plans and failover process Great if you do not have a second location (DC) Potentially complex setup Excellent solution for meeting regulatory or data sovereignty requirements Fully managed experience, no recovery plan creation or failover planning required

25. Planning Registration Capacity Planning Pre-reqs Configure Cloud Configure Networks Storage Protect Identify Candidate Apps Enable Protection Recovery Plans Monitor Jobs Resources Recovery Drill – DR testing Planned Failover Unplanned Failover

26. Unit that fails over together Defines a collection of VM that will be recovered together. Typically models an application. Dependency modelling Specify the order in which the VMs of a recovery plan need to be booted by using groups. VMs of same group failover in parallel. Shutdown is in reverse order of recovery to ensure 0 data loss. Extensible Recovery plans Add custom actions to a recovery plan in between the groups. Manual actions for those that cannot be automated. PowerShell scripts that can be executed on the VMM.

27. Test Failover Recover the VM onto the secondary site without affecting the primary site workload. VM can come up in an isolated environment or a predefined environment. Planned Failover Recover VM by safely turning off the VM on the primary site and sending latest changes. Ensures 0 data loss. VM boots up on the secondary site. Active location changes to secondary VMM. Unplanned Failover Without primary site operations Recover VM when the primary site is no longer reachable. May have data loss. VM boots up on the secondary site. Active location changes to secondary VMM. Unplanned failover with primary site operations Attempts to shutdown VM and send latest changes. If attempt fails, goes ahead with the recovery to ensure better RTO.

30. VMM VersionHyper-V Host VersionHRM Support VMM 2012 R2Windows Server 2012 R2 Or Windows Server 2012 VMM 2012 SP1Windows Server 2012

31. VMM Topology ASR Support Single VMM with Two Sites or more sites (e.g. Branch Office-Head Office setup) Two Sites with Dedicated VMM for each site More than two sites with Dedicated VMM for each site and pair-wise DR configuration

33. 192.31.24.1 215.67.238.2 172.168.1.1 10.1.1.2 Host4.myinternalAD.com HHost20.ServiceProviderAD.com

37. http://www.microsoft.com/en-us/download/details.aspx?id=39057

43. Site to Site VPNWeb-app publishingVirtual desktop Maintain or establish a VPN to your second site Seamless failover for users Potential limit of 400Mbps If using HNV gateway with Windows server 2012 R2 Potentially complex to deploy for remote users or multiple branch offices Excellent solution for web-only application access Requires DNS update planning Provides access in the “all lights out” scenario Potentially a service provided by your DR service provider Does not consume resources while in normal (non-failover) operation Potentially a cost overhead consideration

50. Agent in guest or on physical machine Broker on your site acts as aggregator for all agents Agent in guest replicates all disk IO operations Guarantee's integrity of replicated VHDx Replicated over the Internet securely Broker on service provider receives and writes out to VHDX’s VHDx’s mounted into VM’s Recovery plans created

55. www.microsoft.com/learning http://developer.microsoft.com http://microsoft.com/technet http://channel9.msdn.com/Events/TechEd