1© Copyright 2011 EMC Corporation. All rights reserved.

EMC RECOVERPOINT/CLUSTER ENABLER FOR MICROSOFT FAILOVER CLUSTER

2© Copyright 2011 EMC Corporation. All rights reserved.

Disaster RestartBusiness challenges and requirements

• Meeting recovery point objective (RPO) and recovery time objective (RTO) requirements with current plan

– Business and/or regulatory needs– Need continuous operations with no data loss– Need to reduce RPO and RTO times

• Reduce from days or hours to minutes or seconds

• Cost of assets and maintenance at disaster recovery site

– Need to maintain software (updates and patches)

• Reliability of the disaster recovery plan– Need to address applications requiring dependent

write consistency between and across operating systems

– Need to periodically test to ensure it works when required

3© Copyright 2011 EMC Corporation. All rights reserved.

Business Impact of Application and Data Inaccessibility

Cost of downtime escalates quickly over time

Dedicated hot standby

Database replication

Electronic vaulting

Hot site/cold site

Remote replication

Geographical clusters

TIME

DO

WN

TIM

E C

OST

4© Copyright 2011 EMC Corporation. All rights reserved.

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

5© Copyright 2011 EMC Corporation. All rights reserved.

RecoverPoint/Cluster Enabler 4.1.2Features and capabilities overview

• Integrates RecoverPoint family with Microsoft failover cluster

– Automatic site failover for remote replication operations– Supports majority node set quorum options: Majority Node Set (MNS),

and MNS with File Share Witness

• Supports RecoverPoint continuous remote replication (CRR)

– Tolerates concurrent local and remote (CLR) consistency groups– Optional automatic failover

• Uses Fibre Channel or Gigabit Ethernet for remote replication

– 400 milliseconds maximum latency for asynchronous replication– 4 milliseconds maximum latency for synchronous replication

• Supports Windows Server and Server Core for Windows Server 2008

– Up to eight 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

RecoverPoint/Cluster Enabler 4.1.2 supports RecoverPoint 3.4.2 or later and any array supported by RecoverPoint family

6© Copyright 2011 EMC Corporation. All rights reserved.

Majority Node Set SupportMajority Node Set

• Used as a tie-breaker to avoid split-brain scenarios

• From a cluster-node perspective, each node sees the quorum as a local resource

– Each cluster node stores the configuration information on a local disk

– Each node has access to local disk when it starts up– Cluster service ensures cluster configuration is consistent on each

cluster node– Changes are replicated across the Majority Node Set

File Share Witness

• External to a cluster providing an additional quorum vote

– 2 to 4-node cluster can survive up to N-1 node failures– 4 to 16-node cluster can survive up to N-2 node failures

• Acts as a witness to Majority Node Set– Enhances geographically disbursed failover cluster

•Microsoft recommends that the File Share Witness be configured in a third site

7© Copyright 2011 EMC Corporation. All rights reserved.

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

8© Copyright 2011 EMC Corporation. All rights reserved.

RecoverPoint/Cluster Enabler for Microsoft Failover Cluster: Node FailureRole of major software components

• Microsoft failover cluster software– Protects against server hardware or network connection

failures– Initiates failover actions to a clustered node for

resource group restart

• RecoverPoint/Cluster Enabler 4.1.2 software– Installed on all cluster nodes and on File Share Witness – Responds to queries from the cluster service that

determines cluster behavior– Determines RecoverPoint state and initiates

RecoverPoint actions

• RecoverPoint software– Remote mirroring of production data– DVR-like recovery of production data for access outside

of Microsoft failover cluster software

9© Copyright 2011 EMC Corporation. All rights reserved.

RecoverPoint/Cluster Enabler and Node Failure Event

• Site A node fails, resulting in heartbeat response timeout

• Cluster reforms between the Site B node and the File Share Witness node

• The Site B node brings resource groups from the Site A node online

• The latest image of the RecoverPoint volumes listed in the resource group is automatically recovered, read/write enabled, and mounted to the Site B node

• Application listed as part of the failed Site A node resource group is restarted

• The Site A node network address is added to the network interface of the Site B node and client traffic is routed to the Site B node

Failover steps

Site A Site B

RecoverPoint

Majority Node Set with File Share

Witness

10© Copyright 2011 EMC Corporation. All rights reserved.

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

11© Copyright 2011 EMC Corporation. All rights reserved.

Hyper-V OverviewRecoverPoint/CE 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

12© Copyright 2011 EMC Corporation. All rights reserved.

Hyper-V Virtual Machine Failure Event

• Site A Hyper-V physical node fails, resulting in heartbeat response timeout

• Cluster reforms between the Site B node and the File Share Witness node

• The Site B node brings Hyper-V virtual machine resource groups from the Site A node online

• RecoverPoint target volumes for consistency groups listed in affected resource groups are recovered and mounted to the Site B node

• Virtual machines listed as part of the failed Site A node resource group are restarted

• The Site A node network address is added to the network interface of the Site B node and client traffic is routed to the Site B node

Failover steps with RecoverPoint/Cluster Enabler

VMs can failover within and between failover cluster

nodes

Site A Site B

RecoverPoint

Majority Node Set with File Share

Witness

13© Copyright 2011 EMC Corporation. All rights reserved.

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

14© Copyright 2011 EMC Corporation. All rights reserved.

Multi-Array SupportEach named cluster group’s associated devices reside in a single RecoverPoint consistency group of the same name

File Share Witness with RecoverPoint/CE

installed

RecoverPoint RecoverPoint

Devices forCluster Group1

Devices forCluster Group2

Cluster nodes with RecoverPoint/CE installed

WAN

15© Copyright 2011 EMC Corporation. All rights reserved.

Microsoft Failover Clusters Deployed

with Oracle on Windows

RecoverPoint

Majority Node Set with File Share

Witness

Target 2

Prod 1

Prod 2

Target 1

Network

Oracle

Oracle

Oracle

Oracle

16© Copyright 2011 EMC Corporation. All rights reserved.

Benefits of RecoverPoint/Cluster Enabler

• Provides rapid site restart with RecoverPoint– Automatic site failover for common disruptions,

including complete site disasters and server, storage, or network-related failures

• Minimizes site failback time with RecoverPoint

– Only changes are replicated to resynchronize the primary cluster storage system

• Provides multi-array support– One cluster can span multiple storage arrays at the

same or different sites– Different clusters can share storage arrays

• Supports heterogeneous storage arrays– A mix of arrays can be used– Storage arrays do not have to be identical between

sites