Documente Academic
Documente Profesional
Documente Cultură
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
Name
Title
Contact Number
Joshua Reader
Solutions
Architect
joshua.reader@emc.com
Rob Anderson
Project
Manager
robert.anderson2@emc.com
Table 2 reflects the creation date, along with any alterations since inception.
Table 2.
Version
Date
Author
Description
0.1
23/10/2013
Ian Stewart
Setup document
0.2
30/10/2013
Joshua Reader
0.3
25/11/2013
Joshua Reader
0.4
29/11/2013
Joshua Reader
Updated template
1.0
29/11/2013
Rob Anderson
1.1
02/12/2013
Joshua Reader
Amendments following
initial review from Paul
Comerford
2.0
03/12/2013
Rob Anderson
2.1
04/12/2013
Joshua Reader
Amendments applied
following 2nd review by
Paul Comerford
Table of contents
Version
Date
Author
Description
3.0
05/12/2013
Rob Anderson
3.1
05/12/2013
Joshua Reader
Updated information
based on Design review.
4.0
18/12/2013
Paul Comerford
Table of contents
Document
Authorisation
Signature: _______________________
Date: ______________
Robert Anderson
Project Manager
VCE
Signature: _______________________
Date: ______________
Paul Comerford
Project Manager
WIPRO Ltd
Signature: _______________________
Date: ______________
Lal Sebastian
Project Manager
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
RecoverPoint Configurations.................................................................................................... 9
CDP Configurations ........................................................................................................................ 9
CRR Configurations ...................................................................................................................... 10
CLR configurations ....................................................................................................................... 10
Chapter 1: Introduction
Synchronous Replication Mode..................................................................................................... 16
Dynamic Sync Mode..................................................................................................................... 17
A.
B.
C.
Chapter 1: Introduction
List of Tables
Table 1.
Table 2.
Table 3.
Table 4.
Table 5.
Table 6.
Table 7.
Table 8.
Table 9.
Table 10.
Table 11.
Table 12.
Table 13.
Table 14.
Table 15.
Table 16.
Table 17.
Table 18.
Table 19.
Table 20.
Table 21.
Table 22.
Table 23.
Table 24.
Table 25.
Table 26.
Table 27.
Table 28.
Table 29.
Alerting Information....................................................................................... 28
Table 30.
Table 31.
Chapter 1: Introduction
List of Figures
Figure 1.
Figure 1.
Figure 2.
Figure 3.
Figure 4.
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 staff responsible for the ongoing maintenance of the EMC
infrastructure.
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.
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
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
SLOT2
PS1
AMP
Switch B
PS1
L1
PS2
PS2
PS1
SLOT2
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
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
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
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
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
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
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
STATUS
DS-13SLT-FAB2
FABRIC MODULE 2
STATUS
2
LINK
DS-13SLT-FAB2
FABRIC MODULE 2
MGMT
STATUS
LINK
DS-X9248-48K9
STATUS
SYSTEM
DS-X9248-48K9
1
STATUS
PWR
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
CISCO
PWR
RPA 2
CISCO
CONSOLE
STATUS
SERIES
MDS-9513
SAN B
MDS 9500
SERIES
MDS-9513
SAN A
VMAX
40K
External Ethernet
Figure 1.
VMAX
40K
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
RecoverPoint/EX
RecoverPoint/EX provides all of the data protection of RecoverPoint/CL, with the
following limitations:
VMAX series
VNX series
Block LUNs from Fibre Channel Celerra NS20, NS40, NS80, NS120, NS-240, and NS-960
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:
Design Decision
Recoverpoint/EX has been chosen to handle replication between the Norwest and
Eastern Creek Data Centers
RecoverPoint
Configurations
within the same site or to a local bunker site some distance away, CDP
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:
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.
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.
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.
10
RecoverPoint
Appliance (RPA)
Recoverpoint Software
Software
Version
6 x 1GE ports (RJ-45) WAN, LAN & Remote management + 3 ports are
unused
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.
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.
11
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.
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
Splitter
Details
Array
Based
12
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
Replication Sets
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.
13
Volumes
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.
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.
14
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
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.
15
Bookmarks
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
16
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.
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.
17
Recoverpoint Configuration
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.
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.
Fabric
RPA
RPA Port
Switch
Switch Port
RPA 1
nw1-mds-edg-fab-a-06
fc1/11
18
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.
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.
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
19
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.
Fabric
Zone Name
Zone Member
WWN
RPA-RPA_woolworths_com_au
RPA-RPA_woolworths_com_au
TBA
TBA
TBA
TBA
Table 11.
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
255.255.255.0
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
-
20
Time Zone
Local DNS Domain Name
Table 12.
woolworths.com.au
Norwest Recoverpoint Configuration
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
255.255.255.0
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
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
21
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
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
22
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
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.
PG Name
Member Ports
RPA_PG
RPA_Replica_PG
Table 17.
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
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.
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
23
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.
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.
PG Name
Member Ports
PG-RPA
PG-RPA_Replica
7g0, 8g0, 9g0, 10g0, 5e0, 6e0, 5f0, 6f0, 5g0, 6g0
Table 21.
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
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.
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
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.
24
Journals
Figure 3.
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
Consistency Group
Journal Type
VMAX Device
CG-NOR-Test1
Production
TBA
CG-NOR-Test2
Production
TBA
CG-NOR-Test3
Production
TBA
25
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
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
Group Set
Remote Copy
Production CG
Remote CG
GS-NOR-Test
CG-NOR-Test2
CG-NOR-Test2-remote
CG-NOR-Test3
CG-NOR-Test3-remote
26
RecoverPoint User
Accounts
Alerting
Information
Table 28.
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
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.
27
Figure 4.
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
InfraSupportVBLOCK@woolworths.com.a
u
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
28
syd123
SYSLOG Server
N/A
TBA
TBA
Recoverpoint
29
A.
Firewall Ports
The following firewall ports are used by Recoverpoint for administration, user
access, cluster communication and cluster to cluster replication.
Table 30.
Port
Effect if closed
20
RPA->FTP server
RPA->ESRS
RPA->FTP server
RPA->ESRS
SSH client->RPA
30
Effect if closed
23
RPA->FC switch
No log collection
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
53
RPA->DNS server
80
HTTP; web server for management No GUI (can be run with HTTPS)
(TCP)
RPA->NTP server or
another RPA
31
Effect if closed
161
MIB Browser->RPA
No SNMP notification
389
443
RPA->LDAP server
No SNMP notification
RPA->vCenter
RPA->VPLEX
RPA->EMC Secure
Remote Support server
514
RPA->Syslog server
RPA->LDAP server
989
RPA->FTPS server
No FTPS transfers.
32
Effect if closed
990
RPA->FTPS server
No FTPS transfers.
5045
RPA->RPA
5050
RPA->RPA
No Symmetrix splitter
SRM server->RPA
VPLEX->RPA
No functional API
8082
No deployment tools
33
Effect if closed
34
B.
CE
Customer Engineer
CDP
CLR
CPU
CRR
CSC
DR
Disaster Recovery
ECDC
FAST
GB
Gigabyte
HBA
IDS
IO
Input / Output
LAN
MB
Megabyte
Norwest
PM
Project Manager
RPA
Recoverpoint Appliance
RPO
SA
Solutions Architect
SAN
SAN
SCSI
SE
Systems Engineer
SOS
35
Abbreviation or Acronym
SP
Service Processor
SSH
TBA
VP
Virtual Provisioning
WAN
36
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
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
37