RecoverPoint Installation and Deployment Guide Rev A11

EMC®
RecoverPoint
Installation and Deployment Guide

P/N 300-010-476
REV 11
Copyright © 2006 - 2013 EMC Corporation. All rights reserved. Published in the USA.
Published August, 2013
EMC believes the information in this publication is accurate as of its publication date. The information is subject to change without
notice.
The information in this publication is provided as is. EMC Corporation makes no representations or warranties of any kind with respect
to the information in this publication, and specifically disclaims implied warranties of merchantability or fitness for a particular
purpose. Use, copying, and distribution of any EMC software described in this publication requires an applicable software license.
EMC2, EMC, and the EMC logo are registered trademarks or trademarks of EMC Corporation in the United States and other countries.
All other trademarks used herein are the property of their respective owners.
For the most up-to-date regulatory document for your product line, go to EMC Online Support (https://support.emc.com).
2 EMC RecoverPoint Installation and Deployment Guide

CONTENTS
Chapter 1 Preparing for Deployment

RecoverPoint connectivity ........................................................................... 22
NTP server............................................................................................. 24
Zoning ........................................................................................................ 25
Zoning Gen5 and Gen4 RPAs (QLE2564 HBAs)....................................... 25
Zoning Gen3 RPAs (QLE24xx HBAs) ....................................................... 27
Zoning Gen1 RPAs (QLA23xx HBAs) ....................................................... 27
LUN masking......................................................................................... 28
Multiple WWNs ..................................................................................... 28
Connectivity for switchless configurations............................................. 28
Unpacking the RPAs .................................................................................... 29
3.2 and later RPA .................................................................................. 29
Chapter 2 About Deploying RecoverPoint

Deploying RecoverPoint............................................................................... 32
Deployment Manager .................................................................................. 33
Accessing Deployment Manager............................................................ 33
Launching Deployment Manager ........................................................... 33
Wizards in Deployment Manager 2.0.SP1 .............................................. 33
System requirements ............................................................................ 34
Networking requirements ...................................................................... 34
Notes about Deployment Manager ........................................................ 35
Chapter 3 RecoverPoint/SE Installation

RecoverPoint/SE Installer Wizard................................................................. 38
About the RecoverPoint/SE Installer Wizard .......................................... 38
System requirements ............................................................................ 38
Launch RecoverPoint/SE Installer Wizard .............................................. 39
RecoverPoint 4.0 or later ............................................................................. 40
Access the Wizard ................................................................................. 40
Prerequisites......................................................................................... 41
Configuration file .................................................................................. 42
Environment settings ............................................................................ 43
RPA discovery ....................................................................................... 44
IP and connectivity settings................................................................... 45
Login credentials................................................................................... 46
Connectivity results............................................................................... 47
RPA iSCSI configuration......................................................................... 48
EMC Online Support credentials ............................................................ 49
Update RecoverPoint release................................................................. 50
ISO settings .......................................................................................... 51
Installation change management procedures ........................................ 53
Apply configuration results.................................................................... 55
Upgrade and Apply configuration results............................................... 55
Storage configuration............................................................................ 56
Apply configuration ............................................................................... 62
Summary .............................................................................................. 63
Post-installation requirements .............................................................. 64
EMC RecoverPoint Installation and Deployment Guide 3

Contents
RecoverPoint 3.5 or earlier .......................................................................... 65

Prerequisites......................................................................................... 66
Sites ..................................................................................................... 69
Apply configuration ............................................................................... 71
Apply .................................................................................................... 72
Storage Configuration - Site1Name - VNX/CLARiiON login credentials.... 76
Storage Configuration - Site1Name - VNX/CLARiiON login status ........... 76
Storage Configuration - Site1Name - Zoning .......................................... 77
Storage Configuration - Site1Name - SAN Diagnostics ........................... 80
Storage Configuration - Site1Name - Repository volume ........................ 80
Storage configuration - Site2Name - VNX/CLARiiON login credentials .... 81
Storage configuration - Site2Name - VNX/CLARiiON login status............ 81
Storage configuration - Site2Name - Zoning........................................... 81
Storage configuration - Site2Name - SAN Diagnostics............................ 81
Storage Configuration - Apply configuration .......................................... 81
Summary .............................................................................................. 82
Post-installation requirements .............................................................. 84
Chapter 4 RecoverPoint Installation

RecoverPoint Installer Wizard ...................................................................... 86
About the RecoverPoint Installer Wizard ................................................ 86
Launch RecoverPoint Installer Wizard .................................................... 86
RecoverPoint 4.0 or later ............................................................................. 88
Prerequisites......................................................................................... 89
RPA discovery ....................................................................................... 93
IP and connectivity settings................................................................... 94
Login credentials................................................................................... 95
Connectivity results............................................................................... 96
RPA iSCSI configuration......................................................................... 96
Update RecoverPoint release................................................................. 98
ISO settings .......................................................................................... 99
Apply configuration results.................................................................. 102
Upgrade and Apply configuration results............................................. 102
Storage configuration.......................................................................... 103
Summary ............................................................................................ 108
Post-installation requirements ............................................................ 108
RecoverPoint 3.5 or earlier ........................................................................ 109
Access the Wizard ............................................................................... 109
1Prerequisites..................................................................................... 110
Configuration file ................................................................................ 110
Environment settings .......................................................................... 111
Sites ................................................................................................... 113
Apply configuration ............................................................................. 116
Apply .................................................................................................. 118
Storage configuration - Site1Name - Zoning and LUN masking............. 121
Storage configuration - Site1Name - SAN diagnostics .......................... 121
Storage configuration - Site1Name - Repository volume....................... 122
Storage configuration - Site1Name - Site summary .............................. 123

Contents
Storage configuration - Site2Name - Zoning and LUN masking............. 124

Storage configuration - Site2Name - SAN diagnostics .......................... 124
Storage configuration - Site2Name - Repository volume....................... 124
Storage configuration - Site2Name - Site summary .............................. 124
Summary ............................................................................................ 124
Post-installation requirements ............................................................ 126
Chapter 5 Cluster Connection

Connect Cluster Wizard ............................................................................. 128
About the Connect Cluster Wizard ....................................................... 128
Networking requirements .................................................................... 128
Launch Connect Cluster Wizard ........................................................... 128
Select connection step........................................................................ 131
Prepare for new cluster for connection................................................. 132
Preparation prerequisites.................................................................... 132
New cluster login credentials .............................................................. 133
Connect now or later ........................................................................... 134
Connection prerequisites .................................................................... 135
Existing cluster login credentials ......................................................... 136
Cluster connection settings ................................................................. 136
Additional cluster connections ............................................................ 137
Summary ............................................................................................ 138
Post-connection requirements............................................................. 138
Chapter 6 RPA Replacement

RPA Replacement Wizard........................................................................... 142
About the RecoverPoint RPA Replacement Wizard ............................... 142
Launch the RPA Replacement Wizard................................................... 142
RecoverPoint 4.0 or later ........................................................................... 143
Prerequisites for replacement ............................................................. 144
Login credentials................................................................................. 145
Cluster and RPA selection.................................................................... 146
RPA replacement preparations ............................................................ 146
RPA replacement prerequisites............................................................ 147
New RPA configuration ........................................................................ 149
SAN diagnostics.................................................................................. 149
System modifications.......................................................................... 150
Apply changes .................................................................................... 151
Summary ............................................................................................ 151
Prerequisites for replacement ............................................................. 153
Site and RPA selection ........................................................................ 154
RPA replacement preparations ............................................................ 155
RPA replacement prerequisites............................................................ 155
New RPA configuration ........................................................................ 157
Storage configuration - SAN diagnostics.............................................. 158

Contents
System modifications.......................................................................... 158

Apply changes .................................................................................... 159
Summary ............................................................................................ 160
Chapter 7 RPA Addition

Add New RPAs Wizard ............................................................................... 162
About the RecoverPoint Add New RPAs Wizard .................................... 162
Launch Add New RPAs Wizard ............................................................. 162
Prerequisites....................................................................................... 165
Add New RPAs..................................................................................... 167
IP and connectivity settings................................................................. 168
RPA iSCSI configuration....................................................................... 169
Apply changes .................................................................................... 176
Summary ............................................................................................ 177
Prerequisites....................................................................................... 179
Add New RPAs..................................................................................... 181
RPA IP settings .................................................................................... 181
Apply changes .................................................................................... 188
Summary ............................................................................................ 189
Chapter 8 Upgrade RPA Software

About upgrading RecoverPoint .................................................................. 192
Upgrade matrix to the latest RecoverPoint releases ................................... 193
Upgrading to the latest 4.0 release............................................................ 195
Upgrading from 4.0 and later............................................................... 195
Upgrading from 3.2 SP2 and later........................................................ 196
Upgrading from 3.2 and 3.2 SP1.......................................................... 196

Contents

Upgrade Cluster Wizard............................................................................. 200
Launch Deployment Manager .............................................................. 201
Launch Upgrade Cluster Wizard........................................................... 202
Select upgrade step ............................................................................ 204
Prepare for upgrade ............................................................................ 204
Login credentials summary ................................................................. 206
EMC Online Support site credentials ................................................... 207
Update RecoverPoint release............................................................... 207
System diagnostics ............................................................................. 215
Save system files ................................................................................ 216
Apply upgrade configuration ............................................................... 217
Cluster diagnostics ............................................................................. 220
Apply upgrade summary...................................................................... 221
Post-upgrade activities........................................................................ 222
Upgrade RPAs Wizard ................................................................................ 224
Launch Deployment Manager .............................................................. 225
Launch Upgrade RPAs Wizard.............................................................. 226
Prepare for upgrade ............................................................................ 228
ISO file distribution ............................................................................. 231
System diagnostics ............................................................................. 237
Save system files ................................................................................ 237
Environment diagnostics..................................................................... 242
Apply upgrade summary...................................................................... 243
Post-upgrade requirements ................................................................. 244
Chapter 9 Environment Conversion

Converter Wizard....................................................................................... 250
About the Converter Wizard................................................................. 250
Launch Converter Wizard..................................................................... 250
Choose Converter Type........................................................................ 253
Prerequisites (when converting to RecoverPoint/SE)............................ 254
Apply changes .................................................................................... 261
Summary ............................................................................................ 262
Prerequisites (when converting to RecoverPoint) ................................. 263

Contents

Apply changes .................................................................................... 267
Summary ............................................................................................ 268
Choose Converter Type........................................................................ 271
Prerequisites (when converting to RecoverPoint/SE)............................ 272
Apply changes .................................................................................... 278
Summary ............................................................................................ 279
Prerequisites (when converting to RecoverPoint) ................................. 280
Apply changes .................................................................................... 283
Summary ............................................................................................ 284
Chapter 10 Modification
Cluster or System Modification Wizard ...................................................... 286
About the Modification Wizard ............................................................ 286
Launch Modification Wizard ................................................................ 286
Prerequisites....................................................................................... 289
Cluster IPs........................................................................................... 293
RPA iSCSI configuration....................................................................... 294
Storage iSCSI ports ............................................................................. 296
Summary ............................................................................................ 297
Prerequisites....................................................................................... 299
Sites ................................................................................................... 302
Apply system modifications ................................................................ 304
Summary ............................................................................................ 304
Chapter 11 Other Operations

Power down and power up RPA ................................................................. 306
When this procedure should be used .................................................. 306
Powering down RPAs ........................................................................... 306
Powering up RPAs ............................................................................... 306
Changing system parameters .................................................................... 307
Verifying time synchronization .................................................................. 309
Verifying management access ................................................................... 311
Using the RecoverPoint GUI ................................................................. 311
Using the RecoverPoint CLI .................................................................. 311
Removing Kashya Reservation Manager support........................................ 312

Contents
Chapter 12 Splitters
Array-based splitters ................................................................................. 314
VNX/CLARiiON..................................................................................... 314
Symmetrix........................................................................................... 314
VPLEX.................................................................................................. 314
Host-based splitters (KDrivers).................................................................. 315
Installing KDrivers ............................................................................... 315
Uninstalling KDrivers........................................................................... 318
Upgrading KDrivers ............................................................................. 321
Changing KDriver parameters .............................................................. 322
Fabric-based splitters................................................................................ 323
SANTap ............................................................................................... 323
Brocade .............................................................................................. 323

Contents

FIGURES
Title Page
1 Dual fabric topology .................................................................................................... 22

2 Direct attach topology ................................................................................................. 23
3 RecoverPoint Gen4 RPA (Dell PowerEdge R610) ........................................................... 23
4 RecoverPoint Gen5 RPA (Intel R1000) .......................................................................... 24
5 Check for newer release screen ................................................................................... 39
6 Deployment Manager login screen .............................................................................. 40
7 Deployment Manager wizard selection screen ............................................................. 41
8 Prerequisites screen.................................................................................................... 42
9 Configuration file screen ............................................................................................. 43
10 Environment settings screen ....................................................................................... 44
11 RPA discovery screen .................................................................................................. 45
12 IP and connectivity settings screen.............................................................................. 46
13 Login credentials screen ............................................................................................. 47
14 Connectivity results screen.......................................................................................... 47
15 Cluster iSCSI settings screen ....................................................................................... 48
16 RPA iSCSI Ports screen ................................................................................................ 49
17 EMC Online Support credentials screen....................................................................... 50
18 Update RecoverPoint release screen............................................................................ 51
19 ISO image download details screen............................................................................. 52
20 Installation change management screen ..................................................................... 54
21 Installation change management message screen ...................................................... 54
22 Apply configuration results screen - update................................................................. 55
23 Upgrade and Apply configuration results screen.......................................................... 56
24 VNX/CLARiiON login credentials screen ....................................................................... 57
25 NX/CLARiiON login status screen................................................................................. 57
26 Storage iSCSI Ports screen - update............................................................................. 58
27 Apply iSCSI configuration results screen ..................................................................... 59
28 SAN diagnostics screen............................................................................................... 61
29 Repository volume screen ........................................................................................... 62
30 Apply configuration screen.......................................................................................... 63
31 Summary screen - update............................................................................................ 64
32 Deployment Manager login screen .............................................................................. 65
34 Verify requirements screen.......................................................................................... 67
35 Configuration file screen ............................................................................................. 68
36 Environment screen .................................................................................................... 69
37 Sites - Site1Name RPA Discovery................................................................................. 70
38 Sites - Site1Name IP settings....................................................................................... 71
39 Apply configuration screen.......................................................................................... 72
40 Connectivity results screen.......................................................................................... 73
41 Apply configuration results screen .............................................................................. 73
42 ISO file information screen .......................................................................................... 75
43 Apply configuration results screen .............................................................................. 75
44 Storage configuration - Site1Name - VNX/CLARiiON login credentials screen ............... 76
45 Storage configuration - Site1Name - VNX/CLARiiON login status screen....................... 77
46 Storage configuration - Site1Name - Zoning................................................................. 79
47 Storage configuration - Site1Name - SAN diagnostics .................................................. 80
48 Storage configuration - Site1Name - Repository volume............................................... 80
49 Storage configuration - Apply configuration................................................................. 82
50 Summary screen ......................................................................................................... 83

51 Check for newer release screen.................................................................................... 87
52 Select RecoverPoint release screen.............................................................................. 87
53 Deployment Manager login screen ............................................................................... 88
55 Prerequisites screen .................................................................................................... 90
56 Configuration file screen.............................................................................................. 91
57 Environment settings screen........................................................................................ 93
58 RPA discovery screen ................................................................................................... 94
59 IP and connectivity settings screen .............................................................................. 95
60 Login credentials screen .............................................................................................. 95
61 Connectivity results screen .......................................................................................... 96
62 Cluster iSCSI Settings screen ....................................................................................... 97
63 RPA iSCSI Ports screen................................................................................................. 98
64 Update RecoverPoint release screen ............................................................................ 99
65 ISO image download details screen ........................................................................... 100
66 ISO file information screen......................................................................................... 101
67 Apply configuration results screen ............................................................................. 102
68 Upgrade and Apply configuration results screen ........................................................ 102
69 Storage iSCSI Ports screen......................................................................................... 103
70 Storage iSCSI settings dialog box............................................................................... 104
71 Apply iSCSI configuration results screen .................................................................... 104
72 RPA iSCSI Qualified Names screen ............................................................................. 105
73 Zoning and LUN masking screen ................................................................................ 105
74 SAN diagnostics screen ............................................................................................. 106
75 Repository volume screen.......................................................................................... 107
76 Cluster summary screen............................................................................................. 107
77 Summary screen........................................................................................................ 108
78 Deployment Manager login screen ............................................................................. 109
79 Deployment Manager wizard selection screen ........................................................... 109
80 Prerequisites screen .................................................................................................. 110
81 Configuration file screen............................................................................................ 111
82 Environment settings screen...................................................................................... 112
83 Sites - Site1Name RPA Discovery ............................................................................... 113
84 Sites - Site1Name IP settings ..................................................................................... 114
85 Sites - Site1Name advanced settings ......................................................................... 116
86 Apply configuration screen ........................................................................................ 117
87 Connectivity results screen ........................................................................................ 118
91 Storage configuration - Site1Name - Zoning and LUN masking screen ........................ 121
92 Storage configuration - Site1Name - SAN diagnostics screen ..................................... 122
93 Storage configuration - Site1Name - Repository volume screen .................................. 123
94 Storage configuration - Site1Name - Site summary screen ......................................... 123
95 Summary screen........................................................................................................ 125
96 Deployment Manager screen ..................................................................................... 129
101 Select connection step screen ................................................................................... 131
102 Preparation prerequisites screen ............................................................................... 132
103 Login credentials screen ............................................................................................ 133
104 Connect cluster selection screen................................................................................ 134
105 Connection prerequisites screen................................................................................ 135
12
EMC RecoverPoint Installation and Deployment Guide
106 Existing cluster login credentials screen .................................................................... 136
107 Cluster connection settings screen ............................................................................ 137
108 Additional cluster connections screen....................................................................... 138
109 Summary screen ....................................................................................................... 138
110 Deployment Manager login screen ............................................................................ 143
112 Configuration file screen ........................................................................................... 145
113 Login credentials screen ........................................................................................... 145
114 RPA selection screen ................................................................................................. 146
115 RPA replacement preparations screen ....................................................................... 146
116 RPA replacement prerequisites screen ...................................................................... 147
117 Storage configuration screen..................................................................................... 148
118 Warning message...................................................................................................... 149
119 New RPA configuration screen ................................................................................... 149
120 SAN diagnostics screen............................................................................................. 150
121 System modifications screen..................................................................................... 150
122 Apply changes screen ............................................................................................... 151
123 Summary screen ....................................................................................................... 151
128 Site and RPA selection screen ................................................................................... 154
129 RPA replacement preparations screen ....................................................................... 155
130 RPA replacement prerequisites screen ...................................................................... 156
131 Storage configuration screen..................................................................................... 157
132 Warning message...................................................................................................... 157
133 New RPA configuration screen ................................................................................... 157
134 Storage configuration - SAN diagnostics screen......................................................... 158
135 System modifications screen..................................................................................... 159
137 Summary screen ....................................................................................................... 160
140 Prerequisites screen.................................................................................................. 165
143 Add new RPAs screen ................................................................................................ 167
144 IP and connectivity settings screen............................................................................ 168
145 Cluster iSCSI Settings screen..................................................................................... 169
146 RPA iSCSI Ports screen .............................................................................................. 170
147 Apply configuration results screen ............................................................................ 170
148 Storage iSCSI Ports screen ........................................................................................ 171
149 VNX/CLARiiON login credentials ................................................................................ 172
150 Zoning (RecoverPoint/SE).......................................................................................... 174
151 Zoning (RecoverPoint) ............................................................................................... 175
152 SAN diagnostics ........................................................................................................ 175
153 Configure new RPAs .................................................................................................. 176
155 Summary screen ....................................................................................................... 177
160 Installation configuration screen ............................................................................... 180
13
161 Add new RPAs screen ................................................................................................ 181
162 RPA IP settings - Site1Name IP settings...................................................................... 182
164 Storage configuration - Site1Name - VNX/CLARiiON login credentials......................... 183
165 Storage configuration - Site1Name - Zoning (RecoverPoint/SE) .................................. 186
166 Storage configuration - Site1Name - Zoning (RecoverPoint)........................................ 186
167 Storage configuration - Site1Name - SAN diagnostics ................................................ 187
168 Storage configuration - Site1Name - Configure new RPAs ........................................... 187
169 Apply changes screen................................................................................................ 188
170 Summary screen........................................................................................................ 189
175 Deployment Manager Upgrade Cluster Wizard selection screen ................................. 204
176 Prepare for upgrade screen ........................................................................................ 205
178 Login credentials summary screen ............................................................................. 206
179 EMC Online Support credentials screen ..................................................................... 207
180 Update RecoverPoint release screen .......................................................................... 208
181 ISO image download details screen ........................................................................... 209
183 FTP credentials summary screen ................................................................................ 212
184 Upgrade Change Management procedures screen ..................................................... 213
185 Upgrade Change Management message screen ......................................................... 213
186 ISO file distribution summary screen ......................................................................... 214
187 System diagnostics screen ........................................................................................ 215
188 Save system files screen............................................................................................ 217
189 Apply/Resume upgrade configuration screen............................................................. 218
190 Apply upgrade configuration screen........................................................................... 219
191 Cluster diagnostics screen ......................................................................................... 220
192 Apply/Resume upgrade summary screen ................................................................... 221
193 Collect system information screen ............................................................................. 222
198 Prepare for upgrade screen ........................................................................................ 229
200 Login credentials summary screen ............................................................................. 230
201 EMC Online Support credentials screen ..................................................................... 231
203 FTP credentials summary screen ................................................................................ 234
204 Upgrade change management procedures screen...................................................... 235
205 Upgrade change management message dialog box ................................................... 235
206 ISO file distribution summary screen ......................................................................... 236
207 System diagnostics screen ........................................................................................ 237
208 Save system files screen............................................................................................ 238
211 Environment diagnostics screen ................................................................................ 242
212 Apply upgrade summary screen ................................................................................. 243
213 Collect system information screen ............................................................................. 244
14
216 Choose converter type screen.................................................................................... 253
219 Login credentials summary screen ............................................................................ 256
220 VNX/CLARiiON login credentials screen ..................................................................... 257
221 VNX/CLARiiON login status screen............................................................................. 258
222 SAN diagnostics ........................................................................................................ 259
223 Storage groups diagnostics ....................................................................................... 260
225 Summary screen ....................................................................................................... 262
228 Login credentials summary screen ............................................................................ 265
229 Storage configuration - SAN diagnostics screen......................................................... 266
231 Summary screen ....................................................................................................... 268
234 Choose converter type screen.................................................................................... 271
237 Storage configuration - VNX/CLARiiON login credentials ............................................ 274
238 Storage configuration - VNX/CLARiiON login status.................................................... 275
239 Storage configuration - SAN diagnostics.................................................................... 276
240 Storage configuration - Storage groups diagnostics................................................... 277
242 Summary screen ....................................................................................................... 279
245 Storage configuration - SAN diagnostics.................................................................... 282
247 Summary screen ....................................................................................................... 284
253 Environment settings screen ..................................................................................... 292
254 Cluster IPs screen...................................................................................................... 293
255 Cluster iSCSI settings screen ..................................................................................... 294
256 RPA iSCSI ports screen .............................................................................................. 295
257 Storage iSCSI ports screen ........................................................................................ 296
258 Summary screen ....................................................................................................... 297
264 Environment settings screen ..................................................................................... 302
265 Sites screen .............................................................................................................. 303
266 Apply system modifications screen ........................................................................... 304
267 Summary screen ....................................................................................................... 304
15
16
Preface
PREFACE
As part of an effort to improve its product lines, EMC periodically releases revisions of its
software and hardware. Therefore, some functions described in this document might not
be supported by all versions of the software or hardware currently in use. The product
release notes provide the most up-to-date information on product features.
Contact your EMC technical support professional if a product does not function properly or
does not function as described in this document.
Note: This document was accurate at publication time. Go to EMC Online Support
(https://support.emc.com) to ensure that you are using the latest revision of this
document.
This document is part of the EMC RecoverPoint documentation set, and is intended for use
by those who are responsible for deploying an EMC RecoverPoint system.
17
Preface
Purpose
This document describes how to install, upgrade and maintain the EMC RecoverPoint
system.
Audience
This document is intended for the host system administrator, system programmer, or
operator who is involved in deploying and managing the RecoverPoint system.
Related documentation
The following EMC publications provide additional information:
◆ EMC RecoverPoint Release Notes
◆ EMC RecoverPoint Deployment Manager Release Notes
◆ EMC RecoverPoint Administrator’s Guide
◆ EMC RecoverPoint CLI Reference Guide
◆ EMC RecoverPoint Security Configuration Guide
Conventions used in this document

EMC uses the following conventions for special notices:

DANGER indicates a hazardous situation which, if not avoided, will result in death or
serious injury.

WARNING indicates a hazardous situation which, if not avoided, could result in death or
serious injury.

CAUTION, used with the safety alert symbol, indicates a hazardous situation which, if not
avoided, could result in minor or moderate injury.

NOTICE is used to address practices not related to personal injury.
Note: A note presents information that is important, but not hazard-related.
IMPORTANT
An important notice contains information essential to software or hardware operation.

Preface
Typographical conventions
EMC uses the following type style conventions in this document:
Bold Use for names of interface elements, such as names of windows, dialog
boxes, buttons, fields, tab names, key names, and menu paths (what the
user specifically selects or clicks)
Italic Use for full titles of publications referenced in text
Monospace Use for:
• System output, such as an error message or script
• System code
• Pathnames, filenames, prompts, and syntax
• Commands and options
Monospace italic Use for variables.
Monospace bold Use for user input.
[] Square brackets enclose optional values
| Vertical bar indicates alternate selections — the bar means “or”
{} Braces enclose content that the user must specify, such as x or y or z
... Ellipses indicate nonessential information omitted from the example
Where to get help

EMC support, product, and licensing information can be obtained as follows:
Product information — For documentation, release notes, software updates, or
information about EMC products, go to EMC Online Support at:
https://support.emc.com
Technical support — Go to EMC Online Support and click Service Center. You will see
several options for contacting EMC Technical Support. Note that to open a service request,
you must have a valid support agreement. Contact your EMC sales representative for
details about obtaining a valid support agreement or with questions about your account.
Your comments
Your suggestions will help us continue to improve the accuracy, organization, and overall
quality of the user publications. Send your opinions of this document to:
techpubcomments@emc.com
19
Preface

CHAPTER 1
Preparing for Deployment
RecoverPoint is an intelligent data protection and recovery solution that runs on

out-of-band appliances attached to SAN and IP networks. RecoverPoint uses the
enterprise’s existing network and storage systems. To prepare for deployment, you should
be familiar with how the RecoverPoint system integrates with your existing systems.
To facilitate a successful deployment of RecoverPoint and RecoverPoint/SE, it is important
to assemble selected information about the installed networks and storage systems. It is
also necessary to ensure that the LUNs needed by RecoverPoint are available on the
storage. EMC Global Services will assist you with these pre-deployment activities:
◆ RecoverPoint connectivity ....................................................................................... 22
◆ Zoning .................................................................................................................... 25
◆ Unpacking the RPAs ................................................................................................ 29
Preparing for Deployment 21

RecoverPoint connectivity
The following sections describe the connectivity of a RecoverPoint deployment. Figure 3
on page 23 shows a diagram of the back of a Gen4 RPA (Dell PowerEdge R610). Figure 4 on
page 24 shows a diagram of the back of a Gen5 RPA (Intel R1000).
Fibre Channel (RecoverPoint)

The RPAs connect to the hosts and storage subsystems using a Fibre Channel SAN. Before
deploying RecoverPoint, these subsystems should be in place.
In preparation for RecoverPoint deployment, ensure that there is one RPA Fibre Channel
port available per RPA per fabric. This ensures high availability by providing redundancy
between all components at the site.
Note: A dual fabric configuration is required at all sites for RPA, host, and storage
connectivity.
Fibre Channel (RecoverPoint/SE)

RecoverPoint/SE supports the following network topologies, all of which ensure high
availability:
◆ “Dual fabric” on page 22
◆ “Direct attach” on page 23
Dual fabric
A dual-fabric topology is recommended, and must include the following connections:
◆ A port on each VNX/CLARiiON storage processor to each fabric.
Note: In most installations, the storage-to-switch connections already exist.
◆ Each RPA to each fabric.

An example of this topology is shown in the following diagram.
Figure 1 Dual fabric topology

Direct attach
A direct attach, “switchless” topology, intended for iSCSI host-connected environments,
must include the following connections:
◆ Each RPA to one port on each VNX/CLARiiON storage processor.
◆ Two Fibre Channel ports connecting the two RPAs.
An example of this topology is shown in the following diagram.
Figure 2 Direct attach topology
Ethernet/IP for WAN interface

RPAs are linked to the WAN interface using an Ethernet/IP connection (eth0). The WAN
interface site IP addresses can be entered either in IPv4 or IPv6 format, but the versions
must be the same for both sites.
Ethernet/IP for management (LAN) interface

RPAs are linked to the management (LAN) interface using an Ethernet/IP connection
(eth1). The management IP addresses for all RPAs at a site, and the virtual IP address used
for site management, must all reside on the same subnet. This may be a different subnet
from those used for the WAN interfaces. A management station (a computer running SSH
or a web browser) can be used to access the management interface. The management site
IP addresses can be entered in IPv4 or IPv6 format, or both.
Figure 3 RecoverPoint Gen4 RPA (Dell PowerEdge R610)
RecoverPoint connectivity 23
Figure 4 RecoverPoint Gen5 RPA (Intel R1000)
NTP server
RecoverPoint uses the Network Time Protocol (NTP) to synchronize the clocks across all of
the machines that are attached to a given installation. It is highly recommended that you
configure an external NTP server, that runs on Linux machines, for use by the RecoverPoint
system prior to RecoverPoint installation.
When an external NTP server is configured at a site, the first RPA at that site will
synchronize to the external NTP server. All other RPAs in the system at both sites will
synchronize to the first RPA. To increases the accuracy of the time, you may enter a second
external NTP server address.
The nature of the NTP configuration has the following implications regarding the correct
order for installation of the RPA cluster:
◆ If you are using an external NTP server, it is recommended that the first RPA that you
install is one of the RPAs at the site at which the NTP server is configured (even if this
is the secondary site). Designate this as RPA 1 at this site.
◆ If you are not using an external NTP server, it is recommended to designate the first
RPA that you install at site 1 as RPA 1. In this case, RPA 1 will use its internal clock as
an NTP server, and the RPA will serve as the NTP server for all of the RPAs in the
system. In this scenario, though all RPAs in the installation will be internally
synchronized, they may not necessarily keep correct time.

Zoning
For the effective use of RecoverPoint, particularly in scaled environments, zoning must
adhere to the guidelines listed here. This applies for RecoverPoint systems that use
host-based splitters, intelligent fabric-based splitters, and array-based splitters.
Zoning instructions vary according to the type of HBA ports installed in the RPAs. To
determine which HBA ports are installed in the system, check the HBA card bracket at the
back of the RPA:
◆ QLE2564 HBA has “8 Gb” stamped on the card bracket.
◆ QLE24xx HBA has “4 Gb” stamped on the card bracket.
◆ QLA23xx HBA has nothing written on the card bracket.
RPA WWNs can be recognized in the SAN by their 5001248 prefix. You can use the RPA
Installation Manager option Diagnostics > Fibre Channel diagnostics > View Fibre Channel
details to list the WWNs of each RPA.
Zoning Gen5 and Gen4 RPAs (QLE2564 HBAs)

RecoverPoint 3.4 SP4 and later, 3.5 SP1 and later, and 4.0 and later support Gen5 RPAs.
RecoverPoint 3.1 SP3 and later, 3.2 SP1 and later, and later RecoverPoint releases support
Gen4 RPAs. Gen5 and Gen4 RPAs both contain QLogic QLE2564 HBAs. With these HBAs,
you do not need to separate RPA HBA ports into initiator zones and target zones.
On Gen4 RPAs, the HBA ports read (left to right): 0, 1, 2, 3.
On Gen5 RPAs, the HBA ports read (left to right): 3, 2, 1, 0.
Note: On some Gen5 RPAs, HBA ports “3, 2, 1, 0” are labeled “A, B, C, D”, respectively.
The following guidelines apply:

◆ RPA HBA ports as both initiators and targets. Best practice is to use the RPA HBA ports
as both initiators and targets. In this configuration, maximum performance and
redundancy is achieved with optimal use of resources. The number of ITLs used (when
using Connectrix intelligent switches) for two HBA ports zoned together is nearly the
same as when four HBA ports are zoned separately, either initiator zone or in the
target zone.
If, because of system requirements or other non-RecoverPoint considerations, you
need to zone RPA HBA ports separately either in the initiator zone or in the target zone,
there will be only minor differences in performance and availability. However,
initiator-target separation is not supported in the following cases:
• when mixing different splitter types in the same site
• when using remote replication over Fibre Channel
• when using distributed consistency groups
◆ Zone members. In general, EMC recommends single-initiator zoning, that is, zones
with one initiator and one or more targets. However, RecoverPoint Gen3, Gen4, and
Gen5 RPA ports can act as both initiators and targets. In some configurations, it is
Zoning 25
required to add all RPA ports in a fabric to the same zone. The best practice is always
to zone Gen3, Gen4, and Gen5 RPA ports in the same zone. In some configurations, it
is required.
◆ Server-to-storage zones. Every server must be able to access its production storage. In
most installations, these zones already exist as part of the SAN implementation.
Confirm that these zones exist. EMC requires single-initiator zoning.
◆ RPA-to-storage zones. The zoning guidelines are different for RecoverPoint and
RecoverPoint/SE.
• RecoverPoint. All RPA ports in a fabric must be zoned with all storage ports that are
available for RecoverPoint replication. The best practice is always to use only one
zone per fabric between Gen3, Gen4, and Gen5 RPAs and storage. This applies to
all splitters.
• RecoverPoint/SE. On each fabric, there should be a zone for each RPA, which
includes:
– One HBA port of that RPA
– One port for each VNX/CLARiiON storage processor (SP A and SP B)
◆ Zoning for distributed consistency groups. Distributed consistency groups require that
all RPA Fibre Channel ports in the fabric can communicate with each other. All RPA
ports in a fabric must, therefore, be in one zone. Normally, the RPA-to-storage zone
satisfies this requirement.
◆ Zoning for remote replication over Fibre Channel. Create one zone per fabric that
includes all of the site 1 RPA ports together with all of the site 2 RPA ports.
◆ VNX/CLARiiON ports with MirrorView™. As a best practice, do not share
VNX/CLARiiON ports between MirrorView™ and RecoverPoint. For VNX/CLARiiON
splitters, not sharing ports between MirrorView™ and RecoverPoint is required.
MirrorView™ should, therefore, be excluded from RecoverPoint zones.
◆ Zoning for host-based splitters. Create a zone for each server HBA. That zone should
include one server HBA and all RPA ports in the fabric. These zones enable host-based
splitters to split writes to RPAs.
Note: Host-based splitters are not supported with RecoverPoint 4.0 or later releases.
◆ Zoning for fabric-based splitters. The zoning requirements for RecoverPoint

deployment with intelligent fabric-based splitters are presented in the following:
• EMC RecoverPoint Deploying with the Brocade Splitter Technical Notes
• EMC RecoverPoint Deploying with SANTap and SAN-OS Technical Notes
• EMC RecoverPoint Deploying with SANTap and NX-OS Technical Notes
Note: Fabric-based splitters are not supported with RecoverPoint 4.0 or later releases.

Zoning Gen3 RPAs (QLE24xx HBAs)

RecoverPoint 3.0.x to RecoverPoint 3.4.x supports Gen3 RPAs. Gen3 RPAs contain QLogic
QLE24xx HBAs. With these HBAs, you do not need to separate RPA HBA ports into initiator
zones and target zones.
Zoning and storage mapping (LUN masking) are performed the same as for the Gen4 and
Gen5 RPAs (QLE2564 HBAs).
Zoning Gen1 RPAs (QLA23xx HBAs)

RecoverPoint 2.4.x to RecoverPoint 3.3.x supports Gen1 RPAs. Gen1 RPAs contain QLogic
QLE23xx HBAs. With these HBAs, target-initiator zone separation is required.
Note: RecoverPoint 3.4 and later releases do not support Gen1 RPAs.
The following guidelines apply:

◆ RPA port initiator/target separation. The zone containing RPA initiator ports may not
contain any target ports; the zone containing RPA target ports may not contain any
initiator ports. The odd ports (1 and 3) should be zoned as initiators and the even
ports (0 and 2) should be zoned as targets.
The following features are not supported:
• Different splitter types in the same site
• Remote replication over Fibre Channel
• Distributed consistency groups
◆ Zone members. In general, EMC requires single-initiator zoning, that is, zones with
one initiator and one or more targets; therefore, create a separate zone for each RPA
initiator port.
◆ Server-to-storage zones. Every server must be able to access its production storage. In
most installations, these zones already exist. EMC requires single-initiator zoning.
◆ RPA-to-storage zones. The following applies to all splitters except VNX/CLARiiON. All
RPA initiator ports (1 and 3) must be zoned with all storage ports available for
RecoverPoint replication. Create one zone for each RPA initiator. That zone should
include one RPA initiator and all storage ports available for RecoverPoint replication.
◆ Zoning for VNX/CLARiiON-based splitters. Create one zone for each RPA port. That
zone should include one RPA port and all VNX/CLARiiON ports available for
replication; at least one VNX/CLARiiON port must be on SPA and at least one on SPB.
Half of the RPA ports will automatically be dedicated for initiator functions and half for
target functions.
◆ VNX/CLARiiON ports with MirrorView™. As a best practice, do not share
VNX/CLARiiON ports between MirrorView™ and RecoverPoint. For VNX/CLARiiON
splitters, not sharing ports between MirrorView™ and RecoverPoint is required.
MirrorView™ should, therefore, be excluded from RecoverPoint zones.
◆ Zoning for host-based splitters. Create a zone for each server HBA. That zone should
include one server HBA and all RPA target ports (0 and 2) in the fabric. These zones
enable host-based splitters to split writes to RPAs.
Zoning 27
◆ Zoning for fabric-based splitters. The zoning requirements for RecoverPoint

deployment with intelligent fabric-based splitters are presented in the following:
• EMC RecoverPoint Deploying with the Brocade Splitter Technical Notes
• EMC RecoverPoint Deploying with SANTap and SAN-OS Technical Notes
• EMC RecoverPoint Deploying with SANTap and NX-OS Technical Notes
LUN masking
RecoverPoint operation requires proper LUN masking at each site, according to the
following guidelines. Where initiator/target port separation is in force (when zoning for
Gen1 RPAs), volumes should be exposed only to the initiator ports.
Production and replica volumes must be exposed to all relevant hosts (all hosts that write
to the volume) and all RPA ports in the fabric.
Repository and all journal volumes must be exposed to all RPA ports in the fabric.
For LUN masking instructions when using the Symmetrix splitter, refer to the EMC
RecoverPoint Deploying with Symmetrix Arrays and Splitter Technical Notes.
For LUN masking instructions when using the VNX/CLARiiON splitter, refer to the EMC
RecoverPoint Deploying with VNX/CLARiiON Arrays and Splitter Technical Notes.
For LUN masking instructions when using the VPLEX splitter, refer to the EMC RecoverPoint
Deploying with VPLEX Technical Notes.
LUN mapping should be performed during RecoverPoint installation. The best practice is
not to make changes in LUN masking after installation. If changes must be made later,
follow the instructions in “Changing LUN mapping” in the EMC RecoverPoint Changing LUN
Mapping Technical Notes.
Multiple WWNs
In some configurations, you can use virtual ports to enable an RPA to belong to several
storage groups simultaneously. The menu option for configuring this feature is located in
Setup > Modify settings of the Installation Manager (boxmgmt).
Connectivity for switchless configurations

In iSCSI host-connected environments, ensure all RPAs are physically connected to each
other through their HBA FC ports. In such configurations, there can be a maximum of two
RPAs per RPA cluster since two of the four existing RPA HBA FC ports are already connected
directly to the storage (for high availability). If more than two RPAs are required for the
cluster, connect all of the RPAs in the cluster through FC switches and zone them together.

Unpacking the RPAs

Each RPA package should contain a number of items.
3.2 and later RPA

Each 3.2 and later RPA package should contain:
◆ 1 EMC RecoverPoint Appliance
◆ 1 standard EMC rackmount kit
◆ 1 EMC bezel
◆ 1 Quick-Start Guide
◆ 2 country-specific power cables
If items are missing from the package, promptly notify EMC Customer Support.
Unpacking the RPAs 29


About Deploying RecoverPoint
CHAPTER 2
This chapter explains how to deploy RecoverPoint. Instructions are provided for the
following procedures:
◆ Deploying RecoverPoint........................................................................................... 32
◆ Deployment Manager .............................................................................................. 33
31
Deploying RecoverPoint
Deploying RecoverPoint requires installing and configuring a number of components. This
includes installing RecoverPoint Appliances (RPAs), RecoverPoint software, and
RecoverPoint splitter software.
These deployment procedures are discussed throughout this guide.
Most operations involved with deploying RecoverPoint 3.2 and later require usage of EMC
RecoverPoint Deployment Manager 2.0 SP1, including:
◆ Installing RecoverPoint
◆ Installing RecoverPoint/SE
◆ Connecting RPA clusters (from release 4.0 and later)
◆ Upgrading RecoverPoint software (from release 3.1 and later)
◆ Adding RPAs to existing RPA clusters
◆ Replacing RPAs in existing RPA clusters
◆ Converting a system to a RecoverPoint/SE or RecoverPoint system (from release 3.4
SP1 and later)
◆ Modifying the settings of a RecoverPoint or RecoverPoint/SE system (from release 3.5
and later)
For details on all of the above operations, refer to “Deployment Manager” on page 33.
RecoverPoint deployments require the installation of RecoverPoint splitters, responsible
for “splitting” application writes to their normally designated storage volumes and to the
RPAs.
RecoverPoint supports three splitter types:
◆ Array-based splitters (VNX/CLARiiON, Symmetrix, and VPLEX)
◆ Host-based splitters (also known as KDrivers)
◆ Fabric-based splitters (SANTap and Brocade)
Note: As of release 4.0, only array-based splitters are supported in a RecoverPoint system.
For details on all of the above, refer to “Splitters” on page 313.

RecoverPoint supports the mixing of splitters within an RPA cluster at a site, subject to
certain limitations. Refer to the “Limitations” section of the relevant EMC RecoverPoint
Release Notes.
For a list of operations performed outside the scope of RecoverPoint Deployment
Manager., refer to “Other Operations” on page 305.

Deployment Manager
EMC RecoverPoint Deployment Manager (DM) 2.0 SP1 is a package of graphical user
interface (GUI) wizards that help you perform a number of important RecoverPoint
operations from a single management point.
IMPORTANT
DM 2.0 SP1 replaces DM 2.0, which was available on the EMC Online Support site.
DM 2.0 and earlier users should start using DM 2.0 SP1 immediately.
Accessing Deployment Manager

Deployment Manager can be downloaded from the RecoverPoint Software Downloads
section in Powerlink (Home > Support > Software Downloads and Licensing > Downloads
P-R > RecoverPoint).
It is available as a zip file for use from a Windows machine.
Open or save the file and extract the archive to a newly created destination folder (that is,
a new, empty folder).
Note: The file size of Deployment Manager is documented in the EMC RecoverPoint
Deployment Manager 2.0 SP1 Release Notes.
Launching Deployment Manager

To launch Deployment Manager, open the folder and double-click the
RecoverPoint_DM.exe executable file.
Wizards in Deployment Manager 2.0.SP1
Wizards available when working on RPAs running 4.0 or later releases

When logging in as EMC personnel (Other operations), Deployment Manager presents the
following wizards:
◆ RecoverPoint/SE Installer — Enables you to install a new RecoverPoint/SE cluster. For
details, see “RecoverPoint/SE Installer Wizard” on page 38.
◆ RecoverPoint Installer — Enables you to install a new RecoverPoint cluster
(RecoverPoint/CL and RecoverPoint/EX). For details, see “RecoverPoint Installer
Wizard” on page 86.
◆ Connect Cluster — Enables you to connect a new RPA cluster to an existing
RecoverPoint system. For details, see “Connect Cluster Wizard” on page 128.
◆ RPA Replacement — Enables you to non-disruptively replace an RPA in an existing RPA
cluster. For details, see “RPA Replacement Wizard” on page 142.
◆ Add New RPAs — Enables you to non-disruptively add new RPAs to existing RPA
clusters. For details, see “Add New RPAs Wizard” on page 162.
Upgrade Cluster — Enables you to non-disruptively upgrade a RecoverPoint cluster.
For details, see “Upgrade matrix to the latest RecoverPoint releases” on page 193.
Deployment Manager 33
◆ Converter — Enables you to convert a system to a RecoverPoint/SE or RecoverPoint

system. For details, see “Converter Wizard” on page 250.
◆ Cluster Modification — Enables you to modify the system settings of an existing
RecoverPoint cluster. For details, see “Cluster or System Modification Wizard” on
page 286.
Wizards available when working on RPAs running 3.5 or earlier releases

When logging in as EMC personnel (Other operations), Deployment Manager presents the
following wizards:
◆ RecoverPoint/SE Installer — Enables you to install a new RecoverPoint/SE
configuration. For details, see “RecoverPoint/SE Installer Wizard” on page 38.
◆ RecoverPoint Installer — Enables you to install a new RecoverPoint configuration
(RecoverPoint/CL and RecoverPoint/EX). For details, see “RecoverPoint Installer
Wizard” on page 86.
◆ RPA Replacement — Enables you to non-disruptively replace an RPA in an existing RPA
cluster. For details, see “RPA Replacement Wizard” on page 142.
◆ Add New RPAs — Enables you to non-disruptively add new RPAs to existing RPA
clusters. For details, see “Add New RPAs Wizard” on page 162.
◆ Upgrade RPAs — Enables you to non-disruptively upgrade RecoverPoint software on
existing RPA clusters.
This operation requires running two wizards:
• Prepare for Upgrade — Prepares the RPA clusters for upgrade. Run this wizard first.
• Apply/Resume Upgrade — Applies the upgrade to the RPA clusters. Run this wizard
second.
For details, see “Upgrade matrix to the latest RecoverPoint releases” on page 193.
◆ Converter — Enables you to convert a system to a RecoverPoint/SE or RecoverPoint
system. For details, see “Converter Wizard” on page 250.
◆ System Modification — Enables you to modify the system settings of an existing
RecoverPoint environment. For details, see “Cluster or System Modification Wizard”
on page 286.
System requirements
To use Deployment Manager, you must have a version of Java™ 7 (update 13 or higher)
installed on the computer running Deployment Manager. It is highly recommended to have
the latest Java 7 update installed.
Networking requirements
To perform a two-site installation or add new RPAs to existing RPA clusters using the
wizards, the station you are working on must be able to communicate with all RPA
management (LAN) networks on both sites.

Thus, if you are performing a two-site installation, but do not have communication
between your work station and RPAs on both sites, you should choose to perform a
two-step installation.
The following networking requirements must be met to complete a two-site installation
using the RecoverPoint Installer:
◆ The work station must be routable to the RPA and site management IPs.
◆ Ensure that TCP ports 21, 22, 8081, and 8082 are open on the work station to enable
communication with all RPAs.
IP connectivity from RPAs to intelligent fabric switches (SANTap and Brocade) is required
for RecoverPoint to be able to collect and retain logs from splitters running on the
switches.
For SANTap, the Telnet port must be accessible.
For Brocade, the hlr_kbox port must be accessible.
To enable VNX/CLARiiON splitter log collection, TCP port 443 (https) must be open.
For further information on RecoverPoint networking requirements, refer to the EMC
RecoverPoint Security Configuration Guide, available on EMC Online Support.
IMPORTANT
Failure to establish an IP connection between RPAs to switches will prevent splitter log
retention and prevent EMC Customer Service from being able to collect system logs from
customers and provide timely and effective support.
Notes about Deployment Manager

Throughout the Deployment Manager wizards:
◆ You can enter a number of settings. To improve system performance, it is
recommended to enter values in all fields (where relevant).
◆ Whenever you click Next, the system saves configuration settings automatically in the
configuration file.
◆ You must complete the wizards in a sequential order. That is, you must complete each
step (screen) of a wizard before proceeding to the next step.
◆ Three unsuccessful login attempts using RecoverPoint Installation (boxmgmt) and CLI
(admin) usernames will lock the user out of the RecoverPoint system. Only users with
Security permission can unlock a user. To do so, use the CLI command unlock_user.
Deployment Manager 35

CHAPTER 3
RecoverPoint/SE Installation
This chapter explains how to install RecoverPoint/SE RPA clusters using RecoverPoint
Deployment Manager 2.0 SP1. Instructions are provided in the following procedures:
◆ RecoverPoint/SE Installer Wizard............................................................................. 38
◆ RecoverPoint 4.0 or later ......................................................................................... 40
◆ RecoverPoint 3.5 or earlier ...................................................................................... 65
RecoverPoint/SE Installation 37
RecoverPoint/SE Installer Wizard

The RecoverPoint/SE Installer Wizard is a graphical user interface (GUI) wizard that helps
you install a new RecoverPoint/SE RPA cluster (site) from a single management point.
Once completing the wizard, you will be able to use Unisphere for RecoverPoint (the name,
as of 4.0, of the RecoverPoint Management Application GUI).
IMPORTANT
The RecoverPoint/SE Installer Wizard is used to install RecoverPoint/SE. A
RecoverPoint/SE system uses array-based splitters on CLARiiON CX3 and CX4 series and
VNX series environments. To install RecoverPoint, refer to “RecoverPoint Installer Wizard”
on page 86.
Installing RecoverPoint/SE using the Deployment Manager RecoverPoint/SE Installer

Wizard is a pre-requisite for using the RecoverPoint/SE for Unisphere management
console.
The Unisphere management console cannot manage RecoverPoint/SE clusters installed by
others means (such as the RecoverPoint Installer Wizard). For such clusters running
release 3.4 SP1 or later, you can run the Deployment Manager Converter Wizard to enable
management using the RecoverPoint/SE for Unisphere management console. For details
on the Converter Wizard, refer to “Environment Conversion” on page 249.
Note: Environments can also be upgraded from RecoverPoint/SE to RecoverPoint. For

information and details contact EMC Customer Support.
About the RecoverPoint/SE Installer Wizard

As of RecoverPoint 4.0, the Installer Wizard allows you to install one RPA cluster at a time.
Therefore, if you plan to deploy multiple clusters, you must run the Installer Wizard as
many times as there are clusters.
Once done installing the clusters, to enable replication and communication between
them, you must run the Connect Cluster Wizard. “Cluster Connection” on page 127
contains information about this wizard.
System requirements
To use the RecoverPoint/SE Installer Wizard, you must have a Telnet connection to Cisco
and Brocade switches, to perform automatic zoning.
When installing:
◆ RecoverPoint/SE 3.4.x and later AND selecting repository volume automatically:
5.72 GB of space available on existing RAID groups (not RAID 0 groups).
◆ RecoverPoint/SE 3.4.x and later AND selecting repository volume manually:
2.86 GB of space available on existing RAID groups (not RAID 0 groups).
◆ RecoverPoint/SE 3.3.x and earlier: 2.86 GB of space available on existing RAID groups
(not RAID 0 groups).

Launch RecoverPoint/SE Installer Wizard

To launch the RecoverPoint/SE Installer Wizard:
1. Launch Deployment Manager by opening the RecoverPoint_DM.exe application file.
2. You are prompted to check for a newer release of Deployment Manager (Figure 5).
Click No if you are certain you are using the latest release, or do not have connectivity
to the internet.
Click Yes if you want to check for the latest release. Deployment Manager checks if a
newer release is available for download from EMC Online Support site:
• If a newer release is not found, click Next to continue with the wizard.
• If a newer release is found, the release number is displayed, and you are provided
with the option to download it and use it now:
– If you click Yes, Deployment Manager closes and your browser window opens to
a direct link on EMC Online Support where a zip file of the latest Deployment
Manager is available for download. Download and extract the file, then perform
step 1 on page 39.
– If you click No, you skip the download and continue with the wizard.
Figure 5 Check for newer release screen
3. You are prompted to choose which RecoverPoint release you plan to install, upgrade
from, or maintain.
4. If you select RecoverPoint 4.0 or later releases, continue from “RecoverPoint 4.0 or
later” on page 40.
5. If you select RecoverPoint 3.5 or earlier releases, continue from “RecoverPoint 3.5 or
earlier” on page 65.
RecoverPoint/SE Installer Wizard 39

RecoverPoint 4.0 or later

Starting in RecoverPoint 4.0, RecoverPoint clusters are installed one at a time. As such, the
RecoverPoint/SE Installer Wizard needs to be run once for every cluster in the system.
Once installs are completed, the Connect Cluster Wizard must be run to connect the
clusters in the system. See “Cluster Connection” on page 127 for detailed information
about this wizard.
Note: A cluster is defined as a group of physical or virtual RPAs at the same geographic
location that serves as a source or target for replication.
Access the Wizard

Follow these steps to access the RecoverPoint/SE Installer Wizard:
1. On the login screen (Figure 6), select Other operations (EMC personnel) and enter your
RecoverPoint login credentials (CLI).
Note: Default CLI username and password = admin.
If you are EMC personnel, it is recommended to install RecoverPoint/SE using the Other
operations (EMC personnel) option, and not the Install RecoverPoint/SE option.
Figure 6 Deployment Manager login screen

2. On the wizard selection screen, select RecoverPoint/SE Installer Wizard (Figure 7).
Figure 7 Deployment Manager wizard selection screen
Prerequisites
◆ Before continuing, ensure the following conditions are met on the RecoverPoint cluster
(Figure 8). If any of the conditions are not fulfilled, close the wizard, fulfill the
conditions, and then run the wizard again.RPAs are connected to SAN and Ethernet
network
◆ RPAs are loaded with the same RecoverPoint/SE ISO image
◆ RPAs are set with IP addresses (optional if the environment includes a DHCP server)
◆ The computer that the wizard is run from must be able to communicate with the cluster
management IP and all of the cluster’s RPA management (LAN) networks.
Ensure that ports 21, 22, 7225, and 8082 (all TCP) are open on the computer to
enable communication with all RPAs.
Tip: Telnet to these ports on the computer to ensure they are open.
◆ RPAs are either all physical RPAs or all virtual RPAs
◆ You have EMC Online Support login credentials.
If you do not have these credentials, or the computer that the wizard is run from does
not have Internet connectivity, you must have an Installation Change Management
XML file available locally to complete the installation.
Note: To obtain the XML file, you must submit an Installation Service Request to EMC
Customer Support.
◆ If installing physical RPAs:

• RPAs are rack mounted
• All RPAs must be Gen4 or later
◆ If installing virtual RPAs:
• Virtual RPAs are deployed using the RecoverPoint OVF package
• VNX arrays are running OE for Block version later than 05.32.000.5.201
• VNX arrays are pre-configured with iSCSI ports
RecoverPoint 4.0 or later 41

• VMware vCenter Server is 5.0 or later, with at least one registered vSphere 5.0 or
later
• Valid segmented network infrastructure between:
– The vSphere host and the VNX array (iSCSI 1G/10G)
– The vSphere host and the existing RPA cluster networks (LAN and WAN)
• Reserved quota is required for virtual system resources: CPU, memory, disk
• At least three virtual networks are required: LAN, WAN, and iSCSI
• CHAP credentials for RPA iSCSI ports and storage iSCSI ports must be different
Select the I have fulfilled the conditions for installing the cluster checkbox, and click Next
to continue.
Figure 8 Prerequisites screen
Configuration file
The RecoverPoint/SE Installer allows you to select one of two installation modes
(Figure 9):
◆ Create a new installation configuration file - The system creates a new installation
configuration file. Starting with a blank configuration, the user must enter
configuration settings for the installation. The system uses these settings to complete
the installation.
Provide a valid file name and directory location. By default, the file name and directory
location is C:\Users\ <username>\RecoverPoint\RPSE_config.properties.

Edit the field to change the information, or click Browse to select a different location to
save the file, as well as rename it.
Note: File name cannot contain the following characters: \/ * ? “ : < > |
◆ Create or continue an installation from a saved configuration file - The system loads
the settings from a previously saved installation configuration file.
• If using the file to create a new installation from a saved file, and the file was
already applied to a previous installation, the system allows you to use the file and
modify the configuration parameters.
Note: To modify the system settings of an existing RecoverPoint/SE RPA cluster, use the
Cluster Modification Wizard.
Figure 9 Configuration file screen
Environment settings
Define the RecoverPoint cluster settings (Figure 10).
General
◆ Cluster name — Name of the cluster being installed.
◆ Number of RPAs — A cluster can have between 2 to 8 RPAs.
◆ Time zone — The time zone for the cluster.
Connectivity
◆ For LAN:
• IP type — IPv4, IPv6, or IPv4 and IPv6.
• MTU — default value is 1500 (do not modify unless instructed to do so).
◆ For WAN:
• IP type — IPv4 or IPv6.
Environment
◆ Domain name (optional) — The cluster domain name.

◆ Primary DNS server (optional) — The IP address of the primary DNS server for the
cluster.
◆ Secondary DNS server (optional) — The IP address of the secondary DNS server for the
cluster.
◆ NTP server (optional) — The IP address of NTP server for the cluster.
Note: Though not mandatory, it is highly recommended to set an NTP server, as it

ensures that all RecoverPoint components synchronize with an external NTP source.
◆ Secondary NTP servers — Cannot be modified.
Figure 10 Environment settings screen
RPA discovery
Define how you want to set the IP addresses of uninstalled RPAs.
Two options are provided (Figure 11):
◆ I have already set IP addresses for the RPAs
This option is recommended when one or more of the following is true:
• You have already set the IP addresses.
• You are installing RPAs running releases earlier than 3.5
• The environment does not include a DHCP server.
◆ I want Deployment Manager to discover the RPA IP addresses
This option is only relevant when RPAs are running release 3.5 or later and the
environment includes a DHCP server. When you select this option, the Discover
uninstalled RecoverPoint Appliances (RPAs) section becomes active.
In the Discover uninstalled RecoverPoint Appliances (RPAs) section:

When you click Discover, you can choose how Deployment Manager discovers the
RPAs and gets their currently set IP addresses:
• Run discovery from work station — The installer tries to discover all unattached
RPAs running 3.5 or later. The work station must be able to communicate with all
RPAs.
• Run discovery from an RPA— The installer tries to discover all unattached RPAs
running 3.5 or later. The RPA must be running 3.5 or later and be able to
communicate with all RPAs.
Enter the RPA’s IP and Password. Username = boxmgmt.
Once you click OK, a Select a discovered RPA link appears beside each RPA field. Click
it and select an IP address of a discovered RPA. Once you do this for all RPAs, click
Next.
Figure 11 RPA discovery screen
IP and connectivity settings

Define the cluster IP configurations and set the RPA IP settings (Figure 12).
Cluster management — LAN, based on IP type entered in “Environment settings” on
page 43. A virtual IP address that is used to configure the RPA cluster. The IP address is
assigned to the RPA that is currently running the active instance of the cluster
management.
Interface netmask — LAN and WAN, based on IP type entered in “Environment settings” on
page 43.
RPA — IP addresses of the cluster RPAs, based on IP type entered in “Environment
settings” on page 43.

Note: If using a mix of RPA hardware types (such as Gen4 and Gen5), It is highly
recommended to assign RPA 1 and RPA 2 (cluster control RPAs) to the latest hardware
types (Gen5), to improve system function and performance.
Gateways configuration
Default gateway — Based on IP type entered in “Environment settings” on page 43.
Additional gateways (optional)
Gateway, Netmask, and Subnet.
Click Add route to add additional gateways.
Figure 12 IP and connectivity settings screen
Login credentials
Enter the default RecoverPoint login credentials (Figure 13).
RecoverPoint login credentials
The system prompts you to enter your RecoverPoint login information. For username
boxmgmt, the default password is boxmgmt.

Figure 13 Login credentials screen
Connectivity results
Review the results of the RecoverPoint connectivity test (Figure 14).
The system communicates and validates the statuses of the RPAs and confirms that all
components are OK or that errors are detected.
The system presents the following results: Status, RPA, Cluster name, LAN IP address,
Hardware platform, RecoverPoint release, and Comment.
If errors are detected for an RPA, a comment appears describing the problem. To proceed
to the next step in the wizard, you must resolve all errors. Once errors are resolved, click
Retry to revalidate the communication statuses.
When all statuses appear OK (green check mark), click Next to continue.
Figure 14 Connectivity results screen

RPA iSCSI configuration
Cluster iSCSI settings

This screen appears only if you are installing a virtual RPA (vRPA). If you are installing a
physical RPA, continue to “EMC Online Support credentials” on page 49.
Define the RPA cluster iSCSI settings (Figure 15).
Connectivity
For iSCSI 1
◆ IP type — IPv4 or IPv6.
◆ MTU — Default value is 1500 (do not modify unless instructed to do so).
For iSCSI 2
If relevant, select the Configure CHAP credentials for the RPAs iSCSI ports checkbox and
modify the CHAP credentials (username and password).
Figure 15 Cluster iSCSI settings screen
RPA iSCSI ports

This screen appears only if you are installing a virtual RPA (vRPA).
The current cluster iSCSI IP configurations and RPA iSCSI IP settings are displayed. Enter
the iSCSI settings for the new RPAs (Figure 16).
page 43.
IMPORTANT
It is strongly recommended to put the iSCSI interface on a different subnet than the LAN
and WAN interface, to avoid iSCSI communication errors.

RPA — iSCSI 1 and iSCSI 2 IP addresses of the existing RPAs in the cluster, and the
addresses of the new RPAs you are adding to the cluster.
Default gateways
Default gateway — Cannot be modified.
Additional gateways
Gateway, Target netmask, and Target subnet.
Figure 16 RPA iSCSI Ports screen
EMC Online Support credentials

Enter EMC Online Support site credentials (username and password) to access relevant
RecoverPoint/SE ISO images to apply to the cluster, and to provide you with the relevant
Installation Change Management information required to complete the upgrade (Figure
17).
If you do not have Internet connectivity, or do not have EMC Online Support credentials,
select the Use an offline Installation Change Management XML file checkbox and load the
XML file into the wizard from a local folder where you have saved the file.
IMPORTANT
To obtain the XML file, you must open an Installation Service Request with Customer
Support (severity level 3). In the request, ask for the latest Installation Change
Management XML file for the RecoverPoint Deployment Manager, and indicate the
intended date of the installation. The file will be provided within one (1) business day as

an email attachment, so ensure a valid email address is provided. Once provided, the file
must be used within 30 days of delivery; any use of the file after 30 days will not be
supported by EMC.
Figure 17 EMC Online Support credentials screen
Update RecoverPoint release

Select how you want to update the RecoverPoint release running on the RPAs (Figure 18).
The RecoverPoint release running on the RPAs is displayed (the ISO image that comes
pre-installed on the RPAs). To ensure the RPAs are running the latest RecoverPoint release,
you should update them now.
IMPORTANT
Upgrading the RecoverPoint release now saves you from having to run the Upgrade Cluster
Wizard after installation to upgrade the RecoverPoint/SE software running on the RPAs.
Update options
◆ Update with an ISO image available from EMC Online Support site (recommended)
Select this option to download an ISO image available from EMC Online Support site
(login credentials required). When you select this option, you continue to “ISO image
download details” on page 51.
Note: This option is grayed out if no ISO image can be found on EMC Online Support.
◆ Update with an ISO image available locally

Select this option if you have an ISO image on your local machine, a DVD, a USB
device, or an FTP server. When you select this option, you continue to “ISO file
information” on page 52.

◆ Do not update. Continue with current RecoverPoint release on RPAs

Select this option to continue installing the RPAs without upgrading the ISO image
running on the RPAs. When you select this option, you continue to “Installation
change management procedures” on page 53.
Figure 18 Update RecoverPoint release screen
ISO settings
ISO image download details

This screen appears only if you selected “Update with an ISO image available from EMC
Online Support site (recommended)” on page 50. Choose the desired ISO image and
define where to save it (Figure 19).
EMC Online Support site credentials

Enter your username and password. Without these credentials, you cannot use this option
to update the RecoverPoint release running on the RPAs you are installing.
RecoverPoint ISO image download details

Release — Deployment Manager connects to EMC Online Support site and presents all
valid ISO images (releases) that you can download and apply to the cluster you are
installing.
Target folder — Select a location on your local machine (the machine running Deployment
Manager) to where you want to save the ISO image, or click Browse to select an alternate
location.

Figure 19 ISO image download details screen
ISO file information

This screen appears only if you selected “Update with an ISO image available locally” on
page 50.
There are three options to download the ISO files to the RPAs:
◆ “Upload from local machine” on page 52
◆ “Copy from DVD or USB device inserted in the RPAs” on page 52
◆ “Download from FTP server” on page 52
For all options, the file name must be the exact name as it appears on the RecoverPoint
“Downloads” section on EMC Online Support, and identical for all options (on both sites,
if relevant) for the upgrade to work properly.
Upload from local machine

Enter the file name of the ISO file that you located on your local machine (the machine
running Deployment Manager), or click Browse to find the file.
Copy from DVD or USB device inserted in the RPAs

Enter the file name of the ISO file that is on the DVD or USB devices.
When using DVD option, a DVD with the ISO file must be loaded in each RPA at the site for
the download to work properly.
When using USB option, a USB with the ISO file must be connected to each RPA at the site
for the download to work properly.
Select the I have a DVD/USB inserted in all the RPAs checkbox if you want Deployment
Manager to automatically begin downloading the ISO files to the RPAs at the site once you
click Next.

Download from FTP server
Enter FTP credentials of an FTP server or servers where the RecoverPoint/SE ISO file is
located to download it to the RPAs.
Qualified FTP servers: CuteFTP, Fedora Linux, FileZilla, Gene6, Xlight, Windows FTP Service.
Enter the FTP server details and ISO file information:

◆ Server IP address
◆ Server port number to connect on FTP server (default is 21)
◆ Username
◆ Password
Example: /files/folder3 ◆ File location (location of ISO file on the FTP server)
Example: ◆ File name (name of the ISO file on the FTP server)
rel3.4.SP2_l.48_release_64
_emc_md5_11ce8b9190e8
788daeb2e7bfe82b2c6.iso
FTP credentials summary

This screen appears only if you selected “Download from FTP server” on page 52.
Review the status of the FTP connectivity results.
The system communicates and validates the connectivity to the FTP servers and confirms
that all connections are OK or that errors are detected.
If errors are detected for an FTP server, a comment appears describing the problem. To
proceed to the next step in the wizard, you must resolve all errors. Once errors are
resolved, click Retry to revalidate the communication statuses.
When all statuses appear OK (green check mark), click Next to begin the download and
distribution of the ISO file(s) to the RPAs.
Installation change management procedures

Once the ISO file is distributed to the RPAs, the wizard analyzes which release you are
installing. Based on this analysis, the wizard presents you with a list of general installation
messages and Installation Change Management procedures that must be completed
before continuing the installation (Figure 20).
IMPORTANT
Failure to complete each procedure may cause the installation to fail and data to be lost. If
a procedure is unclear to you, contact EMC Customer Support for assistance.
General installation messages

These messages are relevant to all installations, regardless of what release you are
installing.
Installation Change Management procedures

These procedures are unique to the RecoverPoint/SE system you are installing.
Click a message or procedure to open it in a new window, and click Export to clipboard if
you would like to view the information in another program (Figure 21).
After reading each message and performing each relevant procedure, select their
checkboxes. Once you have selected all the checkboxes, click Next.

Figure 20 Installation change management screen
Figure 21 Installation change management message screen

Apply configuration results

This screen step appears if you selected the Do not update. Continue with current
RecoverPoint release on RPAs option in “Update RecoverPoint release” on page 50.
The system attempts to log in to each of the RPAs and validate system information. The
results of applying the configuration settings to all RPAs are displayed (Figure 22). Once
installation has completed successfully, click Next.
Figure 22 Apply configuration results screen - update
Upgrade and Apply configuration results

This screen step appears if you selected the Update with an ISO image available locally
option in “Update RecoverPoint release” on page 50 (Figure 23).
Review the results of applying the configuration settings to all RPAs in the environment.
The filename of the ISO file that you applied to the RPAs is displayed, and the distribution
option that you selected (appears in brackets beside the site name).The system
communicates and validates the statuses of the RPAs and confirms that all components
are OK or that errors are detected.

Figure 23 Upgrade and Apply configuration results screen
Storage configuration
VNX/CLARiiON login credentials

Enter the login credentials for the VNX/CLARiiON storage system at the site (Figure 24).
Unisphere/Navisphere login credentials

◆ Array SP A IP — Enter the IP address of array SP A at the site.
◆ Array SP B IP — Enter the IP address of array SP B at the site.
◆ EMC Unisphere/Navisphere username — Enter the Unisphere/Navisphere username
at the site. Default value is admin.
◆ EMC Unisphere/Navisphere password — Enter the Unisphere password at the site.
◆ Authentication scope — Select whether the scope of the user account is Global, Local,
or LDAP. Default value is Global.
Note: For authentication within the local security directory, specify Global or Local
scope.
Click Next to confirm login credentials and continue.

Figure 24 VNX/CLARiiON login credentials screen
VNX/CLARiiON login status

The system now has the necessary information required to validate the VNX/CLARiiON
settings. The system attempts to log in to the VNX/CLARiiON array and validate the
following information (Figure 25):
◆ The RecoverPoint/SE Installer can communicate with VNX/CLARiiON SP A and SP B.
◆ The login credentials are correct for SP A and SP B.
◆ SP A and B are not already attached to RecoverPoint/SE cluster.
◆ IP settings were applied successfully.
components are OK or that errors are detected. If errors are detected, you can click the
error to display details. The array name and serial number of the array are also displayed.
To proceed to the next step in the wizard, you must resolve all errors. Once errors are
resolved, click Refresh to revalidate the communication statuses.
When all statuses appear OK, click Next to continue.
Figure 25 NX/CLARiiON login status screen

Storage iSCSI ports

This screen appears only if you are installing a virtual RPA (vRPA) cluster. Once complete,
you continue to “Apply iSCSI configuration results” on page 58. If you are installing a
physical RPA cluster, continue to “Zoning” on page 59.
Define the storage CHAP and iSCSI IP configurations (Figure 26).
VNX/CLARiiON details
◆ Array name — Name of the array in the RecoverPoint/SE system.
CHAP credentials
◆ Username and password
Storage iSCSI IP addresses

◆ Number of ports — 2-10. Increasing the number of ports requires you to enter
corresponding storage iSCSI IP addresses.
Figure 26 Storage iSCSI Ports screen - update
Apply iSCSI configuration results

you continue to “SAN diagnostics” on page 61.
The results of applying the configuration settings to all RPAs are displayed (Figure 27).
Once installation has completed successfully, click Next.

Figure 27 Apply iSCSI configuration results screen
Zoning
The following zoning screens appear only if you are installing a physical RPA cluster.
Select how you want to perform zoning.
◆ Automatic - The Installer zones the RPAs and the VNX/CLARiiON arrays automatically.
For details, see “Zoning: Automatic” on page 59.
Note: This option is available with Brocade and Cisco switches only.
◆ Semi-automatic - The Installer creates the necessary zoning scripts, but you must
apply them yourself. For details, see “Zoning: Semi-automatic” on page 60.
◆ Manual - The Installer indicates which ports should be zoned together, and you are
responsible for actually creating the zones. For details, see “Zoning: Manual” on
page 60.
◆ Direct-attach Storage - The Installer verifies that, in this switchless configuration, each
RPA is directly connected to SP A and SP B of the VNX/CLARiiON array. For details, see
“Zoning: Direct-attach Storage” on page 61.
Note: If the RPAs are directly attached to the VNX/CLARiiON arrays, then the wizard
automatically skips this screen and continues to “SAN diagnostics” on page 61.
Zoning: Automatic
Automatic zoning can be performed on Cisco fabric switches with an active zoneset, and
on Brocade (Connectrix B-Series) fabric switches running FOS 6.0 and higher with an
active zone configuration.
A Telnet connection to Cisco and Brocade switches is mandatory to perform automatic
zoning.
You must enter switch credentials to allow RecoverPoint/SE to perform automatic zoning.
Enter the following details for each fabric:
◆ Switch type — Cisco or Brocade

◆ IP address of the fabric switch at the site

◆ Username for the fabric switch at the site
◆ Password for the fabric switch at the site
The Installer automatically creates an RPA-to-storage zone for each RPA at this site, where
each zone includes:
◆ One HBA port of that RPA
◆ One port for each VNX/CLARiiON storage processor
Zoning: Semi-automatic
Perform the step presented onscreen using the switch CLI.
Semi-automatic zoning is available for Brocade and Cisco fabric switches.
To use semi-automatic zoning, you must first enter the switch credentials, just as for
automatic zoning. Note that the system does not automatically configure the zoning on
the switch.
Upon entering the switch credentials, the RPA connects to the switch to determine which
WWNs are connected, and creates a script that can be used to create the zoning
accordingly. This script is presented onscreen, and can be exported for further use by
clicking Export to clipboard.
Zoning: Manual
Zone and mask LUNs using the RPA port WWNs displayed in the RPAs WWNs table(s), and
the VNX/CLARiiON array port WWNs displayed in the VNX/CLARiiON Array table.
To create the RPA-to-storage zones at this site, use the following procedure:
1. On each fabric, create a zone for each RPA, which includes:
• One HBA port of that RPA
Note: When multiple virtual WWNs are associated with the HBA port, include all of
those WWNs in the zone.
• One port for each VNX/CLARiiON storage processor

2. At each site, on each fabric, create an RPA-to-RPA zone containing all local RPA HBAs
that are not used in RPA-to-storage zones (best practice). This zone provides an
additional communication link between RPAs. It can also be used for synchronous
replication of distributed consistency groups. If replicating over Fibre Channel, merge
the RPA-to-RPA zones at each site into one.
3. For synchronous or remote replication over Fibre Channel:
• Zone local and remote RPAs together.
• Use dedicated HBA ports (best practice).
4. For asynchronous replication of distributed consistency groups, it is recommended to
use different HBA ports than those used for the RPA-to-storage connections.

Zoning: Direct-attach Storage

Select this option if each RPA is directly connected to SP A and SP B of the VNX/CLARiiON
array.
Note: The number of RPAs that can be directly attached to the VNX/CLARiiON array
depends on the number of FC ports per SP of the VNX/CLARiiON model.
SAN diagnostics
The system performs SAN diagnostics for the site, attempting to validate that the current
configuration is appropriate for the RPA, and that RecoverPoint/SE can successfully
operate in the current SAN environment.
The system presents the following results: Severity, RPA, Message ID, Category, and
Description (Figure 28).
The system confirms that all components are OK and that no errors exist. If errors are
detected, you can click the error to display details.
Once errors are resolved, click Refresh to rerun the SAN diagnostics process.
It is highly recommended to resolve all SAN discovery warnings, even though the system
allows you to ignore them and continue the installation.
Figure 28 SAN diagnostics screen

Repository volume
Determine how you want the repository volume to be selected (In Figure 29, automatic is
selected).
Automatic - The Installer automatically creates and configures a repository volume.
Manual - The Installer lists possible volumes, and you can select the one to be configured
as the repository volume.
Figure 29 Repository volume screen
Apply configuration
Wait for the configuration to be applied (Figure 30).
The steps involved are:
◆ Configuring VNX/CLARiiON array
• Creating internal VNX/CLARiiON storage groups
• Registering RPA WWNs on VNX/CLARiiON array
◆ Configuring RPAs
• Creating repository volume
• Configuring repository volume
◆ Finishing the installation
• Attaching RPAs to cluster
• Waiting for RPAs to come up after reboots
Progress bars indicate that the system is applying settings and completing the
installation. Once the progress bars stop, the system confirms that all components are OK,
or that errors are detected. If errors are detected, you can click the error to display details.
resolved, click Retry to reapply settings and revalidate that the RPA installation is
successful.

Figure 30 Apply configuration screen
Summary
You have successfully completed the RecoverPoint/SE installation.
The RecoverPoint/SE storage group created are displayed.
IMPORTANT
The storage group contains all the VNX/CLARiiON LUNs that RecoverPoint/SE replicates.
Do not change the name of the group, or RecoverPoint/SE may fail to function properly.
To start managing the RecoverPoint system, click the Unisphere for RecoverPoint hyperlink
or click Finish and enter the system using your browser (Figure 31).
Once you open Unisphere for RecoverPoint, you are asked for a license key. For further
information, refer to the “Managing RecoverPoint licenses” section of the EMC
RecoverPoint Administrator’s Guide.
IMPORTANT
If you plan to replicate to a remote RecoverPoint/SE RPA cluster, you must connect this
cluster to the remote cluster using the Connect Cluster Wizard, as documented in
“Connect Cluster Wizard” on page 128.

Figure 31 Summary screen - update
Post-installation requirements
After installing a RecoverPoint/SE system, you must complete the RecoverPoint
Post-Deployment Form. To download the form from EMC Online Support
(http://support.emc.com), click “Support by Product”, type “RecoverPoint SE” in the “Find
a Product” search field. On the “RecoverPoint SE” page, click “Documentation” and
download the form from the list of documents.
Once you have completed it, either:
◆ Email the information to the Install Base group: IBGroup@EMC.com
◆ Or call in the information to the Install Base group:
1-866-436-2411 – Monday to Friday (regular Eastern Time Zone working hours)

RecoverPoint 3.5 or earlier

Access the Wizard
Follow these steps to access the RecoverPoint/SE Installer Wizard:
1. On the login screen (Figure 6), select Other operations (EMC personnel) and enter your
If you are EMC personnel, it is recommended to install RecoverPoint/SE using the Other
operations (EMC personnel) option. Do not select Install RecoverPoint/SE unless
instructed to do so. Contact EMC Customer Support for information on selecting this
option.
2. On the wizard selection screen, select RecoverPoint/SE Installer Wizard (Figure 7).
RecoverPoint 3.5 or earlier 65

Prerequisites
Before continuing, ensure the following conditions are met on your environment
(Figure 34). If any of the conditions are not fulfilled, close the wizard, fulfill the conditions,
and then run the wizard again.
◆ Production hosts are configured to work with VNX/CLARiiON arrays and have SAN
connectivity.
◆ The compatible VNX/CLARiiON-related software for this RecoverPoint/SE release is
installed and enabled, including:
• RecoverPoint splitter engine (driver)
• RecoverPoint splitter enabler
• VNX/CLARiiON splitter bundle (FLARE OE)
◆ RPAs are rack mounted.
Note: To install more than two RPAs per site, RecoverPoint/SE 3.3 SP1 or later must be
installed on each RPA.
◆ RPA and VNX/CLARiiON storage processors are connected to fabrics and switches to
ensure high availability, as presented in “Fibre Channel (RecoverPoint/SE)” on
page 22.
◆ All RPAs are connected to SAN and Ethernet network.
◆ RPAs are loaded with the same RecoverPoint/SE ISO image.
Important: If installing 3.5 or later, all RPAs must be Gen4 RPAs or later.
◆ RPAs are set with IP addresses (optional if installing 3.5 and later and the environment
includes a DHCP server).
Select the I have fulfilled the conditions for installing my environment checkbox, and click
Next to continue.

Figure 34 Verify requirements screen
Configuration file
The RecoverPoint/SE Installer allows you to select one of the following installation modes
(Figure 9):
the installation.
location is C:\Users\ <username>\RecoverPoint\RPSE_config.properties.
• If using the file to continue a RecoverPoint/SE installation, after having already
installed the settings to a first or second site or both, this operation allows you to
complete the installation of the site(s) and apply the settings. To perform this step,
browse and select the file and select the Skip to step Apply Configuration (if a site
has already been installed) checkbox.
Note: When selecting this mode, the system does not allow you to change any site
settings, but rather, allows you to apply the preconfigured settings to the site(s).

Define the structure of the RecoverPoint/SE installation and the site settings (Figure 36).
Installation Structure
◆ Number of sites — The number of sites for this deployment:
• One site — Continuous Data Protection (CDP) at a single site
• Two sites — Continuous Remote Replication (CRR), Concurrent Local and Remote
data protection (CLR), or CDP on two sites.
◆ Number of RPAs per site — 2-8
To install more than two RPAs per site, RecoverPoint/SE 3.3 SP1 or later must be
The IP version used to link the RPAs to the WAN interface.
• Private for one site configuration and two site configuration over FC.
• WAN for two site configuration over IP.
◆ Remote replication to be done over — The protocol used for replication between sites.
• IP — Replication using Internet Protocol (IP).
• Fibre Channel — Replication using Fibre Channel (FC).
If there is IP connectivity between the two sites, select the Allow communication
between the two sites over standard IP for control and time synchronization
purposes checkbox. This option enables extraction of all the system logs from a
single site and enables a centralized NTP server for both sites.
Note: When selecting this option, you must manually zone all site RPAs.
Site Settings (1 or 2 sites)

◆ Site name — Name of the site for this deployment.
◆ Time zone — The time zone for the site.

◆ Management IP type — Determine whether any of the site IP addresses use IPv4, IPv6,
or both IPv4 and IPv6.
◆ Domain name (optional) — The site domain name.
◆ Primary DNS server (optional) — The IP address of the primary DNS server for the site.
site.
◆ NTP Server 1 (optional) — The IP address of NTP server 1 for the site.
You can define one or two external NTP servers for the RecoverPoint/SE configuration;
two NTP servers provide greater time accuracy. If you are installing two sites, you can
define the NTP server on only one of the sites. Therefore, once you select a site that
will be synchronized with the external NTP server, the other RPAs in the configuration
will synchronize time with the NTP server settings. Though not mandatory, it is highly
recommended to set at least one NTP server, as it will ensure that all RecoverPoint/SE
components are synchronized with an external NTP source.
Figure 36 Environment screen
Sites
Site1Name RPA Discovery

The following options are provided (Figure 37):


In the Discover uninstalled RecoverPoint Appliances (RPAs) section, when you click
Discover, you can choose how Deployment Manager discovers the RPAs and get their
currently set IP addresses:
RPAs.
• Run discovery from an RPA — The installer tries to discover all unattached RPAs
Next.
Figure 37 Sites - Site1Name RPA Discovery
Site1Name IP settings
Define the site IP configurations and the RPA IP settings (Figure 38).
Settings (Either Private or WAN, IPv4 or IPv6)
These IP settings must be entered for site control purposes.
◆ Subnet mask
◆ Gateway (optional)
Management settings (Either IPv4, IPv6, or both IPv4 and IPv6)

◆ Subnet mask
◆ Default gateway
◆ Site management IP - A virtual IP address that is used to configure the RPA cluster at a
site as a whole. This IP address is assigned to the RPA that is currently running the
active instance of the site management.
RPAs IP settings (All RPAs must be on the same network, per site)
◆ Management IP address for each new RPA
◆ WAN or Private IP address for each new RPA
◆ MTU (do not modify unless instructed to do so)
Note: The order of IPs assigned to RPAs is significant. If you define an RPA number with an
IP address, the physical RPA with this IP address becomes the RPA number in the cluster.
Figure 38 Sites - Site1Name IP settings

This section appears only for a two-site installation.
Refer to “Site1Name RPA Discovery” on page 69 for details.
Refer to “Site1Name IP settings” on page 70 for details.
Apply configuration
Enter RecoverPoint Appliance login credentials and determine which site to install now
(Figure 39).
RecoverPoint Appliance Login Credentials
The system prompts you to enter your RecoverPoint Appliance login information. For
username boxmgmt, the default password is boxmgmt.

Apply Configuration
Which site do you want to install now? — The system allows a two-step installation when
deploying RecoverPoint/SE on two sites. If you want to phase the installation by applying
the settings to only one of the sites, choose the site to which you want to apply the
settings. If you have already installed one of the sites, choose the site you want to install
now and select the Other site already installed checkbox.
The following options are available:
◆ Site1Name and Site2Name – Applies settings to both sites.
To apply at both sites:
• The RPAs at both sites must be physically installed.
• Management IP addresses must be assigned.
• Networking requirements must be met.
◆ Site1Name – Applies the settings to site 1 only. To complete the installation, you must
continue the installation at site 2 using the saved configuration file.
◆ Site2Name – Applies settings to site 2 only. To complete the installation, you must
Apply
Note: This screen step appears as Upgrade and apply if you selected the checkbox in the
screen “Apply configuration” on page 71.
The system attempts to log in to each of the RPAs and validate system information.
The system presents the following results: Status, RPA, Site name, RPA IP address, Gen
(RPA hardware platform), and Comment (if applicable).


Note: This screen step appears if you did not select the checkbox in the screen “Apply
configuration” on page 71.
Figure 41 Apply configuration results screen

Enter ISO file information to download the ISO file(s) to the RPAs. Select a download
source and enter ISO file name.
Note: This screen step appears only if you selected the checkbox in the screen “Apply

There are three options to download the ISO files to the RPAs (in Figure 42, Upload from
local machine is selected):
Note: When installing RPAs running releases earlier than 3.5, “Download from FTP server”
is the only available option for ISO file downloads. When installing RPAs running 3.5 or
later releases, all three options are available.

(Only available when installing RPAs already running 3.5 or later)

click Next.

Enter FTP credentials of an FTP server or servers where the RecoverPoint 3.2 or later ISO file
is located to download it to the RPAs.
Note: If upgrading a two-site setup, it is recommended to download the ISO file from two
local FTP servers (one FTP server at each site). This operation may significantly reduce the
ISO file download time.
Enable FTP credentials (per site, if relevant):

◆ Username
◆ Password

_emc_md5_e11ce8b9190e Once all information has been entered, click Next to begin the download and distribution
8788daeb2e7bfe82b2c6.is of the ISO file(s) to the RPAs.
o
Figure 42 ISO file information screen

Review the results of applying the configuration settings to all RPAs in the environment (in
Figure 42, the screen displayed is that when you did not select “Apply configuration” on
page 71).
If you selected the checkbox in the screen “Apply configuration” on page 71, the screen
displays the filename of the ISO file that you applied to the RPAs, and the distribution
option that you selected (appears in brackets beside the site name).The system
communicates and validates the statuses of the RPAs and confirms that all components
are OK or that errors are detected.

Storage Configuration - Site1Name - VNX/CLARiiON login credentials

Enter the login credentials for the VNX/CLARiiON storage system at the site (Figure 24).
Unisphere/Navisphere login credentials:
◆ Array SP A IP — Enter the IP address of array SP A at the site.
◆ Array SP B IP — Enter the IP address of array SP B at the site.
◆ EMC Unisphere/Navisphere username — Enter the Unisphere/Navisphere username
at the site. Default value is admin.
◆ EMC Unisphere/Navisphere password — Enter the Unisphere password at the site.
◆ Authentication scope — Select whether the scope of the user account is Global, Local,
scope.
Figure 44 Storage configuration - Site1Name - VNX/CLARiiON login credentials screen
Storage Configuration - Site1Name - VNX/CLARiiON login status

◆ The RecoverPoint/SE Installer can communicate with VNX/CLARiiON SP A and SP B.
When all statuses appear OK, click Next to continue.

Figure 45 Storage configuration - Site1Name - VNX/CLARiiON login status screen
Storage Configuration - Site1Name - Zoning

Select how you want to perform zoning (In Figure 29, automatic zoning is selected).
Note: For RecoverPoint/SE releases earlier than 3.4, it is recommended that you create
zones manually, rather than using the automatic or semi-automatic zoning options.
◆ Automatic - The Installer zones the RPAs and the VNX/CLARiiON arrays automatically.
For details, see “Zoning: Automatic” on page 78.
apply them yourself. For details, see “Zoning: Semi-automatic” on page 78.
◆ Manual - The Installer indicates which ports should be zoned together, and you are
responsible for actually creating the zones. For details, see “Zoning: Manual” on
page 78.
◆ Direct-attach Storage - The Installer verifies that, in this switchless configuration, each
RPA is directly connected to SP A and SP B of the VNX/CLARiiON array. For details, see
“Zoning: Direct-attach Storage” on page 79.
Note: If installing RecoverPoint 3.3 SP2 and later, and the RPAs are directly attached to
the VNX/CLARiiON arrays, then the wizard automatically skips this screen and
continues to “Storage Configuration - Site1Name - SAN Diagnostics” on page 80.

Zoning: Automatic
zoning.
Enter the following details for each fabric:
◆ IP address of the fabric switch at the site
◆ Username for the fabric switch at the site
◆ Password for the fabric switch at the site
The Installer automatically creates an RPA-to-storage zone for each RPA at this site, where
each zone includes:
Semi-automatic zoning is available for Brocade and Cisco fabric switches.
For RecoverPoint 3.4 and later, to use semi-automatic zoning, you must first enter the
switch credentials, just as for automatic zoning.
Whether you have entered switch credentials (RecoverPoint/SE 3.4, or later) or not (earlier
than RecoverPoint/SE 3.4), in semi-automatic zoning, the system does not automatically
configure the zoning on the switch.
Zoning: Manual
Zone and mask LUNs using the RPA port WWNs displayed in the RPAs WWNs table(s), and
To create the RPA-to-storage zones at this site, use the following procedure:

2. At each site, on each fabric, create an RPA-to-RPA zone containing all local RPA HBAs
that are not used in RPA-to-storage zones (best practice). This zone provides an
additional communication link between RPAs. It can also be used for synchronous
replication of distributed consistency groups. If replicating over Fibre Channel, merge
the RPA-to-RPA zones at each site into one.
3. For synchronous or remote replication over Fibre Channel:
• Zone local and remote RPAs together.
• Use dedicated HBA ports (best practice).

array.
This option is available only when installing RecoverPoint/SE 3.3 SP1 and later service
pack and patch releases, and all releases of RecoverPoint 3.4 and later.
Figure 46 Storage configuration - Site1Name - Zoning

Storage Configuration - Site1Name - SAN Diagnostics

configuration is appropriate for the RPA, and that RecoverPoint/SE can successfully
Figure 47 Storage configuration - Site1Name - SAN diagnostics
Storage Configuration - Site1Name - Repository volume

Determine how you want the repository volume to be selected (Figure 29).
Automatic - The Installer automatically creates and configures a repository volume.
Manual - The Installer lists possible volumes, and you can select the one to be configured
as the repository volume.
Figure 48 Storage configuration - Site1Name - Repository volume

Storage configuration - Site2Name - VNX/CLARiiON login credentials

Refer to “Storage Configuration - Site1Name - VNX/CLARiiON login credentials” on
page 76 for details.
Storage configuration - Site2Name - VNX/CLARiiON login status

Refer to “Storage Configuration - Site1Name - VNX/CLARiiON login status” on page 76 for
details.
Storage configuration - Site2Name - Zoning

Refer to “Storage Configuration - Site1Name - Zoning” on page 77 for details.
Storage configuration - Site2Name - SAN Diagnostics

Refer to “Storage Configuration - Site1Name - SAN Diagnostics” on page 80 for details.
Storage Configuration - Apply configuration

Wait for the configuration to be applied. (In Figure 30, a two-site installation configuration
is applied.)
The steps involved are:
◆ Configuring VNX/CLARiiON array
• Creating internal VNX/CLARiiON storage groups
• Registering RPA WWNs on VNX/CLARiiON array
◆ Configuring RPAs
• Creating repository volume
• Configuring repository volume
◆ Finishing the installation
• Attaching RPAs to cluster
• Waiting for RPAs to come up after reboots
or that errors are detected. If errors are detected, you can click the error to display details.
resolved, click Retry to reapply settings and revalidate that the RPA installation is
successful.

Figure 49 Storage configuration - Apply configuration
Summary
The summary screen presents a summary of site configurations. For a two-site installation,
tabs are available for each site, and can be clicked to display the relevant site information
(In Figure 31, a two-site installation is displayed, as indicated by the two tabs).
◆ Paths from RPAs — Port, WWN, Controller, Serial number, LUN.
◆ Zoning - The zoning information for Fabric A and Fabric B.
◆ Storage Groups - The RecoverPoint/SE storage group created.
Note: A RecoverPoint storage group contains all the VNX/CLARiiON LUNs that
RecoverPoint/SE replicates. Do not change the name of the storage group, or
RecoverPoint/SE may fail to function properly.
Installation complete at one or two sites

Once you have successfully completed the RecoverPoint/SE installation (at all sites), you
can start managing the RecoverPoint/SE system using the RecoverPoint Management
Application. To do so, click the site management IP address displayed.
The wizard closes and the RecoverPoint Management Application opens. Once open, the
Getting Started Wizard appears. For further information, refer to the “Getting Started
Wizard” section of the EMC RecoverPoint Administrator’s Guide.
Installation complete at two sites, but only applied at one site

If you have completed installation of two sites, but only applied the configuration to one of
them, you must complete the following installation steps:
1. Have the saved configuration file (as described in “Configuration file” on page 67)
available at the other site.
2. Launch Deployment Manager at the other site.
3. On the login screen, select Other operations (EMC personnel) and enter your

4. On the wizard selection screen, select RecoverPoint/SE Installer Wizard.

5. Select the I have fulfilled the conditions for installing my environment checkbox, if
true, and click Next.
6. On the Configuration file screen:
• Select Create or continue an installation from a saved configuration file and open
the file.
• Select the Skip to step Apply Configuration (if a site has already been installed)
checkbox.
Note: The system does not allow you to change any site settings, but rather apply
the preconfigured settings to the site(s).
7. On the Apply Configuration screen:

• Enter RecoverPoint Appliance login credentials.
• Determine which site to install now.
• Select the Other site already installed checkbox.
8. The applied settings are loaded and allow you to complete the installation. Complete
the wizard as detailed in the relevant sections above.
Figure 50 Summary screen

After installing a RecoverPoint/SE system, you must complete the RecoverPoint
(http://support.emc.com), click “Support by Product”, type “RecoverPoint SE” in the “Find
a Product” search field. On the “RecoverPoint SE” page, click “Documentation” and

CHAPTER 4
RecoverPoint Installation
This chapter explains how to install RecoverPoint RPA clusters using RecoverPoint
Deployment Manager 2.0 SP1. Instructions are provided in the following procedures:
◆ RecoverPoint Installer Wizard .................................................................................. 86
◆ RecoverPoint 4.0 or later ......................................................................................... 88
◆ RecoverPoint 3.5 or earlier .................................................................................... 109
RecoverPoint Installation 85
RecoverPoint Installer Wizard

The RecoverPoint Installer Wizard is a graphical user interface (GUI) wizard that helps you
install a new RecoverPoint RPA cluster (site) from a single management point. Once
completing the wizard, you will be able to use Unisphere for RecoverPoint (the name, as of
4.0, of the RecoverPoint Management Application GUI).
IMPORTANT
The RecoverPoint Installer Wizard is used to install RecoverPoint. To install
RecoverPoint/SE, refer to “RecoverPoint/SE Installation” on page 37.
About the RecoverPoint Installer Wizard

As of RecoverPoint 4.0, the Installer Wizard allows you to install one RPA cluster at a time.
Therefore, if you plan to deploy multiple clusters, you must run the Installer Wizard as
many times as there are clusters.
Once done installing the clusters, to enable replication and communication between
them, you must run the Connect Cluster Wizard. “Cluster Connection” on page 127
contains information about this wizard.
Launch RecoverPoint Installer Wizard

To launch the RecoverPoint Installer Wizard:
to the internet.
newer release is available for download from EMC Online Support site.
with the option to download it and use it now.
step 1 on page 86.

Figure 51 Check for newer release screen
from, or maintain (such as add an RPA to a cluster). (Figure 52)
• If you select RecoverPoint 4.0 or later releases, continue from “RecoverPoint 4.0 or
• If you select RecoverPoint 3.5 or earlier releases, continue from “RecoverPoint 3.5
or earlier” on page 109.
Figure 52 Select RecoverPoint release screen
RecoverPoint Installer Wizard 87


Starting in RecoverPoint 4.0, RecoverPoint clusters are installed at a time.
Furthermore, a RecoverPoint system can contain between two and five clusters. As such,
the RecoverPoint Installer Wizard needs to be run once for every cluster in the setup. Once
installs are completed, the Connect Cluster Wizard must be run to connect the clusters in
the setup. “Cluster Connection” on page 127 contains information about this procedure.
Access the Wizard

Follow these steps to access the RecoverPoint Installer Wizard:
1. On the login screen (Figure 53), select Other operations (EMC personnel) and enter
your RecoverPoint login credentials (CLI).

2. On the wizard selection screen, select RecoverPoint Installer Wizard (Figure 54).
Prerequisites
Before continuing, ensure the following conditions are met on the RecoverPoint cluster
◆ RPAs are connected to SAN and Ethernet networks
◆ RPAs are loaded with the same RecoverPoint ISO image
◆ RPAs are set with IP addresses (optional if the environment includes a DHCP server)
◆ RPAs are either all physical RPAs or all virtual RPAs
◆ If installing physical RPAs:
• RPAs are rack mounted

◆ If installing virtual RPAs:

• Virtual RPAs are deployed using the RecoverPoint OVF package
• VNX arrays are running OE for Block version later than 05.32.000.5.201
• VNX arrays are pre-configured with iSCSI ports
• VMware vCenter Server is 5.0 or later, with at least one registered vSphere 5.0 or
later
• Valid segmented network infrastructure between:
– The vSphere host and the VNX array (iSCSI 1G/10G)
– The vSphere host and the existing RPA cluster networks (LAN and WAN)
• Reserved quota is required for virtual system resources: CPU, memory, disk
• At least three virtual networks are required: LAN, WAN, and iSCSI
• If planning to configure CHAP credentials:
– CHAP credentials for RPA iSCSI ports and storage iSCSI ports must be different
– CHAP credentials for storage iSCSI ports must be identical on the VNX array
ports
• Connection sets have been configured between the VNX iSCSI ports and virtual
RPAs
Select the I have fulfilled the conditions for installing the RecoverPoint cluster checkbox
and click Next to continue.

Configuration file
The RecoverPoint Installer allows you to select one of two installation modes (Figure 56):
the installation.
location is C:\Users\ <username>\RecoverPoint\ RPI_config.properties.
Note: To modify the system settings of an existing RecoverPoint RPA cluster, use the
Cluster Modification Wizard.

Define the RecoverPoint cluster settings (Figure 57).
General
◆ Cluster name — Name of the cluster being installed.
◆ Number of RPAs — A cluster can have between 2 to 8 RPAs.
Connectivity
◆ For LAN:
• IP type — IPv4, IPv6, or IPv4 and IPv6.
◆ For WAN:
• IP type — IPv4 or IPv6.
Environment
◆ Domain name (optional) — The cluster domain name.
◆ Primary DNS server (optional) — IP address of the primary DNS server for the cluster.
◆ Secondary DNS server (optional) — IP address of the secondary DNS server for the
cluster.
◆ NTP server (optional) — IP address of NTP server for the cluster.
◆ Secondary NTP servers — IP addresses of additional NTP servers for the cluster.
Cannot be modified.
Advanced settings
RPAs should expose additional virtual WWNs (optional) — Select this checkbox if you are
replicating a non-EMC storage array that does not allow sharing of WWNs between storage
groups. Once selected, you must define the number of virtual WWNs the RPA should
expose to the non-EMC storage array. RecoverPoint supports up to 32 storage groups in
this configuration, with a dedicated virtual WWN for each storage group.

RPA discovery
RPAs and get their currently set IP addresses:
RPAs.

Next.
Figure 58 RPA discovery screen

Define the cluster IP configurations and set the RPA IP settings (Figure 59).
Cluster management — LAN, based on IP type entered in “Environment settings” on
page 92. A virtual IP address that is used to configure the RPA cluster. The IP address is
assigned to the RPA that is currently running the active instance of the cluster
management.
page 92.
RPA — IP addresses of the cluster RPAs, based on IP type entered in “Environment
settings” on page 92.
recommended to assign RPA 1 and RPA 2 (cluster control RPAs) to the latest hardware
types (Gen5), to improve system function and performance.
Gateways configuration
Default gateway — Based on IP type entered in “Environment settings” on page 92.


Login credentials
Enter the default RecoverPoint login credentials (Figure 60).
RecoverPoint Login Credentials

The system presents the following results: Status, RPA, Cluster name, RPA LAN IP address,
RPA hardware platform, RecoverPoint release, and Comment (if applicable).

Define the RPA cluster iSCSI settings (Figure 62).
Connectivity
For iSCSI 1
For iSCSI 2

Figure 62 Cluster iSCSI Settings screen
RPA iSCSI ports

page 92.
IMPORTANT
It is strongly recommended to put the iSCSI interface on a different subnet than the LAN
and WAN interface, to avoid iSCSI communication errors.
Default gateways
Additional gateways


The RecoverPoint release running on the RPAs is displayed (the ISO image that comes
pre-installed on the RPAs). To ensure the RPAs are running the latest RecoverPoint release,
you should update them now.
IMPORTANT
Upgrading the RecoverPoint release now saves you from having to run the Upgrade RPAs
Wizard after installation to upgrade the RecoverPoint software running on the RPAs.
Update options
◆ Update with an ISO image available from EMC Online Support site (recommended)
(login credentials required). When you select this option, you continue to “ISO image
download details” on page 99.
Note: This option is grayed out if no ISO image is found on EMC Online Support.
◆ Update with an ISO image available locally

Select this option if you have an ISO image on your local machine, a DVD, a USB
device, or an FTP server. When you select this option, you continue to “ISO file
◆ Do not update. Continue with current RecoverPoint release on RPAs
Select this option to continue installing the RPAs without upgrading the ISO image
running on the RPAs.

ISO settings

This screen appears only if you selected “Update with an ISO image available from EMC
Online Support site (recommended)” on page 98.
Provide EMC Online Support site credentials, choose the desired ISO image and define
where to save it (Figure 65).

Enter your username and password. Without these credentials, you cannot use this option
to update the RecoverPoint release running on the RPAs you are installing.
RecoverPoint ISO image download details

Release — Deployment Manager connects to EMC Online Support site and presents all
valid ISO images (releases) that you can download and apply to the cluster you are
installing.
Target folder — Select a location on your local machine (the machine running Deployment
Manager) to where you want to save the ISO image, or click Browse to select an alternate
location.


This screen appears only if you selected “Update with an ISO image available locally” on
page 98.


click Next.

Enter FTP credentials of an FTP server or servers where the RecoverPoint ISO file is located
to download it to the RPAs.

Enter the FTP server details and ISO file information:

◆ Username
◆ Password
_emc_md5_11ce8b9190e8
788daeb2e7bfe82b2c6.iso

This screen appears only if you selected “Download from FTP server” on page 100.
Review the status of the FTP connectivity results.
When all statuses appear OK (green check mark), click Next to begin the download and
distribution of the ISO file(s) to the RPAs.


This screen step appears if you selected the Do not update. Continue with current
RecoverPoint release on RPAs option in “Update RecoverPoint release” on page 98.
The system attempts to log in to each of the RPAs and validate system information. The
results of applying the configuration settings to all RPAs are displayed (Figure 67). Once
installation has completed successfully, click Next.
Upgrade and Apply configuration results

This screen step appears if you selected the Update with an ISO image available locally
option in “Update RecoverPoint release” on page 98.
Review the results of applying the configuration settings to all RPAs in the system
(Figure 68).
The screen displays the filename of the ISO file that you applied to the RPAs, and the
distribution option that you selected.
Figure 68 Upgrade and Apply configuration results screen

Storage iSCSI ports

you continue to “Apply iSCSI configuration results” on page 104. If you are installing a
physical RPA cluster, continue to “Zoning and LUN masking” on page 105.
One or more iSCSI array configurations can be configured (Figure 69).
Click Add array to enter settings.
In the Storage iSCSI settings dialog box, enter the following information (Figure 70):
◆ Array name — Name of the array in the RecoverPoint system.
◆ CHAP credentials — The current storage CHAP and iSCSI IP configurations are
displayed. Modify the values you want to change (username and password).
◆ Storage iSCSI IP addresses — Number of ports — 2-10. Increasing the number of ports
requires you to enter corresponding storage iSCSI IP addresses.
Figure 69 Storage iSCSI Ports screen

Figure 70 Storage iSCSI settings dialog box
Apply iSCSI configuration results

Figure 71 Apply iSCSI configuration results screen
RPA iSCSI Qualified Names

After completing this screen, continue to “SAN diagnostics” on page 106.
Use the RPA iSCSI Qualified Names (IQNs) shown to register the new virtual RPA initiators
in the VNX array and to perform LUN masking (Figure 72). The system displays the RPA
number, IQNs, and iSCSI IP addresses of each RPA.
IMPORTANT
If you configured storage CHAP credentials in “Storage iSCSI ports” on page 103, you must
use the displayed IQNs, along with the storage CHAP credentials, to create a new CHAP
entry in the VNX array.
The information presented onscreen can be exported for further use by clicking the Export
to CSV file button.

Figure 72 RPA iSCSI Qualified Names screen
Zoning and LUN masking

The system displays the port numbers, port WWNs, and node WWNs of each RPA HBA at
the site (Figure 73). Use this information to zone and mask LUNs for the RPAs.
to CSV file button.
Figure 73 Zoning and LUN masking screen

SAN diagnostics
The system performs SAN diagnostics for the cluster, attempting to validate that the
current configuration is appropriate for the RPA and that RecoverPoint can successfully
Repository volume
As part of the installation process, you must create a repository volume from one of the
storage array LUNs (Figure 75). The repository volume holds RecoverPoint configuration
data that is created in the replication process.
LUNs presented in the table can be chosen as a repository volume and by definition must:
◆ Reside in a storage environment that guarantees high availability.
◆ Be 5.72 GB in size; capacity beyond 5.72 GB is not used.
◆ Be provisioned on a non-thin LUN, except on the VMAX10K array where a thin LUN
must be used, and on the VNX/CLARiiON array where a thin LUN may be used.
◆ Be accessible to all RPAs at the site.
IMPORTANT
Since the RPA formats (clears) the selected LUN, you should ensure that the LUN is new
and does not contain any valuable data.

Figure 75 Repository volume screen
Cluster summary
The general details of the selected volume are displayed (Figure 76). If you wish to change
the selected volume, click Back and select a different volume.
The system communicates with each RPA and performs the following steps:
◆ Applies settings per RPA.
◆ Selects and formats the repository volume.
◆ Attaches each RPA to the cluster.
◆ Reboots each RPA.
Figure 76 Cluster summary screen

Summary
You have successfully completed the RecoverPoint installation. To start managing the
RecoverPoint system, select the Open Unisphere for RecoverPoint now at for cluster
checkbox and click Finish (Figure 77).
Once you open Unisphere for RecoverPoint, you are asked for a license key. For further
information, refer to the “Managing RecoverPoint licenses” section of the EMC
RecoverPoint Administrator’s Guide.
IMPORTANT
If you plan to replicate to remote RecoverPoint RPA clusters, you must connect this cluster
to the remote clusters using the Connect Cluster Wizard, as documented in “Connect
Cluster Wizard” on page 128.
After installing a RecoverPoint system, you must complete the RecoverPoint
(http://support.emc.com), click “Support by Product”, type “RecoverPoint CL” in the “Find
a Product” search field. On the “RecoverPoint CL” page, click “Documentation” and


Access the Wizard
Follow these steps to access the RecoverPoint Installer Wizard.
2. On the wizard selection screen, select RecoverPoint Installer Wizard (Figure 54).

1 Prerequisites
◆ RPAs are rack mounted.
◆ RPAs are connected to SAN and Ethernet networks.
◆ RPAs are loaded with the same RecoverPoint ISO image.
Important: If installing 3.5 or later, all RPAs must be Gen4 RPAs or later.
◆ RPAs are set with IP addresses (optional if installing 3.5 and later and the environment
includes a DHCP server).
◆ An RPA is connected to your installation station.
Select the I have fulfilled the conditions for installing RecoverPoint checkbox and click
Next to continue.
Configuration file
The RecoverPoint Installer allows you to select one of two installation modes (Figure 56):
the installation.
location is C:\Users\ <username>\RecoverPoint\RPI_config.properties.

• If using the file to continue a RecoverPoint installation, after having already
installed the settings to a first or second site or both, this operation allows you to
complete the installation of the site(s) and apply the settings. To perform this step,
browse and select the file and select the Skip to step Apply Configuration (if a site
has already been installed) checkbox.
Note: When selecting this mode, the system does not allow you to change any site
settings but rather apply the preconfigured settings to the site(s).
Note: You cannot use the Installer to change the settings of an installed RPA.
Define the structure of the RecoverPoint installation and the site settings (Figure 82).
• 1 site — Continuous Data Protection (CDP) at a single site
• 2 sites — Continuous Remote Replication (CRR), Concurrent Local and Remote
(CLR) data protection, or CDP on two sites.
◆ Number of RPAs per site — A site can have between 2 to 8 RPAs. The number of RPAs
must be equal at both sites.
• Private for one site installation.
• WAN for two site installation.

Note: When selecting this option, you must manually zone all site RPAs.

site.
You can define one or two external NTP servers for the RecoverPoint configuration; two
NTP servers provide greater time accuracy. If you are installing two sites, you can
will synchronize with the RPA with the NTP server settings. Though not mandatory, it is
highly recommended to set at least one NTP server, as it will ensure that all
RecoverPoint components are synchronized with an external NTP source.

Sites


RPAs and get their currently set IP addresses:
RPAs.
Next.
Figure 83 Sites - Site1Name RPA Discovery

Define the site IP configurations and the RPA IP settings (Figure 59).
Settings (Either Private or WAN, IPv4 or IPv6)
◆ Subnet mask
Site1Name Management Settings (Either IPv4, IPv6, or both IPv4 and IPv6)
◆ Subnet mask
◆ Default gateway
◆ Site management IP- A virtual IP address that is used to configure the RPA cluster at a
site as a whole. This IP address is assigned to the RPA that is currently running the
active instance of the site management.
Site1Name RPAs IP settings (All RPA must be on the same network, per site)
◆ Management IP address for each new RPA
◆ WAN or Private IP address for each new RPA
◆ MTU (do not modify unless instructed to do so)
Figure 84 Sites - Site1Name IP settings
Site1Name advanced settings

Define the advanced configuration, if relevant (Figure 85).
RecoverPoint allows you to define advanced settings for unique installations. Use the
Advanced Mode for the following use cases:
◆ If you are replicating VMware volumes with splitters running on the virtual machines.

If you respond Yes, you must specify the largest number of VMware virtual machines
that will be running on any one ESX server at this site. Refer to the EMC RecoverPoint
Replicating VMware Technical Notes for instructions on how to count the number of
paths accurately.
If you set the number too low, you will not be able to create all the replication paths
you need. If you set it too high, you may trigger unnecessary system discovery, which
may affect system performance.
◆ If you are replicating a single VNX/CLARiiON storage array with more than 256 LUNs
being presented to the RPA.
If you respond Yes, you must define the number of virtual WWNs the RPA should
expose to the VNX/CLARiiON array.
Since an RPA must be placed within a VNX/CLARiiON storage group, and each storage
group can contain up to 256 LUNs, to allow an RPA to access more than 256 LUNs per
VNX/CLARiiON array, you must increase the number of virtual WWNs that the RPA
exposes in the SAN per physical HBA port.
Once you have increased the number of virtual WWNs, you can map each virtual WWN
into a different storage group, therefore assigning more than 256 LUNs per RPA.
◆ If you are replicating a non-EMC storage array that does not allow sharing of WWNs
between storage groups.
If you respond Yes, you must define the number of virtual WWNs the RPA should
expose to the non-EMC storage array.
Since some storage arrays cannot share LUNs between storage groups and cannot
share initiator WWNs between storage groups, to allow support of multiple storage
groups an RPA must present more initiators in the SAN and assign initiators to
different storage groups.
To support this situation, RecoverPoint supports up to 32 storage groups in this
configuration, with a dedicated virtual WWN for each storage group.
◆ If you are replicating a non-EMC storage array that is not compatible with RPA HBA
ports that operate in both initiator and target mode.
If you select Yes for each site that requires this support, the RPA will set the odd HBA
ports to act as initiator only, and set the even HBA ports to act as both initiator and
target. Map only the RPA HBA ports that act as initiator only to the storage arrays.
By default, RPA ports operate as both initiator and target ports, as an RPA must access
both storage data (as initiator) and receive splitting information from the various
splitters (as target). Some storage arrays prevent LUN masking if a WWN operates as
both an initiator and a target.
If none of the above cases apply to your deployment, skip to the Next step.

Figure 85 Sites - Site1Name advanced settings

Refer to “Site1Name RPA Discovery” on page 113 for details.
Site2Name advanced settings

Refer to “Site1Name advanced settings” on page 114 for details.
Apply configuration
Enter RecoverPoint login credentials and determine which site to install now (Figure 64).
RecoverPoint Login Credentials
Apply Configuration
Which site do you want to install now? — The system allows a two-step installation when
deploying RecoverPoint on two sites. If you want to phase the installation by applying the
settings to only one of the sites, choose the site to which you want to apply the settings. If
you have already installed one of the sites, choose the site you want to install now and
select the Other site already installed checkbox.


◆ Site1Name and Site2Name – Applies settings to both sites.
To apply at both sites:
• The RPAs at both sites must be physically installed.
• Management IP addresses must be assigned.
• Networking requirements must be met.
◆ Site1Name – Applies the settings to site 1 only. To complete the installation, you must
◆ Site2Name – Applies settings to site 2 only. To complete the installation, you must
RPA Release
Select Do you want to apply a newer ISO? checkbox if you want to upgrade the
RecoverPoint ISO file that comes preinstalled on the RPA cluster(s). This upgrade option is
beneficial if the ISO file on the RPA cluster(s) is an older release than what you want to
install now.
Note: You must have the ISO file available to continue with this option.
IMPORTANT
Upgrading the file in this wizard saves you from having to run the Upgrade RPAs Wizard
after completing the installation.

Apply
This screen step appears as Upgrade and apply if you selected the checkbox in the screen
“Apply configuration” on page 116.
The system attempts to log in to each of the RPAs and validate system information.
The system presents the following results: Status, RPA, Site name, RPA IP address, Gen
(RPA hardware platform), and Comment (if applicable).

Note: This screen step appears if you did not select the checkbox in the screen “Apply

Note: This screen step appears only if you selected the checkbox in the previous screen
(“Apply configuration” on page 116).
Note: When installing RPAs running releases earlier than 3.5, “Download from FTP server”
is the only available option for ISO file downloads. When installing RPAs running 3.5 or


Select the I have a DVD/USB inserted of all the RPAs checkbox if you want Deployment
click Next.

Enter FTP credentials of an FTP server or servers where the RecoverPoint 3.2 or later ISO file
is located to download it to the RPAs.


◆ Server IP address.
◆ Server port number to connect on FTP server (default is 21).
◆ Username.
◆ Password.
Example: /files/folder3 ◆ File location (location of ISO file on the FTP server).
Example: ◆ File name (name of the ISO file on the FTP server).
_emc_md5_e11ce8b9190e Once all information has been entered, click Next to begin the download and distribution
8788daeb2e7bfe82b2c6.is of the ISO file(s) to the RPAs.
o

Review the results of applying the configuration settings to all RPAs in the environment (in
Figure 90, the screen displayed is that when you did not select “Apply configuration” on
page 116).
Note: If you selected the checkbox in the screen “Apply configuration” on page 116, the
screen displays the filename of the ISO file that you applied to the RPAs, and the
distribution option that you selected (appears in brackets beside the site name).

Storage configuration - Site1Name - Zoning and LUN masking

The system displays the port numbers, port WWNs, and node WWNs of each RPA HBA at
the site (Figure 73). Use this information to zone and mask LUNs for the RPAs.
to CSV file button.
Figure 91 Storage configuration - Site1Name - Zoning and LUN masking screen
Storage configuration - Site1Name - SAN diagnostics

configuration is appropriate for the RPA and that RecoverPoint can successfully operate in
the current SAN environment.
If errors or warnings are found, the system presents the following results: Severity, RPA,
Message ID, Category, and Description. If no errors or warnings are found, the screen
displays a green check mark, indicating that the test completed successfully (Figure 74).

Figure 92 Storage configuration - Site1Name - SAN diagnostics screen
Storage configuration - Site1Name - Repository volume

As part of the installation process, you must create a repository volume from one of the
storage array LUNs (Figure 75). The repository volume holds RecoverPoint configuration
data that is created in the replication process.
LUNs presented in the table can be chosen as a repository volume and by definition must:
◆ Reside in a storage environment that guarantees high availability.
◆ When installing:
• RecoverPoint 3.3.x and earlier: Size should be 2.86 GB; capacity beyond 2.86 GB
is not used.
• RecoverPoint 3.4.x and later: Size should be 5.72 GB; capacity beyond 5.72 GB is
not used.
◆ Be provisioned on a non-thin LUN, except on the VMAX10K array where a thin LUN
must be used, and on the VNX/CLARiiON array where a thin LUN may be used.
◆ Be accessible to all RPAs at the site.
IMPORTANT
Since the RPA formats (clears) the selected LUN, you should ensure that the LUN is new
and does not contain any valuable data.

Figure 93 Storage configuration - Site1Name - Repository volume screen
Storage configuration - Site1Name - Site summary

The general details of the selected volume are displayed (Figure 76). If you wish to change
the selected volume, click Back and select a different volume.
The system communicates with each RPA and performs the following steps:
◆ Applies settings per RPA.
◆ Selects and formats the repository volume.
◆ Attaches each RPA to the cluster.
◆ Reboots each RPA.
Figure 94 Storage configuration - Site1Name - Site summary screen

Storage configuration - Site2Name - Zoning and LUN masking

Refer to “Storage configuration - Site1Name - Zoning and LUN masking” on page 121 for
details.
Storage configuration - Site2Name - SAN diagnostics

Refer to “Storage configuration - Site1Name - SAN diagnostics” on page 121 for details.
Storage configuration - Site2Name - Repository volume

Refer to “Storage configuration - Site1Name - Repository volume” on page 122 for details.
Storage configuration - Site2Name - Site summary

Refer to “Storage configuration - Site1Name - Site summary” on page 123 for details.
Summary
The final step of the RecoverPoint Installer depends on whether you have performed one
of the following:
◆ Installation complete of one or two sites.
◆ Installation complete of two sites, but only applied on one site.
Installation complete of one or two sites

You have successfully completed the RecoverPoint installation. To start managing the
RecoverPoint system, select the Open RecoverPoint Management Application now at site
checkbox, select a site management IP address, and click Finish (Figure 77).
The wizard closes and the RecoverPoint Management Application opens. Once open, a
pop-up box asks you for a license key. For further information, refer to the “Managing
RecoverPoint licenses” section of the EMC RecoverPoint Administrator’s Guide.
Installation complete of two sites, but only applied on one site

You have partially completed the RecoverPoint installation. Both sites have been installed,
but the configuration has been applied to only one site.
To complete the RecoverPoint installation:
1. Have the saved configuration file (as described in “Configuration file” on page 110)
available at the other site.
2. Launch Deployment Manager at the other site.
3. On the login screen, select Other operations (EMC personnel) and enter your

4. On the wizard selection screen, select RecoverPoint Installer Wizard.

5. Select the I have fulfilled the conditions for installing RecoverPoint checkbox, if true,
and click Next.
6. On the Configuration file screen:
• Select Create or continue an installation from a saved configuration file and open
the file.
• Select the Skip to step Apply Configuration (if a site has already been installed)
checkbox.
Note: The system does not allow you to change any site settings, but rather apply
the preconfigured settings to the site(s).
7. On the Apply configuration screen:

• Enter RecoverPoint login credentials.
• Determine which site to install now.
• Select the Other site already installed checkbox.
8. The applied settings are loaded and allow you to complete the installation. Complete
the wizard as detailed in the relevant sections above.

After installing a RecoverPoint system, you must complete the RecoverPoint

CHAPTER 5
Cluster Connection
This chapter explains how to connect RPA clusters using RecoverPoint Deployment
Manager 2.0 SP1. Instructions are provided in the following procedures:
◆ Connect Cluster Wizard ......................................................................................... 128
Cluster Connection 127

Cluster Connection
Connect Cluster Wizard

The RecoverPoint Connect Cluster Wizard is a graphical user interface (GUI) wizard that
helps you connect RPA clusters running RecoverPoint 4.0 or later from a single
management point. Once completing the wizard, you can connect to all clusters in the
system using the RecoverPoint user interfaces.
About the Connect Cluster Wizard

As of RecoverPoint 4.0, you install one RecoverPoint cluster at a time. Therefore, if you
plan to deploy multiple clusters in the system, once done installing the clusters, you must
run the Connect Cluster Wizard to enable replication and communication between them.
Networking requirements
To use the Connect Cluster Wizard, the computer that the wizard is run from must be able
to communicate with all the cluster management IP addresses.
Launch Connect Cluster Wizard

To launch the Connect Cluster Wizard:
to the internet.

Cluster Connection
Figure 96 Deployment Manager screen
Manager is available for download (Figure 97). Download and extract the file,
then perform step 1 on page 128.
Connect Cluster Wizard 129

Cluster Connection
3. You are prompted to choose which RecoverPoint release you plan to install, maintain,
or upgrade from (Figure 98). Since you are connecting clusters running 4.0 or later,
select RecoverPoint 4.0 or later releases.
your RecoverPoint login credentials.
Note: Default username and password = admin.

Cluster Connection
5. On the wizard selection screen, select Connect Cluster Wizard (Figure 100).
Select connection step

Connecting a new cluster to an existing RecoverPoint system is performed in two steps
(Figure 101):
◆ Prepare new cluster for connection
This step prepares the new cluster for connection to an existing RecoverPoint system
and must be done prior to “Connect new cluster to an existing system” on page 131.
When you select this step, continue with “Prepare for new cluster for connection” on
page 132.
◆ Connect new cluster to an existing system
This step connects the new cluster to an existing RecoverPoint system and can only be
done after having done “Prepare new cluster for connection” on page 131.
When you select this step, continue with “Connection prerequisites” on page 135.
Figure 101 Select connection step screen

Cluster Connection
Prepare for new cluster for connection

Perform the steps below to prepare the new cluster for connection.
Preparation prerequisites
Before continuing, ensure the following conditions are met (Figure 102). If any of the
conditions are not fulfilled, close the wizard, fulfill the conditions, and then run the wizard
again.
◆ You have RecoverPoint installation login credentials.
◆ All RPAs are running release 4.0 or later.
◆ If you plan to connect the new cluster immediately after preparing it for connection,
ensure:
• You do not install a license in, or modify the settings of, the new cluster before
connecting it to the existing system.
• The new cluster and the existing system are of the same licensing model
(RecoverPoint or RecoverPoint/SE).
• The work station running Deployment Manager is able to communicate with the
existing RecoverPoint system.
• You have installation login credentials for the existing RecoverPoint system.
• You have performed the relevant zoning for Fibre Channel connectivity between the
new cluster and the existing RecoverPoint system (only relevant if the new cluster
is a physical RPA cluster and you are connecting it over FC to an existing physical
RPA cluster).
Select the I have fulfilled the conditions for preparing the new cluster checkbox and click
Next to continue.
Figure 102 Preparation prerequisites screen

Cluster Connection
New cluster login credentials

Enter a cluster management IP address or an RPA IP address and RecoverPoint login
credentials of the new cluster (Figure 103).
Cluster management (LAN)
Enter the management (LAN) IP address of the new cluster, or an IP address of one of the
RPAs in the new cluster.
RecoverPoint installation credentials
Enter the RecoverPoint login credentials of the new cluster. For username boxmgmt, the
default password is boxmgmt.

Cluster Connection
Connect now or later

After logging in to the new cluster, the new cluster is ready to be connected (Figure 104).
Select the desired action:
◆ Connect the new cluster to an existing RecoverPoint system
Select this option if the work station running Deployment Manager is able to
communicate with the existing RecoverPoint system.
If selected, click Next to continue.
◆ Connection the new cluster at a later time
Select this option if the work station running Deployment Manager is unable to
communicate with the existing RecoverPoint system, or you do not want to connect the
new cluster now. If you select this option, click Finish to exit the wizard.
Note: To connect the new cluster at a later time, when you re-enter the wizard, select
“Connect new cluster to an existing system” on page 131.
IMPORTANT
You must copy the following information and enter it later when you want to connect
the new cluster to the existing RecoverPoint system:
- internal cluster name (only displayed if preparing a new physical RPA cluster)
- RPA WAN IP address
Do not install a license in, or modify the settings of, the new cluster before connecting
it to the existing system.
Figure 104 Connect cluster selection screen

Cluster Connection
Connection prerequisites
This screen appears only if you selected “Connect new cluster to an existing system” on
page 131.
Before continuing, ensure the following conditions are met (Figure 105). If any of the
conditions are not fulfilled, close the wizard, fulfill the conditions, and then run the wizard
again.
◆ You have performed the “Prepare new cluster for connection” step on the new cluster.
◆ You have the RPA WAN IP address of the new cluster.
◆ You have the internal cluster name of the new cluster (only relevant if the new cluster
is a physical RPA cluster and you are connecting it to an existing physical RPA cluster).
◆ The new cluster and the existing system are of the same licensing model
(RecoverPoint or RecoverPoint/SE).
◆ You have not installed a license in, or modified the settings of, the new cluster since
performing the above step.
◆ The work station running Deployment Manager is able to communicate with the
existing RecoverPoint system.
◆ You have installation login credentials for the existing RecoverPoint system.
◆ You have performed the relevant zoning for Fibre Channel connectivity between the
new cluster and the existing RecoverPoint system (only relevant if the new cluster is a
physical RPA cluster and you are connecting it over FC to an existing physical RPA
cluster).
Select the I have fulfilled the conditions for connecting the new cluster checkbox and click
Next to continue.
Figure 105 Connection prerequisites screen

Cluster Connection
Existing cluster login credentials

Enter a cluster management IP address or an RPA IP address and RecoverPoint login
credentials of the existing cluster to which you want to connect (Figure 106).
Enter the management (LAN) IP address of the existing cluster, or an IP address of one of
the RPAs of the existing cluster.
Enter the RecoverPoint login credentials of the existing cluster. For username boxmgmt,
the default password is boxmgmt.
Figure 106 Existing cluster login credentials screen
Cluster connection settings

Define the connection between the new cluster and the cluster to which you want to
connect (Figure 107).
Cluster connection settings

This section appears only if you selected Connect new cluster to an existing system in
screen “Select connection step” on page 131.
Internal cluster name (if relevant) and RPA WAN IP address values must be entered if you
are connecting a new cluster to an existing system. These values were displayed on screen
“Connect now or later” on page 134, and should have been copied for use at this stage of
the wizard.
Additional gateway
If you select IP, you can add an additional WAN gateway (gateway IP, target netmask, and
target subnet).

Cluster Connection
Note: The additional gateway only needs to be configured if the gateway specified during
cluster installation is not suitable for connectivity between clusters in this environment.
Otherwise, this section can be left blank.
Figure 107 Cluster connection settings screen
Additional cluster connections

If the system you are connecting the new cluster to contains more than one RPA cluster,
this screen appears in the wizard. If the system you are connecting to consists of only one
RPA cluster, this screen does not appear and instead you continue to “Summary” on
page 138.
To enable replication between the new cluster and additional clusters in the system, you
must set a connection between the new cluster and the existing clusters. To do so, set the
connection type between each cluster to IP or Fibre Channel (Figure 108)
If you do not want to connect the new cluster to additional clusters, set the connection
type to No Connection.
The cluster to which you already connected to earlier in the wizard is displayed, but
disabled for editing.

Cluster Connection
Figure 108 Additional cluster connections screen
Summary
The summary screen appears once connection of RPA clusters is complete (Figure 109).
Once you have completed the connection of the new cluster to the RecoverPoint system,
you can start using Unisphere for RecoverPoint.
Post-connection requirements
After connecting RPA clusters of a RecoverPoint system, you must complete the
RecoverPoint Post-Deployment Form. To download the form from EMC Online Support

Cluster Connection

Cluster Connection

RPA Replacement
CHAPTER 6
RPA Replacement
This chapter explains how to replace a RecoverPoint Appliance (RPAs) in existing RPA
clusters using the RecoverPoint Deployment Manager. Detailed instructions are provided
in the following procedures:
◆ RPA Replacement Wizard....................................................................................... 142
◆ RecoverPoint 4.0 or later ....................................................................................... 143
141
RPA Replacement
RPA Replacement Wizard

The RecoverPoint RPA Replacement Wizard is a graphical user interface (GUI) wizard that
helps you replace an existing RPA in an RPA cluster with a new RPA without any application
or replication downtime.
Note: When using a mix of supported RPA hardware types in a physical RPA cluster (such
as Gen4 and Gen5 with RecoverPoint 3.5 SP1), it is highly recommended to configure the
latest hardware type as RPA 1 and RPA 2 (cluster control RPAs).
About the RecoverPoint RPA Replacement Wizard

The RPA Replacement Wizard allows you to replace one RPA at a time. Therefore, if you
need to replace multiple RPAs in an RPA cluster, you must run the wizard again for each
RPA that you want to replace.
Launch the RPA Replacement Wizard

To launch the RPA Replacement Wizard:
2. You are prompted to check for a newer release of Deployment Manager.
to the internet.
step 1 on page 142.
from, or maintain (such as RPA replacement).

RPA Replacement

Starting in RecoverPoint 4.0, maintenance operations, such as RPA replacement, are
performed on one cluster at a time. To replace an RPA of another cluster in a system, you
must log into that cluster using another instance of the RPA Replacement Wizard.
Starting in RecoverPoint 4.0.SP1, you can use the wizard to replace a virtual RPA (vRPA) in
a RecoverPoint/SE vRPA cluster.
Access the Wizard

Follow these steps to access the RPA Replacement Wizard.

RPA Replacement
2. On the wizard selection screen, select RPA Replacement Wizard (Figure 125).
Prerequisites for replacement

Before you begin using the RPA Replacement Wizard, ensure the following conditions are
met:
1. You know the cluster management IP address or an RPA IP address.
2. You have valid RecoverPoint login credentials.
3. The new RPA has a RecoverPoint software ISO image that is the same release as that
running on the other RPAs in the cluster.
Configuration file
The RPA Replacement Wizard allows you to select one of the following (Figure 126):
◆ Create a new RPA replacement configuration file - The system creates a new RPA
replacement configuration file. The configuration settings of the existing RPAs are
added to the configuration file. The system uses these settings to complete the RPA
replacement.
location is C:\Users\<username>\RecoverPoint\ HWR_config.properties.
◆ Continue from a saved RPA replacement configuration file - The system loads the
settings from a previously saved RPA replacement configuration file. The system
allows you to complete the RPA replacement using this file.
Note: You cannot use the wizard to change the RPA settings of an installed RPA.

RPA Replacement
Login credentials
Enter the RecoverPoint cluster management IP address and login credentials to connect to
the cluster (Figure 127):
◆ Cluster management (LAN)
Enter a cluster management or an RPA IP address. If continuing from a saved
configuration file, an IP address is automatically entered.
◆ RecoverPoint installation credentials
Enter a RecoverPoint username and password. For username boxmgmt, the default
password is boxmgmt.
◆ RecoverPoint administrator credentials
Enter a RecoverPoint username and password. For username admin, the default
password is admin.

RPA Replacement
Cluster and RPA selection

Review the statuses of the RPAs in the cluster (Figure 128).
Select the RPA to be replaced. If continuing from a saved configuration file, these values
are automatically entered.
Select the checkbox at the bottom of the screen if the RPA to be replaced has been
physically removed from the system and the new RPA is racked, connected, up, and has
the relevant ISO image applied to it.
Figure 114 RPA selection screen
RPA replacement preparations

During this stage of the wizard, the system will retrieve information of the RPA being
replaced, prepare the cluster for replacement of the RPA, and verify the RPA being replaced
is shut down (Figure 129).
Once the cluster has successfully prepared the RPA for replacement, click Next to
continue.
Figure 115 RPA replacement preparations screen

RPA Replacement
RPA replacement prerequisites

(Figure 130). If any of the conditions are not fulfilled, it is recommended to close the
wizard, fulfill the conditions, then run the wizard again:
◆ Verify that the RecoverPoint release on new RPA corresponds to the release running on
the other RPAs in the cluster.
◆ Verify that the new RPA is the same type (physical or virtual) as the other RPAs in the
cluster.
◆ Log in to the new RPA as user boxmgmt, enter the temporary IP address, subnet mask,
and gateway of the replaced RPA, then log out.
◆ If replacing a physical RPA:
• Record the orientation of the network and Fibre Channel (FC) cables of the RPA
being replaced, then disconnect the cables from the RPA.
• Disconnect the power cables from the RPA being replaced and remove it from the
rack.
• Place the new RPA in the rack, connect the network, FC, and power cables, and
power on the RPA.
Listed in the table is information about the RPA to be replaced.
Select the I have fulfilled the conditions for replacing the RPA checkbox, and click Next to
continue.
Figure 116 RPA replacement prerequisites screen

RPA Replacement
To configure the storage, you must select whether to spoof the HBA WWN settings of the
RPA being replaced (recommended), as shown in Figure 131, or use the HBA WWNs of the
new RPA.
If you select Spoof the HBA WWNs of the RPA being replaced (recommended) and click
Next, a warning message appears (Figure 118). Click Yes if you want to continue with
spoofing. Click No if you want to select Use the HBA WWNs of the new RPA instead.
If you select Use the HBA WWNs of the new RPA, before clicking Next, continue with Zoning
and LUN masking.
If you decide to use the HBA WWN settings of the new RPA, the wizard displays a table of
the new and existing RPA numbers, port numbers, port WWNs, and node WWNs. Select
the Show only new RPA HBA WWN settings checkbox to hide the existing RPA information
from the table. Use this information to manually zone and mask LUNs for the new RPA you
are adding to the cluster, to be consistent with the existing zoning and LUN masking.
Note: When replacing RPAs, automatic and semi-automatic zoning options are not
available, including for RecoverPoint/SE.
The information presented in the table can be exported for further use by clicking the
Export to CSV file button.
Figure 117 Storage configuration screen

RPA Replacement
Figure 118 Warning message
New RPA configuration

During this stage of the wizard, the system validates the RecoverPoint software release
running on the new RPA, applies settings to the new RPA, and applies configuration
parameters to the new RPA (Figure 133).
Figure 119 New RPA configuration screen
SAN diagnostics
resolved, click Refresh to rerun the SAN diagnostics process.

RPA Replacement
System modifications
If tweak parameters or signed scripts were found on the RPA being replaced, they are
displayed in this screen (Figure 135). When the RPA is down, these system modifications
are taken from a cluster control RPA.
As recommended, and by default, all the system modifications are selected to run on the
new RPA. However, you can select which ones to apply, and clear which ones you do not
want to apply, to the new RPA.
Figure 121 System modifications screen

RPA Replacement
Apply changes
During this stage of the wizard, the system finalizes the configuration of the new RPA,
verifies the new RPA is up and attached, and resumes the RPA and system from
maintenance mode (Figure 136).
Figure 122 Apply changes screen
Summary
Once you have completed the replacement of the RPA in the RPA cluster, you can continue
using Unisphere for RecoverPoint (Figure 123).

RPA Replacement

Access the Wizard
Follow these steps to access the RPA Replacement Wizard.
2. On the wizard selection screen, select RPA Replacement Wizard (Figure 125).

RPA Replacement
Prerequisites for replacement

Before you begin using the RPA Replacement Wizard, ensure the following conditions are
met:
1. You know at least one site management or RPA IP address.
2. You have valid RecoverPoint login credentials.
3. The new RPA has a RecoverPoint software ISO image that is the same release as that
running on the other RPAs in the cluster.
Configuration file
The RPA Replacement Wizard allows you to select one of the following (Figure 126):
◆ Create a new RPA replacement configuration file - The system creates a new RPA
replacement configuration file. The configuration settings of the existing RPAs are
added to the configuration file. The system uses these settings to complete the RPA
replacement.
location is C:\Users\<username>\RecoverPoint\ HWR_config.properties.
◆ Continue from a saved RPA replacement configuration file - The system loads the
settings from a previously saved RPA replacement configuration file. The system
allows you to complete the RPA replacement using this file.

RPA Replacement
Login credentials
Enter a site management or an RPA IP address and RecoverPoint login credentials to
connect to the RPAs (Figure 127):
1. IP credentials
Enter a site management or an RPA IP address. If continuing from a saved
2. RecoverPoint login credentials
Enter a RecoverPoint username and password.
For username boxmgmt, the default password is boxmgmt.
Site and RPA selection

Review the statuses of the RPAs in the system (Figure 128).
Select the site of RPA replacement and the number of the RPA to be replaced. If continuing
from a saved configuration file, these values are automatically entered.
Select the checkbox at the bottom of the screen if the RPA to be replaced has been
physically removed from the system and the new RPA is racked, connected, up, and has
the relevant ISO image applied to it.
Figure 128 Site and RPA selection screen

RPA Replacement
RPA replacement preparations

During this stage of the wizard, the system retrieves information of the RPA being
replaced, prepares the system for replacement of the RPA, and verifies the RPA being
replaced is shut down (Figure 129).
Once the system has successfully prepared the RPA for replacement, click Next to
continue.
Figure 129 RPA replacement preparations screen
RPA replacement prerequisites

◆ Record the orientation of the network and Fibre Channel (FC) cables of the RPA being
replaced, then disconnect the cables from the RPA.
◆ Disconnect the power cables from the RPA being replaced and remove it from the rack.
◆ Place the new RPA in the rack, connect the network, FC, and power cables, and power
on the RPA.
◆ Verify that the RecoverPoint release on new RPA corresponds to the release running on
the other RPAs in the cluster.
Note: If system is running release 3.5 or later, new RPAs must be Gen4 or later
◆ Log in to the new RPA as user boxmgmt, enter the temporary IP address, subnet mask,
and gateway of the replaced RPA, then log out.
Listed in the table is information about the site of RPA replacement and the RPA to be
replaced.
Select the I have fulfilled the conditions for replacing the RPA checkbox, and click Next to
continue.

RPA Replacement
Figure 130 RPA replacement prerequisites screen
To configure the storage, you must select whether to spoof the HBA WWN settings of the
RPA being replaced (recommended), as shown in Figure 131, or use the HBA WWNs of the
new RPA.
If you select Spoof the HBA WWNs of the RPA being replaced (recommended) and click
Next, a warning message appears (Figure 132). Click Yes if you want to continue with
spoofing. Click No if you want to select Use the HBA WWNs of the new RPA instead.
If you select Use the HBA WWNs of the new RPA, before clicking Next, continue with Zoning
and LUN masking.
If you decide to use the HBA WWN settings of the new RPA, the wizard displays a table of
the new and existing RPA numbers, port numbers, port WWNs, and node WWNs. Select
the Show only new RPA HBA WWN settings checkbox to hide the existing RPA information
from the table. Use this information to manually zone and mask LUNs for the new RPA you
are adding to the site, to be consistent with the existing zoning and LUN masking.
Note: When replacing RPAs, automatic and semi-automatic zoning options are not
available, including for RecoverPoint/SE.
The information presented in the table can be exported for further use by clicking the
Export to CSV file button.

RPA Replacement
Figure 131 Storage configuration screen
Figure 132 Warning message
New RPA configuration

During this stage of the wizard, the system validates the RecoverPoint software release
running on the new RPA, applies settings to the new RPA, and applies configuration
parameters to the new RPA (Figure 133).
Figure 133 New RPA configuration screen

RPA Replacement
Storage configuration - SAN diagnostics

the current SAN environment.
Figure 134 Storage configuration - SAN diagnostics screen
System modifications
If tweak parameters or signed scripts were found on the RPA being replaced, they are
displayed in this screen (Figure 135). When the RPA is down, these system modifications
are taken from a site control RPA.
As recommended, and by default, all the system modifications are selected to run on the
new RPA. However, you can select which ones to apply, and clear which ones you do not
want to apply, to the new RPA.

RPA Replacement
Figure 135 System modifications screen
Apply changes
During this stage of the wizard, the system finalizes the configuration of the new RPA,
verifies the new RPA is up and attached, and resumes the RPA and system from
maintenance mode (Figure 136)

RPA Replacement
Summary
Once you have completed the replacement of the RPA in the RPA cluster, you can start
using the RecoverPoint Management Application (Figure 123).

RPA Addition
CHAPTER 7
RPA Addition
This chapter explains how to add new RPAs to existing RPA clusters using the RecoverPoint
Deployment Manager. Instructions are provided for the following procedures:
◆ Add New RPAs Wizard ........................................................................................... 162
161
RPA Addition
Add New RPAs Wizard

The RecoverPoint Add New RPAs Wizard is a graphical user interface (GUI) wizard that
helps you non-disruptively add new RPAs to existing RPA clusters from a single
management point. That is, you can add new RPAs to a cluster (4.0 and later) or up to two
clusters (3.5 and earlier) without the need for cluster reinstallation, replication downtime,
full sweep, or journal loss.
Note: When using a mix of RPA hardware types (Gen3, Gen4, Gen5) in a cluster, it is highly
recommended to configure the latest hardware type as RPA 1 and RPA 2 (site control
RPAs).
About the RecoverPoint Add New RPAs Wizard

As of RecoverPoint 4.0, the Add New RPAs Wizard allows you to add new RPAs to one RPA
cluster at a time. Therefore, if the system is composed of multiple RPA clusters, you must
add the new RPAs to each cluster by running the wizard on each cluster in the system.
The wizard prevents addition of more RPAs than that permitted by the currently installed
license (only relevant to RecoverPoint 3.5.x and earlier releases).
Launch Add New RPAs Wizard

To launch the Add New RPAs Wizard:
to the internet.
step 1 on page 162.
from, or maintain (such as RPA addition).

RPA Addition

Starting in RecoverPoint 4.0, maintenance operations, such as RPA addition, are
performed on one cluster at a time. To add an RPA to another cluster in a system, you must
log into that cluster using another instance of the Add New RPAs Wizard.
Access the Wizard


RPA Addition
2. On the wizard selection screen, select Add New RPAs Wizard (Figure 157).

RPA Addition
Prerequisites
conditions, and then run the wizard again.
◆ New RPAs are connected to SAN and Ethernet networks
◆ New RPAs are set with IP addresses
◆ New RPAs are loaded with RecoverPoint software ISO images that correspond to the
release running on the existing RPAs in the cluster
◆ New RPAs are of the same type as the existing RPAs in the cluster (physical or virtual)
◆ All RPAs are running release 4.0 or later
◆ If adding new physical RPAs:
• New RPAs are rack mounted and powered on
◆ If adding new virtual RPAs:
• Connection sets must be configured between the VNX iSCSI ports and the virtual
RPAs.
• Virtual RPAs must be deployed using the RecoverPoint OVF package
• You must have CHAP credentials (only relevant if CHAP credentials are configured
on the cluster)
Select the I have fulfilled the conditions for adding new RPAs to clusters checkbox, and
click Next to continue.

RPA Addition
Configuration file
The Add New RPAs Wizard allows you to select one of the following (Figure 159):
◆ Create a new RPA addition configuration file
The system creates a new RPA addition configuration file. Starting with a blank
configuration, the user must enter configuration settings for the RPAs being added to
the cluster. The system uses these settings to complete the RPA addition.
location is C:\Users\<username>\RecoverPoint\ DNC_config.properties.
◆ Create or continue from a saved RPA addition configuration file
The system loads the settings from a previously saved RPA addition configuration file.
If the file was already applied, the system allows you to use it by changing the
configuration parameters.

RPA Addition
Login credentials
configuration file, an IP address is entered automatically.
password is admin.
Add New RPAs

Enter the number of RPAs to add to the cluster (Figure 161).
A cluster can have between 2 to 8 RPAs.
Displayed onscreen is the existing cluster name, the number of existing RPAs at the
cluster, and the number of RPAs that you plan to add to the cluster.
Figure 143 Add new RPAs screen

RPA Addition

Review the cluster IP configurations and set the new RPA IP settings (Figure 162).
Cluster management — LAN, based on IP type of the cluster, is displayed. This is a virtual
IP address that is used to configure the RPA cluster. The IP address is assigned to the RPA
that is currently running the active instance of the cluster management.
Interface netmask — LAN and WAN, based on IP type of the cluster, are displayed.
RPAs
◆ IP addresses of the existing RPAs of the cluster are displayed, based on IP type of the
cluster.
◆ IP addresses of the new RPAs of the cluster must be entered, based on the IP type of
the cluster.
recommended to assign RPA 1 and RPA 2 (site control RPAs) to the latest hardware types
(Gen5), to improve system function and performance.
Default gateways
Default gateway — Based on IP type entered when the cluster was installed. Cannot be
modified.
Gateway, Target netmask, and Target subnet. Cannot be modified.

RPA Addition

This screen appears only if you are adding a virtual RPA (vRPA) to a vRPA cluster.
Define the RPA cluster iSCSI settings.
Connectivity
For iSCSI 1
◆ IP type — Cannot be modified.
◆ MTU — Cannot be modified.
For iSCSI 2
◆ IP type — Cannot be modified.
◆ MTU — Cannot be modified.
If relevant, select the I want to configure CHAP credentials for the RPAs iSCSI ports
checkbox and modify the CHAP credentials (username and password).
Figure 145 Cluster iSCSI Settings screen
RPA iSCSI ports

This screen appears only if you are adding a virtual RPA (vRPA) to a vRPA cluster.
Interface netmask — Cannot be modified.
Default gateways
Additional gateways
Gateway, Target netmask, and Target subnet. Click Add route to add additional gateways.

RPA Addition

The system communicates and validates the status of the new RPAs and confirms that all
components are OK or that errors are detected (Figure 163).
When all statuses appear OK (green check mark), click Next.

RPA Addition
Define the storage configuration at the cluster.
Cluster configuration
Define the storage configuration at the site where the RPA cluster is located.
If adding RPAs to a RecoverPoint/SE environment composed of vRPAs, you continue with
the following storage configuration screens: “Storage iSCSI ports” on page 171, “SAN
diagnostics” on page 175, and “Configure new RPAs” on page 176.
If adding RPAs to a RecoverPoint/SE environment composed of physical RPAs, you
continue with the following storage configuration screens: “VNX/CLARiiON login
credentials” on page 172, “Zoning (RecoverPoint/SE)” on page 172, “SAN diagnostics” on
page 175, and “Configure new RPAs” on page 176.
If adding RPAs to a RecoverPoint environment, you continue with the following storage
configuration screens: “Zoning (RecoverPoint)” on page 175, “SAN diagnostics” on
Storage iSCSI ports

This screen appears only if you are adding a virtual RPA (vRPA) to a vRPA cluster. Once you
complete, you continue to “SAN diagnostics” on page 175.
The current storage CHAP and iSCSI IP configurations are displayed. Modify the values you
want to change (Figure 148).
CHAP credentials
Figure 148 Storage iSCSI Ports screen

RPA Addition

Enter the login credentials for the VNX/CLARiiON storage array at the cluster (Figure 164):
◆ Array SP A IP - Enter the IP address of array SP A at the site.
◆ Array SP B IP - Enter the IP address of array SP B at the site.
◆ EMC Unisphere/Navisphere username - Enter the Unisphere username at the site.
Default value is admin.
◆ EMC Unisphere/Navisphere password - Enter the Unisphere password at the site.
◆ Authentication scope - Select whether the scope of the user account is Global, Local,
scope.
Figure 149 VNX/CLARiiON login credentials
Zoning (RecoverPoint/SE)
◆ Automatic - The Installer zones the RPAs and the VNX/CLARiiON arrays automatically
(possible only with Brocade and Cisco switches). For details, see “Zoning: Automatic”
on page 173.
apply them yourself (possible only with Brocade and Cisco switches). For details, see
“Zoning: Semi-automatic” on page 173.
◆ Manual - The Installer indicates which ports should be zoned together, and you must
zone them yourself. For details, see “Zoning: Manual” on page 173.
◆ Direct-attach Storage - The Installer verifies that each RPA is directly connected to SP A
and SP B of the VNX/CLARiiON array. For details, see “Zoning: Direct-attach Storage”
on page 174.

RPA Addition
Note: If adding RPAs to a RecoverPoint 4.0 and later installation, and the RPAs are
directly attached to the VNX/CLARiiON arrays, then the wizard skips this screen
automatically and continues to “SAN diagnostics” on page 175.
Zoning: Automatic
zoning.
Enter the following fabric credentials:
◆ IP — address of the fabric switch at the site
◆ Username — for the fabric switch at the site
◆ Password — for the fabric switch at the site
The system automatically creates an RPA-to-storage zone for each new RPA at the site,
where each zone includes:
You must enter switch credentials to allow RecoverPoint/SE to perform semi-automatic
zoning. Enter the following fabric credentials:
Semi-automatic zoning is available for Brocade and Cisco fabric switches. To use
semi-automatic zoning, you must first enter the switch credentials, just as for automatic
zoning.
Even if you have entered switch credentials, in semi-automatic zoning, the system does
not automatically configure the zoning on the switch.
Zoning: Manual
Zone and mask LUNs using the RPA port WWNs displayed in the RPAs WWNs tables, and
To create the new RPA-to-storage zones at this site, use the following procedure:

RPA Addition


2. If it doesn’t already exist, create at the cluster, on the fabric, an RPA-to-RPA zone
containing all local RPA HBAs that are not used in RPA-to-storage zones (best
practice). This zone provides an additional communication link between RPAs. It can
also be used for synchronous replication of distributed consistency groups. If
replicating over Fibre Channel, merge the RPA-to-RPA zones at each cluster into one.
If this zone already exists at the cluster, add the new RPAs to this zone.

array.
Figure 150 Zoning (RecoverPoint/SE)

RPA Addition
Zoning (RecoverPoint)
The system displays the port numbers, port WWNs, and node WWNs of each RPA at the
cluster (Figure 166).
Use this information to zone and mask LUNs for the RPAs.
to CSV file button.
Figure 151 Zoning (RecoverPoint)
SAN diagnostics
operate in the current SAN environment (Figure 167).
Description.
detected for an RPA, a description of the error appears.
Figure 152 SAN diagnostics

RPA Addition
Configure new RPAs

Figure 153 Configure new RPAs
Apply changes
During this stage of the wizard (Figure 169), the system:
◆ Registers RPA initiators on the array (only relevant for a RecoverPoint/SE
environment).
◆ Prepares to add the new RPAs to the cluster.
◆ Applies the new settings to all the RPAs in the cluster.
◆ Finishes installation of the new RPAs.
◆ Finishes adding the new RPAs.
◆ Verifies the system state is OK.

RPA Addition
Summary
Once you have completed adding RPAs to the existing RPA cluster, you can redistribute
existing consistency groups to the new RPAs, or create new consistency groups and assign
the new RPAs as the preferred RPAs (Figure 170).

RPA Addition

Access the Wizard
2. On the wizard selection screen, select Add New RPAs Wizard (Figure 157).

RPA Addition
Prerequisites
conditions, and then run the wizard again.
◆ New RPAs are rack mounted and powered on.
◆ New RPAs are connected to SAN and Ethernet networks.
◆ New RPAs are set with IP addresses.
◆ New RPAs are loaded with RecoverPoint software ISO images that correspond to the
release running on the existing RPAs in the cluster.
Note: If system is running release 3.5 or later, new RPAs must be Gen4 or later.
Select the I have fulfilled the conditions for adding new RPAs to clusters checkbox,
Configuration file
The Add New RPAs Wizard allows you to select one of the following (Figure 159):
◆ Create a new RPA addition configuration file
The system creates a new RPA addition configuration file. Starting with a blank
configuration, the user must enter configuration settings for the RPAs being added to
the system. The system uses these settings to complete the RPA addition.
location is C:\Users\<username>\RecoverPoint\ DNC_config.properties.
◆ Create or continue from a saved RPA addition configuration file
The system loads the settings from a previously saved RPA addition configuration file.
If the file was already applied, the system allows you to use it by changing the
configuration parameters.

RPA Addition
Login credentials
connect to the RPAs (Figure 142).
Figure 160 Installation configuration screen
◆ IP credentials
Enter a site management or an RPA IP address.
Note: You are not required to enter IP credentials if you are creating or continuing from
a saved RPA addition configuration file.
◆ RecoverPoint login credentials


RPA Addition
Add New RPAs

Enter the number of RPAs to add to each site (Figure 161).
A site can have between 2 to 8 RPAs. The number of RPAs must be equal at both sites.
Displayed onscreen are the existing site names, the number of existing RPAs at each site,
and the number of RPAs that you plan to add to each site.
Figure 161 Add new RPAs screen
RPA IP settings
Define the new RPA IP settings at each site.
The following information is displayed (Figure 162):
◆ Site1Name IP settings
(Either WAN or Private, IPv4 or IPv6)
• Subnet mask
• Gateway
◆ Site1Name Management IP settings
(Either IPv4, IPv6, or both IPv4 and IPv6)
• Subnet mask
• Default gateway
• Site management IP
◆ Site1Name RPAs IP settings
For each new RPA, enter the management IP address (IPv4, IPv6, or both) and the WAN
(or Private) IP address (IPv4 or IPv6).
All RPAs must be on the same network (per site).

RPA Addition
Note: The order of IPs assigned to RPAs is significant. If you define an RPA number with
an IP address, the physical RPA with this IP address becomes the RPA number in the
cluster.
Figure 162 RPA IP settings - Site1Name IP settings


RPA Addition
Define the storage configuration at each site.
Site1Name configuration
Define the storage configuration at site 1.
If adding RPAs to a RecoverPoint environment, you continue with the following storage
configuration screens: “Zoning (RecoverPoint)” on page 186, “SAN diagnostics” on
If adding RPAs to a RecoverPoint/SE 3.3 SP1 and later environment, you continue with the
following storage configuration screens: “VNX/CLARiiON login credentials” on page 183,
“Zoning (RecoverPoint/SE)” on page 184, “SAN diagnostics” on page 187, and “Configure
new RPAs” on page 187.

Enter the login credentials for the VNX/CLARiiON storage array at the site (Figure 164):
Default value is admin.
scope.
Figure 164 Storage configuration - Site1Name - VNX/CLARiiON login credentials

RPA Addition
Zoning (RecoverPoint/SE)
Note: For RecoverPoint/SE releases earlier than 3.4, it is recommended that you create
zones manually, rather than using the automatic or semi-automatic zoning options.
◆ Automatic - The Installer zones the RPAs and the VNX/CLARiiON arrays automatically
(possible only with Brocade and Cisco switches). For details, see “Zoning: Automatic”
on page 184.
apply them yourself (possible only with Brocade and Cisco switches). For details, see
“Zoning: Semi-automatic” on page 184.
◆ Manual - The Installer indicates which ports should be zoned together, and you must
zone them yourself. For details, see “Zoning: Manual” on page 185.
◆ Direct-attach Storage - The Installer verifies that each RPA is directly connected to SP A
and SP B of the VNX/CLARiiON array. For details, see “Zoning: Direct-attach Storage”
on page 185.
Note: If adding RPAs to a RecoverPoint 3.3 SP2 and later installation, and the RPAs are
directly attached to the VNX/CLARiiON arrays, then the wizard skips this screen
automatically and continues to “SAN diagnostics” on page 187.
Zoning: Automatic
zoning.
Enter the following fabric credentials:
The system automatically creates an RPA-to-storage zone for each new RPA at this site,
where each zone includes:
You must enter switch credentials to allow RecoverPoint/SE to perform semi-automatic
zoning. Enter the following fabric credentials:

RPA Addition

Semi-automatic zoning is available for Brocade and Cisco fabric switches. For
RecoverPoint 3.4 and later, to use semi-automatic zoning, you must first enter the switch
credentials, just as for automatic zoning.
Whether you have entered switch credentials (RecoverPoint/SE 3.4 or later) or not (earlier
than RecoverPoint/SE 3.4), in semi-automatic zoning, the system does not automatically
configure the zoning on the switch.
Zoning: Manual
Zone and mask LUNs using the RPA port WWNs displayed in the RPAs WWNs tables, and
To create the new RPA-to-storage zones at this site, use the following procedure:

2. If it doesn’t already exist, create, at each site, on each fabric, an RPA-to-RPA zone
containing all local RPA HBAs that are not used in RPA-to-storage zones (best
practice). This zone provides an additional communication link between RPAs. It can
also be used for synchronous replication of distributed consistency groups. If
replicating over Fibre Channel, merge the RPA-to-RPA zones at each site into one.
If this zone already exists at each site, add the new RPAs to this zone.

array.
This option is only available when installing RecoverPoint/SE 3.3 SP1 and later service
pack and patch releases, and all releases of RecoverPoint 3.4 and later.

RPA Addition
Figure 165 Storage configuration - Site1Name - Zoning (RecoverPoint/SE)
Zoning (RecoverPoint)
The system displays the port numbers, port WWNs, and node WWNs of each RPA at the
site (Figure 166).
Use this information to zone and mask LUNs for the RPAs.
to CSV file button.
Figure 166 Storage configuration - Site1Name - Zoning (RecoverPoint)

RPA Addition
SAN diagnostics
the current SAN environment (Figure 167).
Description.
Figure 167 Storage configuration - Site1Name - SAN diagnostics
Configure new RPAs

Figure 168 Storage configuration - Site1Name - Configure new RPAs

RPA Addition
Refer to “Site1Name configuration” on page 183 for details.
Apply changes
◆ Registers RPA initiators on the array (only relevant for a RecoverPoint/SE 3.3 SP1 and
later environment).
◆ Prepares to add the new RPAs to the clusters.
◆ Applies the new settings to all the RPAs in the clusters.
◆ Finishes installation of the new RPAs.
◆ Finishes adding the new RPAs.
◆ Verifies the system state is OK.

RPA Addition
Summary
Once you have completed adding RPAs to the existing RPA clusters, you can redistribute
existing consistency groups to the new RPAs, or create new consistency groups and assign
the new RPAs as the preferred RPAs (Figure 170).

RPA Addition

Upgrade RPA Software
CHAPTER 8
This chapter explains how to upgrade RecoverPoint Appliance (RPA) software using the
RecoverPoint Deployment Manager. Information and instructions are provided in the
following sections:
◆ About upgrading RecoverPoint .............................................................................. 192
◆ Upgrade matrix to the latest RecoverPoint releases ............................................... 193
◆ Upgrading to the latest 4.0 release........................................................................ 195
◆ Upgrade Cluster Wizard......................................................................................... 200
◆ Upgrade RPAs Wizard ............................................................................................ 224
191
About upgrading RecoverPoint

Upgrading RecoverPoint Appliance (RPA) software to the latest RecoverPoint release is
recommended to gain the latest RecoverPoint features and functionalities.
Upgrades from RecoverPoint 3.1 and later are performed using RecoverPoint Deployment
Manager and are non-disruptive to the environment (do not cause application or
replication downtime, nor journal loss). Information on the various upgrade paths, as well
as links to the relevant procedures, are presented in “Upgrade matrix to the latest
RecoverPoint releases” on page 193.
Upgrades are performed by EMC Customer Support and authorized partners and require
opening an Update Service Request and initiating the RecoverPoint Change Control
Activity (CCA) process, which is required for all upgrades.
As of RecoverPoint Deployment Manager 2.0, customers can perform their own upgrades
of RecoverPoint/SE 3.5 and later releases. Interested customers should download the
RecoverPoint/SE Upgrade Kit, available on the “RecoverPoint SE” product page on EMC
Online Support.

Upgrade matrix to the latest RecoverPoint releases

Table 1 on page 193 provides a high-level overview of the procedures involved in
non-disruptively upgrading from earlier RecoverPoint releases to the latest RecoverPoint
releases.
Table 1 Upgrade matrix to latest RecoverPoint releases (page 1 of 2)
To From Procedure Reference
4.0 and later 1. Deployment Manager upgrade to latest 4.0 “Upgrading from 4.0 and later” on page 195
2. Deployment Manager upgrade to latest 4.0
3.2 SP2 and later 1. Deployment Manager upgrade to latest 3.3 “Upgrading from 3.2 SP2 and later” on
2. Deployment Manager upgrade to latest 3.4 page 198
latest 3. Deployment Manager upgrade to latest 3.5
4.0
release
3.2 and 3.2 SP1 1. Deployment Manager upgrade to latest 3.2 “Upgrading from 3.2 and 3.2 SP1” on

3.1 and later 1. Deployment Manager upgrade to latest 3.2 “Upgrade RPAs Wizard” on page 224
Upgrade matrix to the latest RecoverPoint releases 193

Table 1 Upgrade matrix to latest RecoverPoint releases (page 2 of 2)
To From Procedure Reference
latest 3. Deployment Manager upgrade to latest 3.5

3.5
release 3.2 and 3.2 SP1 1. Deployment Manager upgrade to latest 3.2 “Upgrading from 3.2 and 3.2 SP1” on

latest
3.4 3.2 and 3.2 SP1 1. Deployment Manager upgrade to latest 3.2 “Upgrading from 3.2 and 3.2 SP1” on
release 2. Deployment Manager upgrade to latest 3.3 page 198
page 198
latest
3.3 3.2 and 3.2 SP1 1. Deployment Manager upgrade to latest 3.2 “Upgrading from 3.2 and 3.2 SP1” on
release page 198
latest 3.2 and later 1. Deployment Manager upgrade to latest 3.2 “Upgrading from 3.2 and later” on page 199
3.2
release 3.1 and later 1. Deployment Manager upgrade to latest 3.2 “Upgrade RPAs Wizard” on page 224

Upgrading to the latest 4.0 release

The following RecoverPoint upgrades are performed in non-disruptive procedures using
Deployment Manager:
◆ “Upgrading from 4.0 and later” on page 195
◆ “Upgrading from 3.2 SP2 and later” on page 196
◆ “Upgrading from 3.2 and 3.2 SP1” on page 196
◆ “Upgrade RPAs Wizard” on page 224
IMPORTANT
RecoverPoint 4.0 releases are not supported on the Gen3 RPA platform.
If the system contains Gen3 RPAs, you must:
1) Use the RPA Replacement Wizard to replace them with supported RPAs (as detailed in
the EMC RecoverPoint Release Notes).
2) Use the Upgrade RPAs Wizards to upgrade to a 4.0 release.
Upgrading from 4.0 and later

To upgrade RPAs to the latest RecoverPoint 4.0 release from RecoverPoint 4.0 and later
requires using Deployment Manager one time. Follow the procedure presented in
“Upgrade Cluster Wizard” on page 200.

“Upgrade RPAs Wizard” on page 224.

requires using Deployment Manager two times. Follow the procedure presented in
Upgrading to the latest 4.0 release 195


requires using Deployment Manager three times. Follow the procedure presented in
Upgrading from 3.2 SP2 and later

To upgrade RPAs to the latest RecoverPoint 4.0 release from RecoverPoint 3.2 SP2 and
later requires using Deployment Manager four times. Follow the procedure presented in
Upgrading from 3.2 and 3.2 SP1

To upgrade RPAs to the latest RecoverPoint 4.0 release from RecoverPoint 3.2 and 3.2 SP1
requires using Deployment Manager five times. Follow the procedure presented in

Deployment Manager:
IMPORTANT




requires using Deployment Manager two times. Follow the procedure presented in

later requires using Deployment Manager three times. Follow the procedure presented in

requires using Deployment Manager four times. Follow the procedure presented in

Deployment Manager:
IMPORTANT




later requires using Deployment Manager two times. Follow the procedure presented in

requires using Deployment Manager three times. Follow the procedure presented in

Deployment Manager:


later requires using Deployment Manager one time. Follow the procedure presented in

requires using Deployment Manager two times.Follow the procedure presented in


The following RecoverPoint upgrades are performed in one non-disruptive procedure using
Deployment Manager:



Upgrade Cluster Wizard

To upgrade RPAs to the latest RecoverPoint 4.0 release from RecoverPoint 4.0 and later,
you must use the Upgrade Cluster Wizard. The procedure is presented here.
IMPORTANT
As of RecoverPoint 4.0, RecoverPoint systems are upgraded one RPA cluster at a time.
Therefore, if you plan to upgrade a system composed of two or more RPA clusters to the
same release, you must run the wizard on each RPA cluster of the system.
Introduction
RecoverPoint Deployment Manager 2.0.SP1 contains the Upgrade Cluster Wizard, a
Java-based GUI wizard that allows you to perform non-disruptive upgrades of the
RecoverPoint software running on an RPA cluster. The wizard is composed of two steps —
Prepare for Upgrade and Apply/Resume Upgrade.
The Prepare for Upgrade step guides you through the verification of RecoverPoint/SE
credentials and downloads ISO files to all RPAs in the environment. The Apply/Resume
Upgrade step applies the upgrade to all RPAs. Once the upgrade is complete, you can
continue using Unisphere for RecoverPoint (the RecoverPoint GUI).
While the upgrade procedure does not upgrade the VNX splitter, a RecoverPoint/SE
environment can simultaneously support splitters from two adjacent releases (for
example, a 4.0.SP1 environment can support both a 4.0.SP1 splitter and a 3.5.SP1
splitter). However, EMC strongly advises you to upgrade splitters to the same
RecoverPoint release to gain the latest splitter functionalities and features.
Note: The upgrade procedure may take a number of hours to complete, depending on the
ISO file distribution, network speed, and size of environment being upgraded.

Launch Deployment Manager

To launch Deployment Manager:
1. Open the RecoverPoint_DM.exe application file.
to the internet.
step 1 on page 225.
3. You are prompted to choose which RecoverPoint release you would like maintain, or
upgrade from (Figure 195).
Upgrade Cluster Wizard 201

4. Select RecoverPoint 4.0 or later releases and click Next.
Launch Upgrade Cluster Wizard

IMPORTANT
Selecting Upgrade RecoverPoint/SE is intended for RecoverPoint/SE customers running
4.0 or later code that have chosen to perform an upgrade on their own. EMC personnel
should upgrade RecoverPoint/SE using the Other operations (EMC personnel) option.

2. On the wizard selection screen, select Upgrade Cluster Wizard (Figure 197).

Select upgrade step

On the selection upgrade step screen, you are presented with two options (Figure 175):
◆ Prepare for Upgrade
This option prepares the RPA cluster for upgrade. This step must be run and completed
before running the Apply Upgrade step.
◆ Apply Upgrade
This option applies the upgrade to a prepared RPA cluster. This step can only be done
after having run and completed the Prepare for Upgrade step.
To begin the upgrade, select Prepare for Upgrade and click Next.
Figure 175 Deployment Manager Upgrade Cluster Wizard selection screen
Prepare for upgrade

Before continuing, ensure the following conditions are met on the system (Figure 176):
management IP and the cluster’s RPA management (LAN) networks. Ensure that ports
21, 22, 7225, and 8082 (all TCP) are open on the computer to enable communication
with all RPAs.
Tip: Telnet to these computer ports to ensure they are open.
◆ You have RecoverPoint login credentials (installation and administrator).
◆ If planning to download an ISO file from an FTP server, you must have FTP access from
all RPAs and FTP server credentials.
not have Internet connectivity, you must have an Upgrade Change Management XML
file available locally to complete the upgrade.
Note: To obtain the XML file, you must submit an Upgrade Service Request to EMC
Customer Support.

Select the I have fulfilled the conditions for upgrading the cluster checkbox and click Next.
Figure 176 Prepare for upgrade screen
Login credentials

Enter a cluster management IP address or an RPA IP address.

Enter RecoverPoint installation username and password.
Note: Installation username and default password = boxmgmt.
RecoverPoint administrator credentials

Enter RecoverPoint administrator username and password.
Note: Administrator username and default password = admin.

Login credentials summary

Review the results of the login connectivity to all RPAs in the cluster (Figure 178).
components are OK or that warnings or errors are detected.
If warnings or errors are detected for an RPA, a comment will appear describing the issue.
When ready to continue, click Next.
Figure 178 Login credentials summary screen


Enter EMC Online Support site credentials to access relevant RecoverPoint ISO images to
apply to the cluster, and to provide you with the relevant Upgrade Change Management
information required to complete the upgrade (Figure 179).
If you do not have Internet connectivity, select the Use an offline Upgrade Change
Management XML file checkbox and load the XML file into the wizard from a local folder
where you have saved the file.
IMPORTANT
To obtain the XML file, you must open an Upgrade Service Request with Customer Support
(severity level 3). In the request, ask for the latest Upgrade Change Management XML file
for the RecoverPoint Deployment Manager, and indicate the intended date of the upgrade.
The file will be provided within one (1) business day as an email attachment, so ensure a
valid email address is provided. Once provided, the file must be used within 30 days of
delivery; any use of the file after 30 days will not be supported by EMC.


◆ “Update with an ISO image available from EMC Online Support site (recommended)”
on page 208
◆ “Update with an ISO image available locally” on page 208

Update with an ISO image available from EMC Online Support site
(recommended)
(login credentials required).
When you select this option and click Next, continue to “ISO image download details” on
page 209.
Note: If no ISO image is found on EMC Online Support site, this option will be greyed out.
Update with an ISO image available locally

Select this option if you have an ISO image on your local machine, a DVD, a USB device, or
an FTP server.
When you select this option and click Next, continue to “ISO file information” on
page 210.


Continue here if you selected “Update with an ISO image available from EMC Online
Support site (recommended)” on page 208.
Provide EMC Online Support site credentials, choose the desired ISO image, and define
where to save it (Figure 181).
The ISO images that are presented to you are the relevant ISO images currently found on
EMC Online Support site, based on the release you are upgrading from (for example, if you
are upgrading from release 4.0, only releases later than 4.0 are presented for download).
Note the location of the target folder where you are saving the ISO image, as you will need
it in the next step of the wizard, Upload from local machine option in “ISO file


Continue here if you selected “Update with an ISO image available locally” on page 208 or
if you are continuing from “ISO image download details” on page 209.
Choose an option on how to distribute the ISO file to the RPAs.
The following options are available (in Figure 182, “Download from FTP server” is shown):
IMPORTANT
For all options, the ISO file name must be the exact same name as the ISO image that you
downloaded or obtained using other means. Renaming the file may prevent the upgrade
from working properly.


Enter the file name of the ISO file that you located on your local machine (the computer
Continue to “Upgrade Change Management procedures” on page 212.

When using DVD option, a DVD with the ISO file must be loaded in each RPA of the cluster
When using USB option, a USB with the ISO file must be connected to each RPA of the
cluster for the download to work properly.
If all of the RPAs being upgraded have DVD/USB devices inserted in them, select the A
DVD/USB is inserted in all of the RPAs checkbox. This will enable Deployment Manager to
automatically download the ISO files to the RPAs of the cluster once you click Next.
Continue to “Upgrade Change Management procedures” on page 212.

Enter credentials of an FTP server where the ISO file is located to download it to the RPAs:
◆ FTP server IP address
◆ FTP username
◆ FTP password
rel4.0_f.221_release_em
c_md5_4bd4d0f56eb21 Note: If you have set up a default directory, either place a slash in the File location field or
59dd5fe8a5c97f3ba.iso leave it blank. If you have not set up a default directory, enter the entire path to the file in
the File location field.
Once all information has been entered, click Next to begin the download and distribution
of the ISO file to the RPAs.
Continue to “FTP credentials summary” on page 211.

Review the status of the FTP connectivity results (Figure 183).

If errors are detected for an FTP server, a comment will appear describing the problem. To
Figure 183 FTP credentials summary screen
Upgrade Change Management procedures

Before the ISO file is distributed to the RPAs, the wizard analyzes which release you are
upgrading from and which release you are upgrading to. Based on this analysis, the
wizard will present you with a list of general upgrade messages and Upgrade Change
Management procedures that must be completed before continuing the upgrade (Figure
184).
IMPORTANT
Failure to complete each procedure may cause the upgrade to fail and data to be lost.
General upgrade messages

These messages are relevant to all upgrades, regardless of what release you are
upgrading from or to.

These procedures are unique to the RecoverPoint/SE cluster you are upgrading. That is,
the procedures displayed are relevant to the release from which you are upgrading and to
the release to which you are upgrading.
you would like to view the information in another program (Figure 185).

Figure 184 Upgrade Change Management procedures screen
Figure 185 Upgrade Change Management message screen

ISO file distribution summary

Review the status of the ISO file distribution results (in Figure 186, Download from FTP
server is shown).
If you selected:
◆ “Upload from local machine” on page 211, the file distribution will start automatically.
However, once download begins, you can click Stop to stop the download.
◆ “Copy from DVD or USB device inserted in the RPAs” on page 211:
• and selected the checkbox, the file distribution will start automatically.
• and did not select the checkbox, you must click Start to begin downloading the file.
◆ “Download from FTP server” on page 211, the file distribution will start automatically.
The system verifies the ISO file download and distribution to all RPAs and confirms that
they are OK or that errors are detected.
If errors are detected for an ISO file for a particular RPA, a comment will appear describing
the problem. To proceed to the next step in the wizard, you must resolve all errors. Once
errors are resolved, click Retry to revalidate the communication statuses.
Figure 186 ISO file distribution summary screen

System diagnostics
System diagnostics are performed for the cluster and the RPAs. By doing so, the system
attempts to validate that the current configuration is appropriate and that
RecoverPoint/SE can successfully operate in the current environment (Figure 187).
The system will confirm that all components are OK and that no errors or warnings exist. If
errors are detected, you must correct them to be able to continue. If warnings are
detected, it is recommended to fix them before you continue.
If errors and warnings are found in the cluster system diagnostics, they are presented by
Level and Description.
If errors and warnings are found in the RPA system diagnostics, they are presented by
Level, RPA, and Description.
Once errors and warnings are resolved, click Refresh to rerun the system diagnostics
process.
Figure 187 System diagnostics screen

Save system files

Before applying the upgrade, you must save a configuration file and export a system
modifications file to Customer Support, if relevant (Figure 188).
Save configuration file

A configuration file is required to apply the upgrade. Specify a path and file name to save
the configuration file. By default, the file name is ndu_input.properties.
Export modifications (if relevant)

The system you are upgrading may have modifications. They may need to be applied to
the system before you apply the upgrade.
Specify a path and file name to save a system modifications file. By default, the file name
is ndu_mod.properties.
One of the following results may occur regarding the system modifications file:
◆ If no modifications are found, a message will appear stating that no file was created
and saved. You can continue and apply the upgrade without the need to import a
system modifications file.
◆ If modifications are found, they are saved to a file. You must submit the file to EMC
Customer Support and wait for a response before applying the upgrade.
IMPORTANT
You must submit this file in an Upgrade Service Request to Customer Support for analysis.
In the request, indicate that the attached file needs to be reviewed for a pending upgrade,
and indicate the intended date of the upgrade. Recommended severity is no higher than
3. Allow at least 5 business days for a response from Customer Support before performing
the Apply upgrade configuration step of the wizard. This time frame is to allow Customer
Support to analyze the files, research the contents, and respond to you.
When provided with the option to continue:

◆ If you select the Apply upgrade now checkbox and click Next, the system takes you to
“Apply upgrade configuration” on page 219.
◆ If you leave the Apply upgrade now checkbox clear and click Finish, the Upgrade
Cluster Wizard will close.

Figure 188 Save system files screen
Apply upgrade configuration

If you have already prepared the RPA cluster for upgrade and finished the wizard on “Save
system files” on page 216, and are now attempting to apply the upgrade to a prepared
RPA cluster after having selected Apply Upgrade on “Select upgrade step” on page 204,
continue here. If continuing from “Save system files” on page 216, go to “Apply upgrade
Enter RecoverPoint login credentials, load configuration file, and import modifications
file, if relevant (Figure 189):

RecoverPoint administrator credentials

Enter RecoverPoint administrator username and password.
Note: Administrator username and default password = admin.

Configuration file
This file is required to resume the upgrade.
◆ If you have the file, enter the path and file name you used in “Save configuration file”
on page 216.
◆ If you do not have the file, you must open Deployment Manager again, run Upgrade
RecoverPoint/SE, select Prepare for Upgrade step, and create a configuration file.
Import modifications file (if relevant)

If a modifications file was provided to you by Customer Support, you must import it now.
Enter path and file name of the file.
If Customer Support instructed you to not import a file, or if no system modifications were
found, you can continue without importing a modifications file by clearing the
Modifications file checkbox. Click Yes when the No system modifications file imported
window appears.
IMPORTANT
The system modifications file is important for the upgrade to complete successfully.
Continue only if you are sure that you do not need to import a file.
Figure 189 Apply/Resume upgrade configuration screen


If applying an upgrade configuration as a continuation from “Save system files” on
page 216, continue here. If not, continue to “Cluster diagnostics” on page 220.
Import system modifications file (if relevant)

If a system modifications file was provided to you by Customer Support, you must import
it now. Enter path and file name of the file (Figure 190).
window appears.
IMPORTANT
Figure 190 Apply upgrade configuration screen

Cluster diagnostics
The results of the environment diagnostics test are displayed on this screen. If warnings
or errors are found, they will be displayed in the table (Figure 191).
IMPORTANT
It is strongly recommended to resolve these warnings and error before proceeding. Failure
to do so may lead to disruption in replication or production downtime during a disaster,
and other possible issues during normal operation.
If no warnings or errors are found, Cluster diagnostics completed successfully will be

displayed.
Before clicking Next, note that applying the upgrade may take a number of hours to
complete, depending on the size of the environment you are upgrading (number of RPAs,
number of consistency groups, number of volumes, and so on).
When ready to apply the upgrade, click Next.
Figure 191 Cluster diagnostics screen

Apply upgrade summary

The system performs pre-apply preparations, applies the upgrade to all RPAs, finishes
applying the upgrade, and verifies that the RecoverPoint/SE setup was upgraded
completely (Figure 192).
During this step the system goes into maintenance mode. While in this mode the
RecoverPoint GUI becomes read-only. The GUI can only be used to monitor the system and
modifications cannot be made.
Once upgrade is completed, the system exits maintenance mode and automatically
performs SAN Diagnostics.
Figure 192 Apply/Resume upgrade summary screen

Collect system information

If the wizard is unable to apply the upgrade to an RPA, a Collect system information dialog
box appears (Figure 193). In this screen, you should enter FTP server information, to which
the system information (logs) gathered from the RPA will automatically be saved.
The system information is saved to a TAR file. The file name will automatically be
appended with the IP address of the RPA from which the system information is collected
(example filename: sysInfo-l1-l2-r1-r2-splitters-from-l1-r1-2012.09.28.05.50.00.tar).
IMPORTANT
The file should be submitted to EMC Customer Support to allow them to analyze the file,
research the content, and assist you in successfully completing the upgrade.
To improve response time, it is highly recommended to collect and save the Deployment
Manager logs (found in <Deployment Manager unzip location>/logs) to the FTP server.
Figure 193 Collect system information screen
Post-upgrade activities
Perform the following post-upgrade activities:
◆ “Ensuring upgrade is successful” on page 222
◆ “Configure connectivity (if relevant)” on page 223
◆ “Post-deployment requirements” on page 223
Ensuring upgrade is successful

To ensure that the upgrade is successful, open Unisphere for RecoverPoint to verify that
all system components (splitters, RPAs, and volumes) are functioning properly, and
consistency groups are running on the same RPAs as before the upgrade.

Configure connectivity (if relevant)

To ensure your system can be properly supported, you should configure the system
reports mechanism (preferred method is ESRS) for the RPA cluster. For details on how to
configure system reports, refer to the EMC RecoverPoint Administrator’s Guide of the
release to which you are upgrading.
Post-deployment requirements
After upgrading the RecoverPoint/SE system, you must complete the RecoverPoint
Post-Deployment Form, located in the RecoverPoint/SE Upgrade Kit.

Recovery policy
The Upgrade RPAs Wizard supports auto-recovery. Therefore, if a step fails anywhere in
the procedure, running the wizard again will automatically continue the procedure from
where the step failed.
Some failures (such as an RPA that goes down) may require manual intervention (such as
starting up an RPA) before rerunning the wizard.
Logs
Logs of operations are stored in the following locations:
◆ Prepare for Upgrade logs are named and found in:
<unzip_location>/logs/ndu_prepare.log
◆ Apply/Resume Upgrade logs are named and found in:

<unzip_location>/logs/ndu_apply.log
◆ Previously run wizard logs (Prepare and Apply [or Resume]) are found in:
<unzip_location>/oldlogs/*.log
◆ Current account settings (such as licensing information) is saved to a CLI script file
before the upgrade is applied. This file can be used to recreate the system
configuration. The file is named and found in:
<unzip_location>/logs/account_settings.cli

Upgrade RPAs Wizard

To upgrade RPAs to the latest RecoverPoint 4.0, 3.5, 3.4, 3.3, and 3.2 releases from
RecoverPoint 3.1 and later, you must use the Upgrade RPAs Wizard. The procedure is
presented here.
Introduction
RecoverPoint Deployment Manager 2.0 SP1 contains the Upgrade RPAs Wizard, a
Java-based GUI wizard that allows you to perform non-disruptive upgrades of RPA
software. The Wizard is composed of two flows — Prepare for Upgrade, which must be
completed first, and Apply Upgrade, which must be completed second.
The Prepare for Upgrade wizard guides you through the verification of RecoverPoint
credentials and downloads ISO files to all RPAs in the environment. The Apply Upgrade
wizard applies the upgrade to all RPAs.
While the upgrade procedure does not upgrade RecoverPoint splitters (host-based,
VNX/CLARiiON, SANTap, Brocade, Symmetrix, and VPLEX), a RecoverPoint environment
can simultaneously support splitters from two adjacent releases (for example, a 4.0
environment can support both a 4.0 VNX splitter and a 3.5 SP1 P2 VNX splitter). However,
EMC strongly advises you to upgrade splitters to the same RecoverPoint release to gain the
latest splitter functionalities and features.
Note: The upgrade procedure may take a number of hours to complete, depending on the
ISO file distribution, network speed, and size of environment being upgraded.
IMPORTANT
As of RecoverPoint 4.0, the following splitters types are no longer supported in a
RecoverPoint environment: host-based, SANTap, and Brocade.

Launch Deployment Manager

To launch Deployment Manager:
1. Open the RecoverPoint_DM.exe application file.
to the internet.
step 1 on page 225.
3. You are prompted to choose which RecoverPoint release you would like maintain, or
upgrade from (Figure 195).
Upgrade RPAs Wizard 225

4. Select RecoverPoint 3.5 or earlier releases and click Next.
Launch Upgrade RPAs Wizard

To launch the Upgrade RPAs Wizard:
IMPORTANT
Selecting Upgrade RecoverPoint/SE is intended for RecoverPoint/SE customers running
3.5 or later code that have chosen to perform an upgrade on their own. EMC personnel
should upgrade RecoverPoint/SE using the Other operations (EMC personnel) option.

2. On the wizard selection screen, select Upgrade RPAs Wizards - Prepare for Upgrade
(Figure 197).
Note: The Prepare for Upgrade wizard must be run and completed before running the
Apply Upgrade wizard.

Prepare for upgrade

Before using the Upgrade RPAs Wizard, ensure the following conditions are met
(Figure 198):
◆ The computer that the wizard is run from must be able to communicate with the site
management IP and all RPA management (LAN) networks on both sites. Ensure that
ports 21, 22, and 8082 (all TCP) are open on the computer to enable communication
with all RPAs.
◆ All RPAs are running 3.1 releases, at minimum, and 3.5 releases, at maximum.
IMPORTANT
If upgrading to release 3.5 or later, all RPAs must be Gen4 or later.
If upgrading to a 3.4 release, all RPAs must be Gen3 or later.
◆ You have RecoverPoint login credentials (installation and CLI).

◆ If planning to download an ISO file from an FTP server:
• You have at least one 3.2 SP2 or later ISO file available on the FTP server.
• You have FTP access from all RPAs and you have FTP server credentials.
◆ If planning to download an ISO file from a DVD or USB device:
• You have at least one 3.5 or later ISO file available on the device.
◆ If upgrading to 3.5 or later — You have removed reservations support for consistency
groups that have Reservations Policy=SCSI-2. For the procedure, see “Removing
SCSI-2 reservations support” on page 246.
◆ If upgrading to a release earlier than 3.5 — You have disabled reservations support for
consistency groups that have Reservations Policy=SCSI-2. For the procedure, see
“Verify and disable reservations support” on page 246.
not have Internet connectivity, you must have an Upgrade Change Management XML
file available locally to complete the upgrade.
◆ Note: If upgrading to 4.0 or later, during the upgrade process your existing
RecoverPoint licenses will be converted automatically to temporary ELMS licenses.
At the end of the upgrade process, you will be presented with instructions on how to
request a new permanent ELMS license.
Select the I have fulfilled the conditions for upgrading the RPAs checkbox and click Next.

Figure 198 Prepare for upgrade screen
Login credentials
Enter login credentials to connect to the RPAs (Figure 199):
IP credentials
Enter a site management IP address or an RPA IP address.
RecoverPoint login credentials

RecoverPoint CLI credentials

Enter RecoverPoint CLI username and password.
Only required when upgrading from 3.1.
Note: CLI username and default password = admin.


Review the statuses of the RPAs in the system (Figure 200).

ISO file distribution
EMC Online Support credentials

Enter EMC Online Support site credentials (username and password) to provide you with
the relevant Upgrade Change Management information required to complete the upgrade
(Figure 201).
If you do not have Internet connectivity, select the Use an offline Upgrade Change
Management XML file checkbox and load the XML file into the wizard from a local folder
where you have saved the file.
IMPORTANT
To obtain the XML file, you must open an Upgrade Service Request with Customer Support
(severity level 3). In the request, ask for the latest Upgrade Change Management XML file
for the RecoverPoint Deployment Manager, and indicate the intended date of the upgrade.
The file will be provided within one (1) business day as an email attachment, so ensure a
valid email address is provided. Once provided, the file must be used within 30 days of
delivery; any use of the file after 30 days will not be supported by EMC.


Choose an option on how to distribute the ISO file to the RPAs.
IMPORTANT
The ISO files available for use in this wizard can be accessed by clicking “Downloads” on
the “RecoverPoint CL” or “RecoverPoint SE” page on EMC Online Support.
The following options are available (in Figure 202, “Upload from local machine” is
selected):
Note: When upgrading RPAs running releases earlier than 3.5, “Download from FTP server”
is the only available option for ISO file downloads. When upgrading RPAs running 3.5 or
IMPORTANT
For all options, the ISO file name must be the exact name as it appears on the
RecoverPoint “Downloads” section on EMC Online Support, and identical for all options
on both sites (if performing a two-site upgrade). Renaming the file may prevent the
upgrade from working properly.


(Only available when upgrading RPAs already running 3.5 or later)
Enter the file name of the ISO file that you located on your local machine (the computer
Continue to “Upgrade change management” on page 234.

(Only available when upgrading RPAs already running 3.5 or later)
If all of the RPAs being upgraded have DVD/USB devices inserted in them, select the
I have a DVD/USB inserted in all of the RPAs checkbox. This enables Deployment Manager
to automatically download the ISO files to the RPAs at the site once you click Next.
Continue to “Upgrade change management” on page 234.

Enter FTP credentials of an FTP server where the RecoverPoint ISO file is located to
download it to the RPAs (Figure 202).

◆ FTP server IP address
◆ FTP username
◆ FTP password
Note: If you have set up a default directory, either place a slash in the File location
field or leave it blank. If you have not set up a default directory, enter the entire path to
the file in the File location field.
rel4.0_f.226_release_emc_
md5_4955be5f9ee8a2f93b Once all information has been entered, click Next to begin the download and distribution
86bc95e6c8b154 of the ISO file(s) to the RPAs.
Continue to “FTP credentials summary” on page 234.


Review the status of the FTP connectivity results (Figure 203).
Note: This screen appears only if you selected Download from FTP server for one or more
sites in “ISO file information” on page 232.
Figure 203 FTP credentials summary screen
Upgrade change management

Once the ISO file is distributed to the RPAs, the wizard analyzes which release you are
upgrading from and which release you are upgrading to. Based on this analysis, the wizard
presents you with a list of general upgrade messages and Upgrade Change Management
procedures that must be completed before continuing the upgrade (Figure 204).
IMPORTANT
Failure to complete each procedure may cause the upgrade to fail and data to be lost.
General upgrade messages

These messages are relevant to all upgrades, regardless of what release you are upgrading
from or to.

These procedures are unique to the RecoverPoint/SE system you are upgrading. That is,
the procedures displayed are relevant to the release from which you are upgrading and to
the release to which you are upgrading.
you would like to view the information in another program ().

Figure 204 Upgrade change management procedures screen
Figure 205 Upgrade change management message dialog box

ISO file distribution summary

Review the status of the ISO file distribution results (Figure 206).
Beside the site name is an indication of the ISO distribution option you selected (local
machine, USB/DVD, or FTP).
If you selected:
◆ Upload from local machine, the file distribution starts automatically. However, once
download begins, you can click Stop to stop the download.
◆ Copy from DVD or USB device inserted in the RPAs:
• and selected the checkbox, the file distribution starts automatically.
• and did not select the checkbox, you must click Start to begin downloading the file.
◆ Download from FTP server, the file distribution starts automatically.
The system verifies the ISO file download and distribution to all RPAs and confirms that
they are OK or that errors are detected.
If errors are detected for an ISO file for a particular RPA, a comment appears describing the
problem. To proceed to the next step in the wizard, you must resolve all errors. Once errors
are resolved, click Retry to revalidate the communication statuses.
Figure 206 ISO file distribution summary screen

System diagnostics
System diagnostics are performed for the site(s) and the RPAs. By doing so, the system
attempts to validate that the current configuration is appropriate and that RecoverPoint
can successfully operate in the current environment (Figure 207).
The site system diagnostics presents the following results: Level, Site, and Description.
The RPA system diagnostics presents the following results: Level, RPA, Site, and
Description.
The system confirms that all components are OK and that no errors or warnings exist. If
errors are detected, you must correct them to be able to continue. If warnings are
detected, it is recommended to fix them, if relevant, before you continue, even though the
system allows you to ignore them and continue the upgrade.
Once errors and warnings are resolved, click Refresh to rerun the system diagnostics
process.
Figure 207 System diagnostics screen
Save system files

Before applying the upgrade, you must save a configuration file and export a system
modifications file to Customer Support, if relevant (Figure 208).
Save configuration file

A configuration file is required to apply the upgrade.
Specify a path and file name to save the configuration file.
By default, the file name is ndu_input.properties.

Export modifications (if relevant)

The system you are upgrading may have modifications. They may need to be applied to
the system before you apply the upgrade.
Specify a path and file name to save a system modifications file.
By default, the file name is ndu_mod.properties.
◆ If no modifications are found, a message appears stating that no file was created and
saved. You can continue and apply the upgrade.
◆ If modifications are found, they are saved to a file. You must submit the file to EMC
Customer Support and wait for a response before applying the upgrade.
IMPORTANT
You must submit this file in an Upgrade Service Request to Customer Support for analysis.
In the request, indicate that the attached file needs to be reviewed for a pending upgrade,
and indicate the intended date of the upgrade. Recommended severity is no higher than
3. Allow at least 5 business days for a response from Customer Support before performing
the Apply upgrade configuration step of the wizard. This time frame is to allow Customer
Support to analyze the files, research the contents, and respond to you.
When provided with the option to continue:

◆ If you select the Apply upgrade now checkbox and click Next, the system takes you to
“Apply upgrade configuration” on page 241.
◆ If you leave the Apply upgrade now checkbox clear and click Finish, the Upgrade RPAs
Wizard closes.
Figure 208 Save system files screen


If applying an upgrade configuration after launching the Upgrade RPAs Wizard - Apply
Upgrade wizard from the Deployment Manager wizard selection screen, continue here. If
continuing from “Save system files” on page 237, continue to “Apply upgrade
Apply/Resume upgrade configuration (Figure 209).
Enter login credentials, load configuration file, and import modifications file (if relevant):

RecoverPoint CLI credentials

Enter RecoverPoint CLI username and password.
Only required when upgrading from 3.1.
Note: CLI username and default password = admin.
Load saved configuration file

This file is required to resume the upgrade.
◆ If you have the file, enter the path and file name you used in “Save configuration file”
on page 237 of the Prepare for Upgrade wizard.
◆ If you do not have the file, you must run the Upgrade RPAs Wizard - Prepare for
Upgrade wizard.

If a modifications file was provided to you by Customer Support, you must import it now.
Enter path and file name of the file.
window appears.
IMPORTANT



If applying an upgrade configuration as a continuation from “Save system files” on
page 237, continue here. If not, continue to “Environment diagnostics” on page 242.
Apply upgrade configuration (Figure 210).

If a system modifications file was provided to you by Customer Support, you must import it
now. Enter path and file name of the file.
window appears.
IMPORTANT

Environment diagnostics
The results of the environment diagnostics test are displayed on this screen (Figure 210).
If warnings or errors are found, they are displayed in the table.
IMPORTANT
It is strongly recommended to resolve these warnings and error before proceeding. Failure
to do so may lead to disruption in replication or production downtime during a disaster,
and other possible issues during normal operation.
If no warnings or errors are found, Environment diagnostics completed successfully is

displayed.
Before clicking Next, note that applying the upgrade may take a number of hours to
complete, depending on the size of the environment you are upgrading (number of RPAs,
number of consistency groups, number of volumes, and so on).
When ready to apply the upgrade, click Next.
Figure 211 Environment diagnostics screen

Apply upgrade summary

The system performs pre-apply preparations, applies the upgrade to all RPAs, finishes
applying the upgrade, and verifies that the RecoverPoint setup was upgraded completely
(Figure 212).
During this step the system goes into maintenance mode. While in this mode the
RecoverPoint GUI becomes read-only. The GUI can only be used to monitor the system and
modifications cannot be made.
Once upgrade is completed, RecoverPoint exits maintenance mode and automatically
Figure 212 Apply upgrade summary screen

Collect system information

If the Wizard is unable to apply the upgrade to an RPA (or pair of RPAs, in the event of a
two-site configuration), a Collect system information dialog box appears (Figure 213). In
this screen, you should enter FTP server information, to which the system information
(logs) gathered from the RPA (or RPA pair) is automatically saved.
The system information is saved to a TAR file (or two TAR files for a two-site configuration).
The file name is automatically appended with the IP address of the RPA (or RPAs) from
which the system information is collected (example filename:
sysInfo-l1-l2-r1-r2-splitters-from-l1-r1-2012.09.28.05.50.00.tar).
IMPORTANT
The file(s) should be submitted to Customer Support, to allow them to analyze the file(s),
research the content, and assist you in successfully completing the upgrade.
To improve Customer Support response time, it is highly recommended to collect and save
the Deployment Manager logs (found in <Deployment Manager unzip location>/logs) to the
FTP server.
Figure 213 Collect system information screen
Post-upgrade requirements
Perform the following post-upgrade activities:
◆ “Ensuring upgrade is successful” on page 245
◆ “Re-enabling reservations support (if relevant)” on page 245
◆ “Configure connectivity (if relevant)” on page 245
◆ “Updating license (if relevant)” on page 245
◆ “Post-deployment requirements” on page 245

Ensuring upgrade is successful

To ensure that the upgrade is successful, use the RecoverPoint GUI (or for those who have
upgraded to 4.0, the Unisphere for RecoverPoint GUI) to verify that all system components
are functioning properly, and consistency groups are running on the same RPAs as before
the upgrade.
Re-enabling reservations support (if relevant)

If upgrade was successful and reservations support for consistency groups was disabled
in “Verify and disable reservations support” on page 246, go to each of the consistency
groups and enable reservations support by selecting the Reservations Support checkbox
in the Advanced section of the Policy tab of the consistency group.
Configure connectivity (if relevant)

To ensure the system can be properly supported, you should configure the system reports
mechanism (preferred method is ESRS) for each RPA cluster. For details on how to
configure system reports, refer to the EMC RecoverPoint Administrator’s Guide of the
release to which you are upgrading.
Updating license (if relevant)

After performing a major upgrade (for example, from release 3.5.x to release 4.0.x), the
previous license is automatically converted to the new license format. However, the new
license is temporary and valid for 90 days from the date of upgrade. After that, you must
install one or more permanent license files to replicate with RecoverPoint.
Refer to the EMC RecoverPoint Administrator's Guide for detailed instructions on
upgrading the license.
Refer to the EMC RecoverPoint Release Notes for information on the licensed features for
the release.
Post-deployment requirements
After upgrading the RecoverPoint system, you must complete the RecoverPoint
Recovery policy
The Upgrade RPAs Wizard supports auto-recovery. Therefore, if a step fails anywhere in the
procedure, running the Wizard again automatically continues the procedure from where
the step failed.
Some failures (such as an RPA that goes down) may require manual intervention (such as
starting up an RPA) before rerunning the Wizard.

Logs
Logs of operations are stored in the following locations:
◆ Prepare for Upgrade logs are named and found in:
<unzip_location>/logs/ndu_prepare.log
◆ Apply/Resume Upgrade logs are named and found in:
<unzip location>/logs/ndu_apply.log
◆ Previously run wizard logs (Prepare and Apply [or Resume]) are found in:
<unzip location>/oldlogs/*.log
◆ Current account settings (such as licensing information) is saved to a CLI script file
before the upgrade is applied. This file can be used to recreate the system
configuration. The file is named and found in:
<unzip location>/logs/account_settings.cli
Removing SCSI-2 reservations support

If upgrading to RecoverPoint 3.5 or later, the Upgrade RPAs Wizard does not support such
an upgrade when the system contains consistency groups with SCSI-2 reservations policy
enabled.
To continue, complete one of these procedures:
When the Host server is running a Windows 2000 or Windows 2003

Cluster:
1. Upgrade your Host OS into Windows 2008 Cluster.
2. Verify that your attached SAN Array supports SCSI-3 commands for the replicated
LUNs.
3. Change the consistency group Reservations Policy value from SCSI-2 to Auto.
4. Restart the upgrade process using RecoverPoint Deployment Manager.
When the Host Server is running Windows 2008:

1. Verify that your attached SAN Array supports SCSI-3 commands for the replicated
LUNs.
2. Change the consistency group Reservations Policy value from SCSI-2 to Auto.
3. Restart the upgrade process using RecoverPoint Deployment Manager.
IMPORTANT
Failure to complete this procedure will prevent the Deployment Manager Upgrade RPA
Wizard from being able to upgrade the RPA software code to release 3.5 and later.
Verify and disable reservations support

If upgrading to a release earlier than 3.5, the Upgrade RPAs Wizard does not support
upgrade of consistency groups with SCSI-2 reservations policy enabled. You must verify
and disable reservations support before performing the upgrade procedure.
Use the procedure below to verify and disable reservations support for consistency groups
that have Reservations Policy=SCSI-2.

1. Verify reservations policy of a consistency group:

a. In the Navigation Pane of the RecoverPoint GUI, select and expand a consistency
group under Consistency Groups.
b. Select a copy under the group, click its Policy tab in the Component Pane, and
expand the Advanced section.
If Reservation Policy equals SCSI-2, continue to step 2 on page 247.
If Reservation Policy does not equal SCSI-2, repeat step b on page 247 for another
copy in the same group.
If you have checked all the copies of the group, and none of the copies have
Reservation Policy=SCSI-2, continue to step 4 on page 247 .
2. Record the name of the consistency group that has at least one SCSI-2-enabled copy,
as you will need this information when enabling reservations support after the
upgrade procedure.
3. Disable reservations support for the consistency group:
a. Select the consistency group which has at least one copy with Reservation
Policy=SCSI-2 and click its Policy tab in the Components Pane.
b. Expand the Advanced section and clear the Reservations Support checkbox.
4. Repeat this procedure, beginning from step 1 on page 247, for each consistency
group.
Note: For information about reservations policy settings, refer to the “Copy Advanced
Policy Settings” table in the “Starting Replication” chapter of the EMC RecoverPoint
Administrator’s Guide.
IMPORTANT
Once the upgrade is complete, enable reservations support for groups that you
disabled before upgrade.


Environment Conversion
CHAPTER 9
This chapter explains how to convert a system to a RecoverPoint/SE or RecoverPoint

system using the RecoverPoint Deployment Manager. Instructions are provided for the
following procedures:
◆ Converter Wizard................................................................................................... 250
249
Converter Wizard
The Converter Wizard helps you non-disruptively convert a 3.4 SP1 or later environment to
a RecoverPoint/SE or RecoverPoint (RecoverPoint/CL and RecoverPoint/EX) configuration
from a single management point. The conversion is done without replication downtime,
full sweep, or journal loss.
About the Converter Wizard

Unlike other wizards in RecoverPoint 4.0, the Converter Wizard is used to convert both RPA
clusters of a RecoverPoint/SE system (or a single RPA cluster for a one-site system).
Launch Converter Wizard

To launch the Converter Wizard:
to the internet.
step 1 on page 250.


Access the Wizard

2. On the wizard selection screen, select Converter Wizard (Figure 215).

Choose Converter Type

Select the converter you want to use (Figure 216):
Convert to RecoverPoint/SE
Select this wizard to convert a RecoverPoint/SE environment that was not installed with
the RecoverPoint/SE Installer Wizard to a state that can benefit from all the
RecoverPoint/SE capabilities (such as integration with EMC Unisphere).
Note: Once you convert a RecoverPoint/SE environment to a RecoverPoint

(RecoverPoint/CL and RecoverPoint/EX) environment, you cannot use this wizard to
convert it back to a RecoverPoint/SE environment.
Continue from “Prerequisites (when converting to RecoverPoint/SE)” on page 254.
Convert to RecoverPoint
Select this wizard to convert a RecoverPoint/SE environment that was installed with the
RecoverPoint/SE Installer Wizard to a RecoverPoint (RecoverPoint/CL and
RecoverPoint/EX) environment. After you complete this wizard, you must upgrade the
RecoverPoint/SE license to a RecoverPoint license (RecoverPoint/CL and RecoverPoint/EX)
to benefit from all the RecoverPoint capabilities (such as bandwidth reduction).
Continue from “Prerequisites (when converting to RecoverPoint)” on page 263.
Figure 216 Choose converter type screen

Prerequisites (when converting to RecoverPoint/SE)

Before continuing, ensure the following conditions are met on the RecoverPoint/
SE environment you are converting (Figure 217):
◆ All RPAs in the system must be physical RPAs.

◆ There is only one VNX/CLARiiON splitter per cluster.
◆ There are no more than two RPA clusters in the system.
◆ RPAs and host initiators are not in the same storage group.
◆ All RPAs are part of the cluster in the same storage group.
◆ For each RecoverPoint storage group, there are two paths from each RPA to each SP (if
directly attached, one path from each RPA to each SP is sufficient).
◆ VNX/CLARiiON credentials in all clusters are configured in the RecoverPoint/SE system
settings before running the conversion.
◆ There is a RecoverPoint/SE compatible license.
◆ All Unisphere and RecoverPoint GUIs are closed.
Select the I have fulfilled the conditions for converting my system checkbox, and click
Next to continue.
IMPORTANT
Unisphere does not support RecoverPoint/SE environments using host-based splitters.
Therefore, if such splitters exist in the environment, before continuing with the conversion,
close Unisphere and remove the host-based splitters from RecoverPoint.

Login credentials
Enter the RecoverPoint cluster management IP address and login credentials to connect
to the cluster (Figure 218).
z

password is admin.



Verify the storage configuration at each site.
Verify the storage configuration at site 1.

scope.
Figure 220 VNX/CLARiiON login credentials screen


◆ Deployment Manager can communicate with VNX/CLARiiON SP A and SP B.

Figure 221 VNX/CLARiiON login status screen

SAN diagnostics
configuration is appropriate for the RPA and that RecoverPoint can successfully operate
in the current SAN environment (Figure 222).
Description.
Figure 222 SAN diagnostics

Storage groups diagnostics

(Figure 223).
For a proper RecoverPoint/SE installation, all storage groups that contain RPA initiators
should not contain initiators of any other RPAs or hosts.
When initiator types are not registered properly for the RecoverPoint/SE installation, the
storage groups are shown with the improperly registered initiator types, as follows:
◆ Hosts — The WWNs are not RPA WWNs and should not be in the same storage group as
RPA WWNs.
◆ Improper RPAs — The RPA WWNs are not registered properly in the storage group
(initiator type is not “RecoverPoint Appliance”).
◆ Other cluster RPAs — The RPA WWNs are of RPAs from a different RPA cluster and
should not be in the same storage group as the RPAs of this cluster.
Once errors are resolved, click Refresh to rerun the storage groups diagnostics process.
Figure 223 Storage groups diagnostics

Apply changes
◆ Prepares the system for conversion.
◆ Converts RPAs.
◆ Finishes the system conversion.
◆ Verifies that the system was converted.
During this stage, the system goes into maintenance mode. While in this mode, the
RecoverPoint Management Application becomes read-only. The GUI can only be used to
monitor the system and modifications cannot be made.
Once conversion is completed, RecoverPoint exits maintenance mode and automatically
or that errors are detected.
resolved, click Retry to reapply settings and revalidate that the conversion is successful.

Summary
The wizard indicates when you have completed conversion of the environment to
a RecoverPoint/SE configuration (Figure 225).
Displayed at the bottom of the screen are the new initiator names created by Deployment
Manager in the VNX/CLARiiON storage groups.
IMPORTANT
The new initiator names have a different naming convention than the existing
RecoverPoint initiator names in the storage group. To ensure proper RecoverPoint/SE
functioning with Unisphere, do not change or remove these new initiator names.
You can now begin to benefit from all the RecoverPoint/SE capabilities (such as
integration with EMC Unisphere).

Prerequisites (when converting to RecoverPoint)

If converting to a RecoverPoint (RecoverPoint/CL and RecoverPoint/EX) environment as a
continuation from “Choose Converter Type” on page 271, continue here:
Before continuing, ensure the following conditions are met on the RecoverPoint/
SE environment you are converting (Figure 226):
◆ All RPAs in the system must be physical RPAs.

◆ There are no SAN diagnostic errors or warnings in the system.
Select the I have fulfilled the conditions for converting my environment checkbox, and

Login credentials
Enter the RecoverPoint cluster management IP address and login credentials to connect
to the cluster (Figure 227).
z

password is admin.



SAN diagnostics
configuration is appropriate for the RPA and that RecoverPoint can successfully operate
in the current SAN environment (Figure 229).
Description.
Figure 229 Storage configuration - SAN diagnostics screen

Apply changes
◆ Converts RPAs.
RecoverPoint Management Application becomes read-only. The GUI can only be used to
monitor the system and modifications cannot be made.

Summary
The wizard indicates when you have completed conversion of the environment to a
RecoverPoint configuration (Figure 231).
IMPORTANT
You must now upgrade the existing RecoverPoint/SE license to a RecoverPoint license
(RecoverPoint/CL or RecoverPoint/EX) to benefit from full RecoverPoint functionality (such
as support for additional capacity). For further information, refer to the “Managing


Access the Wizard

2. On the wizard selection screen, select Converter Wizard (Figure 233).

Choose Converter Type

Select the converter you want to use (Figure 234):
Convert to RecoverPoint/SE
Select this wizard to convert a RecoverPoint/SE environment that was not installed with
the RecoverPoint/SE Installer Wizard to a state that can benefit from all the
RecoverPoint/SE capabilities (such as integration with EMC Unisphere).
Note: Once you convert a RecoverPoint/SE environment to a RecoverPoint

(RecoverPoint/CL and RecoverPoint/EX) environment, you cannot use this wizard to
convert it back to a RecoverPoint/SE environment.
Continue from “Prerequisites (when converting to RecoverPoint/SE)” on page 272.
Convert to RecoverPoint
Select this wizard to convert a RecoverPoint/SE environment that was installed with the
RecoverPoint/SE Installer Wizard to a RecoverPoint (RecoverPoint/CL and
RecoverPoint/EX) environment. After you complete this wizard, you must upgrade the
RecoverPoint/SE license to a RecoverPoint license (RecoverPoint/CL and RecoverPoint/EX)
to benefit from all the RecoverPoint capabilities (such as bandwidth reduction).
Continue from “Prerequisites (when converting to RecoverPoint)” on page 280.
Figure 234 Choose converter type screen

Prerequisites (when converting to RecoverPoint/SE)

Before continuing, ensure the following conditions are met on the RecoverPoint/SE
environment you are converting (Figure 235):
◆ All RPAs are running release 3.4 SP1 or later.
◆ RPAs and host initiators are not in the same storage group.
◆ All RPAs are part of the cluster in the same storage group.
◆ For each RecoverPoint storage group, there are two paths from each RPA to each SP (if
directly attached, one path from each RPA to each SP is sufficient).
◆ There is only one VNX/CLARiiON storage system per site.
◆ There is only one VNX/CLARiiON splitter per site.
◆ VNX/CLARiiON credentials in all sites are configured in the RecoverPoint/SE system
settings.
◆ There is a RecoverPoint/SE compatible license.
Note: The wizard verifies that all prerequisites are met and issues an error if a prerequisite
is not met.
IMPORTANT
Unisphere does not support RecoverPoint/SE environments using host-based splitters.
Therefore, if such splitters exist in the RecoverPoint environment, before continuing with
the conversion, close Unisphere and remove the host-based splitters from RecoverPoint.

Login credentials
Enter a site management or an RPA IP address and RecoverPoint/SE login credentials to
IP credentials
RecoverPoint/SE login credentials
Enter a RecoverPoint/SE username and password. For username boxmgmt, the default


scope.
Figure 237 Storage configuration - VNX/CLARiiON login credentials


settings. The system attempts to log in to the VNX/CLARiiON array and validates the
◆ Deployment Manager can communicate with VNX/CLARiiON SP A and SP B.
Figure 238 Storage configuration - VNX/CLARiiON login status

SAN diagnostics
Description.
Figure 239 Storage configuration - SAN diagnostics

Storage groups diagnostics

(Figure 240).
For a proper RecoverPoint/SE installation, all storage groups that contain RPA initiators
should not contain initiators of any other RPAs or hosts.
When initiator types are not registered properly for the RecoverPoint/SE installation, the
storage groups are shown with the improperly registered initiator types, as follows:
◆ Hosts — The WWNs are not RPA WWNs and should not be in the same storage group as
RPA WWNs.
◆ Improper RPAs — The RPA WWNs are not registered properly in the storage group
(initiator type is not “RecoverPoint Appliance”).
◆ Other cluster RPAs — The RPA WWNs are of RPAs from a different RPA cluster and
should not be in the same storage group as the RPAs of this cluster.
Once errors are resolved, click Refresh to rerun the storage groups diagnostics process.
Figure 240 Storage configuration - Storage groups diagnostics

Apply changes
◆ Converts RPAs.
RecoverPoint Management Application GUI becomes read-only. The GUI can only be used
to monitor the system and modifications cannot be made.

Summary
RecoverPoint/SE configuration (Figure 242).
Displayed at the bottom of the screen are the new initiator names created by Deployment
Manager in the VNX/CLARiiON storage groups.
IMPORTANT
The new initiator names have a different naming convention than the existing
RecoverPoint initiator names in the storage group. To ensure proper RecoverPoint/SE
functioning with Unisphere, do not change or remove these new initiator names.
You can now begin to benefit from all the RecoverPoint/SE capabilities (such as
integration with EMC Unisphere).

Prerequisites (when converting to RecoverPoint)

If converting to a RecoverPoint (RecoverPoint/CL and RecoverPoint/EX) environment as a
continuation from “Choose Converter Type” on page 271, continue here:
Before continuing, ensure the following conditions are met on the RecoverPoint/SE
environment you are converting (Figure 243):
◆ All RPAs are running release 3.4 SP1 or later.
◆ There are no SAN diagnostic errors or warnings in the system.
◆ You have a valid RecoverPoint license (RecoverPoint/CL or RecoverPoint/EX) to benefit
from full RecoverPoint functionality (such as support for additional capacity).

Login credentials
Enter a site management or an RPA IP address and RecoverPoint/SE login credentials to
IP credentials
RecoverPoint/SE login credentials
Enter a RecoverPoint/SE username and password. For username boxmgmt, the default

SAN diagnostics
Description.
Figure 245 Storage configuration - SAN diagnostics

Apply changes
◆ Converts RPAs.
RecoverPoint Management Application GUI becomes read-only. The GUI can only be used
to monitor the system and modifications cannot be made.

Summary
RecoverPoint configuration (Figure 247).
You must now upgrade the existing RecoverPoint/SE license to a RecoverPoint license
(RecoverPoint/CL or RecoverPoint/EX) to benefit from full RecoverPoint functionality (such
as support for additional capacity). For further information, refer to the “Managing

Modification
CHAPTER 10
Modification
This chapter explains how to modify the settings of an existing RecoverPoint/SE or

RecoverPoint RPA cluster or system using the RecoverPoint Deployment Manager.
Instructions are provided for the following procedures:
◆ Cluster or System Modification Wizard .................................................................. 286
285
Modification
Cluster or System Modification Wizard

The Modification Wizard helps you non-disruptively modify the settings of a
RecoverPoint/SE or RecoverPoint (RecoverPoint/CL and RecoverPoint/EX) system (3.5.x) or
cluster (4.0 or later) from a single management point. The procedure is done without
replication downtime, full sweep, or journal loss.
About the Modification Wizard

As of RecoverPoint 4.0, the Modification Wizard allows you to modify settings one RPA
cluster at a time. Therefore, if the system is composed of multiple RPA clusters, you must
modify the settings of each cluster by running the wizard on each cluster in the system.
Launch Modification Wizard

To launch the Modification Wizard:
1. Launch the Deployment Manager by opening the RecoverPoint_DM.exe application
file.
to the internet.
– If you click Yes, the Deployment Manager closes and your browser window
opens to a direct link on EMC Online Support where a zip file of the latest
Deployment Manager is available for download. Download and extract the file,
then perform step 1 on page 286.

Modification

Starting in RecoverPoint 4.0, maintenance operations, such as modification of settings,
are performed on one cluster at a time. To modify settings of another cluster in a system,
you must log into that cluster using another instance of the Cluster Modification Wizard.
Access the Wizard


Modification
2. On the wizard selection screen, select Cluster Modification Wizard (Figure 260).

Modification
Prerequisites
◆ All RPAs are up and attached to their cluster.
◆ If modifying virtual RPAs:
• CHAP credentials for RPA iSCSI ports and storage iSCSI ports must be different.
• connection sets must be configured between the VNX iSCSI ports and virtual RPAs.
Select the I have fulfilled the conditions for modifying the system settings checkbox,

Modification
Login credentials
the cluster (Figure 251).

Modification
Configuration file
The Cluster Modification Wizard allows you to select one of the following (Figure 252):
◆ Create a new cluster modification configuration file
The system creates a new cluster modification configuration file. The configuration
settings of the existing RPAs are added to the configuration file. The system uses
these settings to complete the cluster modification.
location is C:\Users\<username>\RecoverPoint\ MOD_config.properties.
◆ Continue a modification from a saved cluster configuration file
The system loads the settings from a previously saved cluster modification
configuration file. The system allows you to complete the cluster modification using
this file.

Modification
The current environment settings of the cluster are displayed. Modify the values that you
General
◆ Cluster name — Name of the cluster being modified.
◆ Number of RPAs — Cannot be modified.
Connectivity
◆ For LAN:
• IP type — Cannot be modified.
• MTU — Default value is 1500 (do not modify unless instructed to do so).
◆ For WAN:
Environment
◆ Domain name — The cluster domain name.
◆ Primary DNS server — The IP address of the primary DNS server for the cluster.
◆ Secondary DNS server — The IP address of the secondary DNS server for the cluster.
◆ NTP server — The IP address of NTP server for the cluster.
◆ Secondary NTP servers — Cannot be modified.

Modification
Cluster IPs
The current cluster IP configurations and RPA IP settings are displayed. Modify the values
you want to change (Figure 265).
Cluster management — LAN, based on IP type entered when the cluster was installed.
Interface netmask — LAN and WAN, based on IP type entered in “3. Environment settings”
on page 23.
RPA — IP addresses of the cluster RPAs, based on IP type entered when the cluster was
installed.
recommended to assign RPA 1 and RPA 2 (site control RPAs) to the latest hardware types
(Gen5), to improve system function and performance.
Default gateways
Default gateway — Based on IP type entered when the cluster was installed.
Figure 254 Cluster IPs screen

Modification

This screen appears only if the RPA cluster is composed of virtual RPAs (vRPAs).
The current RPA cluster iSCSI settings are displayed. Modify the values you want to change
(Figure 255).
Connectivity
◆ For iSCSI 1
◆ For iSCSI 2
Figure 255 Cluster iSCSI settings screen

Modification
RPA iSCSI ports

The current cluster iSCSI IP configurations and RPA iSCSI IP settings are displayed. Modify
the values you want to change (Figure 256).
Interface netmask — Cannot be modified.
RPA — iSCSI 1 and iSCSI 2 IP addresses of the cluster RPAs, based on IP type entered when
the cluster was installed.
Default gateways
Default gateway — Based on IP type entered when the cluster was installed.
Additional gateways
Figure 256 RPA iSCSI ports screen

Modification
Storage iSCSI ports

The current storage CHAP and iSCSI IP configurations are displayed. Modify the values you
CHAP credentials
Figure 257 Storage iSCSI ports screen

Modification
Summary
Once you have completed modifying the settings of the cluster, you can start using
Unisphere for RecoverPoint (Figure 258).

Modification

Access the Wizard
2. On the wizard selection screen, select System Modification Wizard (Figure 260).

Modification
Prerequisites
◆ The computer that the wizard is run from must be able to communicate with all RPA
management (LAN) networks on both sites.
◆ RPAs are running release 3.5 or later.
◆ All RPAs are up and attached to their cluster.
Select the I have fulfilled the conditions for modifying the system settings checkbox,
Login credentials

Modification
◆ IP credentials
◆ RecoverPoint login credentials
Enter a RecoverPoint username and password.
For username boxmgmt, the default password is boxmgmt.
Configuration file
The System Modification Wizard allows you to select one of the following (Figure 252):
◆ Create a new system modification configuration file
The system creates a new system modification configuration file. The configuration
settings of the existing RPAs are added to the configuration file. The system uses
these settings to complete the system modification.
location is C:\Users\<username>\RecoverPoint\ cmd_config.properties.
◆ Continue a modification from a saved system configuration file
The system loads the settings from a previously saved system modification
configuration file. The system allows you to complete the system modification using
this file.

Modification
Modify the structure of the environment and the site settings (Figure 253).
• One site — Continuous Data Protection (CDP) at a single site
• Two sites — Continuous Remote Replication (CRR), Concurrent Local and Remote
data protection (CLR), or CDP on two sites.
◆ Number of RPA per site — 2-8
To install more than two RPAs per site, RecoverPoint/SE 3.3 SP1 or later must be
• Private for one site configuration and two site configuration over FC.
• WAN for two site configuration over IP.

Modification

site.
You can define one or two external NTP servers for the RecoverPoint/SE configuration;
two NTP servers provide greater time accuracy. If you are installing two sites, you can
will synchronize with the RPA with the NTP server settings. Though not mandatory, it is
highly recommended to set at least one NTP server, as it will ensure that all
RecoverPoint/SE components are synchronized with an external NTP source.
Sites
Modify the site IP configurations and the RPA IP settings (Figure 265).
IP Settings (Either Private or WAN, IPv4 or IPv6)
◆ Subnet mask

Modification
Management Settings (Either IPv4, IPv6, or both IPv4 and IPv6)

◆ Subnet mask
◆ Default gateway
◆ Site management IP
RPAs IP settings (All RPA must be on the same network, per site)
◆ Management IP address for each RPA
◆ WAN or Private IP address for each RPA
◆ MTU value for each RPA
Figure 265 Sites screen

Modification
Apply system modifications

During this stage of the wizard (Figure 266), the system performs:
◆ pre-modification actions
◆ system modifications (LAN only)
◆ system modifications
◆ post-modification actions
Figure 266 Apply system modifications screen
Summary
Once you have completed modifying the system settings of the RecoverPoint environment,
you can start using the RecoverPoint Management Application (Figure 258).

Other Operations
CHAPTER 11
Other Operations
This chapter presents RecoverPoint operations that are performed outside the scope of
RecoverPoint Deployment Manager. The topics include:
◆ Power down and power up RPA ............................................................................. 306
◆ Changing system parameters ................................................................................ 307
◆ Verifying time synchronization .............................................................................. 309
◆ Verifying management access ............................................................................... 311
◆ Removing Kashya Reservation Manager support.................................................... 312
305
Other Operations
Power down and power up RPA

This section details how to power down and power up one or more RecoverPoint
Appliances (RPAs) in the recommended sequence.
When this procedure should be used

Use this procedure when:
◆ Following a reboot or power up, switches, RPAs, or hosts do not see the storage LUNs.
◆ Following a reboot or power up, RPAs or hosts do not see the switches or storage LUNs.
◆ Following a reboot or power up, hosts do not see the RPAs, switches, or storage LUNs.
Powering down RPAs

If shutting down all or multiple RPAs, it is recommended that all consistency groups (CGs)
running on the RPAs be paused or disabled, which is a disruptive operation to replication.
When shutting down only one RPA, the “preferred RPA” of the CGs running on the RPA can
usually be moved to one of the other RPAs in the cluster, negating the need to pause and
disable the CG.
The power off sequence of the RPAs does not matter. The power down sequence of host,
switches, RPAs and arrays does matter if you are going to power off the entire
environment, in which case the following order should be followed:
1. Shutdown host/applications.
2. Disable/Pause consistency groups.
3. Shutdown RPAs (boxmgmt user/Shutdown/Reboot operations/Shutdown RPA).
Note: If shutting down an RPA running a version prior to 3.3 that is attached to the
cluster, then using the shutdown RPA command may sometimes result in an RPA
reboot instead. To shut down the RPA so that it stays down, first detach the RPA from
its cluster: boxmgmt user/Cluster operations/Detach from cluster.
4. Shutdown arrays.
5. Shutdown fabric switches.
Powering up RPAs
To power up RPAs, simply reverse the order to power up (at Step 2 on page 306,
enable/unpause the CGs).
To power up the RPAs, plug them in or turn them on using the power button on the front of
the unit.
When you power up the RPA or RPAs, do so one-at-a-time starting with RPA1 and work your
way up until all RPAs are powered up.
Unless the RPAs have been manually detached or there are issues that caused them to go
into reboot regulation, then the RPAs will join the already designated cluster per the
repository selection that should already be defined.

Other Operations
Changing system parameters

As of release 3.5, RecoverPoint Deployment Manager has a Modification Wizard to help
you non-disruptively modify the settings of a system of up to two clusters (3.5.x) or an
individual cluster (4.0 or later) from a single management point. The procedure is done
without replication downtime, full sweep, or journal loss. For details, see “Cluster or
System Modification Wizard” on page 286.
For releases earlier than 3.5, the RecoverPoint system must initialize again whenever
system parameters are modified. Such modifications may include: changing RPA,
gateway, or subnet IP address, or disabling a consistency group while an application is
still writing to the volumes in the group.
The procedure presented here describes how to avoid full sweep initialization when
changing system parameters. The time and resource expense of this process is trivial
compared to a full sweep.
If a site name or time zone is modified, the repository volume must be reformatted. A full
sweep initialization is then required, and the procedure documented here will not be
relevant.
To change system parameters:
1. Ensure all RPAs are working correctly:
a. In the RPA tab of the RecoverPoint GUI, ensure that all RPAs have green check
marks in the RPA Status column.
b. If any error conditions exist, correct them before continuing.
2. In the Policy tab of each consistency group in the RecoverPoint GUI, record the value of
the Preferred RPA for that group. This value will be used to restore the RPA values at
the end of this procedure.
3. Ensure that Preferred RPA=RPA 1 for each consistency group. Click Apply for any
Preferred RPA that you change.
4. In the RecoverPoint GUI, for each enabled group, verify that the title of the Status tab
includes “Running on RPA 1.” If the group is not enabled, check in the Policy tab that
the Preferred RPA = RPA 1.
5. In the Installation Manager, log in as user boxmgmt using the IP address of RPA 2 at
site 1.
6. Detach RPA 2 at site 1 from the RPA cluster by selecting Cluster Operations > Detach
from cluster.
7. Select Setup > Modify, and then select and modify the parameters you want to modify.
8. Apply the changes by selecting Setup > Apply.
9. Reattach RPA 2 at site 1 by selecting Cluster Operations > Attach to Cluster.
The RPA restarts.
10. Log in again to the RecoverPoint GUI. In the RPA tabs, ensure that all RPAs have green
check marks in the RPA Status column.
11. In the Installation Manager, log in as user boxmgmt using the IP address of RPA 2 at
site 2.
Changing system parameters 307

Other Operations
12. Detach RPA 2 at site 2 from the RPA cluster by selecting Cluster Operations > Detach
from cluster.
13. Copy the system parameters from RPA 2 at site 1 by selecting Setup > Get remote
settings, and follow the instructions on screen.
14. Apply the changes by selecting Setup > Apply.
15. Reattach RPA 2 at site 2 by selecting Cluster Operations > Attach to Cluster.
The RPA restarts.
16. Log in again to the RecoverPoint GUI. In the RPA tabs ensure that all RPAs have green
check marks in the RPA Status column.
17. For all enabled consistency groups, set Preferred RPA value to RPA 2.
No user action is required if consistency groups continue to run on RPA 1.
18. Repeat steps 11–16 for RPA 1 at site 1.
19. Repeat steps 11–16 for RPA 1 at site 2.
20. In the RecoverPoint GUI, restore the RPA values to their previous settings.
On the Policy tab of each consistency group, set Preferred RPA to the value you
recorded in Step 2 on page 307.

Other Operations
Verifying time synchronization

It is important that the timing of all RecoverPoint activities across all RPAs in a
RecoverPoint installation be synchronized with an NTP server or servers, or the internal
clock of RPA 1 at site 1. Setting two NTP servers provide the greatest level of time accuracy.
Follow the procedure in this section to verify that all RPAs are synchronized with an NTP
server or servers.
To verify that the each RPA is synchronized:
1. Use an SSH client to log in to the Installation Manager (boxmgmt) using the
management IP address of each RPA.
2. At the prompt, login as user boxmgmt with password boxmgmt (default).
The Main menu of the Installation Manager appears.
3. From the Main menu, select Diagnostics > Synchronization diagnostics.
Output similar to the following appears:
remote refid st t when poll reach delay offset jitter
====================================================================
*ntp_server 192.116.202.203 3 u 438 1024 377 0.337 12.971 6.241
The symbol in the left margin displays the synchronization status of each NTP server:
• * — The NTP server with which this RPA is synchronizing.
• + — An NTP server with which the RPA is willing to synchronize.
• x — An NTP server which is not for synchronization.
When the RPA is not synchronized with an external NTP server or the internal clock, the
RPA that is designated as the NTP server will appear instead of the address of the
ntp_server.
When the RPA is synchronized to its internal clock (that is, there is no external NTP
server), LOCAL (0) will appear instead of the address of the ntp_server.
• LOCAL(0) — The values obtained from the internal clock on the local RPA.
The column headings are:
• remote — Host names or addresses of the servers and peers used for
synchronization
• refid — Current source of synchronization
• st — The stratum
• t — The type (u = unicast, m = multicast, l = local, - = unknown)
• when — Time (in secs) since the NTP server was last heard
• poll — Poll interval (in secs)
• reach — Status of the reachability register (see RFC-1305) in octal
• The remaining output show the latest delay, offset, and jitter (all in milliseconds)
Verifying time synchronization 309

Other Operations
4. Verify that the ntp_server name has an asterisk.

If there is an asterisk, proceed to step Step 5 on page 310.
If there is no asterisk, proceed as follows:
a. Wait 30 minutes and select Synchronization diagnostics again.
b. If the offset is greater than 5000 for an RPA at a site where the NTP server is not
configured, or if the site is site 2 in an installation where an external NTP is
configured at site 1, detach and reattach this RPA.
c. Wait 30 minutes and reselect Synchronization diagnostics.
Note: Waiting time may take more than 30 minutes. The delay is largely dependent
upon connection speed.
d. If the problem persists, it likely indicates that a networking problem is preventing

NTP synchronization. Take action to correct the networking problem.
Note: If the RPA is not synchronizing with an NTP server, it does not prevent you
from completing installation of the RPA and operating the RecoverPoint system.
The impact on system operation is a possible lack of synchronization between log
events from the different RPAs.
5. Verify clock synchronization for each RPA in your RecoverPoint system.

Other Operations
Verifying management access

After completing system installation for the first time and verifying that all clocks are
synchronized, verify that you can access the management interface using both the
RecoverPoint Management Application GUI and the CLI.
Note: To use the Management Application GUI to perform activities such as adding and
attaching splitters, adding volumes, and configuring consistency groups, you must first
install the RecoverPoint license, as described in the EMC RecoverPoint Administrator’s
Guide.
Using the RecoverPoint GUI

To verify access using the RecoverPoint GUI:
1. Open a web browser to the site management IP of one of the sites.
2. Log in as user admin or monitor.
The main window of the Management Application GUI appears.
3. Click RPA in the Navigation Pane and verify that green check marks appear in the
Status and Connectivity columns of each RPA in the system.
Using the RecoverPoint CLI

To verify access using the RecoverPoint CLI:
1. Using an SSH client, open a session by connecting to the site management IP of one of
the sites.
2. Log in as user admin or monitor.
The system returns the CLI prompt.
3. Type a CLI command.
For example, type the help command to display the complete list of CLI commands, or
type the get_system_settings command to display the site management, RPA
management, and IP addresses for each site (which should match those you set
during installation).
Verifying management access 311

Other Operations
Removing Kashya Reservation Manager support

The RecoverPoint host-based splitter (KDriver) provides an integrated Kashya Reservation
Manager component (KRM) that enables SCSI-2 support for Windows 2003 (or earlier)
Cluster deployments with or without third-party storage arrays. However, as of
RecoverPoint 3.5, the host-based splitter no longer supports SCSI-2 reservation policy.
Note: As of RecoverPoint 4.0, the host-based splitter is no longer supported in a

RecoverPoint environment. Therefore, this procedure is not relevant when using release
4.0 and later.
Perform this procedure to enable the host-based splitter to function in RecoverPoint 3.5
and overcome the absence of SCSI-2 support:
1. Upgrade to Windows 2008 Cluster any Windows 2003 (or earlier) Cluster node that is
configured with the RecoverPoint host-based splitter.
2. Verify that your storage array supports and is configured to use SCSI-3 commands.
3. Change the current consistency group copy settings value from Reservations
Policy=SCSI-2 to Reservations Policy=Auto.
You are now ready to upgrade your RPAs and host-based splitters to release 3.5.
IMPORTANT
Failure to complete this procedure will prevent the Deployment Manager Upgrade RPA
Wizard from being able to upgrade the RPA software code to release 3.5 and later.

Splitters
CHAPTER 12
Splitters
There are three types of RecoverPoint splitter technology, based on where the splitter
software is deployed: host-based, array-based, or fabric-based. The sections covered in
this chapter include:
◆ Array-based splitters ............................................................................................. 314
◆ Host-based splitters (KDrivers) .............................................................................. 315
◆ Fabric-based splitters............................................................................................ 323
313
Splitters
Array-based splitters
This section mentions how to deploy EMC RecoverPoint with storage array-based splitters
to deliver a complete data replication solution without host-based agents.
Note: As of RecoverPoint 4.0, array-based splitters are the only type of splitter supported
in a RecoverPoint environment.
VNX/CLARiiON
The EMC VNX series arrays and the CLARiiON CX3 and CX4 Series arrays support a
RecoverPoint array-based splitter. This splitter is commonly referred to as the
VNX/CLARiiON splitter. To deploy RecoverPoint with these arrays and splitter, refer to the
EMC RecoverPoint Deploying with VNX/CLARiiON Arrays and Splitter Technical Notes.
Symmetrix
The EMC Symmetrix VMAX10K array supports a RecoverPoint array-based splitter when
using RecoverPoint 3.4 SP1 and later. The VMAX Series arrays (10K, 20K, and 40K)
support a RecoverPoint array-based splitter when using RecoverPoint 3.5 and later. This
splitter is commonly referred to as the Symmetrix splitter. To deploy RecoverPoint with
these arrays and splitter, refer to the EMC RecoverPoint Deploying with Symmetrix Arrays
and Splitter Technical Notes.
VPLEX
The EMC VPLEX virtual storage platform supports a RecoverPoint array-based splitter when
using RecoverPoint 3.5 and later. This splitter is commonly referred to as the VPLEX
splitter. To deploy RecoverPoint with the VPLEX platform and splitter, refer to the EMC
RecoverPoint Deploying with VPLEX Technical Notes.

Splitters
Host-based splitters (KDrivers)

IMPORTANT
As of RecoverPoint 4.0, the host-based splitter is no longer supported in a RecoverPoint
environment. Therefore, this section is not relevant when using release 4.0 and later.
Install a KDriver on each host that runs an application that writes data to storage, and
where the data is also intended for replication (replication volumes). The primary purpose
of the KDriver is to “split” application writes to their normally designated storage volumes
and to the RPA. EMC personnel will download the KDriver software along with the main
RecoverPoint components.
Installing KDrivers
You can install the KDriver on machines running Windows, Solaris, and AIX Operating
Systems (OS). For the most up-to-date and accurate information about supported OS,
consult the EMC Support Matrix on E-Lab™ Navigator: https://elabnavigator.EMC.com.
On a Windows-based machine
Install a KDriver on any Windows-based machine that has access to a volume that is to be
replicated, regardless of whether the machine writes application data to that volume or
not.
To install the KDriver software on a Windows-based machine:
1. If you have not done so already, ensure you have installed Microsoft Visual C++ 2008
Redistributable Package and .NET Framework 3.5. Log in to your host computer; you
must have local administrator rights.
2. Obtain the KDriver installation package appropriate for your RecoverPoint system from
EMC Customer Service and store it on the host computer in a temporary directory.
3. Double-click the KDriver installation package (a zip file) and extract the contents to a
temporary directory.
4. Double-click the setup.exe file.
If the setup program detects an earlier installed KDriver from the RecoverPoint 3.1
family, it offers an upgrade to the current driver. This procedure is presented in
“Upgrading KDrivers” on page 321.
5. Follow the directions on screen. Unless instructed otherwise by EMC Customer
Service, select the Typical installation option.
The installation package runs diagnostic tests of the host configuration for the storage
area network (SAN). Any errors detected must be corrected before continuing.
After correcting errors, continue with the installation according to the instructions. The
default KDriver log size is 300 MB.
On most machines, the default log file location is C:\Program Files\KDriver\log. On
x64-based machines, the default log file location is
C:\Program Files (x86)\KDriver\log.
Host-based splitters (KDrivers) 315

Splitters
In most cases, there is no need to change the log size or log file location. If, however,
you do need to change one of these settings, follow the procedure in “Changing
KDriver parameters” on page 322.
6. Once the installation of the KDriver is complete, select either Yes, I want to restart my
computer now or No, I will restart my computer later, then click Finish.
7. Repeat steps 1–6 for every Windows host, both at the local site and the remote site.
Installing KVSS
The KVSS package is automatically installed when you install either the Windows KDriver
or the stand-alone Kutils package. In either case, it will be necessary to complete the
installation of KVSS components.
To complete the installation of KVSS:
1. Go to the directory that contains the KVSS installation. If you:
Installed the Windows KDriver, the directory will be ../KDriver/KVSS/
Installed the stand-alone Kutils package, the directory will be ../SAKutils/KVSS/
2. In the KVSS directory, run the command:
>kvss.exe install
This command installs the KVSS hardware provider for this host.
On a Solaris-based machine
Install a KDriver on any Solaris-based machine that has access to a volume that is to be
not.
To install the KDriver software on a Solaris-based machine:
1. Log in to the host as user root.
2. Copy the installation package, as downloaded, to a temporary directory on the host.
The installation package is a compressed file with the format extension .gz.
3. Decompress the file by running the command:
gunzip filename
Note: The .gz extension is dropped from the decompressed filename.
4. Install the package by running the command:

pkgadd -d decompressed_filename
When prompted for which package to install, accept the default by pressing Enter.
When queried about continuing with the installation, type yes. This installs all of the
KDriver files in the KDriver directory.

Splitters
5. The system conducts a series of automatic tests designed to identify problems

regarding the host configuration in the SAN environment on which RecoverPoint is
being installed. Upon completion of these tests, the system confirms successful
completion of the SAN diagnostics by reporting no errors or warnings, or details the
errors or warnings detected in the host configuration on the SAN.
Correct any errors before proceeding with the installation.
6. The configure script helps you configure the KDriver by prompting you to enter values
for the following parameters:
• Log files directory (default: /KDriver/log)
• Log files maximum size (default: 500 MB)
7. To complete installation of the KDriver:
• For first-time installation, type the restart command:
reboot -- -r
• If this is not first-time installation, type the start command:

/etc/init.d/kdrv start
Once the command is run, the KDriver automatically loads every time you
subsequently start the machine.
Note: To verify that the KDriver is up, type the status command:
/etc/init.d/kdrv status.
8. Repeat steps 1–7 for all hosts on both sites.
On an AIX-based machine
Install a KDriver on any AIX-based machine that has access to a volume that is to be
not.
To install the KDriver software on an AIX-based machine:
2. Copy the install file, as downloaded, to the root directory (/) on the host.
The install file is a compressed file with the format extension .gz.
3. Decompress the file by running the command:
gunzip filename
The install file is identified by its .bff extension, as the .gz extension is dropped from
the decompressed filename.
4. Install the package by running the command:
installp -d install_file kdriver 2.0.0.0
The installation proceeds automatically, with on-screen report of its progress,

including:
• Pre-installation verification

Splitters
• Installing software
• Summaries
Note: Run all subsequent commands from the root directory.
5. Configure the KDriver by running the command:

rc.kdrv configure
The system first conducts a series of automatic tests designed to identify a variety of
the most common problems regarding the host configuration in the SAN environment
on which RecoverPoint is being installed. It is desirable to identify these problems
before installing the KDriver on the host. Upon completion of these tests, the system
confirms successful completion of the SAN diagnostics by reporting no errors or
warnings, or details the errors or warnings detected in the host configuration on the
SAN. You must correct any errors before proceeding with the installation.
Continue with the installation only when no errors are reported.
6. The configure script helps you to configure the KDriver by prompting you to enter
values for the following parameters:
• Log files directory (default: /KDriver/log)
Note: The log files directory must be located within the root file system. Writing
logs to any other file system is not supported.
• Log files maximum size (default: 500 MB)
Note: Ensure that the root file system has more free disk space than the log files
maximum size.
7. Start the KDriver by running the command:

rc.kdrv start
8. Repeat steps 1–7 for all hosts on both sites.
Uninstalling KDrivers
You can uninstall the KDriver from machines running Windows, Solaris, and AIX Operating
Systems (OS).
From a Windows-based machine

To uninstall a KDriver from a Windows-based machine:
1. Using the RecoverPoint Management Application GUI or CLI:
a. Detach all volumes from all splitters.
b. Remove all splitters from all hosts.
2. Go to Start > Settings > Control Panel > Add/Remove Programs, select the RecoverPoint
version, and click Remove.
3. Click Remove, then click Next.

Splitters
4. Click OK to uninstall the KDriver.

5. Restart the machine.
As part of the uninstall process of the KDriver, ensure the KDriver directory
C:\Program Files\KDriver is deleted.
If the directory is not deleted, delete it manually; otherwise, the installation process
cannot be completed.
Note: If, before deletion, you want to save the KDriver logs and related information (for
example, for use by EMC Customer Service in troubleshooting a problem), select the
option to save this information, and specify the location to which to save it.
Uninstalling KVSS
To uninstall KVSS:
1. Go to the directory that contains the KVSS installation.
If you installed the Windows KDriver, the directory will be ../KDriver/KVSS/.
If you installed the stand-alone Kutils package, the directory will be ../SAKutils/KVSS/.
2. In the KVSS directory, run the command:
>kvss.exe uninstall
This command uninstalls the KVSS hardware provider for this host.
From a Solaris-based machine

To uninstall a KDriver from a Solaris-based machine:
1. Using the RecoverPoint Management Application or CLI:
3. Stop the KDriver by running the command:
/etc/init.d/kdrv stop
Warning! volumes are currently attached.

1. Stop KDriver, and regulate I/O according to policy for each
volume.
2. Stop KDriver, but allow host to continue writing to RPA
replication volumes.
3. Stop KDriver, and halt all host access to RPA replication volumes.
4. Cancel.
Note: The KDriver will not restart automatically upon reboot of the
host.
To restart the KDriver, run the /etc/init.d/kdrv start command.
how would you like to proceed? (1,2,3,4)
If you choose option 1, a warning appears stating “This may impede operation of the
host operation, and may also necessitate a full resynchronization for some volumes.”

Splitters
This action stops the KDriver and, according to the policy of each volume, either
prevents host I/O writes to the volume or allows host I/O writes to the volume.
If you choose option 2, a warning appears stating “This will necessitate a full
resynchronization.”
This action stops the KDriver and allows host I/O writes to the volumes.
host operation.”
This action stops the KDriver and prevents host I/O writes to the volumes.
Choose one of the options and select yes to continue.
4. Remove the KDriver package by running the command:

pkgrm kdriver
5. Restart the host by running the command:

reboot -- -r.
From an AIX-based machine

To uninstall a KDriver from an AIX-based machine:
1. Using the RecoverPoint Management Application or CLI:
3. Stop the KDriver by running the command:
rc.kdrv stop
The following appears:

Warning! volumes are currently attached.
1. Stop KDriver, and regulate I/O according to policy for each
volume.
2. Stop KDriver, but allow host to continue writing to RPA
replication volumes.
3. Stop KDriver, and halt all host access to RPA replication volumes.
4. Cancel.
Note: The KDriver will not restart automatically upon reboot of the
host.
To restart the KDriver, run the rc.kdrv start command.
how would you like to proceed? (1,2,3,4)
host operation, and may also necessitate a full resynchronization for some volumes.”
This action stops the KDriver and, according to the policy of each volume, either
prevents host I/O writes to the volume or allows host I/O writes to the volume.
If you choose option 2, a warning appears stating “This will necessitate a full
resynchronization.”

Splitters
This action stops the KDriver and allows host I/O writes to the volumes.
host operation.”
This action stops the KDriver and prevents host I/O writes to the volumes.
Choose one of the options and select yes to continue.
4. Remove the KDriver package by running the command:

rc.kdrv uninstall
Upgrading KDrivers
You can upgrade the KDriver on machines running Windows, Solaris, and AIX Operating
Systems (OS).
On a Windows-based machine
When the setup program detects that a RecoverPoint 3.0 and later KDriver exists on the
computer, it offers to upgrade to the latest KDriver.
To upgrade the KDriver:
1. Log in to your host computer; you must have local administrator rights.
2. Obtain the KDriver installation package appropriate for your RecoverPoint system from
EMC Customer Service and store it on the host computer in a temporary directory.
3. Double-click the KDriver installation package (a zip file) and extract the contents to a
temporary directory.
4. Double-click the setup.exe file.
5. Click OK.
6. When queried about restarting the computer, select Yes, I want to restart my computer
now, then click Finish.
IMPORTANT
If you select “No, I will restart my computer later”, replication may not function
properly until you restart the computer.
7. After restart, log in again to the host computer.
On a Solaris-based machine
To upgrade the KDriver, you must uninstall the current version and then install the new
version.
On an AIX-based machine
To upgrade the KDriver, you must uninstall the current version and then install the new
version.

Splitters
Changing KDriver parameters

In most cases, there is no need to change the location or size of the log file. In some cases
(for example, when the KDriver is installed on a boot volume, for a boot-from-SAN host), it
is recommended to save the logs in a location other than the default location.
To change the KDriver log file location or log size:
1. Go to Start > Settings > Control Panel > Add/Remove Programs, select the RecoverPoint
version, and click Change or Remove.
2. Click Reconfigure, then click Next.
3. Specify the desired destination folder, then click Next.
4. Specify the log size, then click Next.
Note: Maximum log size is 1 GB.
5. Click Yes to restart the KDriver service.

Splitters
Fabric-based splitters
IMPORTANT
As of RecoverPoint 4.0, fabric-based splitters are no longer supported in a RecoverPoint
environment. Therefore, this section is not relevant when using release 4.0 and later.
This section mentions how to deploy EMC RecoverPoint with intelligent fabric-based
splitter to deliver a complete data replication solution without host-based agents.
SANTap
To deploy RecoverPoint with SANTap services, refer to the EMC RecoverPoint Deploying
RecoverPoint with SANTap and SAN-OS Technical Notes and the EMC RecoverPoint
Deploying RecoverPoint with SANTap and NX-OS Technical Notes.
Brocade
To deploy RecoverPoint with Brocade intelligent-fabric switches, refer to the EMC
RecoverPoint Deploying with the Brocade Splitter Technical Notes.
Fabric-based splitters 323

Splitters

RecoverPoint Installation and Deployment Guide Rev A11

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

RecoverPoint Installation and Deployment Guide Rev A11

Uploaded by

Copyright:

Available Formats

EMC®

Installation and Deployment Guide

Published August, 2013

2 EMC RecoverPoint Installation and Deployment Guide

Chapter 1 Preparing for Deployment

Chapter 2 About Deploying RecoverPoint

Chapter 3 RecoverPoint/SE Installation

EMC RecoverPoint Installation and Deployment Guide 3

RecoverPoint 3.5 or earlier .......................................................................... 65

Chapter 4 RecoverPoint Installation

4 EMC RecoverPoint Installation and Deployment Guide

Storage configuration - Site2Name - Zoning and LUN masking............. 124

Chapter 5 Cluster Connection

Chapter 6 RPA Replacement

EMC RecoverPoint Installation and Deployment Guide 5

System modifications.......................................................................... 158

Chapter 7 RPA Addition

Chapter 8 Upgrade RPA Software

6 EMC RecoverPoint Installation and Deployment Guide

Upgrading to the latest 3.3 release............................................................ 198

Chapter 9 Environment Conversion

EMC RecoverPoint Installation and Deployment Guide 7

Storage configuration.......................................................................... 266

Chapter 11 Other Operations

8 EMC RecoverPoint Installation and Deployment Guide

EMC RecoverPoint Installation and Deployment Guide 9

10 EMC RecoverPoint Installation and Deployment Guide

1 Dual fabric topology .................................................................................................... 22

EMC RecoverPoint Installation and Deployment Guide 11

Conventions used in this document

Note: A note presents information that is important, but not hazard-related.

18 EMC RecoverPoint Installation and Deployment Guide

Where to get help

20 EMC RecoverPoint Installation and Deployment Guide

RecoverPoint is an intelligent data protection and recovery solution that runs on

Preparing for Deployment 21

Fibre Channel (RecoverPoint)

Fibre Channel (RecoverPoint/SE)

Note: In most installations, the storage-to-switch connections already exist.

◆ Each RPA to each fabric.

Figure 1 Dual fabric topology

22 EMC RecoverPoint Installation and Deployment Guide

Figure 2 Direct attach topology

Ethernet/IP for WAN interface

Ethernet/IP for management (LAN) interface

Figure 3 RecoverPoint Gen4 RPA (Dell PowerEdge R610)

Figure 4 RecoverPoint Gen5 RPA (Intel R1000)

24 EMC RecoverPoint Installation and Deployment Guide

Zoning Gen5 and Gen4 RPAs (QLE2564 HBAs)

The following guidelines apply:

◆ Zoning for fabric-based splitters. The zoning requirements for RecoverPoint

26 EMC RecoverPoint Installation and Deployment Guide

Zoning Gen3 RPAs (QLE24xx HBAs)

Zoning Gen1 RPAs (QLA23xx HBAs)

The following guidelines apply:

◆ Zoning for fabric-based splitters. The zoning requirements for RecoverPoint

Connectivity for switchless configurations

28 EMC RecoverPoint Installation and Deployment Guide

Unpacking the RPAs

3.2 and later RPA

Unpacking the RPAs 29

30 EMC RecoverPoint Installation and Deployment Guide

For details on all of the above, refer to “Splitters” on page 313.