1 © copyright 2009 emc corporation. all rights reserved. manage your risk with business continuity...

1© Copyright 2009 EMC Corporation. All rights reserved.

Manage Your Risk with Business Continuity and Disaster Recovery

EMC RecoverPointNetwork-Based Intelligent Data Protection

Muhammad SalamaSr. Technology Consultant

[email protected]


Data-Replication Pain Points in Heterogeneous Environments

Application-consistent recovery

Corruption protection

Local site Remote site

SANSANSAN

Application response time

infrastructure

Disaster-recovery testing

Oracle Exchange SQLOracle Exchange SQL

Communicationscost

Heterogeneousstorage

SUNIBM HPHDSEMC

SUNIBM HPHDSEMC


Host

RepliStor

Array

MirrorView/SMirrorView/A

SAN Copy

Network

RecoverPoint

Data Replication Technologies…


DECLARE DISASTER

10 a.m.

Recovery Point Objectives(RPO)

Recovery Time Objectives(RTO)

RPO Definition: Amount of data lost from failure, measured as the amount of time from a disaster event

RTO Definition: Targeted amount of time to restart a business service after a disaster event

Remote Recovery: RPO and RTO

5a.m.

6a.m.

7a.m.

8a.m.

9a.m.

10a.m.

11a.m.

12a.m.

1p.m.

2p.m.

3p.m.

4p.m.

5p.m.

6p.m.

7p.m.


Snapshots and Clones

Continuous Data Protection

Creates copies like “time-lapse photographs”

Change-based “VIDEO CAMERA” with DVR-like roll back capabilities

Operational Recovery

Either space efficient change-based snapshots for backup off-loading

Or, full copies or clones for test and development with minimal production impact

Journal every change made and set the window for the amount of time to record


RecoverPoint Continuous Data Protection (CDP)

RecoverPoint splitter drivers– Mirrors server writes to RecoverPoint appliance– Resides on host or in fabric

RecoverPoint appliance– Managed and prioritizes resources– Writes changes to local CDP Journal– Distributes changes to target

Journal– Tracks all data changes to every protected LUN– Utilizes bookmarks for application-aware recovery– Repository for live data updates– Provisioned from existing SAN LUNs– Dynamically compressed, which saves storage

Supports heterogeneous environments– RecoverPoint supports EMC and third-party storage*– RecoverPoint/SE supports CLARiiON arrays only

Applicationservers

Databaseservers

Messagingservers

File andPrint servers

Disksystems

Local CDP Journal

EMCThird-Party

* Support for third-party storage requires intelligent fabric

SAN

ŒŒ Œ Œ

Œ


/ A / C/ B

r A r Cr B

RecoverPoint Local Protection Process—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 splitter

3. Writes are acknowledged back from the RecoverPoint appliance

2b. Intelligent-fabric splitter

2c. CLARiiON splitter


RecoverPoint—Recovery Point Consolidationin Journal

Two days ago Now

ContinuousWeeklyMonthly

JOURNAL RECOVERY POINT TIMELINE

Daily

Continuous Recovery Points

Daily Recovery Points

Weekly Recovery Points

Monthly Recovery Points


RecoverPoint Continuous Remote Replication (CRR)

RecoverPoint splitter drivers– Intercepts server writes (block level)– Resides on host, CLARiiON, or in fabric*– Mirrors write to RecoverPoint appliance

RecoverPoint appliance– Bandwidth reduction with data compression

for WAN transfer– Distributes changes to remote site– Supports instant access to protected data

Journal– Tracks all data changes to every protected LUN– Utilizes bookmarks for application-aware recovery– Dynamically compressed, which saves storage

Provides advanced functionality– Policy-based bandwidth management– 5–10 times bandwidth reduction– Replicate over IP or Fibre Channel

Supports heterogeneous environments– RecoverPoint supports EMC and third-party storage*– RecoverPoint/SE supports CLARiiON arrays only

EMCThird-Party EMC Third-

Party

SANor

WAN

* Support for third-party storage requires intelligent fabric

SAN SANŒ Œ

ŒŒ Œ ŒŒ Œ


RecoverPoint Concurrent Local and Remote (CLR) Data Protection

SAN SANSAN/WAN

PRODUCTION SITE DISASTER RECOVERY SITE

Cluster Passive Node

Cluster Active Node

ReplicationData Flow

RecoverPoint appliances

RecoverPoint Replication Services

Tape Backup Manager

Standby Disaster

Recovery Server

Tape Library

LocalJournal

Storage Groupsand Logs

RemoteJournal

Replicated Storage Groups and Logs

Performance architecture– Out-of-band design leveraging intelligent host and fabric interfaces*– Supports CLARiiON write splitting on CX3 and CX4 arrays– Designed to work in enterprise-class environments

Replication across heterogeneous storage*– Leverage existing storage investments– Co-exists with local CDP

True bi-directional, any-to-any replication– Replicate between arrays at same or different site*

True CDP data protection for applications– All writes stored in Journal with application bookmarks for recovery– Supports Microsoft Volume Shadowcopy Service (VSS) and VDI APIs

Concurrent local and remote data protection– Create local and remote copies of the same LUNs– Recover both locally or remotely to different point-in-time images– No impact to production or the other replica during recovery

Unified management interface– Remotely configure, monitor, manage CDP/CRR– Programming CLI for intelligent scripting

* RecoverPoint/SE does not support intelligent fabric, and only supports a single CLARiiON array at each side/site


RecoverPoint Stretched CDP over Stretch Fibre

Stretched CDP

PRIMARY SITE REMOTE BUNKER SITEApplication

serversFile and

print serversDatabaseservers

Applicationservers

File andprint servers

Databaseservers

Management IP WAN

StretchFibre

RecoverPoint

ProductionVolumes

Failover CDP Journal

Supports synchronous CDP replication to secondary site (such as a bunker site)

− Distance subject to specific configurations; refer to the EMC Support Matrix for guidance

Enables survival of primary site outage

Provides synchronous replication across distance

Remote applications can access any point in time image as read/write without impacting production

All RecoverPoint resources installed at remote site

− CDP target storage, journal

− RecoverPoint appliances

− RecoverPoint repository volume

− Standby/disaster recovery servers

Dual fabric that is extended to remote site

Servers and splitters must be at both sites

Reversing replication by promoting CDP replica to production is not supported

Primary Journal

CDP ReplicaVolumes

SAN SAN


TERTIARY SITESECONDARY SITE

Cascaded RecoverPoint Topology Example

Local and remote data protection minimizes data loss

PRIMARY SITE

ProductionVolumes

Failover CDP Journal

StretchFibre

CRR Journal

CRR Replica

Volumes

Near-Synchronous* Asynchronous Unlimited*

* Refer to the EMC Support Matrix for the maximum distance for your configuration

WANSANSANSAN

Manage-ment

IP WAN

Manage-ment

IP WAN

CDP Journal

CDP Replica

Volumes


Policies for Dynamic Sync/Async Replication


Journaling for Application-Aware Recovery

Time/date– Identifies the time image was saved

Bookmarks:– System-generated group bookmarks

e.g., Volume Shadowcopy Service (VSS) backup

– User-generated bookmarks– Other EMC product bookmarks

EMC Replication Manager

– System-event-generated bookmarks– Microsoft SQL Server

Microsoft Virtual Device Interface (VDI) operations

– Microsoft Exchange Microsoft VSS

Journal Includes Data Plus Metadata


RecoverPoint Recovery Process

Request image via management interfaceŒ User selects by bookmark or point in time

RecoverPoint recovers image as read/write– User chooses virtual or physical target – Existing Journal data used to play back changes to

appropriate bookmark or point in time– Target-mounted read/write to recovery server

All new writes saved in Journal – Existing disaster-recovery protection not impacted– Image changes committed on request

Recovery-image use cases– Failover production to image– Start new application from image– Surgically repair data from image– Fast production resynchronization

Rollback production from changed blocks– Source for backup– Data analysis– Disaster-recovery development and testing (“fire

drill”)

Recoveryrequest

Target volumesHistoryJournal

RecoverPoint appliance

Servers atrecovery site

Œ

v

SAN


Understanding Data Consistency

Applications and data are interrelated (Federated)

All data movement must be stopped/started at the same point in time

To restart applications you must have all the data—not parts of it

Recovery requires dependent-write consistency across all volumes and systems

Systems share information…how do you get a consistent view?

Order Entry

SCM

CRM

DB

DB DB


Grouping for a Consistent View

Allows application recovery to be tiered by service level

– Multiple volumes per group– Mixed recovery point objectives within

same infrastructure

Provides independent replication controls

– Recover by group, locally or remotely– Start/stop by group

Enables grouping of optimization – Importance– Resource usage– Recovery point and recovery time

objectives

Group 3

Group 1

Group 2

E-mail CRR

CRRCDPSCM

CRROE

CRRCRM CDP


2: Windows (CRM)

Grouping for Federated Environments

Each tier has different service level agreements

– Consistency groups per tier – Operational recovery of tier

Parallel consistency across tiers– Federated environments– Recover to a known point for all

applications– Disaster recovery for tier or application– Spans operating systems, applications,

storage, and servers

Enables advanced functions– Full environment cloning– Application upgrade testing– Data mining– Consistent production rebuild

1: Linux (Web OE)

Consistencygroup

Consistencygroup

3: UNIX (SCM, Financials…)

Consistencygroup


Summary

Lowest total cost of ownership – Reduction and consolidation of server, storage

footprint (capital expenditure), and WAN bandwidth (operational expenditure)

Integrated CLARiiON support– CLARiiON-based splitter on CX3 and CX4– Virtual Provisioning support on CLARiiON CX4

Intelligent SAN-switch integration – RecoverPoint supports Connectrix using Brocade

and Cisco technology

Any-point-in-time recovery – Rollback of data at the local site and/or remote site

Highest availability, highest performance – Network-based architecture optimized for

application availability and performance

Heterogeneous support– RecoverPoint supports spectrum of host, storage,

and SAN elements

1 © copyright 2009 emc corporation. all rights reserved. manage your risk with business continuity...

Documents

emc corporation

data changes

party emc

fabric recoverpoint

protected data journal

data compression

recoverpoint concurrent

disaster event remote