building disaster-recovery solution using azure site...

Building disaster-recovery solution using Azure Site Recovery (ASR) for Hyper-V (Part 1)

KR Kandavel

Technical Solutions Professional

Asia Azure Site Recovery Specialist Team

Microsoft Corporation

Hybrid cloud vision

Business continuity challenges

Microsoft solution for Business continuity & Disaster recovery (BCDR)

Azure Site Recovery use case scenarios for DR 1. On-premise to On-premise DR (for Hyper-V and Virtual Machine Manager)

2. On-premise to On-premise DR (for Hyper-V, Virtual Machine Manager and SAN)

3. On-premise to Azure DR (for Hyper-V, and Virtual Machine Manager)

4. On-premise to Azure DR (for Hyper-V)

Wrap up

Microsoft Cloud Platform

The platform for hybrid cloud

enables IT to:

• empower enterprise mobility

• create the Internet of your things

• enable application innovation

• unlock insights on any data

• transform the datacenter

Development Management Data Identity Virtualization

Customer

Service Provider Microsoft

CONSISTENT PLATFORM

Transform the datacenter

Extend to the cloud on demand

Build a software-defined foundation

Automate and secure your infrastructure

Microsoft Azure Windows Server Microsoft System Center

Datacenter Microsoft Azure

Datacenter Microsoft Azure

Impact of data growth

SHARE Standards Group – 7 Tiers of Disaster Recovery

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 or physical VMware

Replication

VMware or physical to Microsoft Azure

VMware or physical Microsoft

Azure

Replication

Hyper-V to Hyper-V (on-premises)

Hyper-V Hyper-V

Replication

SAN SAN

DR Scenario 1:

On-premise to On-premise DR for Hyper-V & Virtual Machine Manager (VMM)

Microsoft Azure Site Recovery

Communication Channel

Replication channel:

Hyper-V Replica

Windows Server

Windows Server

Enterprise / HSP Primary site

Enterprise / HSP

Recovery site

System Center

Virtual Machine

Manager

System Center

Virtual Machine

Manager

System Center

Virtual Machine

Manager

AD

SQL

LOB

System Center

Virtual Machine

Manager

System Center

Virtual Machine

Manager

AD

SQL

LOB

System Center

Virtual Machine

Manager

AD

SQL

LOB

$cloud = Get-SCCloud -Name “CloudName” Get-SCVirtualMachine -Cloud $cloud | where {$_.IsDRProtectionRequired -eq $false} | Set-SCVirtualMachine –DRProtectionRequired $true -RecoveryPointObjective “TimeInSeconds”

Once Hyper-V Replica is enabled, VMs begin replication Once replicated, changes replicated on chosen frequency Upon site failure, VMs can be started on secondary site

System Center

Virtual Machine

Manager

AD

SQL

LOB

System Center

Virtual Machine

Manager

AD

SQL

LOB

System Center

Virtual Machine

Manager

AD

SQL

LOB

System Center

Virtual Machine

Manager

AD

SQL

LOB

AD

SQL

LOB

AD

SQL

LOB

Demo On-premise to On-premise DR for Hyper-V & Virtual Machine Manager (VMM)

DR Scenario 2:

On-premise to On-premise DR for Hyper-V & Virtual Machine Manager (VMM) & SAN storage

Microsoft Azure Site Recovery

Communication channel

Replication channel:

SAN Replication

Enterprise / HSP Primary site

Windows Server

Enterprise / HSP

Recovery site

Windows Server

Microsoft Azure Site Recovery

Customer selects recovery region

CREATE VAULT

1

Define DR Plan

CREATE RECOVERY PLAN

7

Register VMM Server

REGISTER

2

Consistency Group in SAN

CREATE REPLICATION GROUP

3

Define protection policy

CONFIGURE PROTECTION

4

Add Replication Group and Protect VMs

PROTECT VIRTUAL MACHINES

6

Define DR networking

Network Mapping

5

Test the deployment

RUN DR DRILL

8

DR Scenario 3:

On-premise to Azure DR for Hyper-V & Virtual Machine Manager (VMM)

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

Enterprise / HSP Primary site

Windows Server

Enterprise / HSP

Recovery site

Windows Server

Consistent experience: Centralized view of replication and recovery across on-premises locations, and between on-premises and Microsoft Azure.

Network mapping: Mapping of on-premises VM networks into precreated Microsoft Azure virtual networks.

Streamlined configuration: Only 1 additional step—installation of Site Recovery agent on Hyper-V Hosts.

Quick setup for protection of on-premises clouds, with Microsoft Azure as a target.

Support for encryption of data at rest, along with flexible replication frequencies, additional recovery points and VSS-aware application consistent checkpoints.

Recovery plans: Automation of the orderly recovery into Microsoft Azure, in the event of a site outage at the primary datacenter.

Support for manual actions that require some form of human intervention during the implementation of the recovery plan.

Shutdown of VMs upon implementation is in reverse order of recovery to ensure zero data loss.

Flexible failover and failback options: Support for test, unplanned and planned failover into Microsoft Azure.

Able to be used for compliance assurance without affecting production workloads, and also as a mechanism to migrate into Microsoft Azure for longer term usage.

Streamlined process for failback into on-premises environment.

System Center

Virtual Machine

Manager

System Center

Virtual Machine

Manager

AD

SQL

LOB 7. Configure

Protection

of Clouds

System Center

Virtual Machine

Manager

AD

SQL

LOB

• Automatically map to closest Azure size - you

can change.

• Guest supported by Azure IAAS

• VHDX is supported

• Data VHD size supported upto 31TB

• 31 disks of 1TB each

• OS VHD size limited to 127 GB

• Gen 2 not supported today

System Center

Virtual Machine

Manager

AD

SQL

LOB

System Center

Virtual Machine

Manager

AD

SQL

LOB

AD

SQL

LOB

AD

SQL

LOB

Flexible options for failback into on-premises environment.

Network Mapping

Connecting back to OnPrem

Transfer large data to Azure

Demo On-premise to Azure DR for Hyper-V & Virtual Machine Manager (VMM)

DR Scenario 4:

Branch office to Azure DR for Hyper-V

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

Communication and replication

Microsoft Azure Site Recovery

SMB & Branch

Primary site

Windows Server

New!

New

SMB-focused: Simple, reliable and cost effective disaster recovery solution for SMB and branch offices

Consistent experience: Create vault, create site, generate registration key, and install provider on Hyper-V hosts directly. This installs 2 components:

• ASR Provider—Handles communication and orchestration between Hyper-V and the ASR portal

• Azure Recovery Services Agent—Handles data transport between VMs running on Hyper-V and Azure storage

Protection Groups: Streamlined configuration of replication settings, including RPO, recovery points, VSS-snapshot integration, and initial replication

VM protection: In just a few clicks, ASR automates replication from on-premises into Azure

VM config: Adjust name, size and join recovery VM to a network upon failover. Size is automatically determined based on on-premises size.

Recovery plans: Automation of the orderly recovery into Microsoft Azure, in the event of a site outage at the primary location.

Scripts: Scripts from Azure Automation can be injected into recovery plan before or after groups

Manual actions: require some form of human intervention during the implementation of the recovery plan.

Flexible failover and failback options: Support for test, unplanned and planned failover into Microsoft Azure.

Able to be used for compliance assurance without affecting production workloads, and also as a mechanism to migrate into Microsoft Azure for longer term usage.

Streamlined process for failback into on-premises environment.

Demo Branch Office to Azure DR for Hyper-V

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 or physical VMware

Replication

VMware or physical to Microsoft Azure

VMware or physical Microsoft

Azure

Replication

Hyper-V to Hyper-V (on-premises)

Hyper-V Hyper-V

Replication

SAN SAN

At scale configuration

Compute, storage and network

Variable RPO to meet needs of various apps

Azure VM auto-sized based on size of on-premises VM

User can change per needs

Data resides in customer storage

Stored securely using encryption

Automated failovers – test, planned and unplanned

Failback as first class gesture

Rich application level recovery Dependency groups

Manual actions

Azure Automation

ASR Capabilities Summary

•Getting Started with On-premises to On-premises DR (Hyper-V platform – windows and Linux OS)

•Getting Started with On-premises to On-premises DR (Hyper-V platform – windows and Linux OS using SAN replication)

•Getting Started with On-premises to Azure DR (Hyper-V platform – windows and Linux OS)

•Getting started for Branch office to Azure DR (Hyper-V platform – windows and Linux OS)

References

http://aka.ms/MDC396

Session Evaluation