03 - Обеспечение доступности данных и приложений Михаил Войтко | Технический директор, Energy Time

Михаил Войтко Технический директор, Energy Time 10 лет в ИТ-индустрии mvoytko@en-ti.ru 10 лет в ИТ-индустрии Опыт работы в проектах по внедрению программных продуктов Microsoft у заказчиков среднего и крупного сегментов Экспертиза по частному облаку, Azure, EMS и Office 365. Тренер Программы обучения партнеров Microsoft

План Общие сведения о резервном восстановлении Сценарии использования Azure Site Recovery в OMS Демонстрация возможностей

40% компаний не восстанавливаются после краха Как правило, для бизнеса есть механизмы страхования. Какая политика защищает ваши ИТ- системы? According to the Federal Emergency Management Agency (FEMA), 40% of businesses hit by a disaster never reopen for business. And another 25% close within two years. Businesses today are more focused than ever on making sure they are covered in case of a disaster. And it’s not just natural disasters. Systems can go down for many reasons, whether it’s a break-in, a fire, or power outage. Most companies have insurance policies for their business—but what about an insurance policy for your data and IT systems? Recovering from a disaster is about getting your applications and systems back to where they were before the disaster. This can take days—even weeks without a proper disaster recovery solution in place. Disaster recovery solutions are designed to minimize downtime and help ensure business continuity when unexpected events occur. With disaster recovery solutions, you can dramatically reduce the amount of lost data, and you can be back online in hours or even minutes. But traditional disaster recovery solutions require significant capital investment in an off-site datacenter and ongoing IT maintenance costs. Sources: 1 Federal Emergency Management Agency, fema.gov Forty percent of businesses do not reopen after a disaster and another 25 percent fail within one year according to the Federal Emergency Management Agency (FEMA). http://www.fema.gov/protecting-your-businesses http://www.chamber101.com/2programs_committee/natural_disasters/disasterpreparedness/Forty.htm 1 Federal Emergency Management Agency, fema.gov

Зачем нужно резервное восстановление? Стоимость простоя Потерянная прибыль, сниженная продуктивность сотрудников, штрафы, другие санкции. Конкурентное преимущество Ваши конкуренты уходят вперед, пока вы восстанавливаете. Ответственность Высшее руководство компании понимает риски Ожидания На стыке надежности и скорости работы для всех затронутых ролей. Source: http://nationalpostnews.files.wordpress.com/2012/10/hurricane-sandy091.jpg Source: March 2013 M&M Forecast

Azure Site Recovery ASR предлагает единое DR-решение, работающее на разных платформах (Hyper-V, VMWare, Physical), разных облаках (публичное, частное и провайдерское) и на разных рабочих нагрузках для предоставления требуемых RTO/RPO с помощью разных каналов (Replica, Scout, SAN etc). Гетерогенное Гибридное Для разных нагрузок Простое Надежное Допустимое

Azure Site Recovery Одно решение для разных инфраструктур 1/9/2018 Azure Site Recovery Одно решение для разных инфраструктур Защита Локально-Локально Защита в Azure Microsoft Azure Site Recovery Подключение к облаку Канал репликации: Hyper-V Replica, SAN Основн ой сайт Windows Server Резервны й сайт Загрузка Scout Канал репликации: репликация через Scout Основно й сайт Physical/VMWare VMWare ASR Scout Microsoft Azure Site Recovery VMWare/Physical ASR Scout Управление и репликация: Hyper-V Replica Windows Server Управление и репликация: 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.

Microsoft Azure Site Recovery Одно решение для разных инфраструктур 1/9/2018 Microsoft Azure Site Recovery Одно решение для разных инфраструктур Hyper-V to Hyper-V (локально) 1 Hyper-V Replication Hyper-V to Hyper-V (локально) 2 Hyper-V Replication SAN Hyper-V to Microsoft Azure 3 Hyper-V Microsoft Azure Replication VMware or physical to VMware (локально) 4 VMware or physical VMware Replication VMware or physical to Microsoft Azure 5 VMware or physical Replication What are the different infrastructures that Azure Site Recovery can provide a solution for? Well first, 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. So let’s dive into each of these in more detail, starting with Hyper-V to Hyper-V replication and recovery with ASR. <next slide> Защита важных приложений через объединение и восстановление реплик частных облаков между сайтами Защита приложений на вашем вторичном сайте, на хостинге или в Azure © 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.

1/9/2018 OnPrem to OnPrem (Локальный ЦОД в другое размещение) (Hyper-V 2012 управляемый VMM с использованием Hyper-V replica) © 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.

1/9/2018 Управляемое резервное копирование В локальном размещении и/или у провайдера Microsoft Azure Site Recovery Communication Channel Replication channel: Hyper-V Replica Primary Site Windows Server Recovery Site Microsoft Azure Site Recovery was first introduced in January 2014, and helps customers to protect important services by coordinating the replication and recovery of System Center 2012 private clouds at a secondary location. Azure Site Recovery provides three key functions: automated protection, continuous health monitoring, and orchestrated recovery. Simple, Automated Protection Your environment can be protected by automating the replication of the virtual machines based on policies that you set and control. Site Recovery coordinates and manages the ongoing replication of data by integrating with existing technologies such as Hyper-V Replica, System Center, and SQL Server AlwaysOn. Continuous Health Monitoring Site Recovery monitors the state of System Center Virtual Machine Manager clouds continuously and remotely from Azure. When replicating between two sites you control, only the Virtual Machine Manager servers communicate directly with Azure - your virtual machines data and replication remains on your networks. All communication with Azure is encrypted. Orchestrated Recovery The service helps automate the orderly recovery of services in the event of a site outage at the primary datacenter. Virtual machines can be brought up in an orchestrated fashion to help restore service quickly, even for complex multi-tier workloads. Recovery plans are simple to create through the Azure management portal, where they are stored. The plans can be as simple or as advanced as your business requirements demand, including the execution of custom Windows PowerShell scripts and pauses for manual interventions. Networks can also be customized by mapping virtual networks between the primary and recovery sites. These plans can be tested whenever you like without disrupting the services at your primary location. Lets learn a little more about the process, and how easy it is to setup, configure, and execute… <next slide> Опции RPO с использованием Hyper-V Replica: 30 секунд, 5 минут, 15 минут © 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.

Локальный ЦОД-локальный ЦОД с Hyper-V Replica Заказчик выбирает регион Создать хранилище 1 Пошаговая инструкция Быстрый старт 2 Регистрация вашего VMM сервера Регистрация 3 Определение политик Настройка защиты 4 Назначение сети для DR Сетевая часть 5 Репликация дисков на целевое хранилище Защита ВМ 6 Назначение DR плана Создание плана восстановления 7 Тестирование Запуск и тестирование 8

1/9/2018 Пошаговые инструкции: http://azure.microsoft.com/en-us/documentation/articles/site-recovery-vmm-to-vmm/ © 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.

Microsoft Azure Site Recovery 1/9/2018 Microsoft Azure Site Recovery Как это работает: Начальная настройка 1. Вход Основной сайт System Center Virtual Machine Manager 2. Создать хранилище и подготовить сертификат 3. Импорт сертификата и установка провайдера 4. Метаданные VMM управляются через Azure Site Recovery, по HTTPS 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> System Center Virtual Machine Manager Резервный сайт © 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 1/9/2018 Microsoft Azure Site Recovery Как это работает: Настройка защиты и назначение сети Основной сайт AD System Center Virtual Machine Manager SQL 7. Настройка защиты в облако LOB 5. На локальном сайте создание облака VMM и самих ВМ 9. Переключение сети с основного на резервный сайты 8. Контроль состояния здоровья 6. На вторичном сайте создание облака VMM <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> System Center Virtual Machine Manager Резервный сайт © 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 1/9/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 via self-service. Clouds are also a container object for Site Recovery, containing the VMs that you wish to 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 ensure 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 new static IP address into the VM upon failover. © 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 1/9/2018 Microsoft Azure Site Recovery Как это работает: Завершение защиты Основной сайт 10. Добавление защиты для ВМ в консоли VMM или на портале Azure AD System Center Virtual Machine Manager SQL LOB 11. ASR выбирает подходящие хосты, которые соответствуют требованиям и запускает репликацию с использованием механизма Hyper-V Replica Engine 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> System Center Virtual Machine Manager Резервный сайт AD SQL LOB © 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 1/9/2018 Microsoft Azure Site Recovery Как это работает: Завершение защиты Добавление защиты ВМ Use Azure Portal, VMM GUI or PowerShell to enable VM protection within configured clouds. Пример PowerShell: $cloud = Get-SCCloud -Name “CloudName” Get-SCVirtualMachine -Cloud $cloud | where {$_.IsDRProtectionRequired -eq $false} | Set-SCVirtualMachine –DRProtectionRequired $true -RecoveryPointObjective “TimeInSeconds” В результате инициируется реплика Site Recovery automatically configures Hyper-V Replica for the selected VMs, between your protected and recovery clouds. © 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 Hyper-V Replica—механизм репликации 1/9/2018 Microsoft Azure Site Recovery Hyper-V Replica—механизм репликации Встроенная в сервер программная логика репликации ВМ: построено на Windows Server 2012 R2 Hyper-V. Частота репликаций 30 секунд, 5 минут и 15 минут. Безопасная репликация по сети, защищено сертификатами. Гибкое решение, которое можно построить на разном сетевом железе, серверах или хранилище. Дешевле – нет необходимости добавлять другие технологии репликации ВМ. Постое управление и настройка - через Hyper-V Manager, Windows PowerShell или Azure Site Recovery. Once replicated, changes replicated on chosen frequency Once Hyper-V Replica is enabled, VMs begin replication После краха основного сайта, ВМ могут быть запущены на вторичном сайте Основное размещние Резервный сайт Реплцируемые изменения Стартовая реплика 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> CSV хранилище Хранилище SMB Share © 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 1/9/2018 Microsoft Azure Site Recovery Как это работает: Планы восстановления Основной сайт AD System Center Virtual Machine Manager SQL LOB 12. Создать план восстановления 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> System Center Virtual Machine Manager Резервный сайт AD SQL LOB © 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 1/9/2018 Microsoft Azure Site Recovery Управление с использованием Планов восстановления Планы восстановления состоят из одной или нескольких упорядоченных групп, содержащих защищенные виртуальные машины или группы репликации (для репликации сети SAN). Отработка отказа для виртуальных машин осуществляется в соответствии с условиями групп. Для виртуальных машин в определенных группах отработка отказа выполняется одновременно. Работа со скриптами Скрипт может быть добавлен для запуска Scripts до или после добавления группы ВМ в план восстанолвнения. Скрипты могут использоваться например для интеграции с SQL Server AlwaysOn. Ручные действия Ручные действия также могут быть добавлены при необходимости. © 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 1/9/2018 Microsoft Azure Site Recovery Как это работает: Создание планов восстановления Основной сайт System Center Virtual Machine Manager AD SQL LOB AD SQL LOB 13. Выполнение плана восстановления 16. Когда закончится репликация, ВМ можно запускать становится актуальными на основном сайте 15. Когда первичный сайт снова запускается, стартует механизм обратной репликации 14. Site Recovery управляет ВМ <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> System Center Virtual Machine Manager Резервный сайт AD SQL LOB AD SQL LOB © 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 1/9/2018 Microsoft Azure Site Recovery Реализация планов восстановления Test Failover Проверка стратегии репликации или анализа работы системы аварийного восстановления. Не приводит к потерям данных и простоям. Не оказывает влияния на репликацию. Не оказывает влияния на рабочую среду Unplanned Failover Такая обработка отказа необходима, когда основной сайт становится недоступным из-за неожиданного инцидента, например из-за сбоя питания. Planned Failover Отработка отказа для обеспечения непрерывного выполнения рабочих нагрузок во время прогнозируемых неблагоприятных обстоятельств, например при плановых отключениях питания или экстремальных погодных условиях. © 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.

1/9/2018 OnPrem to Azure (Локально в Azure) (Hyper-V 2012 R2 управляемый через VMM) © 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.

1/9/2018 Управляемое резервное копирование Для машин Hyper-V между локальным размещением И Microsoft Azure Communication and replication Microsoft Azure Site Recovery Primary Site Windows Server * Требует Requires Azure account и Azure Storage account Канал репликации: Hyper-V Replica 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> RPO на основе Hyper-V Replica: 30 сек, 5 мин, 15 мин © 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.

Virtual Machine, Storage & Network 1/9/2018 Ключевые компоненты Защита локальной среды в Azure (Site-to-Azure) Virtual Machine, Storage & Network Microsoft Azure Azure Site Recovery Orchestration Azure Site Recovery follows service oriented architecture composed of three key components: Azure Site Recovery protection & recovery experiences are in the Azure Management Portal, which provides a single management interface for customers managing all Azure assets across multiple disaster recovery sites with 24/7 access anywhere, everywhere. Azure Site Recovery Provider is an on-premises component which is installed on the System Center Virtual Machine Manager (VMM) server and connects to the Azure Site Recovery service by making only outbound connections. The provider needs to connect to the Internet and can leverage an on-premises proxy server thereby removing the need for a direct Internet connection from VMM server. Azure Recovery Service Agent is an on-premises component installed on each of the Windows Hyper-V Server hosting virtual machines for on-premises to Azure protection. The agent needs to connect to the Internet and can leverage an on-premises proxy server thereby removing the need for a direct Internet connection from the Hyper-V server. Compute Storage Networks Agent Orchestration & Replication Channel Локально © 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.

Когда применять Azure как DR site 1/9/2018 Когда применять Azure как DR site DR в Azure Восстановление приложений в 1 клик Восстановление в случае реальных аварий– пожар, землетрясение. Реализация требований без закупки резервного катастрофоустойчивого ЦОД Управляемое предупреждение аварий – угрозы ураганов Создание гибридных сред Планируемая миграция в облако © 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.

1/9/2018 Пошаговая инструкция: https://azure.microsoft.com/en-us/documentation/articles/site-recovery-vmm-to-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.

Агенты Agent Name Why Is It Required? Microsoft Azure Site Recovery Provider Over all Disaster recovery orchestration. ASR communicates with ASR Provider installed on VMM. If ASR provider or VMM is not able to reach internet (Azure ASR service) – the E-E replication still continues. Microsoft Azure Recovery Services Agent Channel from Host to Azure. Hyper-V tracks the data churn in the form of HRL (Hyper-V replica logs) MARS Agent transfer the HRL from Host to Protection Service. During failback – MARS Agent can get data from Azure and create the VHD. Needs to be installed on every host in a cluster also.

Локально в Azure Филиал в Azure (Hyper-V 2012 R2 без VMM) 1/9/2018 Локально в Azure Филиал в Azure (Hyper-V 2012 R2 без VMM) © 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.

Управляемое резервирование для Hyper-V ВМ, между локальными сайтами 1/9/2018 Управляемое резервирование для Hyper-V ВМ, между локальными сайтами И Microsoft Azure Communication and replication Microsoft Azure Site Recovery Primary Site Hyper-V Host * Требует Azure account и Azure Storage account Канал репликации: Hyper-V Replica 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> RPO : 30 сек, 5 мин, 15 мин © 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 Клиент выбирает регион хранения Создание хранилища 1 Пошаговая инструкция Быстрый старт 2 Группа серверов в основном размещении или филиале. Создание сайта 3 Регистрация Hyper-V Server Регистрация 4 Определение политики защиты Настройка защиты 5 6 Репликация данных в Azure Защита ВМ DR Планы Создание планов восстановления 7 8 Тестовое восстановление Выполнение тестирования

1/9/2018 Пошаговая инструкция: https://azure.microsoft.com/en-us/documentation/articles/site-recovery-hyper-v-site-to-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.

Выполнение резервного копирования сайта Hyper-V через ASR

Локальные сайты (VMware) 1/9/2018 Локальные сайты (VMware) © 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.

Гетерогенная среда VMware vSphere ВМ и физические сервера с ASR Scout 1/9/2018 Гетерогенная среда VMware vSphere ВМ и физические сервера с ASR Scout Microsoft Azure Site Recovery Загрузить ASR Scout Реплики и управление: ASR Scout Replication Primary site VMware/Physical Recovery site VMware ASR Scout All of the 3 previous examples have showcased how Azure Site Recovery provides a scalable, feature-rich solution that enables orchestrated replication & recovery between Hyper-V based datacenters, however, with the acquisition of InMage, Microsoft now provides replication and recovery for organizations who have datacenters, either their own, or those of service providers, based either on VMware vSphere, or still using pure-physical hardware. With these new heterogeneous capabilities, this acquisition will accelerate our strategy to provide hybrid cloud business continuity solutions for any customer IT environment, be it Windows or Linux, physical or virtualized on Hyper-V, VMware or others. Going forward, Microsoft is working to integrate InMage Scout with Azure Site Recovery, to extend the capabilities to replicate and recovery of VMware-based VMs, along with physical hosts, from on-premises locations, into Azure, for either a temporary period in the event of a failover, or for a permanent migration. However, today, customers who license Azure Site Recovery will have the ability to download the InMage Scout software, install and configure on their on-premises locations, with support for replicating and recovering between those locations. InMage operates within the OS layer, rather than at the virtual disk layer, thus customers install the lightweight InMage agent inside the OS, either virtualized on VMware vSphere, or a physical OS, and configure, centrally, for replication to a VMware vSphere-based VM in another location. <next slide> ASR Scout: Репликация ОС Поддержка VMware vSphere и физических серверов как источника репликации Поддержка VMware vSphere как целевого сайта для восстановления © 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 - Scout 1/9/2018 Azure Site Recovery - Scout 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 - Scout Streamlined Protection 1/9/2018 Azure Site Recovery - Scout Streamlined Protection Primary server discovery: Administrator provides details of vSphere environment, with or without vCenter and select VMs and their disks, for protection. Provide target vSphere information, select a particular Process Server, retention values and target datastore on the secondary site. Advanced replication settings: Granular replication controls for retention, folder structure, compression, encryption, resource pools and provisioning. 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> Rich monitoring: Deep insight into protection of the infrastructure, including protected workloads, and InMage component health. Detailed views of protection, including RPO, recovery windows, and consistency points. © 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.

1/9/2018 Пошаговые инструкции: https://azure.microsoft.com/en-us/documentation/articles/site-recovery-vmware-to-vmware/ © 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.

Поддерживаемые ОС 64-bit и 32-bit (если доступно) версии: Windows Server 2012/R2, 2008/R2 и 2003/R2 Red Hat Enterprise Linux 5, 6 CentOS 5, 6 SUSE Linux Enterprise Server 10, 11 Oracle Linux 5, 6

Поддерживаемые платформы Платформа Версия vCenter vCenter Server 5.5 & 5.1 vSphere ESX ESXi 5.5, ESXi 5.5U1, ESXi 5.1 vSphere CLI vSphere CLI 5.5 & 5.1 CS and PS Windows Server 2012 R2 64-bit Master Target Server Windows: Windows Server 2008 R2 Windows Server 2012/R2   Linux: CentOS 6.4 64-bit RHEL 6.4 64-bit

1/9/2018 Microsoft Azure Site Recovery - Итоги Одно решение для разных инфраструктур Hyper-V to Hyper-V (локально) 1 Hyper-V Replication Hyper-V to Hyper-V (локально) 2 Hyper-V Replication SAN Hyper-V to Microsoft Azure 3 Hyper-V Microsoft Azure Replication VMware or physical to VMware (локально) 4 VMware or physical VMware Replication VMware or physical to Microsoft Azure 5 VMware or physical Replication What are the different infrastructures that Azure Site Recovery can provide a solution for? Well first, 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. So let’s dive into each of these in more detail, starting with Hyper-V to Hyper-V replication and recovery with ASR. <next slide> Защита важных приложений через объединение и восстановление реплик частных облаков между сайтами Защита приложений на вашем вторичном сайте, на хостинге или в Azure © 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.