Sunteți pe pagina 1din 41

Design Document

RECOVERPOINT Design
Woolworths Limited / VCE / WIPRO Ltd

Abstract
This document details architecture detail, technical considerations, best
practice recommendations, and detailed configuration for the EMC
Recoverpoint solution
18/12/2013

Table of contents

Document Control
Copyright

All the trademarks and registered trademarks referenced within this Design
Document are acknowledged as belonging to their various owners.
Copyright All material published in this Design Document is protected by the
Commonwealth Copyright Act 1968. All rights reserved. No material may be
reproduced, in either part or in whole, in any manner whatsoever, without the
express written consent of EMC.
2013 EMC Corporation. All Rights Reserved. This document is PROPRIETARY
and CONFIDENTIAL and may not be duplicated, redistributed, or displayed to any
other party without the express written permission of EMC.
Use, copying, and distribution of any EMC software described in this publication
requires an applicable software license.
For the most up-to-date listing of EMC product names, see EMC Corporation
Trademarks on EMC.com.

Document
Authorities

If changes are required for this document, please refer to the document
authorities in Table 1.
Table 1.

Drafting and
Release History

Contact Details for Proposed Changes

Name

Title

Email

Contact Number

Joshua Reader

Solutions
Architect

joshua.reader@emc.com

+61 (0)415 924 077

Rob Anderson

Project
Manager

robert.anderson2@emc.com

+61 (0)419 694 830

Table 2 reflects the creation date, along with any alterations since inception.
Table 2.

Drafting and Release History

Version

Date

Author

Description

0.1

23/10/2013

Ian Stewart

Setup document

0.2

30/10/2013

Joshua Reader

Updated tables and device


information

0.3

25/11/2013

Joshua Reader

Updated tables for Test


Consistency Groups

0.4

29/11/2013

Joshua Reader

Updated template

1.0

29/11/2013

Rob Anderson

Draft Release for review


and comment.

1.1

02/12/2013

Joshua Reader

Amendments following
initial review from Paul
Comerford

2.0

03/12/2013

Rob Anderson

2nd Draft Release for review


and comment.

2.1

04/12/2013

Joshua Reader

Amendments applied
following 2nd review by
Paul Comerford

Recoverpoint Design - VCE / WIPRO


Commercial-In-Confidence

Table of contents
Version

Date

Author

Description

3.0

05/12/2013

Rob Anderson

3rd Draft Release for review


and comment.

3.1

05/12/2013

Joshua Reader

Updated information
based on Design review.

4.0

18/12/2013

Paul Comerford

Final Release version for


Acceptance and Signoff.

Recoverpoint Design - VCE / WIPRO


Commercial-In-Confidence

Table of contents

Document
Authorisation

This section details the authorisation for this document.


EMC Corporation

Signature: _______________________

Date: ______________

Robert Anderson
Project Manager

VCE

Signature: _______________________

Date: ______________

Paul Comerford
Project Manager

WIPRO Ltd

Signature: _______________________

Date: ______________

Lal Sebastian
Project Manager

Recoverpoint Design - VCE / WIPRO


Commercial-In-Confidence

Chapter 1: Introduction

Table of contents
Document Control ............................................................................................................. 1
Copyright ............................................................................................................................... 1
Document Authorities ............................................................................................................. 1
Drafting and Release History.................................................................................................... 1
Document Authorisation ......................................................................................................... 3
EMC Corporation........................................................................................................................... 3
VCE............................................................................................................................................... 3
WIPRO Ltd ..................................................................................................................................... 3

Introduction ............................................................................................................ 5
Document Overview .......................................................................................................... 5
Background ............................................................................................................................ 5
Purpose.................................................................................................................................. 5
Scope .................................................................................................................................... 5
Exclusions ..................................................................................................................................... 5

Audience ................................................................................................................................ 5
Document Assumptions .......................................................................................................... 6

Solution Overview ................................................................................................... 7


RecoverPoint Product Family ............................................................................................. 8
RecoverPoint/CL ............................................................................................................................ 8
RecoverPoint/EX ............................................................................................................................ 8
RecoverPoint/SE ............................................................................................................................ 8

RecoverPoint Configurations.................................................................................................... 9
CDP Configurations ........................................................................................................................ 9
CRR Configurations ...................................................................................................................... 10
CLR configurations ....................................................................................................................... 10

RecoverPoint Hardware and Software .............................................................................. 11


RecoverPoint Software ...........................................................................................................11
RecoverPoint Appliance (RPA).................................................................................................11
RPA terminology ....................................................................................................................12
Splitters ................................................................................................................................12
Consistency Groups ...............................................................................................................13
Replication Sets.....................................................................................................................13
Journals.................................................................................................................................13
Volumes ................................................................................................................................14
Links .....................................................................................................................................14
Snapshots .............................................................................................................................15
Bookmarks ............................................................................................................................16
Snapshot consolidation ............................................................................................................... 16

Replication Mode ...................................................................................................................16


Asynchronous Replication mode ................................................................................................... 16

Recoverpoint Design - VCE / WIPRO


Commercial-In-Confidence

Chapter 1: Introduction
Synchronous Replication Mode..................................................................................................... 16
Dynamic Sync Mode..................................................................................................................... 17

VMware Site Recovery Manager Integration .............................................................................17

Recoverpoint Configuration ................................................................................... 18


Recoverpoint Zoning and Port Configuration .................................................................... 18
Recoverpoint Appliance Information ................................................................................ 20
Recoverpoint Storage Configuration ................................................................................ 21
Recoverpoint Consistency Groups ................................................................................... 24
Consistency Groups ...............................................................................................................24
Journals.................................................................................................................................25
Replication Sets.....................................................................................................................26
Group Sets ............................................................................................................................26
Links .....................................................................................................................................26
RecoverPoint User Accounts ...................................................................................................27
Alerting Information ...............................................................................................................27

A.

Firewall Ports ........................................................................................................ 30

B.

Abbreviations and Acronyms ................................................................................. 35

C.

Operational Considerations ................................................................................... 37


Device tagging .......................................................................................................................37

Recoverpoint Design - VCE / WIPRO


Commercial-In-Confidence

Chapter 1: Introduction

List of Tables
Table 1.

Contact Details for Proposed Changes .............................................................. 1

Table 2.

Drafting and Release History ............................................................................ 1

Table 3.

Recoverpoint Software ................................................................................... 11

Table 4.

Write Splitting Methods ................................................................................. 12

Table 5.

ECDC Vblock Fabric Port Allocations ............................................................... 18

Table 6.

ECDC Vblock Fabric Port Zoning...................................................................... 18

Table 7.

Norwest Vblock Fabric Port Allocations ........................................................... 18

Table 8.

Norwest Vblock Fabric Port Zoning ................................................................. 19

Table 9.

Replication Fabric Port Allocations ................................................................. 19

Table 10.

Replication Fabric Zoning............................................................................... 20

Table 11.

ECDC Recoverpoint Configuration................................................................... 20

Table 12.

Norwest Recoverpoint Configuration .............................................................. 21

Table 13.

ECDC LUN Requirements ................................................................................ 21

Table 14.

Norwest LUN Requirements............................................................................ 22

Table 15.

ECDC Initiator Groups .................................................................................... 23

Table 16.

ECDC Port Groups .......................................................................................... 23

Table 17.

ECDC Storage Groups .................................................................................... 23

Table 18.

ECDC Masking Views ..................................................................................... 23

Table 19.

Norwest Initiator Groups ................................................................................ 24

Table 20.

Norwest Port Groups ...................................................................................... 24

Table 21.

Norwest Storage Groups ................................................................................ 24

Table 22.

Norwest Masking Views ................................................................................. 24

Table 23.

Consistency Groups ....................................................................................... 25

Table 24.

Norwest Journal Volumes ............................................................................... 25

Table 25.

ECDC Journal Volumes ................................................................................... 26

Table 26.

Replication Sets ............................................................................................ 26

Table 27.

NorWest Group Sets ...................................................................................... 26

Table 28.

RecoverPoint User Accounts........................................................................... 27

Table 29.

Alerting Information....................................................................................... 28

Table 30.

Recoverpoint Firewall Ports ............................................................................ 30

Table 31.

Abbreviations and acronyms .......................................................................... 35

Recoverpoint Design - VCE / WIPRO


Commercial-In-Confidence

Chapter 1: Introduction

List of Figures
Figure 1.

RecoverPoint Network Topologies .................................................................... 7

Figure 1.

RecoverPoint SE Replication Topologies ......................................................... 10

Figure 2.

RecoverPoint Gen 5 Appliance ....................................................................... 11

Figure 3.

NorWest RecoverPoint Consistency Groups .................................................... 25

Figure 4.

RecoverPoint Logs Screen with Filter .............................................................. 28

Recoverpoint Design - VCE / WIPRO


Commercial-In-Confidence

Chapter 1: Introduction

Introduction

Document Overview
Background

VCE is delivering a solution based on two VMAX 40K based Vblock 720 systems to
Woolworths Ltd, through Wipro Australia Pty Ltd, as a consolidation target for their
End User Compute, Active Directory, P2V and V2V workloads. This will consist of a
new Vblock at the Norwest Data Centre, and a reconfiguration of the existing nonproduction proof of concept Vblock at the Eastern Creek Data Centre.
The Vblock systems will have remote replication set up between then using
RecoverPoint. For this purpose, the RecoverPoint Continuous Remote Replication
(CRR) solution has been sold by VCE as port of the Vblock 720 bill of materials.
EMC has been engaged to provide the services to design and implement the
VMAX 40K storage configuration and RecoverPoint CRR as part of the VCE Vblock
solution. This engagement covers the planning, design and implementation of the
VMAX 40K custom storage configuration and RecoverPoint CRR across two Vblock
720 systems spread across two Woolworths data centres (Norwest and ECDC).

Purpose

This document covers the design of the RecoverPoint replication solution between
the two sites, Norwest and Eastern Creek

Scope

This design includes the RecoverPoint replication between the two sites and the
configuration required to replicate between Norwest and Eastern Creek.
Exclusions

This design document does not include the design for the VMAX and MDS9513 switches, except where it relates directly to the RecoverPoint
replication.

This design does not include RecoverPoint integration with VMware Site
Recovery Manager (SRM).

All compute and network components of the Vblock are outside of the
scope of the EMC engagement.

Audience
The intended audience of this document includes:

VCE / WIPRO technical staff, project stakeholders and sponsors;

EMC implementation team; and

VCE / WIPRO staff responsible for the ongoing maintenance of the EMC
infrastructure.

Recoverpoint Design - VCE / WIPRO


Commercial-In-Confidence

Chapter 1: Introduction

Document
Assumptions

The below assumptions have been made while creating this document:
The reader hasfamiliarity with the technical and conceptual functions of a storage
array, Recoverpoint cluster, IP networking and replication methodologies.

Recoverpoint Design - VCE / WIPRO


Commercial-In-Confidence

Chapter 2: Solution Overview

Solution Overview
RecoverPoint will be used to provide inter-site bi-directional remote replication
between the two Vblocks currently situated at Norwest and ECDC. It is capable of
providing synchronous or asynchronous replication for the storage environment
for full site and partial site failover.
Recoverpoint is currently scoped to replicate 20TB of information.Data will flow
from the Array splitters to the Recoverpoint clusters, and then across the existing
replication and DWDM links via fibre channel.
Nexus 5k B

ECDC Vblock

Nexus 5k B
SLOT2

Cisco Nexus 5010


STAT

L2 MGMTO

MGMT1

CONSOLE

10 11

12 13

14 15

16

10 19

17

20

L1

L2 MGMTO

MGMT1

CONSOLE

Nexus 5k A

10 11

12 13

14 15

16

10 19

17

20

Nexus 5k A
SLOT2

STAT

10

11

12

13

14

15

16

17

18

19

20

21

22

23

SERIES

L2 MGMTO

MGMT1

CONSOLE

10 11

12 13

14 15

16

10 19

17

AMP
Switch B

PS2

PS2
L1

Catalyst 3560
1

Cisco Nexus 5010

SLOT2

Cisco Nexus 5010


STAT

PS1

AMP
Switch B

PS1

L1

PS2

PS2

PS1

SLOT2

Cisco Nexus 5010


STAT

PS1

Norwest Vblock

20

L1

L2 MGMTO

MGMT1

CONSOLE

10 11

12 13

14 15

16

10 19

17

20

PoE-24

Catalyst 3560

24

1X

11X

13X

23X

2X

12X

14X

24X

SYST
RPS

10

11

12

13

14

15

16

17

18

19

20

21

22

23

SERIES

PoE-24

SERIES

PoE-24

24

1X

11X

13X

23X

2X

12X

14X

24X

1X

11X

13X

2X

12X

14X

SYST
RPS

STAT
DUPLX
SPEED
POE

STAT
DUPLX
SPEED
POE

MODE

MODE

Catalyst 3560
1

10

11

12

13

1X

11X

14

15

16

17

18

19

20

21

22

23

SERIES

Woolworths WAN

PoE-24

24

13X

23X

SYST
RPS
STAT
DUPLX
SPEED
POE

1
2X

12X

14X

Catalyst 3560
1

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24
23X

SYST
RPS
STAT
DUPLX
SPEED
POE

24X

MODE

24X

MODE

AMP
Switch A

AMP
Switch A

RPA 1

RPA 1
Replication Fabric A
MDS 9124 MULTILAYER FABRIC SWITCH

CISCO

CONSOLE

MGMT 10/100

MGMT 10/100

STATUS

P/S

P/S

FAN

FAN
RESET

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

RESET

DS-C9124-K9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

MDS 9124 MULTILAYER FABRIC SWITCH

CISCO

CONSOLE

MGMT 10/100
P/S
FAN
2

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

DS-C9124-K9

RESET

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

DS-C9124-K9

DS-C9513

DS-C9513

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

DS-X9248-48K9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

1/2/4/8 Gbps 4/44-port FC Module

STATUS
LINK

DS-13SLT-FAB2

Replication Fabric B

MGMT

CONSOLE

MGMT
10/100

LINK

COM
1

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

LINK

LINK

MGMT

SYSTEM

ACTIVE

RESET

STATUS

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

STATUS

DS-X9530-SF2-K9

MGMT
10/100

CONSOLE

MGMT
10/100

LINK

COM
1

USB 1

CONSOLE

MGMT
10/100

CONSOLE

MGMT
10/100

USB 2

ACT

LINK

COM
1

USB 1
USB 2

ACT
SUPERVISOR 2
DS-X9530-SF2-K9

LINK

COM
1

USB 1

USB 2

ACT

LINK

COM
1

USB 1
USB 2

ACT
SUPERVISOR 2

DS-13SLT-FAB2

8
STATUS

FABRIC MODULE 2
DS-13SLT-FAB2

9
STATUS

FABRIC MODULE 2
DS-13SLT-FAB2

10
STATUS

STATUS

FABRIC MODULE 2
DS-13SLT-FAB2

11

11
STATUS

STATUS

FABRIC MODULE 2

FABRIC MODULE 2

DS-13SLT-FAB2

DS-13SLT-FAB2

12

12
STATUS

STATUS

FABRIC MODULE 2

FABRIC MODULE 2

DS-13SLT-FAB2

DS-13SLT-FAB2

13

13
STATUS

STATUS

FABRIC MODULE 2

FABRIC MODULE 2

MDS 9500

SERIES

MDS-9513
SAN A

FABRIC MODULE 2

CONSOLE

STATUS

MDS 9500

STATUS

DS-13SLT-FAB2

STATUS

STATUS

STATUS

DS-13SLT-FAB2

FABRIC MODULE 2

DS-13SLT-FAB2

STATUS

DS-13SLT-FAB2

FABRIC MODULE 2

DS-13SLT-FAB2

STATUS

1/2/4/8 Gbps 4/44-port FC Module

STATUS

DS-13SLT-FAB2

DS-13SLT-FAB2

DS-X9248-48K9

FAN
STATUS

DS-13SLT-FAB2

DS-13SLT-FAB2

MDS-9513
SAN B

15

14

SUPERVISOR 2

FABRIC MODULE 2

SERIES

14

13

FABRIC MODULE 2

FABRIC MODULE 2

MDS 9500

13

12

FABRIC MODULE 2

13
STATUS

12

11

FABRIC MODULE 2

12
STATUS

DS-13SLT-FAB2

FABRIC MODULE 2

11

10

FABRIC MODULE 2

DS-13SLT-FAB2

FABRIC MODULE 2

10

11
STATUS

FABRIC MODULE 2

10
STATUS

DS-13SLT-FAB2

13

USB 1

STATUS

DS-13SLT-FAB2

FABRIC MODULE 2

11

USB 2

STATUS

DS-13SLT-FAB2

FABRIC MODULE 2

12

SUPERVISOR 2

COM
1

ACT

DS-13SLT-FAB2

FABRIC MODULE 2

10
STATUS

DS-13SLT-FAB2

DS-X9530-SF2-K9

LINK

SUPERVISOR 2

STATUS

DS-13SLT-FAB2

FABRIC MODULE 2

USB 2

ACT

PWR

MGMT

SYSTEM

ACTIVE

RESET

STATUS

PWR

USB 1
USB 2

STATUS

DS-13SLT-FAB2

FABRIC MODULE 2

USB 1

SUPERVISOR 2

COM
1

ACT

DS-13SLT-FAB2

FABRIC MODULE 2

STATUS

MGMT
10/100

DS-X9530-SF2-K9

LINK

SUPERVISOR 2

DS-X9530-SF2-K9

CONSOLE

USB 2

ACT
SUPERVISOR 2
DS-X9530-SF2-K9

10

FABRIC MODULE 2

SYSTEM

ACTIVE

USB 1

RESET

MGMT
10/100

COM
1

STATUS

CONSOLE

LINK

PWR

MGMT

SYSTEM

ACTIVE

RESET

STATUS

PWR

MGMT
10/100

5
STATUS

DS-X9530-SF2-K9

CONSOLE

STATUS

DS-13SLT-FAB2

FABRIC MODULE 2

DS-X9530-SF2-K9

1/2/4/8 Gbps 4/44-port FC Module

STATUS

DS-13SLT-FAB2

FABRIC MODULE 2

5
STATUS

FABRIC MODULE 2

2
LINK
DS-13SLT-FAB2

FABRIC MODULE 2

4
STATUS

DS-13SLT-FAB2

1/2/4/8 Gbps 4/44-port FC Module

STATUS
LINK

DS-X9248-48K9

STATUS

DS-13SLT-FAB2

FABRIC MODULE 2

DS-X9248-48K9

1
STATUS

2
FAN
STATUS

STATUS

FABRIC MODULE 2

DS-C9513

1/2/4/8 Gbps 4/44-port FC Module

1
LINK
DS-X9248-48K9

FAN
STATUS

MGMT

12

11

SYSTEM

11

10

ACTIVE

10

RESET

STATUS

PWR

MGMT

SYSTEM

ACTIVE

RESET

STATUS

PWR

MGMT

SYSTEM

ACTIVE

STATUS

DS-13SLT-FAB2

RESET

1/2/4/8 Gbps 4/44-port FC Module

STATUS

DS-13SLT-FAB2

FABRIC MODULE 2

STATUS

2
LINK
DS-13SLT-FAB2

FABRIC MODULE 2

MGMT

1/2/4/8 Gbps 4/44-port FC Module

STATUS
LINK

DS-X9248-48K9

STATUS

SYSTEM

DS-X9248-48K9

1
STATUS

PWR

1/2/4/8 Gbps 4/44-port FC Module

ACTIVE

DS-C9513

RESET

RESET

DS-X9248-48K9

RPA 2

MGMT 10/100

STATUS

P/S
FAN

STATUS

CONSOLE
STATUS

FAN
STATUS

DS-C9124-K9

MDS 9124 MULTILAYER FABRIC SWITCH

CISCO

PWR

RPA 2

MDS 9124 MULTILAYER FABRIC SWITCH

CISCO

CONSOLE
STATUS

SERIES

MDS-9513
SAN B

MDS 9500

SERIES

MDS-9513
SAN A

Internal Fibre Channel


External Fibre Channel
Internal Ethernet

VMAX
40K

External Ethernet

Figure 1.

VMAX
40K

RecoverPoint Network Topologies

Not all of the data on the Vblocks will be replicated. Specifically, only part of the
data assigned to the GP clusters will be replicated. Replication will be bidirectional, i.e. Norwest to ECDC and ECDC to Norwest.
The purpose of the replication is to provide DR capability in the event of a failure
of the entire site or entire Vblock. In the event of one of these failures, all of the
replicated data will be failed over to the surviving site. Partial failover at a
consistency group level is also supported by the technology. This allows virtual
machines to be reemployed, or tested, at the disaster recovery site.
The RecoverPoint installation is also not intended to provide backup and recovery
capability of historical data. It is intended only to provide DR Failover using the
current or near current version of the data.
Recoverpoint Design - VCE / WIPRO
Commercial-In-Confidence

Chapter 2: Solution Overview

RecoverPoint Product Family


The RecoverPoint product family consists of three products, RecoverPoint/CL,
RecoverPoint/EX and RecoverPoint/SE.
RecoverPoint/CL
EMC RecoverPoint provides block-level continuous data protection and
continuous remote replication for on-demand protection and recovery at any point
in time, and enables you to implement a single, unified solution to protect and/or
replicate data across heterogeneous servers and storage.

RecoverPoint/EX
RecoverPoint/EX provides all of the data protection of RecoverPoint/CL, with the
following limitations:

Only the following storage arrays are supported:


o

VMAX series

VNX series

CLARiiON AX4-5, CX4, CX3, and CX series

Block LUNs from Fibre Channel Celerra NS20, NS40, NS80, NS120, NS-240, and NS-960

Only the following splitter types are supported:


o

VNX/CLARiiON-based splitters

Symmetrix-based splitters

RecoverPoint/SE
RecoverPoint/SE helps customers with homogenous VNX/CLARiiON environments
implement a single unified solution for data protection, simplifying management,
reducing costs, and avoiding data loss due to server failures or data corruption.
RecoverPoint/SE gives you on-demand protection and recovery at any point in
time, and enables you to implement a single unified solution for the data
protection of your midrange networked storage.
RecoverPoint/SE has the same features and capabilities of RecoverPoint/CL, with
the following exceptions:

RecoverPoint/SE limits the number of arrays that can be replicated, per


RecoverPoint configuration.
o

In CDP configurations, replication can only be performed on a


single VNX/CLARiiON array, meaning both the production and the
replica copy must reside on the same VNX/CLARiiON array

In CRR and CLR configurations, replication can only be performed


from one production VNX/CLARiiON array to another
VNX/CLARiiON array at the DR site.

Recoverpoint Design - VCE / WIPRO


Commercial-In-Confidence

Chapter 2: Solution Overview

Design Decision
Recoverpoint/EX has been chosen to handle replication between the Norwest and
Eastern Creek Data Centers

RecoverPoint
Configurations

EMC RecoverPoint replicates data over any distance:

within the same site or to a local bunker site some distance away, CDP
configurations

to a remote site, CRR configurations

to both a local and a remote site simultaneously, CLR configurations

CDP Configurations
RecoverPoint continuous data protection (CDP) tracks changes to data at a block
level and journals these changes. The journal then allows rolling data to a
previous "Point-In-Time" in order to view the drive contents as they were before a
certain data corruption. CDP can journal each write individually, hence enabling
"Any-Point-In-Time" snapshots, or it can be configured to combine consecutive
writes in order to reduce journal space and improve bandwidth.
There are two types of CDP configurations:

(Standard) CDP - in which all components (splitters, storage, RPAs, and


hosts) exist at the same site.

Stretch CDP - in which the production host exists at the local site, splitters
and storage exist at both the bunker site and the local site, and the RPAs
only exist at the bunker site. In this configuration, the repository volume
and both the production and local journals exist at the bunker site.

RecoverPoint CDP can instantly recover data to any PIT by leveraging bookmarks
from the replica journal. In CDP configurations, data can be replicated locally at a
distance that does not exceed the limitation specified in the EMC RecoverPoint
Release Notes, and the data is transferred by Fibre Channel. By definition, writes
from the splitter to the RPA are written synchronously, and snapshot granularity is
set to per second, so the exact data size and contents are ultimately dependent
upon the number of writes made by the host application per second.
Users can change the snapshot granularity to per write, if necessary. Users can
also set the replication mode to synchronous, when an RPO time of zero is
required.

Recoverpoint Design - VCE / WIPRO


Commercial-In-Confidence

Chapter 2: Solution Overview

CRR Configurations
RecoverPoint continuous remote replication (CRR) enables a replica in a remote
site.
In CRR configurations, data is transferred between two sites over Fibre Channel or
a WAN. In this configuration, the RPAs, storage and splitters exist at both the local
and the remote site.
By default, the replication mode is set to asynchronous, and snapshot granularity
is set to dynamic, so the exact data size and contents are ultimately dependent
upon the policies set by the user and system performance. This provides
protection to application consistent, and other specific points in time.
CLR configurations
Continuous Local and Remote Protection (CLR) provide the benefits of both
previous forms of protection.
Both RecoverPoint CDP and CRR feature bidirectional replication and a point-intime recovery mechanism which enables replica volumes to be rolled back to a
previous point-in-time and used for read/write operations without effecting the
ongoing replication process or data protection.

Figure 1.

RecoverPoint SE Replication Topologies

Design Decision
CRR will be utilized in the environment to provide remote protection to allow for
full site and partial site failover of the environment.
Recoverpoint is bi-directional and will allow each array will be a target for their
remote partner.

Recoverpoint Design - VCE / WIPRO


Commercial-In-Confidence

10

Chapter 2: Solution Overview

RecoverPoint Hardware and Software


The following replication hardware and software is used in the RecoverPoint
solution:
RecoverPoint
Software

RecoverPoint
Appliance (RPA)

The current supported version of RecoverPoint is currently 4.0.


Table 3.

Recoverpoint Software

Software

Version

RecoverPoint Operating System

EMC RecoverPoint Appliance 4.0 SP1

The RPA is Recoverpoint's intelligent data protection appliance. In RecoverPoint,


RPAs manage all aspects of reliable data replication at all sites.
The RecoverPoint appliance (RPA) is a 1U hardware based server. The
specification of the RPA is as follows:

2 x Quad Core Sandy Bridge Processors

Two 300GB 10K RPM 2.5 SAS Drives in RAID1 configuration

6 x 1GE ports (RJ-45) WAN, LAN & Remote management + 3 ports are
unused

16 Gig DDR3 Memory

8Gb quad HBA

Port usage for WAN, LAN and the HBA Port Sequence (left to right) 0-1-2-3
(labelled a-b-c-d) are outlined in Figure 2.

Figure 2.

RecoverPoint Gen 5 Appliance

During replication for a given consistency group, an RPA at the production site
makes intelligent decisions regarding when and what data to transfer to the
replica site. It bases these decisions on its continuous analysis of application
load and resource availability, balanced against the need to prevent degradation
of host application performance and to deliver maximum adherence to the
specified replication policy. The RPAs at the replica site distribute the data to the
replica storage.
In the event of failover, these roles can be reversed. Moreover, RecoverPoint
supports simultaneous bidirectional replication, where the same RPA can serve as
the production RPA for one consistency group and the replica RPA for another.

Recoverpoint Design - VCE / WIPRO


Commercial-In-Confidence

11

Chapter 2: Solution Overview

Each RPA has the following dedicated interfaces:

Fibre Channel. Used for data exchange with local host applications and
storage subsystems. The RPA supports a dual-port configuration to the
Fibre Channel, thereby providing redundant connectivity to the SANattached storage and the hosts.

WAN. Used to transfer data to other sites (Ethernet).

Management. Used to manage the RecoverPoint system (Ethernet).

You can access each RPA directly through an SSH connection to the RPAs
dedicated box-management IP address. You can also access all RPAs in the
RecoverPoint configuration through the virtual site-management IP address of
each site in the RecoverPoint configuration. In other words, once RecoverPoint is
configured, you can manage the entire installation from a single location.

RPA terminology

Splitters

In RecoverPoint, the following terminology is used when referencing RPAs:

Preferred RPA - Each consistency group must be assigned one or more


preferred RPAs.

RecoverPoint Cluster - A group of inter-linked RPAs, working together


closely, to provide replication services. A RecoverPoint cluster can be
deployed within a single site for CDP (or stretched CDP) configurations, or
deployed in two sites for CRR and CLR configuration.

A splitter is proprietary software that is installed on either host operating systems,


storage subsystems, or intelligent fibre switches.
The primary function of a splitter is to split application writes so that they are
sent to their normally designated storage volumes and the RPA simultaneously.
The splitter carries out this activity efficiently, with little perceptible impact on
host performance, since all CPU-intensive processing necessary for replication is
performed by the RPA.
Table 4.

Write Splitting Methods

Splitter

Details

Array
Based

An array-based splitter performs write splitting on the storage array.


Array-based splitters are available for the following storage systems:
CLARiiON CX3 and CX4
VNX Series
Symmetrix VMAX (requires RecoverPoint 3.4 SP1 or later)
The RecoverPoint array based splitters are included in the array
firmware (Enginuity for VMAX, VNX OE for VNX). The splitter enabler is
required to enable the splitter driver.

Recoverpoint Design - VCE / WIPRO


Commercial-In-Confidence

12

Chapter 2: Solution Overview

Design Decision
As of RecoverPoint version 4.0, only array based splitters are supported. Other
methods that were available in previous versions of Recoverpoint have been
deprecated.

Consistency
Groups

A consistency group is the fundamental building block of the Recoverpoint


environment
They each consist of one or more replication sets. Each replication set consists of
a production volume and the replica volumes to which it is replicating.
The consistency group ensures that updates to the replicas are always consistent
and in correct write order; that is, the replicas can always be used to continue
working or to restore the production source, in case it is damaged.
The consistency group monitors all the volumes added to it to ensure consistency
and write-order fidelity. If two data sets are dependent on one another (e.g.
Database and a Database log), they must be in the same consistency group.
Consistency groups are referenced in Table 23.

Replication Sets

Every SAN-attached storage volume in the production storage must have a


corresponding volume at each copy. A production volume and its associated
replica volumes are called a replication set (Table 26). Each consistency group
contains as many replication sets as there are volumes in the production storage
to replicate. Data consistency and write-order fidelity are maintained across all
volumes assigned to a consistency group, including volumes on different storage
systems.

Journals

One or more volumes are dedicated on the storage at each replica site for the
purpose of holding images that are either waiting to be distributed, or that have
already been distributed, to the replica storage.
Each journal holds as many images as its capacity allows. Subsequently, the
oldest image (provided that it has already been distributed to the copy storage) is
removed to make room for the newest one, in a first-in, first-out manner. The
actual number of images in the journal varies, depending on the size of the
images and the capacity of the storage dedicated to this purpose.
A list of Norwest and ECDC journals are referenced in Table 24 andTable 25.
You can address individual images in a replica journal. Hence, if required due to a
disaster, you can roll back the stored data image to an earlier image that was
unaffected by the disaster. Frequent small-aperture snapshots provide high
granularity for achieving maximum data recovery in the event of such a rollback.

Recoverpoint Design - VCE / WIPRO


Commercial-In-Confidence

13

Chapter 2: Solution Overview

Volumes

In the EMC RecoverPoint Management Application, LUNs are represented as


volumes. The following types of volumes exist in all RecoverPoint configurations:

Production Copy - The production copies are the volumes that are written
to by the host applications at the production site.

Local Copies - The local copies are the volumes that the production copies
are replicated to at the local site.

Remote Copies - The remote copies are the volumes that the production
copies are replicated to at the remote site.

Production Journals - The production journal volume stores information


about the replication process (called marking information) that is used to
make synchronization of the replication volumes at the two sites, when
required, much more efficient.

Copy Journals - Copy journals are dedicated to holding point-in-time


information for each image on the production storage, as well as
bookmarks that mark significant points in time. The copy journals hold all
changes to data, so that the copy storage can be rolled back to a previous
point in time (PIT). There are as many copy journals as there are local and
remote copies in a consistency group

Repository Volume - A special volume, called the repository volume, must


be dedicated on the SAN-attached storage at each site, for each RPA
cluster. The repository volume serves all RPAs of the particular cluster and
splitters associated with that cluster. It stores configuration information
about the RPAs and consistency groups, which enables a properly
functioning RPA to seamlessly assume the replication activities of a failing
RPA from the same cluster.

Design Decision
Copy Journals will be housed in a dedicated journal pool (RP-FC).
The journal pool is allocated at both data centers, with capacity for 6Tb of journal
storage. Apart from this pool, there has been no requirement for journals to
maintain specific RPOs within the environment.
With an assumed change rate of up to 20% per day, then the number of journals
allocated are sufficient to hold 24 hours worth of checkpoints.
Journal pool sizing and configuration referenced Woolworths WoW VMAX and
MDS 9513 Design v3.0. Individual volumes are referenced in Journals section of
the Recoverpoint configuration.

Links

A link is the communication pipe between the production and a copy, through
which data is transferred. In RecoverPoint, data transfer for each link can be over
WAN or Fibre Channel. There can be multiple links per consistency group, and the
number of links depends on the number of copies in the RecoverPoint system.

Recoverpoint Design - VCE / WIPRO


Commercial-In-Confidence

14

Chapter 2: Solution Overview

The following terms are used to describe the link placement in relation to the
production environment:

Remote linkIn remote replication, this is the link between the production
and the remote copy.

Local linkIn local replication, this is the link between the production and
the local copy.

Links are also a logical entity that consists of protection policies such as
replication mode (synchronous or asynchronous), RPO, compression, and
snapshot granularity. The link can be open, meaning that transfer is possible. The
link can be closed, meaning that transfer is not possible to the copy. A user or
system-triggered pause in transfer can trigger a link to close.

Design Decision
Remote links will be used and the transportation method will be over Fibre
Channel. No local links will be used at this time.
Snapshots

A snapshot is a point in time marked by the system for recovery purposes. A


snapshot includes only that data that has changed from the previous image. Upon
being distributed, it creates a new current image on the remote storage.
A snapshot is the difference between one consistent image of stored data and the
next. Snapshots are taken seconds apart. The application writes to storage; at the
same time, the splitter provides a second copy of the writes to the RecoverPoint
appliance. In asynchronous replication, the appliance gathers several writes into
a single snapshot. The exact time for closing the snapshot is determined
dynamically depending on replication policies and the journal of the consistency
group. In synchronous replication, each write is a snapshot. When the snapshot is
distributed to a replica, it is stored in the journal volume, making it possible to
revert to previous images by selecting the stored snapshots.
For each consistency group, a Snapshot Granularity policy can be configured to
regulate data transfer, and the following granularities can be defined:

Fixed (per write): To create a snapshot from every write operation.

Fixed (per second): To create one snapshot per second.

Dynamic: To have the system determine the snapshot granularity


according to available resources.

Design Decision
When replicating synchronously, it is mandated to use a fixed write capability so
that each write is a snapshot in order to maintain fully synchronous rollback
capability.
Fixed (per write) snapshots will be taken, in order to duplicate the minimum
functionality mandated by Woolworths and currently provided by SRDF/S.

Recoverpoint Design - VCE / WIPRO


Commercial-In-Confidence

15

Chapter 2: Solution Overview

Bookmarks

A bookmark is a named snapshot. The bookmark uniquely identifies an image.


Bookmarks can be set and named manually; they can also be created
automatically by the system either at regular intervals or in response to a system
event. Bookmarked images are listed by name.

Design Decision
Bookmarks are going to be taken and handled by the SRM application. Naming
standards may be referenced in the SRM design.

Snapshot consolidation
RecoverPoint captures every write, enabling you to recover data from any point in
time. Keeping days to months of every point in time, however, requires very large
journals. Over time, re-writes to a single disk location consume a large amount of
journal space. Additionally, the need to recover back to an exact point in time
decreases as the data ages. The granularity of snapshots becomes less important
over time. Snapshot consolidation enables longer-term point-in-time recovery
using the same storage consumption. Snapshot consolidation discards re-writes
to the same disk location to save on journal space, which allows a longer history
to be retained in the journal.

Design Decision
No Snapshot consolidation is being undertaken at this stage, as there is no
requirement for the consistency groups to be recovered beyond 24 hours.
Snapshot consolidation can be turned on at any time if requirements.
Replication Mode

Regardless of the replication mode, RecoverPoint is unique in its ability to


guarantee a consistent replica at the target side under all circumstances, and in
its ability to retain write order fidelity in multi-host heterogeneous SAN
environments.
Asynchronous Replication mode
The host application initiates a write, and does not wait for an acknowledgment
from the remote RPA before initiating the next write. The data of each write is
stored in the local RPA, and acknowledged at the local site. The RPA decides
based on the lag policy and system loads/available resources when to transfer
the writes in the RPA to the replica storage. This is the default replication mode.
The primary advantage of asynchronous replication is its ability to provide
synchronous-like replication without degrading the performance of host
applications.
Synchronous Replication Mode
The host application initiates a write, and then waits for an acknowledgment from
the remote RPA before initiating the next write. This is not the default replication
mode, and must be specified by the user.

Recoverpoint Design - VCE / WIPRO


Commercial-In-Confidence

16

Chapter 2: Solution Overview

Replication in synchronous mode produces a replica that is always one hundred


percent up-to-date with its production source. The trade-off is that to ensure that
no subsequent writes are made until an acknowledgement is received from the
remote RPA, host applications can be regulated by RecoverPoint, and this could
impact application performance. Alternatively, users can configure RecoverPoint
to dynamically alternate between synchronous and asynchronous replication
modes, according to predefined lag and/or throughput conditions.
Dynamic Sync Mode
Dynamic sync mode is a subset of the synchronous replication mode. In this
mode, protection policies can be defined that enable the group to automatically
begin replicating asynchronously whenever the groups data throughput or
latency reaches a maximum threshold.

Design Decision
Synchronous replication (Synchronous Replication Mode) will be used between
the Norwest and the Eastern Creek Data Center. This is to replicate the same base
functionality currently provided by SRDF/S
The functionality for asynchronous replication is available in the current
Recoverpoint environment, and can be utilized at a future time where deemed
necessary at a Consistency group level.

VMware Site Recovery Manager Integration


RecoverPoint can be integrated with VMware Site Recovery Manager (SRM). When
integrating RecoverPoint with SRM the following should be noted:

Failover is controlled by SRM rather than being manually initiated from


RecoverPoint

SRM protection groups should correspond to RecoverPoint consistency


groups

For RecoverPoint 4.0SP1, SRM version 5.1, 5.1u1 or 5.5 is required, with
the RecoverPoint Storage Replication Adapter (SRA) version 2.2.

Design Decision
SRM integration is not in the scope of this design document. WIPRO have been
contracted to provide automated integration between the EMC VMAX, the VMware
environment, and the Recoverpoint clusters.

Recoverpoint Design - VCE / WIPRO


Commercial-In-Confidence

17

Chapter 3: Recoverpoint Configuration

Recoverpoint Configuration

Recoverpoint Zoning and Port Configuration


Below are the physical connectivity requirements for the RP environment,
including port allocation on the fibre-channel switches and zoning configuration
for replication traffic.
Table 5.

ECDC Vblock Fabric Port Allocations

Fabric

RPA

RPA Port

Switch

Switch Port

RPA 1

ec1-mds-edg-fab-a-06

fc1/11

RPA 2

ec1-mds-edg-fab-a-06

fc2/24

RPA 1

ec1-mds-edg-fab-b-06

fc1/11

RPA 2

ec1-mds-edg-fab-b-06

fc2/24

Table 6.

ECDC Vblock Fabric Port Zoning

Fabric

Zone Name

Zone Member

WWN

RPA-journal_woolworths_com_au

RPA 1 Port 3

TBA

RPA 2 Port 3

TBA

VMAX FA-7h0

50:00:09:75:00:04:49:D8

VMAX FA-9h0

50:00:09:75:00:04:49:E0

RPA 1 Port 1

TBA

RPA 2 Port 1

TBA

VMAX FA-8h0

50:00:09:75:00:04:49:DD

VMAX FA-10h0

50:00:09:75:00:04:49:E4

RPA 1 Port 3

TBA

RPA 2 Port 3

TBA

VMAX FA-7f0

50:00:09:75:00:04:49:58

VMAX FA-9f0

50:00:09:75:00:04:49:60

RPA 1 Port 1

TBA

RPA 2 Port 1

TBA

VMAX FA-8f0

50:00:09:75:00:04:49:5C

VMAX FA-10f0

50:00:09:75:00:04:49:64

RPA-journal_woolworths_com_au

RPA-replicas_woolworths_com_au

RPA-replicas_woolworths_com_au

Table 7.

Norwest Vblock Fabric Port Allocations

Fabric

RPA

RPA Port

Switch

Switch Port

RPA 1

nw1-mds-edg-fab-a-06

fc1/11

Recoverpoint Design - VCE / WIPRO


Commercial-In-Confidence

18

Chapter 3: Recoverpoint Configuration


Fabric

RPA

RPA Port

Switch

Switch Port

RPA 2

nw1-mds-edg-fab-a-06

fc2/24

RPA 1

nw1-mds-edg-fab-b-06

fc1/11

RPA 2

nw1-mds-edg-fab-b-06

fc2/24

Table 8.

Norwest Vblock Fabric Port Zoning

Fabric

Zone Name

Zone Member

WWN

RPA-journals_woolworths_com_au

RPA 1 Port 3

TBA

RPA 2 Port 3

TBA

VMAX FA-7h0

50:00:09:75:00:06:E5:D8

VMAX FA-9h0

50:00:09:75:00:06:E5:E0

RPA 1 Port 1

TBA

RPA 2 Port 1

TBA

VMAX FA-8h0

50:00:09:75:00:06:E5:DC

VMAX FA-10h0

50:00:09:75:00:06:E5:E4

RPA 1 Port 3

TBA

RPA 2 Port 3

TBA

VMAX FA-7g0

50:00:09:75:00:06:E5:98

VMAX FA-9g0

50:00:09:75:00:06:E5:A0

VMAX FA-5e0

50:00:09:75:00:06:E5:10

VMAX FA-5f0

50:00:09:75:00:06:E5:50

VMAX FA-5g0

50:00:09:75:00:06:E5:90

RPA 1 Port 1

TBA

RPA 2 Port 1

TBA

VMAX FA-8g0

50:00:09:75:00:06:E5:9C

VMAX FA-10g0

50:00:09:75:00:06:E5:A4

VMAX FA-6e0

50:00:09:75:00:06:E5:14

VMAX FA-6f0

50:00:09:75:00:06:E5:54

VMAX FA-6g0

50:00:09:75:00:06:E5:94

RPA-journals_woolworths_com_au

RPA-replicas_woolworths_com_au

RPA-replicas_woolworths_com_au

Table 9.

Replication Fabric Port Allocations

Site

Fabric

RPA

RPA Port

Switch

Switch Port

ECDC

RPA 1

ec1-mds-rdf-fab-a-01

fc2/2

ECDC

RPA 2

ec1-mds-rdf-fab-a-01

fc2/6

ECDC

RPA 1

ec1-mds-rdf-fab-b-02

fc2/2

ECDC

RPA 2

ec1-mds-rdf-fab-b-02

fc2/6

Recoverpoint Design - VCE / WIPRO


Commercial-In-Confidence

19

Chapter 3: Recoverpoint Configuration


Site

Fabric

RPA

RPA Port

Switch

Switch Port

Norwest

RPA 1

nw1-mds-rdf-fab-a-01

fc2/2

Norwest

RPA 2

nw1-mds-rdf-fab-a-01

fc2/6

Norwest

RPA 1

nw1-mds-rdf-fab-b-02

fc2/2

Norwest

RPA 2

nw1-mds-rdf-fab-b-02

fc2/6

Table 10.

Replication Fabric Zoning

Fabric

Zone Name

Zone Member

WWN

RPA-RPA_woolworths_com_au

Norwest RPA 1 Port 0 TBA


Norwest RPA 2 Port 0 TBA

RPA-RPA_woolworths_com_au

ECDC RPA 1 Port 0

TBA

ECDC RPA 2 Port 0

TBA

Norwest RPA 1 Port 2 TBA


Norwest RPA 2 Port 2 TBA
ECDC RPA 1 Port 2

TBA

ECDC RPA 1 Port 2

TBA

Recoverpoint Appliance Information


The information required to install and configure the Recoverpoint appliance for
each site cluster is included below.

Table 11.

ECDC Recoverpoint Configuration

RecoverPoint Appliance Information - Source Site

ec1vbkrp001
Site Name
Management Interface IP
Management Interface Subnet mask
Management Interface Gateway
Cluster Interface IP (Management
Subnet)
WAN/Private Interface IP

ec1vbkrp002
ECDC

10.171.148.13

10.171.148.14

255.255.255.0
10.171.148.1
10.171.148.15
10.166.224.11

10.166.224.12

WAN/Private Interface Subnet mask

255.255.255.0

WAN/Private Interface Gateway

10.166.224.1

Primary DNS IP
Secondary DNS IP
Network Time Protocol IP
Remote Maintenance TCP Port (optional)

10.166.177.139
10.134.177.139
10.134.131.253, 10.134.131.254
-

Recoverpoint Design - VCE / WIPRO


Commercial-In-Confidence

20

Chapter 3: Recoverpoint Configuration


Australia/Sydney

Time Zone
Local DNS Domain Name
Table 12.

woolworths.com.au
Norwest Recoverpoint Configuration

RecoverPoint Appliance Information - Source Site

nw1vbkrp001

nw1vbkrp002

Norwest

Site Name
Management Interface IP
Management Interface Subnet mask
Management Interface Gateway
Cluster Interface IP (Management Subnet)

10.139.148.13

10.139.148.14

255.255.255.0
10.139.148.1
10.139.148.15

WAN/Private Interface IP

10.134.224.1
1

10.134.224.12

WAN/Private Interface Subnet mask

255.255.255.0

WAN/Private Interface Gateway

10.134.224.1
10.134.177.139

Primary DNS IP
Secondary DNS IP
Network Time Protocol IP
Remote Maintenance TCP Port (optional)
Time Zone
Local DNS Domain Name

10.166.177.139
10.134.131.253, 10.134.131.254
Australia/Sydney
woolworths.com.au

Recoverpoint Storage Configuration


VMAX storage needs to be assigned for the Recoverpoint appliance production
and journal volumes.
Table 13.

ECDC LUN Requirements

Purpose

Size

Thin Pool /
Disk Group

Device #

Repository

5.72 GB

Pool RP-FC

TBA

Journal

100 GB

Pool RP-FC

TBA

Journal

100 GB

Pool RP-FC

TBA

Journal

100 GB

Pool RP-FC

TBA

Journal

100 GB

Pool RP-FC

TBA

Journal

100 GB

Pool RP-FC

TBA

Journal

100 GB

Pool RP-FC

TBA

Journal

100 GB

Pool RP-FC

TBA

Journal

100 GB

Pool RP-FC

TBA

Gatekeeper

3 cylinder

Disk Group 1

007D

Gatekeeper

3 cylinder

Disk Group 1

007E

Comments

Recoverpoint Design - VCE / WIPRO


Commercial-In-Confidence

21

Chapter 3: Recoverpoint Configuration


Purpose

Size

Thin Pool /
Disk Group

Device #

Gatekeeper

3 cylinder

Disk Group 1

007F

Gatekeeper

3 cylinder

Disk Group 1

0080

Gatekeeper

3 cylinder

Disk Group 1

0081

Gatekeeper

3 cylinder

Disk Group 1

0082

Gatekeeper

3 cylinder

Disk Group 1

0083

Gatekeeper

3 cylinder

Disk Group 1

0084

Gatekeeper

3 cylinder

Disk Group 1

0085

Gatekeeper

3 cylinder

Disk Group 1

0086

Gatekeeper

3 cylinder

Disk Group 1

0087

Gatekeeper

3 cylinder

Disk Group 1

0088

Gatekeeper

3 cylinder

Disk Group 1

0089

Gatekeeper

3 cylinder

Disk Group 1

008A

Gatekeeper

3 cylinder

Disk Group 1

008B

Gatekeeper

3 cylinder

Disk Group 1

008C

Table 14.

Comments

Norwest LUN Requirements

Purpose

Size

Thin Pool /
Disk Group

Device #

Repository

5.72 GB

Pool RP-FC

TBA

Journal

100 GB

Pool RP-FC

TBA

Journal

100 GB

Pool RP-FC

TBA

Journal

100 GB

Pool RP-FC

TBA

Journal

100 GB

Pool RP-FC

TBA

Journal

100 GB

Pool RP-FC

TBA

Journal

100 GB

Pool RP-FC

TBA

Journal

100 GB

Pool RP-FC

TBA

Journal

100 GB

Pool RP-FC

TBA

Gatekeeper

3 cylinder

Disk Group 1

00A9

Gatekeeper

3 cylinder

Disk Group 1

00AA

Gatekeeper

3 cylinder

Disk Group 1

00AB

Gatekeeper

3 cylinder

Disk Group 1

00AC

Gatekeeper

3 cylinder

Disk Group 1

00AD

Gatekeeper

3 cylinder

Disk Group 1

00AE

Gatekeeper

3 cylinder

Disk Group 1

00AF

Comments

Recoverpoint Design - VCE / WIPRO


Commercial-In-Confidence

22

Chapter 3: Recoverpoint Configuration


Purpose

Size

Thin Pool /
Disk Group

Device #

Gatekeeper

3 cylinder

Disk Group 1

00B0

Gatekeeper

3 cylinder

Disk Group 1

00B1

Gatekeeper

3 cylinder

Disk Group 1

00B2

Gatekeeper

3 cylinder

Disk Group 1

00B3

Gatekeeper

3 cylinder

Disk Group 1

00B4

Gatekeeper

3 cylinder

Disk Group 1

00B5

Gatekeeper

3 cylinder

Disk Group 1

00B6

Gatekeeper

3 cylinder

Disk Group 1

00B7

Gatekeeper

3 cylinder

Disk Group 1

00B8

Table 15.

Comments

ECDC Initiator Groups

IG Name

Member WWNs

Member IGs

Consistent LUN

RPA_1_IG

TBA

None

Yes

RPA_2_IG

TBA

None

Yes

RPA_Cluster_IG

None

RPA_1_IG, RPA_2_IG

Yes

Table 16.

ECDC Port Groups

PG Name

Member Ports

RPA_PG

7h0, 8h0, 9h0, 10h0

RPA_Replica_PG

7f0, 8f0, 9f0, 10f0

Table 17.

ECDC Storage Groups

SG Name
RPA_1_SG

Member Devices
007D,007E,007F,0080,0081,0082,0083,0084

RPA_2_SG

0085,0086,0087,0088,0089,008C,008B,008C

RPA_Cluster_SG

TBA (Repository and Journals)

RPA_Replica_SG

S_VMAX_PRD_A0274_GP-010-S
S_VMAX_PRD_A0274_GP-011-S
S_VMAX_PRD_A0274_GP-012-S

Table 18.

ECDC Masking Views

MV Name

Initiator Group

Storage Group

Port Group

RPA_1_MV

RPA_1_IG

RPA_1_SG

RPA_PG

RPA_2_MV

RPA_2_IG

RPA_2_SG

RPA_PG

Recoverpoint Design - VCE / WIPRO


Commercial-In-Confidence

23

Chapter 3: Recoverpoint Configuration


MV Name

Initiator Group

Storage Group

Port Group

RPA_Cluster_MV

RPA_Cluster_IG

RPA_Cluster_SG

RPA_PG

RPA_Replica_MV

RPA_Cluster_IG

RPA_Replica_SG

RPA_Replica_PG

Table 19.

Norwest Initiator Groups

IG Name

Member
WWNs

Member IGs

Consistent LUN

IG-RPA_1

TBA

None

Yes

IG-RPA_2

TBA

None

Yes

IG-RPA_Cluster

None

IG-RPA_1, IG-RPA_2

Yes

Table 20.

Norwest Port Groups

PG Name

Member Ports

PG-RPA

7h0, 8h0, 9h0, 10h0

PG-RPA_Replica

7g0, 8g0, 9g0, 10g0, 5e0, 6e0, 5f0, 6f0, 5g0, 6g0

Table 21.

Norwest Storage Groups

SG Name

Member Devices

SG-RPA_1

00A9,00AA,00AB,00AC,00AD,00AE,00AF,00B0

SG-RPA_2

00B1,00B2,00B3,00B4,00B5,00B6,00B7,00B8

SG-RPA_Cluster

TBA (Repository and Journals)

SG-RPA_Replica

S_VMAX_PRD_A0441_GP-010-S
S_VMAX_PRD_A0441_GP-011-S
S_VMAX_PRD_A0441_GP-012-S

Table 22.

Norwest Masking Views

MV Name

Initiator Group

Storage Group

Port Group

MV-RPA_1

IG-RPA_1

SG-RPA_1

PG-RPA

MV-RPA_2

IG-RPA_2

SG-RPA_2

PG-RPA

MV-RPA_Cluster

IG-RPA_Cluster

SG-RPA_Cluster

PG-RPA

MV-RPA_Replica

IG-RPA_Cluster

SG-RPA_Replica

PG-RPA_Replica

Recoverpoint Consistency Groups


Consistency
Groups

Due to the evolving nature of the environment, Consistency groups are to be set
up as follows to test the functionality of the Recoverpoint Solution.

Recoverpoint Design - VCE / WIPRO


Commercial-In-Confidence

24

Chapter 3: Recoverpoint Configuration

Journals

Figure 3.

Norwest RecoverPoint Consistency Groups

Table 23.

Consistency Groups

CG Name

Direction

Primary
RPA

Priority

Distributed

External
Management

CG-NOR-Test1

Norwest ->
ECDC

Norwest
RPA 1

Normal

No

None

CG-NOR-Test2

Norwest ->
ECDC

Norwest
RPA 2

Normal

No

None

CG-NOR-Test3

Norwest ->
ECDC

Norwest
RPA 2

Normal

No

None

List all journal policy settings (same for all journals)


Table 24.

Norwest Journal Volumes

Consistency Group

Journal Type

VMAX Device

CG-NOR-Test1

Production

TBA

CG-NOR-Test2

Production

TBA

CG-NOR-Test3

Production

TBA

Recoverpoint Design - VCE / WIPRO


Commercial-In-Confidence

25

Chapter 3: Recoverpoint Configuration


Table 25.

ECDC Journal Volumes

Consistency Group

Journal Type

VMAX Device

CG-NOR-Test1

Copy

TBA
TBA

CG-NOR-Test2

Copy

TBA
TBA
TBA
TBA

CG-NOR-Test3

Copy

TBA
TBA
TBA

Table 26.

Replication Sets

Production
Copy

Direction

Production VMAX Device

Remote VMAX Device

CG-NORTest1

Norwest ->
ECDC

S_VMAX_PRD_A0441_GP010-S

S_VMAX_PRD_A0274_GP010-S

CG-NORTest2

Norwest ->
ECDC

S_VMAX_PRD_A0441_GP011-S

S_VMAX_PRD_A0274_GP011-S

CG-NORTest3

Norwest ->
ECDC

S_VMAX_PRD_A0441_GP012-S

S_VMAX_PRD_A0274_GP012-S

Table 27.

Group Sets

Links

Replication Sets

Norwest Group Sets

Group Set

Remote Copy

Production CG

Remote CG

GS-NOR-Test

Norwest -> ECDC

CG-NOR-Test2

CG-NOR-Test2-remote

CG-NOR-Test3

CG-NOR-Test3-remote

Woolworths, in conjunction with WIPRO, have advised EMC to use a 300Mbit


Ethernet network for the use of RecoverPoint. With an average of 8% of Network
overhead RecoverPoint is expected to use 43MB/sec of throughput. EMC have
used this information along with Performance Data from the hosts to be replicated
and have validated the following consistency groups

Recoverpoint Design - VCE / WIPRO


Commercial-In-Confidence

26

Chapter 3: Recoverpoint Configuration

RecoverPoint User
Accounts

Alerting
Information

Table 28.

RecoverPoint User Accounts

Username

Password

Permissions

Description

Admin

Admin

All, except
install and web
download

Preconfigured account,
cannot be removed, default
password should be
changed.

boxmgmt

Boxmgmt

Install

Preconfigured account,
cannot be removed, default
password should be
changed.

Monitor

Monitor

None (read
only)

Preconfigured account,
cannot be removed, default
password should be
changed.

webdownload

Webdownload

Webdownload

Preconfigured account,
cannot be removed, default
password should be
changed.

Root

Boxmgmt

All

Allows access to the iDRAC


card for offline management

RecoverPoint supports email, SNMP and syslog servers for event notification.
The system records log entries in response to a wide range of pre-defined events.
Each event carries an event ID. In addition, each event is defined by a topic, level
of severity, and scope.
Event topics correspond to the components of the RecoverPoint system where the
events occur, including: Site; Splitter; Management (i.e., RecoverPoint
Management Console and CLI); Consistency group; RPA. A single event can
generate multiple log entries.
To display event logs, in the Navigation pane, select Logs. The most recent events
in the event log are displayed (you can sort the various columns). For more
information about a particular event log, double-click it. The Log Event Properties
dialog box displays more details about the individual event.
The Scope parameter is used to filter events when displaying the log.
This allows for easier viewing of events and quicker analysis of issues, as there is
no need to sort through a large number of messages to find the relevant events or
start of an issue.

Recoverpoint Design - VCE / WIPRO


Commercial-In-Confidence

27

Chapter 3: Recoverpoint Configuration

Figure 4.

RecoverPoint Logs Screen with Filter

Normal scope events - Are created when the system analyses a wide range of
system data in order to generate a single event that explains the root cause for an
entire set of detailed and advanced events. In most cases, these events are
sufficient for effective monitoring of system behaviour. By default RecoverPoint
2.4 sets the scope to Normal to filter out Detailed and Advanced events.
Detailed scope events - All events that are generated for use by users, and that
are not included among the events that have a scope of normal. The display of
detailed events includes normal events also.
Advanced scope events - In specific casese.g., for troubleshooting a problem
Customer Service may ask you to retrieve information from the advanced log
events. These events contain information that is more technical in nature. The
display of advanced events includes normal and detailed events also. With
detailed or advanced scope, the rows in the log are shaded according to the
scope of the event that is displayed on that line.
RecoverPoint, once configured with appropriate SMTP details can send automatic
systems alerts and reports; this can be configured within the System Settings
screen.
Table 29.

Alerting Information

Purpose

Value

Service Provider (to) Email address

InfraSupportVBLOCK@woolworths.com.a
u

Service Provider (from) Email address

InfraSupportVBLOCK@woolworths.com.a
u

SMTP Server

smtprelay.woolworths.com.au

SNMP

Prod
10.168.35.176 ECDC
10.136.35.176 NSO
10.168.35.177 ECDC
10.136.35.177 NSO
UAT
10.170.35.173 ECDC

Recoverpoint Design - VCE / WIPRO


Commercial-In-Confidence

28

Chapter 3: Recoverpoint Configuration


10.138.35.173 NW
Test
camtrapuat.gss.woolworths.com.au
SNMP Community String

syd123

SYSLOG Server

N/A

Trap Destination West Pennant Hills

TBA

Trap Destination Norwest

TBA

Unisphere Logon Account for Splitters

Recoverpoint

Recoverpoint Design - VCE / WIPRO


Commercial-In-Confidence

29

Chapter 3: Recoverpoint Configuration

A.

Firewall Ports
The following firewall ports are used by Recoverpoint for administration, user
access, cluster communication and cluster to cluster replication.
Table 30.

Recoverpoint Firewall Ports

Port

Source -> Destination

Protocol and description

Effect if closed

20

RPA->FTP server

Outgoing FTP communications


(TCP) (output only)

Not possible to download ISO


image or to upload logs using FTP

RPA->ESRS

Used during installation and


Not possible to register on the
upgrades to download ISO image, ESRS server
if FTP is specified as the source;
not required if the Deployment
Manager server is used as the ISO
source (then HTTPs can be used)
Can be used to upload support
logs to the specified FTP server;
not required if the support logs
are manually downloaded using
the webdownload user (then
HTTPs can be used)

Replication not affected

Used to register on the ESRS


server
21

RPA->FTP server

Outgoing FTP communications; for Not possible to download ISO


system info collection (TCP)
image or to upload logs using FTP
(output only)

RPA->ESRS

Used during installation and


Not possible to register on the
upgrades to download ISO image, ESRS server
if FTP is specified as the source;
not required if the Deployment
Manager server is used as the ISO
source (then HTTPs can be used)
Can be used to upload support
logs to the specified FTP server;
not required if the support logs
are manually downloaded using
the webdownload user (then
HTTPs can be used)

Replication not affected

Registration to the ESRS server


22

SSH client->RPA

SSH and communications


between RPAs (TCP)

No remote connection to CLI

Recoverpoint Design - VCE / WIPRO


Commercial-In-Confidence

30

Chapter 3: Recoverpoint Configuration


Port

Source -> Destination

Protocol and description

Effect if closed

Required for CLI access to RPAs. Replication not affected


The source is the Management
Server, the destination is the RPA.
RPA->RPA

23

RPA->FC switch

Communications between RPAs


(TCP)

No log collection

Used for support log collection.

Replication not affected

Telnet (TCP) (output only)

RecoverPoint SE automatic
zoning fails if telnet to Fibre
Channel switch is not available
Used during RP/SE installation to RecoverPoint installation fails;
carry out Fibre Channel switch
after installation, not needed
zoning
Used during installation when
Replication not affected
using an intelligent fabric splitter
Used for log collection when
using an intelligent fabric switch

25

RPA->SMTP server

Used for sending system mail


(SMTP) email alerts from RPA, if
configured (TCP) (output only);

No email alerts sent.

Used for Call Home events, if


configured

No system reports sent.


Replication not affected

53

RPA->DNS server

DNS (TCP, UDP)


Used for name resolution. Only
required if in the RecoverPoint
configuration, domain names are
used for external servers instead
of |P addresses.

80

Browser (running the


Management Server)>RPA

No name resolution of remote


servers, e-mail alerts, system
reports

HTTP; web server for management No GUI (can be run with HTTPS)
(TCP)

Used to run RecoverPoint GUI, but Replication not affected, but


GUI can also be run using HTTPS RecoverPoint is designed to be
when HTTP is disabled.
used with the GUI
Can be used to download RPA
logs.
123

RPA->NTP server or
another RPA

NTP (TCP, UDP)

Used for synchronizing with


Network Time Protocol server.

No synchronization with time


server. RPAs may show incorrect
time. Event time stamps may be
incorrect.
Replication not affected, but
snapshots may show incorrect
times. Write-order of snapshots
not affected

Used between RPAs in a cluster


for time synchronization.

Recoverpoint Design - VCE / WIPRO


Commercial-In-Confidence

31

Chapter 3: Recoverpoint Configuration


Port

Source -> Destination

Protocol and description

Effect if closed

161

MIB Browser->RPA

SNMP (TCP, UDP)

No SNMP notification

Used for SNMP notifications. Also Replication not affected


see port 10161.
162

389

443

RPA -> Trap receiver

RPA->LDAP server

Browser (running the


Management Server)>RPA
RPA->VNX

SNMP (TCP, UDP) (output only)

No SNMP notification

Used for SNMP notifications.

Replication not affected

LDAP (TCP) (output only)

No LDAP authentication (unless


using SSL)

Used for LDAP user authentication


and authorization. Only required
if LDAP is configured. Also see
port 636.
HTTPS for management (TCP)
No RecoverPoint GUI (unless
port 80 is available)
Used to download RPA logs,
RP/SE unable to configure
System Report alerts, EMC Secure VNX/CLARiiON; RP/SE
Remote Support, and
installation will fail
communication with third-party
hardware (such as VNX, ESXs and
VMs, VPLEX).

RPA->vCenter
RPA->VPLEX
RPA->EMC Secure
Remote Support server

514

RPA->Syslog server

Syslog (TCP, UDP) (output only)

No log collection from


VNX/CLARiiON
No vCenter Server information
(ESXs and VMs) displayed in
RecoverPoint
RecoverPoint will not be able to
display information about VPLEX
volumes and will not be able to
prevent errors in configuring
VPLEX volumes for replication; if
configured manually without
errors, replication is not affected
System logs not available

Used to send Syslog information Replication not affected


to an external server. Only
required if Syslog is enabled and
an external server is specified.
636

RPA->LDAP server

LDAP over SSL (TCP) (output only) No LDAP over SSL


authentication
Used for LDAP over SSL user
authentication and authorization.
Required only if LDAP using SSL is
configured.

989

RPA->FTPS server

FTPS (output only)

No FTPS transfers.

Used for System Reports alerts


and reporting via FTPS. Only
required if FTPS alerts or reports
are configured.

If system reports (SyR) is


configured to transfer by FTPS,
reports will not be transferred to
EMC System Reports database

Recoverpoint Design - VCE / WIPRO


Commercial-In-Confidence

32

Chapter 3: Recoverpoint Configuration


Port

Source -> Destination

Protocol and description

Effect if closed

990

RPA->FTPS server

FTPS (output only)

No FTPS transfers.

Used for System Reports alerts


and reporting via FTPS. Only
required if FTPS alerts or reports
are configured.

If system reports (SyR) is


configured to transfer by FTPS,
reports will not be transferred to
EMC System Reports database

5045

RPA->RPA

RecoverPoint (TCP, UDP)

RPA failure will cause a full


sweep of volumes attached to
Used between RPAs in the cluster the Symmetrix splitter in some
disaster scenarios. The splitter
for Symmetrix splitter
itself will continue to function
functionality.

5050

RPA->RPA

RecoverPoint (TCP, UDP)

No Symmetrix splitter

Used between RPAs in the cluster


for Symmetrix splitter
functionality.
7115

SRM server->RPA

For VMware Site Recovery


Manager communication (TCP)

No vCenter Server information


or commands available

Used by the RecoverPoint Storage Replication not affected


Replication Adapter to query and
manage the RPA. Only required if
Site Recovery Manager is used.
7225

Replication Manager ->


RPA

HTTPS protocol for


communicating with the
RecoverPoint functional API.

VPLEX->RPA

Used by the Management server


running the RecoverPoint GUI to
communicate with RPAs.

UEM GUI -> RPA

Used by third-party devices and


services to communicate with the
RPA.

No functional API

KVSS -> RPA


RP//CE-> RPA

8082

Replication Enabler for


Exchange-> RPA
Deployment Manager -> HTTPS protocol for
RPA
communication with the
RecoverPoint Installation Server

No deployment tools

Used by the Deployment Manager No installations or upgrades


during installation and upgrades.
Deployment Manager needs to
communicate with all RPAs in all
clusters. Management are ports
preferred; WAN ports are used as
fallback.
Replication not affected

Recoverpoint Design - VCE / WIPRO


Commercial-In-Confidence

33

Chapter 3: Recoverpoint Configuration


Port

Source -> Destination

10161 MIB Browser->RPA

Protocol and description

Effect if closed

SNMP over TLS (TCP);SNMP over No encrypted SNMP


DTLS (UDP)
Used for SNMP reporting. Only
required if SNMP is configured.

Recoverpoint Design - VCE / WIPRO


Commercial-In-Confidence

34

Chapter 3: Recoverpoint Configuration

B.

Abbreviations and Acronyms


The abbreviations and acronyms that are used within this document are detailed
in Table 31.
Table 31.
Term

Abbreviations and acronyms


Abbreviation or Acronym

CE

Customer Engineer

CDP

Continuous Data Protection

CLR

Continuous Local and Remote Replication

CPU

Central Processing Unit

CRR

Continuous Remote Replication

CSC

Customer Support Centre

DR

Disaster Recovery

ECDC

Woolworths Easter Creek Data center

FAST

Fully Automated Storage Tiering

GB

Gigabyte

HBA

Host Bus Adapter

IDS

Implementation Delivery Specialist

IO

Input / Output

LAN

Local Area Network

MB

Megabyte

Norwest

Woolworths North West Data center

PM

Project Manager

RPA

Recoverpoint Appliance

RPO

Recover Point Objective

SA

Solutions Architect

SAN

Storage Area Network

SAN

Storage Area Network

SCSI

Small Computer Serial Interface

SE

Systems Engineer

SOS

Storage Operations Specialist

Recoverpoint Design - VCE / WIPRO


Commercial-In-Confidence

35

Chapter 3: Recoverpoint Configuration


Term

Abbreviation or Acronym

SP

Service Processor

SSH

Secure Shell. Used for secure communication

TBA

To Be Advised, by the customer

VP

Virtual Provisioning

WAN

Wide Area Network

Recoverpoint Design - VCE / WIPRO


Commercial-In-Confidence

36

Chapter 3: Recoverpoint Configuration

C.
Device tagging

Operational Considerations
In Recoverpoint, volumes cannot be added to a replication set unless they are
tagged as being used by Recoverpoint.
All gatekeepers, journal volumes, repository as well as the production and
replicate volumes must be tagged.
To tag the devices in a storage group as being used by Recoverpoint

Select the storage group from the object tree in Unisphere

Right click on the desired storage group. From the pop up menu slect
Replication > Recoverpoint > Enable Recoverpoint

All devices in the storage group will be tagged as being used by Recoverpoint
To use CLI syntax
Symconfigure sid <symmetrix ID> -cmd set dev <device list or device range>
Attribute=RCVRPNT_TAG; commit

Recoverpoint Design - VCE / WIPRO


Commercial-In-Confidence

37

S-ar putea să vă placă și