Building Disaster Recovery as a Service:
•Download as PPTX, PDF•
1 like•1,569 views
This document discusses business continuity challenges related to increasing data growth and insufficient data protection solutions. It presents Microsoft solutions for addressing these challenges, including Azure Site Recovery for orchestrated replication and recovery across on-premises and Azure environments. The solutions aim to automate processes, eliminate tape management, increase protection breadth and depth, and provide testable disaster recovery.
Recommended
More Related Content
What's hot
What's hot (20)
Similar to Building Disaster Recovery as a Service:
Similar to Building Disaster Recovery as a Service: (20)
More from Alexandre Verkinderen
More from Alexandre Verkinderen (9)
Recently uploaded
Recently uploaded (20)
Building Disaster Recovery as a Service:
- 2. Business Continuity Challenges Data growth's impact on business continuity Increasing costs Too many complications, problems and mistakes Business Continuity Not enough data retention Time-intensive media management Untested DR & decreasing recovery confidence Too much data with insufficient protection
- 3. Business Continuity Challenges Bypassing the obstacles Increasing costs Too many complications, problems and mistakes Business Continuity Not enough data retention Time-intensive media management Untested DR & decreasing recovery confidence Too much data with insufficient protection Automate, automate, automate Tighter integration between systems & availability / data protection Eliminate tape management Achieve cost and operations stability Increase breadth and depth of continuity protection Implement testable solutions for data recovery
- 5. 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
- 6. Microsoft Disaster Recovery Stack Compute Storage Networks
- 7. Orchestration and Replication: InMage Scout Microsoft Azure Site Recovery Primary Site InMage Scout Orchestration and Replication: Hyper-V Replica, SQL AlwaysOn Microsoft Azure Site Recovery Primary Site Hyper-V Microsoft Azure Site Recovery Orchestration Channel Replication channels: Hyper-V Replica, SQL AlwaysOn, SAN Primary Site Hyper-V Recovery Site Hyper-V Microsoft Azure Site Recovery Orchestration and Replication channel: InMage Scout Primary Site VMware / Physical Recovery Site InMage Scout InMage Scout Key features include: Automated VM protection and replication Remote health monitoring Near zero RPO No-impact recovery plan testing Customizable recovery plans Minimal RTO – few minutes to hours Orchestrated recovery when needed Replicate to – and recover in – Azure Heterogeneous physical and virtual support On-premises to Azure protection (Site-to-Azure) VMware / Physical VMware / Physical Download InMage Scout CY2015 Azure Site Recovery One solution for multiple infrastructures
- 9. Source: Hyper-V Workloads Target: Hyper-V Workloads Microsoft Azure Site Recovery HSP Data Center 1 HSP Data Center 2 DR OrchestrationDR Orchestration for Windows Server 2012+ Hyper-V Hosted Workloads to Second Site Extensible Data Channel
- 11. Source: Hyper-V Workloads Target: Hyper-V Workloads Microsoft Azure Site Recovery HSP Data Center 1 / CPS Stamp 1 HSP Data Center 2 / CPS Stamp 2 DR OrchestrationDR Orchestration Microsoft Azure Pack Integration Extensible Data Channel
- 12. Microsoft Azure Pack Integration
- 14. Azure Site Recovery SDK
- 16. Source: Hyper-V Workloads Hosted Workloads to Azure Target: Microsoft Azure Microsoft Azure Site Recovery HSP Data Center Microsoft Azure DR OrchestrationDR Orchestration for Windows Server 2012+ Hyper-V Extensible Data Channel
- 18. SCVMMMicrosoft Azure Pack Tenant 1 Subscription HSP Management Subscription HSP Billing Account VM Replication DRP DR Orchestration HSP Data Center Microsoft Azure Failover Hosted Workloads to Azure – Tenant Isolation Tenant 2 Subscription Tenant 1 Tenant 2 Tenant 2 Tenant 1 VM Replication
- 19. Hosted Workloads to Azure – Tenant Isolation
- 20. Customer Workloads to HSP Cloudfor Windows Server 2012+ Hyper-V Customer 1 DC HSP Data Center Customer 2 DC Target: Hyper-V Workloads Microsoft Azure Site Recovery DR OrchestrationDR Orchestration Extensible Data Channel
- 21. Customer Workloads to Azure Customer 1 DC Microsoft Azure Site Recovery Microsoft Azure Customer 2 DC DR OrchestrationDR Orchestration Target: Microsoft Azure for Windows Server 2012+ Hyper-V Extensible Data Channel
- 23. Source: VMware vSphere VMs & Physical Servers Hosted Workloads to Second Sitefor VMware vSphere-based VMs & Physical Servers Process Server Target: VMware vSphere VMs Config Server Master Target InMage Scout Data Channel Download InMage Scout Microsoft Azure Site Recovery Download InMage Scout RX Server Process Server – Used for Caching, Compression & Encryption Config Server – Used for Centralized Management of InMage Scout Master Target – Used as a repository & for retention Mobility Service – Captures all data writes from memory RX Server – Used for multi- tenant management
- 24. (Future) Hosted Workloads to Azure Microsoft Azure InMage Scout Data Channel Microsoft Azure Site Recovery Process Server – Used for Caching, Compression & Encryption Config Server – Used for Centralized Management of InMage Scout Master Target – Used as a repository & for retention for VMware vSphere-based VMs & Physical Servers Customer 1 Customer 2 Source: VMware vSphere VMs & Physical Servers Process Server Target: Microsoft Azure Mobility Service – Captures all data writes from memory
- 25. Customer Workloads to HSP Cloud HSP Data Center InMage Scout Data Channel Microsoft Azure Site Recovery for VMware vSphere-based VMs & Physical Servers Customer 1 Customer 2 RX Server Orchestration Orchestration Source: VMware vSphere VMs & Physical Servers Process Server Customer 1 Process Server Customer 2 Source: VMware vSphere VMs & Physical Servers Process Server – Used for Caching, Compression & Encryption Config Server – Used for Centralized Management of InMage Scout Master Target – Used as a repository & for retention Mobility Service – Captures all data writes from memory RX Server – Used for multi- tenant management
- 26. (Future) Customer Workloads to Azure Microsoft Azure InMage Scout Data Channel Microsoft Azure Site Recovery Process Server – Used for Caching, Compression & Encryption Config Server – Used for Centralized Management of InMage Scout Master Target – Used as a repository & for retention for VMware vSphere-based VMs & Physical Servers Source: VMware vSphere VMs & Physical Servers Process Server Customer 1 Process Server Customer 2 Source: VMware vSphere VMs & Physical Servers Mobility Service – Captures all data writes from memory Microsoft Azure Customer 1 Customer 2 Target: Microsoft Azure
- 37. Azure Site Recovery (ASR) Kit Grow your business with Disaster Recovery services Complete DR Solution Expand Your Services Get Started Quickly ASR enables hybrid disaster recovery solutions for both physical and virtual environments The ASR Kit is an on-premises and cloud solution backed by Azure The ASR Kit is available now, allowing you to rapidly add DR to your service portfolio Drive new revenue streams with premium DR solutions Improve SLAs with orchestrated recovery, automated replication, and reduced data loss Extend your reach with Azure’s global, geo-coverage Go-to-Market materials including value propositions and licensing guides Technical documentation so you can stand up DR services A large ecosystem of SI partners to help bring you to market
- 38. Pricing Guide Planning Guide Capacity Planner Tool Deployment Guide Configuration Tutorials WAN Optimization with Riverbed InMage Website ASR MSDN Forum Azure Feedback Forum – ASR User Voice ASR Wiki ASR Resources
- 40. Data protection challenges It’s expensive to protect all that data. Some data may go without protection. • Storage costs growing. • Backup costs scale with data
- 41. Introducing Windows Azure Backup • Offsite data protection in Windows Azure storage. • Data is encrypted and secure. • Efficient use of network and storage resources. • Enhances Microsoft backup tools with cloud backup capabilities.
- 42. Continuous backup and protection Data protection manager disaster recovery (with offsite replication and tape)Tape-based backup Disk-based recovery Up to every 15 minutes Windows Azure Backup Active Directory Hyper-V File Services Windows Client System Center Operations Manager System Center Data Protection Manager
- 43. Geo-replication Windows Azure Storage Defend against regional disasters
- 44. 4. Back up encrypted data 2. Install agent 1. Sign up 5. Recover to the same or a different server How Windows Azure Backup works Enterprises with System Center System Center DPM Server
Editor's Notes
- Windows Azure Backup is a new service in Windows Azure. In a nutshell, it provides simple and reliable server backup to the cloud. Another way to think about it is that it enhances existing Microsoft backup tools with cloud backup capabilities they haven’t had before. These cloud backups are efficient, and secure – two key properties to keep in mind when considering cloud services. But let’s look at the solution in more detail.
- So you can be sure that every piece of data that you store in the Azure Blob is available as well as protected against regional disasters (we call this geo-replication). Data is asynchronously copied to another datacenter that’s at least 400 miles away. Geo replication is a unique feature, that differentiates us. Hearing about cloud services and giant datacenters, it’s easy to become inured to the numbers. But think for a moment how much complexity and cost you’d introduce to your environment if you tried to implement a solution involving 6 copies of your data, and two datacenters 400 miles apart!