RecoverPoint 5.1 Customer Installation and Upgrade Guide
RecoverPoint 5.1 Customer Installation and Upgrade Guide
Version 5.1
Dell 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.“ DELL 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 DELL SOFTWARE DESCRIBED
IN THIS PUBLICATION REQUIRES AN APPLICABLE SOFTWARE LICENSE.
Dell, EMC, and other trademarks are trademarks of Dell Inc. or its subsidiaries. Other trademarks may be the property of their respective owners.
Published in the USA.
Dell EMC
Hopkinton, Massachusetts 01748-9103
1-508-435-1000 In North America 1-866-464-7381
www.DellEMC.com
Tables 5
Preface 7
As part of an effort to improve its product lines, we periodically release 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 technical support professional if a product does not function properly or
does not function as described in this document.
Note
Purpose
This document describes how to install RecoverPoint/SE, connect RPA clusters, and
upgrade RPA software.
Audience
This document is intended for customers who need to perform RecoverPoint/SE
operations using the Deployment Manager.
Related documentation
The following publications provide additional information:
l RecoverPoint Release Notes
l RecoverPoint Deployment Manager Release Notes
l RecoverPoint Customer Installation and Upgrade Guide
l RecoverPoint Installation and Deployment Guide
l RecoverPoint Product Guide
l RecoverPoint Administrator's Guide
l RecoverPoint CLI Reference Guide
l RecoverPoint Performance Guide
l RecoverPoint REST API Programming Guide
l RecoverPoint Security Configuration Guide
l RecoverPoint Simple Support Matrix
In addition to the core documents, we also provide White papers and Technical Notes
on applications, arrays, and splitters.
Typographical conventions
This document uses the following style conventions:
l System code
l System output, such as an error message or script
l Pathnames, filenames, prompts, and syntax
l Commands and options
Technical support
Go to Online Support and click Service Center. You will see several options for
contacting Technical Support. Note that to open a service request, you must
have a valid support agreement. Contact your 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
[email protected].
The Deployment Manager is a tool that guides you in the deployment and upgrade of
classic RecoverPoint systems.
NOTICE
l SolVe Desktop.................................................................................................... 10
l Verifying prerequisites........................................................................................10
l Unpacking and racking RPAs...............................................................................11
l Rear panel description........................................................................................ 12
l Connecting RPAs................................................................................................13
l NTP server......................................................................................................... 14
l Zoning................................................................................................................ 15
l LUN mapping......................................................................................................16
l Multiple WWNs...................................................................................................16
SolVe Desktop
Customer procedures on SolVe Desktop are now customer viewable. SolVe Desktop
gathers critical information from existing content to generate a concise procedural
document.
To download and authorize:
Procedure
1. Go to online support: https://support.emc.com/.
2. Search for SolVe Desktop.
3. Click the executable and download.
4. Follow the prompts to install.
5. Accept the End User License Agreement.
6. Click Not yet authorized for content.
7. Click Authorize and download list of available products.
8. Click OK.
9. Click OPEN.
10. Open the SolVe Desktop (Start > All Programs > EMC SolVe Desktop > EMC
SolVe Desktop) and click the RecoverPoint icon to update or install the
content.
After you finish
For feedback and questions, send an email to: mailto:%[email protected].
Verifying prerequisites
Procedure
1. Download the RecoverPoint Customer Installation Kit:
a. At https://support.emc.com, select Downloads.
b. In the Type a Product Name field, enter RecoverPoint SE.
c. Click RecoverPoint Customer Installation Kit to download it.
2. Collect the infrastructure data in "IP & SAN Setup Details Templates"
(Appendix A).
3. Ensure the following items are available:
Virtual Four Ethernet cables per ESX server (LAN, WAN, iSCSI1, iSCSI2)
4. Ensure that you have a dedicated computer running Windows workstation with
Java™ 8 (or later), 32-bit.
5. Ensure that your workstation can communicate with the management (LAN)
networks for the RPAs at both sites. If communication from the workstation to
both sites is not possible, you can perform the deployment independently at
each site.
6. Ensure that TCP ports 21, 22, 8081, and 8082 are open on your workstation. To
enable log retrieval from the array-based splitter, ensure that TCP port 443
(HTTPS) is open to each storage array.
To verify that these ports are open, you can use Telnet: telnet <IP_address>
<port #>
N M F L
Item Control/Indicator/Port Purpose
A 1 Gbe BMC Management Dedicated BMC service port
SP system LEDs
Top to bottom:
l Do not remove - White
l System power applied - Blue
l SP service - Blue (good)/Amber (fault)
Connecting RPAs
Procedure
1. Connect the RPA Fibre Channel ports.
Option Description
Dual-fabric Connect one RPA Fibre Channel port to Fabric A and a
topology different RPA Fibre Channel port to Fabric B on each RPA.
For example, connect odd-numbered RPA ports (1, 3) to
Fabric A and even-numbered ports (0, 2) to Fabric B.
Note
Direct attach Connect one RPA Fibre Channel port to Storage Processor
topology to A, and a different RPA Fibre Channel port to Storage
midrange Processor B. Connect the remaining RPA Fibre Channel
storage arrays ports to the other RPA in the cluster.
Direct attach A RecoverPoint cluster can support up to two Xbricks.
topology to The RecoverPoint cluster must have exactly two RPAs.
XtrermIO Every RPA must be connected to all storage controllers.
Connecting RPAs 13
Preparing for customer installation
NOTICE
A dual fabric configuration is required at all clusters for RPA, host, and storage
connectivity.
Option Description
1 Attach an external computer using a console cable to the RPA serial
port.
2 Attach an external computer using an Ethernet crossover cable to the
RPA WAN port.
localhost.localdomain login:
Password:
If the login prompt does not appear, press Enter until it does.
NTP server
Network Time Protocol (NTP) synchronizes the clocks across all of the machines that
are attached to a particular installation.
Best practice is to configure an external NTP server, running on Linux machines,
before RecoverPoint installation.
When an external NTP server is configured at a site, the first RPA in a cluster at that
site synchronizes to the external NTP server. All other RPAs in all clusters of the
RecoverPoint system synchronize to the first RPA. To increase the accuracy of the
time, you may type secondary external NTP server addresses.
Best practice is that the first RPA you install is one of the RPAs at the site at which
the NTP server is configured. Designate this RPA as RPA 1 in this cluster.
If you are not using an external NTP server, the first RPA that you install at site 1, RPA
1, uses its internal clock as an NTP server. This RPA serves as the NTP server for all
RPAs in the system. In this scenario, although all RPAs in the installation are internally
synchronized, they may not necessarily keep correct time.
Zoning
Zoning must adhere to the guidelines.
RPA HBA ports as both initiators and targets
Best practice is to use the RPA HBA ports as both initiators and targets.
If you must zone RPA HBA ports separately either in the initiator zone or in the
target zone, you observe only minor differences in performance and availability.
However, initiator-target separation is not supported when:
l Mixing different splitter types in the same site
l Using remote replication over Fibre Channel
l Using distributed consistency groups
Zone members
The best practice is to zone RPA Fibre Channel 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 exist as part of the SAN implementation. Confirm that these zones
exist. Single-initiator zoning is required.
RPA-to-storage zones
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 RPAs and storage. This practice applies to all splitters.
RecoverPoint with Unity, VNXe, or VNX using SE licenses - On each fabric, there
should be a zone for each RPA, which includes:
l One HBA port of that RPA
l One port for each Unity/VNX/VNXe storage processor (SP A and SP B)
RecoverPoint with XtremIO - Create one zone per fabric and include all RPA Fibre
Channel ports and all XtremIO Storage Controller ports in that fabric.
Zoning 15
Preparing for customer installation
LUN mapping
RecoverPoint operation requires proper LUN mapping at each site.
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.
l Repository and all journal volumes must be exposed to all RPA ports in the fabric.
l For LUN mapping instructions when using a specific splitter, refer to the Technical
Notes for that splitter.
NOTICE
RecoverPoint supports the mixing of splitters within an RPA cluster at a site, and
the mixing of storage systems with which RPA clusters are deployed within the
same RecoverPoint system, subject to certain limitations. Refer to the relevant
RecoverPoint Release Notes.
l LUN mapping should be done during RecoverPoint installation. The best practice is
to avoid changing the LUN mapping after installation. If changes must be made
later, follow the instructions in the 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 the boxmgmt menus under Setup > Modify settings.
Virtual RPAs (vRPAs) can be deployed on RecoverPoint. If you are creating vRPAs,
deploy the OVF template.
Creating vRPAs 17
Creating vRPAs
vRPA Less than 256 VMs 256+ VMs 256+ VMs 256+ VMs
performance Low performance Low Medium High
profile performance performance performance
Virtual CPUs 2 2 4 8
RAM 4 GB 8 GB 8 GB 8 GB
VMDK capacity 35 GB 35 GB 35 GB 35 GB
When using 4CPU/8GB or 8CPU/8GB configurations to run vRPA, the best practice is
to reserve all RAM for RecoverPoint.
Procedure
1. In the vSphere Web Client, right-click an ESXi host and select Deploy OVF
Template....
2. In the Select source screen, specify the vRPA OVF package location.
3. In the Review details screen, review the general properties of the OVF
template. To accept, click Next.
4. In the Accept License Agreements screen, if you accept the terms of the End-
User License Agreement, click Accept and Next.
5. In the Select name and folder screen, type a name for this vRPA and select a
folder or data center.
If you type the name of an existing vRPA, you are not permitted to continue.
6. In the Select configuration screen, select the desired vRPA performance
profile.
7. If prompted to select a resource, in the Select a resource screen, select a
cluster, host, or resource pool.
8. In the Select storage screen, select a disk format, storage policy, and high-
performance data store (best practice) to host the vRPA virtual machine files.
All ESXi hosts in the cluster where the vRPAs reside must share the data store
where the repository VMDK resides.
9. In the Setup networks screen, select a destination network for the
RecoverPoint Management Network, and select an IP protocol.
10. In the Customize template screen, type these vRPA LAN settings: IP address,
subnet mask, and gateway.
Follow instructions on the screen for using DHCP or static IP addresses
depending on the network adapter topology.
11. The Ready to Complete screen summarizes all the selections. Select Power on
after deployment. To create the vRPA, click Finish.
The Deploying vRPA screen appears, showing the progress.
12. To create additional vRPAs, repeat this procedure.
Results
When the vRPA is created, the vRPA Summary tab shows the vRPA package
contents as specified. The selected IP policy is implemented automatically when the
vRPA is powered on.
Customer installation 21
Customer installation
Option Description
Create a new To save your settings to a file in case you need to
installation repeat this installation.
configuration file By default, the file name and directory location is C:
\Users\<username>\RecoverPoint
\RPSE_config.properties.
File name cannot contain the following characters: \/
*?“:<>|
Create or continue If you previously saved a configuration file, to load the
an installation from saved settings as defaults for this installation.
a saved
configuration file
the RPA, use boxmgmt to change the network adapter topology, and
reattach the RPA to the cluster. Repeat for all RPAs in all clusters.
IP type
IP type must be the same for all clusters.
MTU
Default value is 1500 (do not modify unless instructed to do so).
Domain name
The cluster domain name is optional.
When IP addresses are provided by DHCP and an RPA reboots, the RPA will
acquire a new IP address from the DHCP server. If the DHCP server is not
available, the RPA will not be able to return to the operational state; therefore it
is recommended to supply redundant, high-available DHCP servers in the
network when using the DHCP option.
If both control RPAs in the cluster reboot and are assigned new IP addresses,
operations cannot resume unless the repository is available.
NOTICE
14. Also on the Cluster iSCSI settings screen, enter the iSCSI settings for RPAs.
MTU — Default value is 1500 (do not modify unless instructed to do so).
If replicating midrange storage volumes over iSCSI, select the Configure CHAP
credentials for the RPAs iSCSI ports checkbox and enter the CHAP
credentials.
15. The RPA iSCSI ports screen appears only if you are replicating virtual
machines. Follow instructions on screen.
Default gateway
Cannot be modified.
Add route
To add additional gateways.
16. On the EMC Online Support credentials screen, select how to obtain the
RecoverPoint software and Installation Change Management information:
Option Description
If you have Enter EMC Online Support login credentials.
Internet
connectivity…
If you do not have Select Use an offline Change Management XML file
Internet and browse to a local version of the file. To obtain an up-
connectivity… to-date XML file for offline installation, browse to
https://rplicense.emc.com/download. This page provides
an option to download or email the a-cca.xml file. If this
option is not available, 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. The file must be used within
30 days.
Option Description
Not authenticated, not Communication between RPAs is not
encrypted authenticated nor encrypted.
Authenticated and RPAs use certificates to authenticate each other
encrypted before communicating, and all communication
between RPAs is encrypted.
21. On the Security configuration screen, select the Local users' security level.
Option Description
Basic Minimum five characters.
High Minimum eight characters, including two lower case, two upper case,
and two non-alphabetical (digits or special characters). Change
passwords immediately.
22. If deploying with VNX storage, the Storage Registration screen appears.
Follow instructions on screen.
Authentication scope
Select whether the scope of the user account is Global, Local, or LDAP.
Default value is Global. For authentication within the local security
directory, specify Global or Local scope.
23. If deploying with VNX storage, the Storage connectivity screen appears.
Resolve any errors that are detected, and click Refresh.
24. If deploying with VNX storage, The VNX/CLARiiON Zoning screen appears
only if you are using physical RPAs. Select an option.
Zoning: Zoning:
RPA 1, Port 0 to Storage Port RPA 1, Port 2 to Storage Port
(SPA, SPB): (SPA, SPB):
zone name RP_London_0_0 vsan 25 zone name RP_ London _0_0 vsan
[pwwn 50:01:24:82:00:92:4a:86] 55
[pwwn 50:06:01:64:3d:e0:0a:99] [pwwn 50:01:24:82:01:b2:4a:86]
[pwwn 50:06:01:6c:3d:e0:0a:99] [pwwn 50:06:01:65:3d:e0:0a:99]
RPA2, Port 2 to Storage Port (SPA, [pwwn 50:06:01:6d:3d:e0:0a:99]
SPB): RPA2, Port 0 to Storage Port (SPA,
zone name RP_ London _1_0 vsan SPB):
25 zone name RP_ London _1_0 vsan
[pwwn 50:01:24:82:00:89:9a:c2] 55
[pwwn 50:06:01:64:3d:e0:0a:99] [pwwn 50:01:24:82:01:a9:9a:c2]
[pwwn 50:06:01:6c:3d:e0:0a:99] [pwwn 50:06:01:65:3d:e0:0a:99]
RPA 1, Port 0 to RPA2, Port 2: [pwwn 50:06:01:6d:3d:e0:0a:99]
zone name RP_London_COMMON_0 RPA 1, Port 2 to RPA2, Port 0:
vsan 25 zone name RP_London_COMMON_0
[pwwn 50:01:24:82:00:89:9a:c2] vsan 55
[pwwn 50:01:24:82:00:92:4a:86] [pwwn 50:01:24:82:01:b2:4a:86]
[pwwn 50:01:24:82:01:a9:9a:c2]
25. If deploying with Unity or VNXe storage, the Storage configuration - Zoning
and LUN masking screen appears. To save this information, click Export to
CSV file.
26. On the SAN diagnostics screen, resolve any errors that are detected. Then,
click Refresh. It is recommended to resolve all SAN discovery warnings.
27. If deploying with VNX storage, on the Select repository option screen, select
an option.
Option Description
Automatic In step 28 on page 27, you will select a resource pool. Minimum
size of a repository volume automatically provisioned is 5.72 GB.
Manual In step 28 on page 27, you will select a LUN. Minimum size is
2.86 GB.
NOTICE
l The RPA formats the repository volume. Ensure that the LUN is new and
does not contain any valuable data.
l The repository volume must be highly available.
l Capacity beyond 5.72 GB (automatic) or 2.86 GB (manual) is not used.
Configure a repository volume on Unity or VNXe storage manually.
l The repository volume may be provisioned on a thin or non-thin LUN.
l The repository volume must be accessible to all RPAs in the cluster.
29. On the Apply storage configuration screen, resolve any errors that are
detected. You may click on an error for more details. When all errors are
resolved, click Retry. If there are errors that you are unable to resolve, contact
customer support.
After you finish
To… Do…
Install a second cluster Repeat this procedure.
Connect two clusters Proceed to the Connect Cluster wizard.
To begin local replication (on a Use the link on the Summary screen to open
single cluster) Unisphere for RecoverPoint management GUI.
l Connecting a cluster.......................................................................................... 30
Connecting clusters 29
Connecting clusters
Connecting a cluster
Use this procedure to connect a new RecoverPoint cluster to an existing
RecoverPoint system.
The computer running the Connect Cluster Wizard must communicate with all the
cluster management IP addresses. Both clusters in the system must have the same
supported storage type and the RecoverPoint/SE license.
Procedure
1. Launch Deployment Manager by opening the RecoverPoint_DM.exe
application file.
2. On the RecoverPoint Deployment Manager Wizard screen, select the
Connect Cluster wizard.
3. On the Connect Cluster Wizard screen, select the Prepare new cluster for
connection option.
4. On the Prerequisites screen, if any of the conditions are not fulfilled, close the
wizard, fulfill the conditions, and run the wizard again.
5. On the New cluster login credentials screen, enter boxmgmt credentials for
the new cluster.
6. On the Connect Now or Later screen, select the Connect the new cluster to
an existing RecoverPoint system option.
Do not install a license in, or modify the settings of, the new cluster before
connecting it to the existing system.
7. In the Existing cluster login credentials screen, enter the cluster management
IP address and boxmgmt credentials of the existing cluster.
8. (Optional) On the Cluster connection settings screen, add a WAN gateway for
additional network connectivity between RPA clusters, if required.
9. The Additional cluster connections screen appears if the system you are
connecting to contains more than one RPA cluster.
The added cluster receives the security settings of the existing cluster.
10. When the Summary screen appears, you have completed the connection of the
new cluster, and you can start using Unisphere for RecoverPoint.
After you finish
After installing a RecoverPoint system, you must complete the RecoverPoint Post-
Deployment Form and send it to the Install Base (IB) group to register your
RecoverPoint system.
If you are installing RecoverPoint 4.1 or later, and you have external connectivity, you
can perform this process automatically, using the Unisphere for RecoverPoint Getting
Started wizard or Admin > Register RecoverPoint screen. See the RecoverPoint
Administrator’s Guide for further instruction on how to automatically fill out the Post-
Deployment form and send it to the IB group.
If you are installing a RecoverPoint version prior to 4.1 or are installing a RecoverPoint
version later than 4.1 without connectivity:
1. Download the form from online support at https://support.emc.com. In the online
support site:
a. Click Support by Product.
Connecting a cluster 31
Connecting clusters
Customer upgrade 33
Customer upgrade
Choice Description
Customer upgrade For RecoverPoint with Unity, VNXe or VNX
customers who have elected to perform an upgrade
on their own.
Other operations All other upgrades
(support personnel)
Choice Description
If no system modifications Select Apply upgrade now and click Next.
are found
If system modifications Submit the file in an Upgrade Service Request to
are found Customer Support. When you receive a response
from Customer Support, go to the Apply upgrade
configuration screen.
Time Zone
Local Domain
Secondary DNS
Server (optional)
Cluster Management
IPv4
Management Default
Gateway IPv4
Management Subnet
Mask IPv4
WAN Default
Gateway
SMTP (optional)
RPA WAN IP
RPA WAN IP
RPA WAN IP
RPA WAN IP
RPA WAN IP
RPA WAN IP
RPA WAN IP
RPA WAN IP
Time Zone
Local Domain
Secondary DNS
Server (optional)
Cluster Management
IPv4
Management Subnet
Mask IPv4
WAN Default
Gateway
SMTP (optional)
vRPA WAN IP
iSCSI1 IP
iSCSI2 IP
vRPA WAN IP
iSCSI1 IP
iSCSI2 IP
vRPA WAN IP
iSCSI1 IP
iSCSI2 IP
vRPA WAN IP
iSCSI1 IP
iSCSI2 IP
vRPA WAN IP
iSCSI1 IP
iSCSI2 IP
vRPA WAN IP
iSCSI1 IP
iSCSI2 IP
vRPA WAN IP
iSCSI1 IP
iSCSI2 IP
vRPA WAN IP
iSCSI1 IP
iSCSI2 IP