Business Continuity and DR Alexandre Brisebois Azure Technical Solutions Professional B....
-
Upload
rebecca-eaton -
Category
Documents
-
view
213 -
download
0
Transcript of Business Continuity and DR Alexandre Brisebois Azure Technical Solutions Professional B....
Business Continuity and DR
Alexandre BriseboisAzure Technical Solutions Professional
B. alexandrebrisebois.com
T. @brisebois
Business continuity challengesImpact of data growth on business continuity
Higher costs as data size and number of virtual machines increase
Complexity of protecting data and applications
Business continuit
y
Long data-retention requirements
Time-intensive media management Roadbloc
k
Untested disaster recovery and decreasing recovery confidence
Too much data—often with insufficient protection
Too much data—often with insufficient protection
Roadblock
Business continuity challengesBypassing the obstacles
Costs scale with data size and number of VMs
Protecting data and applications is complex
Business continuit
y
Long data retention requirements
Time-intensive media management Roadbloc
k
Untested DR and decreasing recovery confidence
Integrate solutions which scale with data and VMs
Eliminate media management
Achieve cost and operations stability
Increase breadth and depth of protection
Implement testable solutions
Automate, automate, automate
RPO | RTO Explained
Secs
MinsHours
DaysWeeks
Weeks
Days
Hours
MinsSecs
SynchronousCDP
Near CDP
Snap Shot
Tape Backup CDP
Azure
Recovery Point Objective (RPO)
Recovery Time Objective (RTO)Time Required To Resume
Data Lost
Minimize Downtime & Data Loss
deduplication
Tape
Hybrid Cloud DR Solution
Site to SiteDisaster Recovery
Migration toAzure
Disaster Recovery In Azure
DRaaS
Azure Site Recovery One solution, multiple infrastructures
Site to Site protection of physical assets
Wide range of Windows and Linux operating systems supported
Storage agnostic
Automated orchestration of recovery into Azure
Remote health monitoring
Wide range of hypervisor support including Hyper-V, VMware
Unified user interface shows both physical and virtual assets
assets in Azure and private cloud
Seamlessly replicate and protect assets in Azure and the private cloud
Virtual
Hybrid CloudCloud
Physical
Manage on premises infrastructure alongside
Our Technology
2 Tier - Host Offload Architecture
Network Based
WAN Optimization
Encryption
Block Level
Asynchronous
Continuous Data Protection (CDP)
Application Consistent
Server and Storage Agnostic
Orchestration and Replication
Microsoft Azure Site Recovery
Primary Site
InMage Scout
Orchestration and Replication
Microsoft Azure Site Recovery
Primary Site
Hyper-V
On-premises to On-premises protection (Site-to-Site)
Microsoft Azure Site Recovery
Orchestration
Replication
Primary Site
Hyper-V
Recovery Site
Hyper-V
Microsoft Azure Site Recovery
Orchestration and
Replication
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 Scout
NEW
Azure Site RecoveryOne solution for multiple infrastructures
Orchestrated disaster recoveryAcross on-premises, service provider locations or both
Microsoft Azure Site Recovery
Communication Channel
Replication channel: Hyper-V Replica
Windows Server
Windows Server
Enterprise / HSP Primary site
Enterprise / HSP Recover
y site
3. Copy registration key to SCVMM servers & install ASR Provider
Microsoft Azure Site RecoveryHow it works: Initial configuration
Primary site
System Center Virtual MachineManager
1. Sign up
System Center Virtual MachineManager
Secondary site
2. Create recovery vault and generate
registration key
4. VMM Metadata pushed to Azure Site Recovery, outbound, over HTTPS
Microsoft Azure Site RecoveryHow it works: Configuring protection and map networks
Primary site
System Center Virtual MachineManager
AD
SQLLOB
System Center Virtual MachineManager
Secondary site
5. On primary site, createclouds and add VMs
7. Configure protectionof clouds
6. On secondary site, create corresponding
recovery clouds
8. Continuoushealth monitoring
9. Map VM networks from primary to secondary
Virtual Machine Manager clouds: A cloud presents an abstracted view of pooled resources, and can be accessed through self-service.
Microsoft Azure Site RecoveryHow it works: Configuring protection of clouds and networks
Map virtual machine networks: Mapping between virtual machine networks on source and target VMM servers to ensure correct connectivity on failover.
Where virtual machines use static IPs and primary and secondary sites have different IP ranges, Azure Site Recovery integrates with VMM to automatically inject a new static IP address into the virtual machine upon failover.
Clouds are also a container object for site recovery, containing the VMs that you want to protect.Cloud configuration: Configuration of replication settings is streamlined, and includes setting frequency, recovery points, VSS-snapshot integration, compression, and initial replication.
Microsoft Azure Site RecoveryHow it works: Finalizing protection
Primary site
System Center Virtual MachineManager
AD
SQLLOB
System Center Virtual MachineManager
Secondary site
11. Azure Site Recovery selects a suitable host that meets requirements and starts
replication using the Hyper-V Replica engine
AD
SQLLOB
10. Enable virtual machine protection in
VMM or in Azure portal
Enable virtual machine protection: Use the Azure portal, VMM GUI or Windows PowerShell to enable virtual machine protection within configured clouds.
Microsoft Azure Site RecoveryHow it works: Finalizing protection
Replication initiates: Azure Site Recovery automatically configures Hyper-V Replica for the selected virtual machines, across your protected and recovery clouds.
Sample PowerShell script:$cloud = Get-SCCloud -Name “CloudName”Get-SCVirtualMachine -Cloud $cloud | where{$_.IsDRProtectionRequired -eq $false} |Set-SCVirtualMachine –DRProtectionRequired$true -RecoveryPointObjective “TimeInSeconds”
Integrated software-based VM replication: VM replication capabilities built into Windows Server 2012 R2 Hyper-V.
Configurable replication frequencies of 30 seconds, 5 minutes and 15 minutes.
Secure replication across network, by using certificates.
Flexible solution, agnostic of network, server and storage hardware on either site.
No need for other virtual machine replication technologies, reducing costs.
Automatic handling of live migration.
Simple configuration and management—either through Hyper-V Manager, Windows PowerShell, or with Azure Site Recovery.
Once Hyper-V Replica is enabled, VMs begin replication
Primary site Secondary siteInitial replica
Once replicated, changes replicated on chosen frequency
Replicated changes
Upon site failure, VMs can be started on secondary site
CSV onblockstorage
SMB Share
file-basedstorage
Microsoft Azure Site RecoveryHyper-V Replica—replication engine
Microsoft Azure Site RecoveryHow it works: Recovery plans
Primary site
System Center Virtual MachineManager
AD
SQLLOB
System Center Virtual MachineManager
Secondary site
AD
SQLLOB
12. Create recovery
plan
Orchestrated steps for recovery: Recovery plans help automate the orderly recovery in the event of a site outage at the primary datacenter.
Microsoft Azure Site RecoveryOrchestrated recovery using recovery plans
Manual actions: Manual actions can also be added, to run before or after a selected group. These require some form of physical interaction by a particular user before recovery plan continues.
Recovery Plans consist of a series of groups that contain a list of protected virtual machines. The order the VMs fail over is determined by the group they are within. VMs within a particular group fail over in parallel.
Recovery plans typically model an application that needs to start up, or failover, in a particular order.Script integration: Scripts can be added, to run before or after a specific group in a recovery plan. Scripts could also allow integration with SQL Server AlwaysOn fail over between sites.
Microsoft Azure Site RecoveryHow it works: Executing recovery plans
System Center Virtual MachineManager
Secondary site
AD
SQLLOB
Primary site
System Center Virtual MachineManager
AD
SQLLOB
13. Execute recovery plan
AD
SQLLOB
14. Azure Site Recovery orchestrates VMs starting on
secondary site
AD
SQLLOB
15. When primary site is back online, execute a reverse replication
16. When reverse replication completes, a planned failover returns active VMs to the primary site
Test failover: Verify that your recovery plan and virtual machine failover strategy are working as expected.
Microsoft Azure Site RecoveryExecuting recovery plans
Planned failover: Perform a complete failover and recovery of virtual machines in your recovery plans in a proactive, planned manner.
Applies non-replicated changes to the replica virtual machine with no data loss, before bringing the VM online in the secondary site.
Simulates your failover and recovery mechanism into isolated networks, that you define, or that can be created automatically.
Unplanned failover: Run an unplanned failover when a primary site experiences an unexpected incident, such as a power outage.
Orchestrated disaster recoveryfor Hyper-V VMs, between on-premises
Communication and replication
Microsoft Azure Site Recovery
Enterprise
/ HSP Primary
site
Windows Server
Microsoft Azure Site Recovery
Communication channel
Replication channel:
Hyper-V Replica or SAN replication
Primary site
Windows Server
Recovery site
Windows Server
and Microsoft Azure
Communication and replication
Microsoft Azure Site Recovery
SMB & Branch
Primary site
Windows Server
New!
Key features include:
Automated VM protection and replication
Remote health monitoring
Customizable recovery plans
No-impact recovery plan testing
Orchestrated recovery of tiered applicationsUse Azure as your disaster recovery site
New: Replication into Azure for SMBs and remote branch offices without System Center
Heterogeneous disaster recoveryfor VMware vSphere VMs and physical servers with InMage Scout
InMage Scout:OS-based replication for flexibility
Supports VMware vSphere and physical servers as the
source of replication
Supports VMware vSphere as target for replication and recovery
Ideal for enterprises and service providers that already have VMware investments
Microsoft Azure Site Recovery
Download InMage Scout
Replication and orchestration
channel: InMage Replication
Primary site
VMware/Physical
Recovery site VMware
InMage Scout
InMage Scout
Contoso primary location(On-premises or service
provider)
Source: VMware vSphere VMsand physical servers
Heterogeneous disaster recoveryfor VMware vSphere VMs and physical servers with InMage Scout
ProcessServer
Contoso secondary location(On-premises or service
provider)
Target: VMware vSphere VMs
ConfigServer
MasterTarget
InMage Scout data
channel
DownloadInMageScout
Microsoft Azure Site Recovery
DownloadInMage
Scout
Process Server – Used for caching,compression and encryption
Config Server – Used for centralized management of InMage Scout
Master Target – Used as a repository and for retention
Heterogeneous disaster recoveryInto Microsoft Azure with Azure Site Recovery and InMage Scout
Microsoft Azure Site Recovery
Download InMage Scout
Replication channel:
InMage Scout
Primary site
VMwarePhysical
Recovery site VMware
InMage Scout to AzureOS-based replication for flexibility
Supports VMware vSphere and PhysicalServers 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
Orchestrationand replication
Microsoft Azure Site Recovery
Primary site
VMwarePhysical
InMage Scout
2015
Heterogeneous disaster recoveryInto Microsoft Azure with Azure Site Recovery and InMage Scout
Microsoft Azure
InMage Scout data
channel
Microsoft Azure Site Recovery
Process Server – Used for caching, compression and encryption
Config Server – Used for centralized management of InMage Scout
Master Target – Used as a repository and for retention
Contoso
Fabrikam
RX Server – Used for multi-tenant management in Azure
RX Server
Orchestration
Orchestration
Contoso primary location(On-premises or service
provider)
Source: VMware vSphere VMsand physical servers
ProcessServer
Fabrikam primary location(On-premises or service
provider)
Source: VMware vSphere VMsand physical servers
ProcessServer
ConfigServer
Master Target
ConfigServer
Master Target
Azure Site RecoveryOne solution for multiple infrastructures
Hyper-V to Hyper-V(on-premises)1
Hyper-V Hyper-V
Replication
Hyper-V to Microsoft Azure
3
Hyper-VMicrosoft
Azure
Replication
VMware or Physical to VMware (on-premises)4
VMware or Physical
VMware
Replication
VMware or Physical to Microsoft Azure5
VMware or Physical
MicrosoftAzure
Replication
Hyper-V to Hyper-V(on-premises)2
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.
• Learn more about Microsoft Protection and Site Recovery capabilitieshttp://www.microsoft.com/en-us/server-cloud/solutions/business-continuity.aspx
• Learn more about Windows Server Backuphttp://technet.microsoft.com/library/jj614621.aspx
• Learn more about Microsoft Azure Backuphttp://azure.microsoft.com/en-us/services/backup/
• Learn more about System Center Data Protection Managerhttp://technet.microsoft.com/en-us/library/hh758173.aspx
• Learn more about Microsoft Azure Site Recoveryhttp://azure.microsoft.com/en-us/services/site-recovery/
• Download Windows Server 2012 R2 Evaluationhttp://technet.microsoft.com/en-US/evalcenter/dn205286.aspx
• Download System Center 2012 R2 Evaluationhttp://technet.microsoft.com/en-US/evalcenter/dn205295
Next steps: Transform your datacenter
© 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista 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 marketconditions, 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.