AMicrosoft azure hyper v recovery manager overview
•Download as PPTX, PDF•
2 likes•649 views
This document discusses Windows Azure Hyper-V Recovery Manager, a service that protects virtual machines running in a private cloud by replicating them to a secondary site. It monitors the health of System Center Virtual Machine Manager clouds and orchestrates quick recovery of VMs if an outage occurs at the primary site. The service automates replication using in-box technologies and cloud-based recovery plans. It works by configuring protection through a recovery plan, replicating VMs from Site A to Site B using Hyper-V Replica, and enabling the recovery of services through the orchestrated failover of VMs if Site A fails. Customers can use it to reduce the impact of planned downtime when a secondary site is available.
Recommended
Recommended
More Related Content
Similar to AMicrosoft azure hyper v recovery manager overview
Similar to AMicrosoft azure hyper v recovery manager overview (20)
More from Abhishek Sur
More from Abhishek Sur (20)
Recently uploaded
Recently uploaded (20)
AMicrosoft azure hyper v recovery manager overview
- 1. Windows Azure Hyper-V Recovery Manager Anil Malkani
- 2. Agenda Business continuity challenges Introducing Windows Azure Hyper-V Recovery Manager How it works When to choose Windows Azure Hyper-V Recovery Manager Next steps
- 4. Introducing Windows Azure Hyper-V Recovery Manager Protects vital workloads running in your private cloud by replicating virtual machines to a secondary site • Monitors the health of System Center Virtual Machine Manager clouds • Orchestrates the quick recovery of virtual machines at your secondary site • Automates replication protection with in-box technologies and cloud-based recovery plans
- 5. Windows Azure Hyper-V Recovery Manager Continuous health monitoring • • Orchestrated recovery • • • Automated protection • • •
- 6. How it works: configure Sign up Create a recovery plan Site A System Center Virtual Machine Manager AD SQL Exch System Center Virtual Machine Manager Site B
- 7. How it works: create recovery plan Hyper-V Replica replicates virtual machines Health monitoring Create a recovery plan Create recovery plan Site A System Center Virtual Machine Manager AD SQL Exch Configure System Center Virtual Machine Manager Site B
- 8. How it works: recover from datacenter failure Create a recovery plan System Center Virtual Machine Manager Site B Create recovery plan Orchestrates recovery of services in the event of an outage AD SQL Exch
- 9. Flexible configuration options • Recovery plans are stored in Windows Azure • Select clouds to protect • Customize network mapping • Automatically enable replication of virtual machines • Test recovery plans • Monitor services
- 10. Secure communication Datacenter Hyper-V Recovery Manager Http SC Virtual Machine Manager
- 11. When to choose Windows Azure Hyper-V Recovery Manager If you: Have a secondary site available Use System Center Virtual Machine Manager Have currently unprotected workloads Can benefit from reducing the impact of planned downtime at your primary data center
- 12. Why choose Windows Azure Hyper-V Recovery Manager?
- 13. • Sign up for a Windows Azure account. • Enable Hyper-V Recovery Manager. • Register your System Center Virtual Machine Manager servers. • Configure the service. Hyper-V Recovery Manager charges per VM per year, and you are billed monthly. How to buy
- 14. Next steps Sign up Discover Explore Windows Azure Subscription www.windowsazure.com Configure protection and recovery of private clouds www.windowsazure.com/en- us/manage/services/recovery-services/ Recovery Services on Windows Azure www.windowsazure.com/en- us/home/features/recovery-services/
Editor's Notes
- The session will provide an introduction to Windows Azure Hyper-V Recovery Manager. We’ll start with a look at the challenges that businesses face delivering continuity of services. We’ll use these challenges throughout the session to reference the benefits that Windows Azure Hyper-V Recovery Manager delivers. We’ll then look at Windows Azure Hyper-V Recovery Manager, covering what it is and its major benefits. Next we’ll dive into a high-level overview of how Hyper-V Recovery Manager works, with visual diagrams. We’ll also explore its flexible configuration options as well as security features. Finally, we’ll look at a few questions to help determine whether Hyper-V Recovery Manager might be right for your environment, before ending with a general summary and some next steps to begin using Hyper-V Recovery Manager today. So let’s start with a look at the challenges that businesses face today when trying to maintain continuity of services.
- Businesses looking to protect their workloads face a number of difficult challenges. As with most aspects of business, there are Cost challenges. With business continuity, you need to balance the need to reduce downtime costs with the cost of investing in a disaster recovery solution. Some disaster recovery solutions with synchronous replication prove cost prohibitive to implement – and are rarely used for more than a few key applications. Another challenge comes with the constant Monitoring of services. Monitoring your business continuity solution requires management software and training. And to maximize the protection of a business continuity solution, you really nee some sort of remote datacenter and remote monitoring, further amplifying costs. While simple solutions like failover clustering provide a small level of local protection – and relatively simple recovery – more comprehensive solutions, especially those involving a remote secondary datacenter involve more complex recovery plans. The manual recovery of a service or workload, once it has failed, can be extremely time-consuming and complex. To do business continuity well requires constant testing to ensure procedures are up-to-date and that they work. Finally, businesses often must protect a wide variety of workloads – some of which are multi-tier, or dependent upon several other infrastructure services. (such as DNS, AD, etc.) The result? In most cases, this means only the most critical workloads are protected. Many applications that could benefit from protection go unprotected due to costs and complexity. So what’s the best way to addresses these challenges?
- Windows Azure Hyper-V Recovery Manager protects applications by coordinating the replication of virtual machines at a secondary location. Windows Azure Hyper-V Recovery Manager brings together… Hyper-V Replica asynchronous virtual machine replication capabilities in Windows Server and the Virtual Machine Manager component of system center … and combines them with the power of Windows Azure to provide site-to-site protection of your virtual machines and private clouds. This includes remote health monitoring and orchestrated recovery. Now let’s expand on these core functions.
- Hyper-V Recovery Manager provides three key functions: automated protection, continuous health monitoring, and orchestrated recovery. By integrating with established technologies that come with Windows Server 2012 and System Center, Hyper-V Recovery Manager can provide ongoing automated replication of virtual machines between two sites. It does this using Hyper-V Replica and System Center Virtual Machine Manager. Hyper-V Recovery Manager configures replication options from the management portal. Once configured, the in-box technologies take over using your existing network. No workload data is moved to Window Azure or passes through it. After configuring and setting up automated protection, Hyper-V Recovery Manager next monitors the virtual machines running within the cloud continuously with System Center Virtual Machine Manager. Hyper-V Recovery Manager only communicates with Virtual Machine Manager, looking at the state of the cloud and being ready to recover it in the event of a failure. The final function is to orchestrate the recovery of the virtual machines in the event of a failure, in a timely and orderly manner. When recovering virtual machines in a system center cloud, there is often a prescribed order that the virtual machines need to be started in to support the recovery of multi-tier services. For example: first infrastructure VMs, then the database tier, then the web tier, etc. Hyper-V Recovery Manager enables you to create these customized plans and store them in Windows Azure. Plans also enable you to test your recovery process. It’s always best to be prepared for a failure, and Hyper-V Recovery Manager makes it easy to test plans without disrupting running services - and then adjust those plans as necessary.
- Let’s step through how Hyper-V Recovery Manager works. To use the service, the first step is to create a Windows Azure account and sign in. Once you have signed in to the management portal, you can enable and then configure the service. There are a number of configuration options. At a high-level view, the management portal configures the System Center Virtual Machine Manager server, which in turn configures individual VMs for replication and monitoring.
- Once you’ve created recovery plans, they’re stored in Windows Azure. The replication and monitoring begins begins.
- With health monitoring in place, you’re protected against primary cloud or data center failure. In the event of a failure, Hyper-V Recovery Manager can orchestrate the recovery of the virtual machines according to the plan. Let’s look more at the flexibility of the Hyper-V Recovery Manager configuration options.
- Hyper-V Recovery Manager is configured from the Windows Azure Management Portal. Once you’ve created the Hyper-V Recovery Manager vault, you can drill down into specific configuration options. We’ve mentioned it before, but one key feature is the ability to create and store recovery plans in Windows Azure. These can be customized to your needs and provide the details on how virtual machine recovery will take place. You can also configure which clouds to protect. You may have more than one cloud; Hyper-V Recovery Manager enables you to choose the one you want to configure. You configure customized mapping between virtual machine networks on source and target Virtual Machine Manager servers. Network mapping is used during placement of a replica virtual machine. Replica virtual machines are placed on hosts, which have access to the virtual machine networks. When protection is enabled, the replica virtual machine connects to the virtual machine network. This ensures that when the machine fails over it is connected to the right network. Hyper-V Recovery Manager configures the System Center VMM server, which configures Hyper-V Replica on the physical servers running Hyper-V which host your individual VMs. This helps reduce the configuration and management you have to do manually on your own. You can also test these plans – without disrupting service. Recovery plans can include elements like ordering of virtual machine start-up, pauses, manual intervention steps scripts and other actions. Finally, you can monitor the service from the Windows Azure management portal, seeing what is protected and how the service is working. We’ve talked a lot about how the service communicates with your private cloud. Let’s look at how this communication is kept secure.
- There are three key items I want to talk about on this slide. First, only System Center Virtual Machine Manager communicates with Windows Azure. Your individual applications and servers never talk to Windows Azure. Nor does Windows Azure collect or store any workload data – that data doesn’t even pass through Windows Azure. Second, is support for proxies. If you want to use one, they’re supported, and you only need to configure outbound http from the System Center Virtual Machine Manager Server. Finally, all communication between Windows Azure and the Virtual Machine Manager is encrypted. Part of the configuration process involves the use of certificates to identify servers and encrypt traffic. We’ve talked about what Hyper-V Recovery Manager is, how it works, and the granular configuration. Now let’s talk about when you might use it.
- When considering Hyper-V Recovery Manager, there are some basic requirements. Because Hyper-V Recovery Manager can initiate and orchestrate site-to-site replication, you first need to have two sites available. Next, you need to be using or planning to use System Center Virtual Machine Manager 2012 or R2 and similarly recent versions of Hyper-V. Finally, if you have applications running in VMs that need protection – Hyper-V Recovery Manager may be right for you. The are limitations: The replication is asynchronous – and while this is fine for many workloads, it’s important to note. With WS2012 R2 you can adjust replication frequency to as often as every 30 seconds to help mitigate this limitation. Workload data needs to live in VHDs Hyper-V Recovery Manager can be highly beneficial to many organizations in protecting workloads that are going without protection today. As we think about the business challenges from earlier, let’s recap why you would choose Hyper-V Recovery Manager.
- Hyper-V Recovery Manager does not fit every scenario. If a customer needs synchronous replication, Hyper-V Recovery Manager is not a viable option because Hyper-V Recovery Manager is asynchronous only. When the customer’s workload data is living outside the VHD, this data cannot be replicated because Hyper-V Replica is the only supported replication mechanism and can only handle VHDs. If the customer needs support for physical servers, Hyper-V Recovery Manager cannot be used, as Hyper-V Recovery Manager only replicates System Center Virtual Machine Manager cloud virtual machines – there’s no support for physical machines. This could impact complex recovery scenarios where some infrastructure services, such as DNS or DHCP are living on physical servers. Finally, check the limitations of Hyper-V Replica. The Hyper-V Recovery Manager service shares Hyper-V Replica limitations. For example, guest clustering is not supported. (Although this can be mitigated by configurable, shorter replication windows if you have the bandwidth.)
- Hyper-V Recovery Manager addresses the challenges businesses face when looking to protect workloads. --It automates the replication of virtual machines using out-of-the-box features from a central management portal. --It provides continuous remote monitoring of services and, in the event of a failure of your private cloud, --…and orchestrates the recovery of workloads. Since Windows Azure Hyper-V Recovery Manager is easy to implement, it’s also cost effective. It’s building on out-of-the-box features to provide a recovery solution. These out-of-the-box features in Windows Server and System Center are designed to be easy to use, and Hyper-V Recovery Manager utilizes those features, making it simple to set up and configure. We mentioned earlier that monitoring workloads can be challenging. The complexity and time-consuming nature of manual recovery services was a key factor in why organizations do not protect some workloads. Hyper-V Recovery Manager provides remote monitoring of applications and easy-to-use monitoring tools. The flexibility of the service is shown in the way you can create recovery plans to orchestrate the recovery of applications. Hyper-V Recovery Manager can then take care of the recovery process. The other reason to choose Hyper-V Recovery Manager is something we’ve not really touched on yet. The service is built on Windows Azure; by building on the cloud service, the solution is capable of growing and scaling as you require it. Finally, let’s look at the next steps to start using Hyper-V Recovery Manager today.
- Let’s summarize what we have seen and how to get started (slide is pretty self explanatory). As of October, 2013, the service is in preview and available at a 50% discount. The regular base price in the US is $200 per VM per year. Discounts are available (for example for long term commitments and large Azure enterprise accounts). The Azure website provides more detailed information about pricing in other currencies and regions.
- To start using Windows Azure Hyper-V Recovery Manager, first sign up for an Windows Azure account, then visit the Windows Azure site to get a tutorial on how to configure Hyper-V Recovery Manager.
- Thank you for attending this session on Windows Azure Hyper-V Recovery Manager.