Replicating Microsoft Applications using EMC RecoverPoint

1© Copyright 2011 EMC Corporation. All rights reserved.

Microsoft mSpecialist Summit 2011 – Day #3

Replicating Microsoft Applicationsusing EMC RecoverPoint

Sharon AlmogRecoverPoint Eng.

James BaldwinStrategic Solutions

&

by

2EMC CONFIDENTIAL— DO NOT DISTRIBUTE

Agenda• Introduction to RecoverPoint • Data Protection Roadmap• RecoverPoint Cluster Enabler (RP/CE)• Replicating HyperV applications• Replicating Microsoft SQL Server• EMC RecoverPoint and SQL 2012 “AlwaysOn”


An introduction to RecoverPoint


Bi-directional Local and Remote Replication

SAN

DISASTER RECOVERY SITEPRODUCTION SITE

Prod

LUNs

FibreChannel/WAN

Local copy

Application servers

SAN

RecoverPointappliance

RecoverPoint bi-directional replication/recovery

Remote copy

Standby servers

RecoverPointappliance

Production and local journals

Remote

journal

Storagearrays

StoragearraysHost-based write splitter

Fabric-based write splitterSymmetrix VMAXe, VNX-, and CLARiiON-based write splitter


/ A / C/ B r A r Cr B

Local Protection Process:Continuous Data Protection (CDP)

1. Data is split and sent to the RecoverPoint appliance in one of three ways

4. The appliance writes data to the journal volume, along with time stamp and application-specific bookmarks

5. Write-order-consistent data is distributed to the replica volumes

Production volumes Replica volumes Journal volume

2a. Host write splitter

3. Writes are acknowledged back from the RecoverPoint appliance

2b.Intelligent-fabric write splitter

2c. CLARiiON write splitter


r A r Cr B/ A / C/ B

Remote Protection Process:Continuous Remote Replication (CRR)

Local site

2b.Intelligent-fabric write splitter

7. Data is written to the journal volume

Remote site Journal volume

5. Data is sequenced, checked, deduplicated, compressed, and replicated to the remote appliances over IP or SAN

1. Data is split and sent to the RecoverPoint appliance in one of three ways

8. Consistent data is distributed to the remote volumes

2c. CLARiiON write splitter

3. Writes are acknowledged back from the RecoverPoint appliance

4. Appliance functions• Fibre Channel-IP conversion• Replication• Data reduction and

compression • Monitoring and

management

6. Data is received, uncompressed, sequenced, and verified

2a. Host write splitter


Components and Topology• Application servers

– Accesses data that needs to be replicated

• Heterogeneous storage– Source or target for replicated data

• RecoverPoint appliance (RPA)– Connects to LAN and Fibre Channel

(FC)/WAN for replication management and replicating data over FC/IP

– Connects to Layer 2 FC SAN for storage access

• RecoverPoint appliance cluster– A group of inter-linked RPAs, working

together closely, to provide replication services

– RPAs in a RecoverPoint cluster are called nodes

•WAN bandwidth management– Reduce WAN bandwidth by up to 90%

through deduplication, compression, and write-folding

RecoverPoint appliances

EMC LSIIBM HDS HP

Layer 2Fibre Channel

SAN

Heterogeneous storage

Application servers

FibreChannel/WAN


RecoverPoint Family Details

• One solution for data protection, replication, and disaster recovery

• Local replication for LUNs in one SAN• Remote replication between LUNs in two SANs• Concurrent local and remote data protection that

combines local and remote replication• Heterogeneous operating system support• Disaster recovery for VNX series file systems

RecoverPoint/EXEMC storage environments• Multiple EMC arrays per site • Array-based splitting only• Supports up to 300 TB of

production data

RecoverPoint/SESupports VNX and CLARiiON environments• Single VNX, CLARiiON, or Celerra

unified array per site• Supports Microsoft Windows host-

based and VNX, CLARiiON array-based splitting only

• Supports 300 TB of production data

RecoverPoint/CLSupports EMC and non-EMC storage environments• Heterogeneous storage array

support• Multiple arrays per site, EMC and

non-EMC• Supports up to 300 TB of

production data

• Wizards automate production rebuild/restart • DVR-like recovery and consolidation reduces RPO

and RTO• Application integration for Microsoft Exchange and

SQL, other applications and databases• Integrated consistency groups support federated

servers and storage• Synchronous or asynchronous local and/or remote

replication with optional dynamic selection policies

Common functionality

9EMC CONFIDENTIAL—INTERNAL USE ONLY

RecoverPoint integration with Cluster Enabler (RP/CE)


Microsoft Failover ClusterA high-availability restart solution

Node or resource failure automatically restarts failed nodes on another node where resources are available

Microsoft failover cluster provides high availability; shared-nothing cluster model

Resource Group:Microsoft SQL

Resource Group:Microsoft Exchange

Resource Group:Oracle

Node fails


RecoverPoint/Cluster Enabler for Microsoft Failover Cluster

Failover cluster supports 16 nodes with Windows Server 2003/2008 using Majority Node Set with and without File

Share Witness

Site BSite A

RecoverPoint

File Share Witness with RecoverPoint/CE

installed

Private Interconnect

LAN/WAN

Cluster nodes with RecoverPoint/CE installed


RP/CE & Hyper-V OverviewCluster Enabler 4 supports Hyper-V with failover clusters• Failover of the virtual machine (VM) resource

– RecoverPoint/CE is deployed in the Hyper-V parent partition – Cluster relocation is at the VM level

• Hyper-V Live Migration and Quick Migration—between nodes at the same or different sites – Live Migration supported with RecoverPoint CRR/CLR synchronous

replication – Quick Migration supported with synchronous and asynchronous

replication– Use for planned maintenance, such as VM relocation for hardware

upgrades and software upgrades– Use for VM workload redistribution—move VMs between physical

hosts


Disaster Recovery for Hyper-VAutomated failover operations for Hyper-V environments

Hyper-V with Failover Clusters supports 16 nodes with Windows 2008 R2Site BSite A

RecoverPoint

Majority Node Set with File Share Witness

Private Interconnect

LAN/WAN

Cluster nodes with RecoverPoint/CE installed

Target 2

Prod 1

Prod 2

Target 1


Hyper-V Live Migration

RecoverPoint CRRsynchronous replication

Planned hardware maintenance on physical server requires moving virtual machine(s) to another physical server

Majority Node Set with File Share

Witness

R2

R1

Site A

R1

R2

Site B


RP/CE 4.1.2 (new release) Supported with RP 3.4.2 code Supports RecoverPoint CLR topology

– Failover is still limited to CRR copy (can’t failover to CDP) New CE Group Policy “Auto Failover”

– Provides missing flexibility which was absence in previous “Restricted group” (see next table)

– No need to perform “RecoverPoint manual failover” on specific use cases

Supports Windows Server and Server Core for Windows Server 2008–Up to 8 nodes per site with Windows Server 2003–Up to 16 nodes per site with Windows Server 2008 and Windows

Server 2008 R2–Up to 16 child partitions with Hyper-V


Using RecoverPoint/Cluster Enabler Supports Windows 2003 Cluster Services Supports Windows 2008 Failover Clusters Supported with Hyper-V Repurposing does not work

– MSCS failover enforces that remote cluster nodes can’t be manipulated

– All resources of those nodes are not available outside of nodes• No access, mounting, multi-masking of LUNS to non-clustered hosts

Cluster Enabler 4.1 supports CSV– Requires Windows Server 2008 R2 SP1

Support Majority Node Set, other quorum modes not supported Only supports CRR

– Toleration of CLR will be added 2H’2011 (addresses repurposing issue)

Disaster Scenario Expected BehaviorCan we Failover when CG

policy is “Restricted Group”

Can we Failover when CG policy is “Automatic Failover”

Replication link is down (while Heartbeat link is up) No Failover

No(Can bypass using “Manual Failover”

procedure)

Yes(Risk of data consistency/loss due to the

unknown replication state)

Heartbeat link is down (while replication link is up)

No Failover YesYes

(Risk of data consistency/loss due to the unknown replication state)

Replication & Heartbeat links are down

No Failover(According to MS Cluster Majority Node set

rules)


procedure)



RPA Cluster failure at one site

No Failover(will fail any attempt to failover or

changing cluster group online state)


procedure



Cluster Node Failure Automatic Failover(According to MS Cluster failover rules)

Yes Yes

Clustered Application failure Automatic Failover(According to MS Cluster failover rules)

HBA Failure Automatic Failover(According to MS Cluster failover rules)

Storage failure to Cluster Nodes only (Replication link is up)

Automatic Failover(According to MS Cluster failover rules)

Storage failure to Cluster Nodes and RPA Cluster (replication will fail)

No Failover(will fail any attempt to failover or

changing cluster group online state)

No(Can bypass using “Manual

Failover” procedure




DEMO:

Protecting SQL 2008 using RP/CE (movie)


RecoverPoint integration with MS HyperV

• Clustered HyperV (each VM reside on its own replicated Cluster Disks)

• Clustered HyperV with CSV volume (multiple VMs reside on single replicated CSV volume)

• Standalone HyperV host (since CSV is only supported in Cluster, then each VM reside on its own replicated volume)

Supported Hyper-V configurationsHyperV Host Configuration

VM per LUN topology

CE Supported

Recovery Process without CE

Recovery Process with CE

Clustered HyperV using Cluster Disk

Single Yes 1) Manual Image access on DR Host

2) Online Cluster Disk3) Online Clustered VMs

Automated FailoverCluster Node failure, HBA failure, Application failure, Cluster disk failure, Entire Site SAN is down (but will require Manual online to

failed cluster disk)Manual Failover

Failure of only the replication link, Failure of only the Public or Private

Cluster links

Clustered HyperV using CSV Disk

Multiple No 1) Manual Image access on DR Host

2) Online CSV Disk3) Online Clustered VMs

N/A(CSV not supported)

Standalone HyperV using attached disk

Single Not Relevant 1) Manual Image access on DR Host

2) Create New VM with no Virtual Disk

3) Attach the replicated VHD file into VM disk

N/A (not clustered solution)


RecoverPoint integration with SQL Server


RecoverPoint bookmark type Pros Cons

Periodic/Manual

(Crash consistent)

• DB Recovery is exposed to data corruption/loss might require SQL debug or mounting other bookmark

• Doesn’t require any application integration

VDI using KUTILS(Application consistent)

• DB data are 100% consistent

• During Backup the SQL DB details are exported into metadata file to guarantee identical restored DB characteristics

• Doesn’t exposed to Human error in recovery

• Cannot combine 3rd party log backups (it utilize FULL VDI Backup command)

• In recovery – requires metadata file to import SQL DB details

• The recovered SQL Server cannot consist of existing DB name

(new)

VSS using KVSS(Application Consistent)

• DB data are 100% consistent, no need for any metadata file

• Can recover DB into any name

• Exposed to Human error in recovery

• Requires functional SQL VSS Writer (“Healthy” state ) and VSS attributes removal procedure.


1) Backup using RP Hot Backup command the entire production database 2) Select RecoverPoint Hot Backup

bookmark

3) Mount this Bookmark

4) Restore entire database on DR SQL Server

DEMO #1: SQL VDI Backup/Restore using Kutils


1) Perform SQL VSS bookmark using KVSS utility on production Host

DEMO #2: SQL VSS Backup/Restore using KVSS

3) Mount this Bookmark

2) VSS bookmark created successfully


4) Online replica volumes

5) Remove Hidden/Read-Only disk attributes

6) Assign drive letters

7) Attach SQL database using SQL Mgmt. Studio


EMC RecoverPoint and SQL 2012 “AlwaysOn”


Dynamic Business Intelligence and DR with SQL Server 2012 AlwaysOn and EMC RecoverPoint

1. Local high availability is provided by SQL Server “Denali 2010” AlwaysOn Availability Groups

2. Local data accessibility for destructive data access to enable Dynamic BI is enabled by RecoverPoint

3. Remote site crash-consistent database copies are available over extended distances with WAN optimization and no SQL Server overhead with RecoverPoint

4. Dynamic Business Intelligence is enabled, whereby rapid copies of large OLTP production databases must be available to business intelligence teams;

Within minutes Must have BI SQL Server Instances fully isolated from production environments and networks Supports dynamic BI where databases copies need to be writeable to support dynamic BI

lookup scenarios Continue to ensure the production databases copies are intact


AlwaysOn RecoverPoint

Rapid local HA

Near-site synchronous replication

Distant host replication

Read Only Data accessibility for medium BI workloads

Any point in time recovery and access to Writable copies of data

Rewind-in-time recovery over extended periods of time

Long-haul block-level replication

Writeable data accessibility for any BI workloads

SQL Server AlwaysOn and EMC RecoverPoint- The Best of Both Worlds-

Replicating Microsoft Applications using EMC RecoverPoint

Documents

Transcript of Replicating Microsoft Applications using EMC RecoverPoint