Disaster Recovery to the Cloud with Microsoft Azure
•
4 gostaram•7,078 visualizações
In this session, we will look into DR planning scenario to protect your workload with one solution for different infrastructure either hyper-v, vmware, storage or physical server.
Recomendados
Recomendados
Mais conteúdo relacionado
Mais procurados
Mais procurados (20)
Destaque
Destaque (7)
Semelhante a Disaster Recovery to the Cloud with Microsoft Azure
Semelhante a Disaster Recovery to the Cloud with Microsoft Azure (20)
Mais de Lai Yoong Seng
Mais de Lai Yoong Seng (20)
Último
Último (20)
Disaster Recovery to the Cloud with Microsoft Azure
- 1. Welcome to the Kuala Lumpur, Malaysia
- 2. Disaster Recovery to the Cloud with Microsoft Azure Lai Yoong Seng MVP Hyper-V | www.ms4u.info Yoongseng.lai@infrontconsulting.com Microsoft Azure
- 3. Agenda Challenges Microsoft Solutions
- 4. Top cool comments about DR We’re not big enough to justify a DR site We can get by while we rebuild We’ve never needed DR, so why would we now? We’ve got a Server in our branch office we can just use that The CEO told me to do itWe Backups We have a DR site but testing it is a major headache, so we’ve never done it It’s too hard It’s too expensive
- 5. DR Options
- 7. Microsoft Solutions Breadth & depth solutions for business continuity & disaster recovery Hyper-V Failover Clustering for VM Resilience 1 Hyper-V Guest Clustering for app- level HA, i.e. SQL Server AlwaysOn FCI 2 Centralized backup with Data Protection Manager 4 Simplified protection with Windows Server Backup 3 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
- 9. Protect your data Powerful solutions for Enterprise & SMB Simplified protection & recovery, built into Windows Server with Windows Server Backup Scalable, centralized backup with System Center Data Protection Manager Enhanced through integration with Microsoft Azure Backup
- 11. Site Recovery
- 12. What is Azure Site Recovery? Automated protection and replication of VMs Orchestrated Recovery Health Monitoring 1 3 2
- 13. What is Azure Site Recovery? Zero Impact recovery plan testing On-premises to on-premises protection On-premises to Azure protection
- 14. Transform the datacenter Orchestrated disaster recovery to a second site Microsoft Azure Hyper-V Recovery Manager Communication Channel Replication channel: Hyper-V Replica Primary Site Windows Server Recovery Site Windows Server
- 15. Transform the datacenter Orchestrated disaster recovery to a second site or to Azure Communication and Replication Microsoft Azure Site Recovery Communication Channel Replication channel: Hyper-V Replica Primary Site Windows Server Recovery Site Windows Server Microsoft Azure Site Recovery Primary Site Windows Server Key features include: Automated VM protection and replication Remote health monitoring Customizable recovery plans No-impact recovery plan testing Orchestrated recovery when needed
- 16. System Center 2012 R2 VMM What components are needed?
- 17. SAN Replication Harness the power of your SAN Investments Microsoft Azure Site Recovery Communication & Orchestration
- 18. Network Planning 192.168.111.1 192.168.111.254 192.168.112.1 192.168.112.254 192.168.113.1 192.168.113.254 192.168.114.1 192.168.114.254
- 19. Duplicate Network 192.168.111.1 192.168.111.254 192.168.112.1 192.168.112.254 192.168.113.1 192.168.113.254 192.168.114.1 192.168.114.254 192.168.111.4 192.168.111.254 192.168.112.4 192.168.112.254 192.168.113.4 192.168.113.254 192.168.114.4 192.168.114.254
- 20. 192.168.11.4 192.168.11.254 192.168.12.4 192.168.12.254 192.168.13.4 192.168.13.254 192.168.14.4 192.168.14.254 Hybrid Network 192.168.111.1 192.168.111.254 192.168.112.1 192.168.112.254 192.168.113.1 192.168.113.254 192.168.114.1 192.168.114.254
- 21. 192.168.111.4 192.168.111.254 192.168.112.4 192.168.112.254 192.168.113.4 192.168.113.254 192.168.114.4 192.168.114.254 Test Network 192.168.111.1 192.168.111.254 192.168.112.1 192.168.112.254 192.168.113.1 192.168.113.254 192.168.114.1 192.168.114.254 192.168.111.4 192.168.111.254 192.168.112.4 192.168.112.254 192.168.113.4 192.168.113.254 192.168.114.4 192.168.114.254 192.168.111.4 192.168.111.254 192.168.112.4 192.168.112.254 192.168.113.4 192.168.113.254 192.168.114.4 192.168.114.254
- 24. Heterogeneous disaster recovery Microsoft Azure Site Recovery Download InMage Scout Replication channel: InMage Scout Primary site VMware Physical Recovery site VMware InMage Scout to Azure OS-based replication for flexibility Supports VMware vSphere and Physical Servers as the source of replication Supports Microsoft Azure as target for replication and recovery Ideal for enterprises and service providers that already have VMware investments Orchestration and replication Microsoft Azure Site Recovery Primary site VMware Physical InMage Scout 2015
- 25. Contoso Primary Location (On-Premises/Service Provider) Source: VMware vSphere VMs & Physical Servers Heterogeneous Disaster Recovery for VMware vSphere-based VMs & Physical Servers with InMage Scout Process Server Contoso Secondary Location (On-Premises/Service Provider) Target: VMware vSphere VMs Config Server Master Target InMage Scout Data Channel Download InMage Scout Microsoft Azure Site Recovery Download InMage Scout Process Server – Used for Caching, Compression & Encryption Config Server – Used for Centralized Management of InMage Scout Master Target – Used as a repository & for retention
- 27. Summary
- 28. Azure Site Recovery One solution for multiple infrastructures Hyper-V to Hyper-V (on-premises) Hyper-V Hyper-V Replication Hyper-V to Microsoft Azure Hyper-V Microsoft Azure Replication VMware or Physical to VMware (on-premises) VMware/Physical VMware Replication VMware to Microsoft Azure VMware Microsoft Azure Replication Hyper-V to Hyper-V (on-premises) Hyper-V Hyper-V Replication SAN SAN Protect important applications by coordinating the replication and recovery of private clouds across sites. Protect your applications to your own second site, a hoster’s site, or even use Microsoft Azure as your disaster recovery site
- 29. Hyper-V (2012 or 2012 R2) Hyper-V (2012 or 2012 R2) Inbox Hyper-V Replica Today Hyper-V (2012 R2) Microsoft Azure Inbox Hyper-V Replica Today Hyper-V (2012 or 2012 R2) Hyper-V (2012 or 2012 R2) SAN replication Today (Preview) Hyper-V (2008 or 2008 R2) Hyper-V or Azure InMage Scout Future VMware or physical VMware InMage Scout Today VMware or physical Microsoft Azure InMage Scout Today (Preview) VMware or physical Hyper-V (2012 R2) InMage Scout Future Azure Site Recovery One solution for multiple infrastructures - Positioning
- 30. Your essential IaaS Series IaaS Fundamentals Dive Deep into Networking Storage and Disaster Recovery Scenarios Embrace Open Source Technologies to Accelerate and Scale Solutions Must View Resources
- 31. Fill in evaluation forms and win prizes! • Go to http://malaysia.azurebootcamp.net/ to access links to online evaluation forms • Direct link to this session’s evaluation form: http://www.instant.ly/s/Xuzwh • Please check with registration counter for your participant ID • Winner of each session will be announced after lunch break, afternoon coffee break and during closing • Winner then proceed to registration counter to draw prizes
- 32. Please share our “little” event on the WWW by any means Use the HASHTAG #GLOBALAZURE extensively
- 33. Thank You!
Notas do Editor
- Demo 1- Slide lost -Restore using Windows Backup -Supported client OS – Win 7, 8 and higher version & server OS- Win 2008 R2 above -Useful for mobile users Disaster Recovery to the Cloud with Microsoft Azure. In this session, we will look into DR planning scenario to protect your workload with one solution for different infrastructure either hyper-v, vmware, storage or physical server.
- Hot Sites A “proactive” hot site allows you to keep servers and a live backup site up and running in the event of a disaster. Basically, you replicate your production environment in our data center. This allows for an immediate cutover in case of disaster at your primary site. A hot site is a must for mission critical sites. Warm Sites A “preventative” warm site allows you to pre-install your hardware and pre-configure your bandwidth needs. Then, if disaster strikes, all you have to do is load your software and data to restore your business systems. Cold Sites A “recovery” cold site is essentially just data center space, power, and network connectivity that’s ready and waiting for whenever you might need it. If disaster strikes, our engineer and logistical support teams can readily help you move your hardware into our data center and get you back up and running.
- ….but let’s take a look at how Microsoft provide a breadth of options to help overcome those challenges and roadblocks…. <next slide>
- 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. <click> For application and data protection, Windows Server Backup offers an inbox, small scale, simple protection solution for key applications, file and VM data. <click> 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. <click> 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. <click> 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>
- So now we understand how our fabric, and also our guests can be more resilient, it’s important to understand how we can protect the key data that exists within the environment, and for that, we need to think about backup.
- Now when it comes to data protection, Microsoft has a number of key solutions that enable customers to recover quickly from human error, service outages and disasters. These solutions are cost-effective solutions that automate protection and recovery of key data and applications and are cloud-integrated for reliable off-site protection. On the left, you have Data Protection Manager, part of the System Center product. Data Protection Manager (DPM) enables disk-based and tape-based data protection and recovery for servers such as SQL Server, Exchange Server, SharePoint, virtual servers, file servers, and support for Windows desktops and laptops. DPM can also centrally manage system state and Bare Metal Recovery (BMR). It’s also enhanced, as you’ll learn shortly, through integration with Microsoft Azure. For smaller organizations, with less-complex protection requirements, Windows Server provides a powerful, in-box backup solution for protecting important data. Windows Server Backup provides a set of wizards and other tools for you to perform basic backup and recovery tasks for the server it is installed on, and, similar to DPM, has integration with Microsoft Azure Backup for reliable, off-site protection. <click> So, let’s dive a little deeper into each of these areas, starting with Data Protection Manager, to understand more of the key capabilities of the solution. <next slide>
- 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…
- Refer to https://msdn.microsoft.com/en-us/library/azure/dn469078.aspx VMM2012 SP1 & Hyper-V 2012 – only for on-premise to on-premise Linux- Centos, OpenSuse, SUSE, Ubuntu
- San array on both sites with replication license VMM 2012 R2 with UR5 SMI-S Provider Supported SAN -NetApp -EMC -3Par
- 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>
- 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>
- And so to wrap up.
- 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, a capability of ASR to replicate and recover your on-premises, Hyper-V-based workloads, into Microsoft Azure is now available. 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. 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.