RecoverPoint SolVe Generator

Version: 6.1.0.29 Generated on June 5 2024 09:58 AM

Topic
Installation Procedure

Selections
Select the type of Install: Software Install
Select the type of License: RecoverPoint SE
Select the type of RPA you are installing: Virtual
Select Splitter Technology: CLARiiON / VNX
Select CLARiiON storage-system model: VNX Series
Select Model: VNX5100 (block only)
Select storage type: VNX for Block
Select the type of install: Install / Update FLARE OE
Select the Version to Install: 5.1 SP4 P4
Select the information you want to include: None

If you find any errors in this procedure or have comments regarding this application, send
email to [email protected]

Copyright © 2024 Dell Inc. or its subsidiaries. All Rights Reserved. Dell Technologies, Dell, EMC, Dell EMC and other trademarks are
trademarks of Dell Inc. or its subsidiaries. Other trademarks may be trademarks of their respective owners.

The information in this publication is provided “as is.” Dell Inc. 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 software described in this publication requires an applicable software license.

This document may contain certain words that are not consistent with Dell's current language guidelines. Dell plans to update the
document over subsequent future releases to revise these words accordingly.

This document may contain language from third party content that is not under Dell's control and is not consistent with Dell's current
guidelines for Dell's own content. When such third party content is updated by the relevant third parties, this document will be revised
accordingly.
Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA
Page 1 of 165
 Contents
Preliminary Activity Tasks .......................................................................................................7
Read, understand, and perform these tasks.................................................................................................7

RecoverPoint/SE 5.1 SP4 P3 Installation ...............................................................................8

Mandatory EMC Knowledge Solutions .........................................................................................................8

Preparing for Deployment .......................................................................................................8

Fibre Channel (RecoverPoint/SE) ...........................................................................................................8
Dual fabric................................................................................................................................................8
Direct attach.............................................................................................................................................9
Task 1: Unpacking and racking RPAs...........................................................................................9
Rear panel description ................................................................................................................................10
Gen5 and Gen4 RPA interfaces .................................................................................................................11
Task 2: Connecting RPAs ...........................................................................................................12
NTP server..................................................................................................................................................12
Zoning .........................................................................................................................................................13
Zoning for VNX/CLARiiON splitting .......................................................................................................14
LUN masking .........................................................................................................................................14
Multiple WWNs ......................................................................................................................................14
Overview of vRPA.......................................................................................................................................14
The difference between RPA and vRPA................................................................................................14
Planning ................................................................................................................................15
Prerequisites .........................................................................................................................15
Environment................................................................................................................................................15
Virtual Resources........................................................................................................................................15

Deploying ..............................................................................................................................16
Cluster requirements...................................................................................................................................16
Creating the first or a single vRPA..............................................................................................................16
Creating multiple vRPAs .............................................................................................................................16
Virtualization best practices ........................................................................................................................17
Memory reservation ...............................................................................................................................17
If multiple vRPAs share same vSphere host: ........................................................................................17
Configuring virtual networks for vRPA: ..................................................................................................17
Cloning vRPAs:......................................................................................................................................17
vMotion and storage vMotion.................................................................................................................17
High Availability features: ......................................................................................................................17
iSCSI bandwidth: ...................................................................................................................................17

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 2 of 165
Creating vRPAs using the OVF package....................................................................................................17

Limitations.............................................................................................................................25
Comments and getting help ..................................................................................................26
Getting help.................................................................................................................................................26
Your comments...........................................................................................................................................27
Pre-installation Requirements.....................................................................................................................27
Install software on each RPA.................................................................................................................27
Login to RPA and set IP address...........................................................................................................27
Installing a new cluster ..........................................................................................................................27
Task 3: Changing the root password ..........................................................................................32
Task 4: Change Password ..........................................................................................................32
Verifying time synchronization ...............................................................................................................32
Verifying management access....................................................................................................................34
Using the RecoverPoint GUI..................................................................................................................34
Using the RecoverPoint CLI ..................................................................................................................34
Site 1 Splitter Installation.......................................................................................................34
RecoverPoint Splitter Requirements...........................................................................................................34
Upgrading the VNX Operating Environment ...............................................................................................35
Before you start .....................................................................................................................................35
Updating the VNX operating environment .............................................................................................35
Verifying the VNX for Block software installation with Unisphere ...............................................................39
Connecting a cluster ...................................................................................................................................40
Register RecoverPoint ................................................................................................................................41
Register your RecoverPoint system ......................................................................................................41
Export the post-deployment form to a CSV file......................................................................................44
Registering RecoverPoint by email or phone ........................................................................................45
Licensing RecoverPoint ..............................................................................................................................45
Overview .....................................................................................................................................................46
Audience .....................................................................................................................................................46

The RecoverPoint 4.0 System Architecture and Terminology ..............................................47

The RecoverPoint 4.0 Ordering and Licensing Process .......................................................49
Phase 1 - Ordering......................................................................................................................................49
Phase 2 - Licensing ....................................................................................................................................49
Phase 3 - Installing .....................................................................................................................................49
Phase 4 - Reporting ....................................................................................................................................49
End-to-end process diagram.......................................................................................................................50

Phase 1 – Ordering RecoverPoint via Direct Xpress or Channel Xpress .............................51

How to order RecoverPoint.........................................................................................................................51

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 3 of 165
 Choosing the right RecoverPoint option ................................................................................................51
RecoverPoint license types ...................................................................................................................51
RecoverPoint ordering and licensing basics..........................................................................................52
The RecoverPoint order summary.........................................................................................................55
The RecoverPoint standalone ordering path .........................................................................................55
Phase 2 – Licensing RecoverPoint 4.0 .................................................................................56
Licensing guidelines....................................................................................................................................56
Licensing options at-a-glance ................................................................................................................56
Licensing process overview ........................................................................................................................64
Licensing process at-a-glance ...............................................................................................................64
Licensing illustrations.............................................................................................................................68
Licensing examples ...............................................................................................................................68
Before you begin....................................................................................................................................69
How to license new RecoverPoint purchases.............................................................................................70
Accessing entitlements via LAC email(s) or EMC Online Support ........................................................71
Activating entitlements in Powerlink Licensing ......................................................................................76
Upgrading to RecoverPoint 4.0 from previous RecoverPoint versions (LCT).............................................78
Legacy Customer Transition process overview .....................................................................................78
Legacy Customer Transition process rules ...........................................................................................79
Legacy Customer Transition process ....................................................................................................80
Phase 3 - Installing License Files in Unisphere for RecoverPoint.........................................82
Installing your license files using the Getting Started wizard ......................................................................82
Installing your license files using Admin > Manage Licenses .....................................................................84

Phase 4 – Reporting Back to EMC via Unisphere for RecoverPoint.....................................84

Configure system notifications using the Getting Started wizard................................................................85
Configure system notifications using Admin > Configure System Notifications..........................................86

Appendix A: Ordering and Licensing Examples by Use Case ..............................................87

RecoverPoint/SE replication from VNX7500 to VNX5500 ..........................................................................87
RecoverPoint/EX replication from VNX7500 (L+R) and VMAX 10K to VMAX 10K ....................................89
Replication from two CX-120s to a VNX5300 .............................................................................................91
Replication from VNX7500 (local and remote) and VNX5300 (local only) to VNX5700 .............................92
Replication of 50 TB from VMAX 20K and 30 TB from VMAX 10K to VNX5700 ........................................93
Replication from VNX7500 to VNX5500 with splitter sharing .....................................................................94
Replication from VNX7500 (local and remote) and VMAX 10K to VMAX 10K ...........................................95
Replication from two CX4-120s to a VNX5300 ...........................................................................................96
Replication from VNX7500 to an existing RecoverPoint/SE cluster ...........................................................97
Add VMAX 10K with 50 TB to an existing local RecoverPoint/SE cluster ..................................................98
Replication of 50 TB from VPLEX to VMAX 10K ........................................................................................99
Replication of 150 TB from non-EMC arrays to VMAX 20K......................................................................100

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 4 of 165
Replication from one site to two different sites (example 1) .....................................................................101
Replication from one site to two different sites (example 2) .....................................................................102
Replication of multiple VNXs for new purchases and upgrade scenarios.................................................103
Additional use cases .................................................................................................................................104

Appendix B: RecoverPoint Ordering FAQs and Getting Help .............................................106

RecoverPoint/SE .................................................................................................................................108
RecoverPoint/SE Ordering FAQ ..........................................................................................................111
RecoverPoint for VNX and CLARiiON .................................................................................................111
RecoverPoint/EX .................................................................................................................................113
RecoverPoint for VMAX 10K ...............................................................................................................115
RecoverPoint for the VMAX 20K and VMAX .......................................................................................116
RecoverPoint for the Symmetrix VMAX 40K .......................................................................................116
RecoverPoint for VPLEX .....................................................................................................................117
Ordering FAQs.....................................................................................................................................118
RecoverPoint for VPLEX with Frame-Based VNX...............................................................................120
RecoverPoint/CL..................................................................................................................................123
RPA Questions ....................................................................................................................................123
vRPA Questions ..................................................................................................................................124
Appendix C: RecoverPoint Licensing FAQs and Getting Help............................................128
General Licensing Questions....................................................................................................................128
Frequently Asked Questions: VPLEX frame-based Licenses for VNX ................................................132
RecoverPoint/SE.......................................................................................................................................135
RecoverPoint/CL.......................................................................................................................................136

Appendix D: RecoverPoint 4.0 Models ...............................................................................136

RecoverPoint software models ............................................................................................................136
RecoverPoint physical appliances .......................................................................................................147
RecoverPoint virtual appliances ..........................................................................................................147
Appendix E: RecoverPoint 4.0 License File Example .........................................................148
Appendix F: Rules for Expiring Licenses ............................................................................152
Temporary licenses .............................................................................................................................152
Evaluation licenses ..............................................................................................................................152
Emergency licenses.............................................................................................................................152
Appendix G: How to Find Locking IDs ................................................................................153
How to find your RPA cluster IDs..............................................................................................................153
How to find your array serial numbers ......................................................................................................153
For VNX arrays ....................................................................................................................................154
For Symmetrix arrays .........................................................................................................................154
For VPLEX arrays...............................................................................................................................154
Appendix H: Where to Get Support.....................................................................................155

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 5 of 165
Appendix I: RecoverPoint Ordering and Licensing Terminology.........................................155
Appendix J: The RecoverPoint Ordering Path ....................................................................165
Starting Replication...................................................................................................................................165

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 6 of 165
Preliminary Activity Tasks
This section may contain tasks that you must complete before performing this procedure.

Read, understand, and perform these tasks

1. Table 1 lists tasks, cautions, warnings, notes, and/or knowledgebase (KB) solutions that you need to
be aware of before performing this activity. Read, understand, and when necessary perform any
tasks contained in this table and any tasks contained in any associated knowledgebase solution.

Table 1 List of cautions, warnings, notes, and/or KB solutions related to this activity

546589: RecoverPoint Classic 5.1.2 and later customers: Use RPClassicUI utility to access the
Unisphere for RecoverPoint UI.As Adobe Flash player is being deprecated December, 2020, and
browser vendors will not support Flash player after deprecation.
Review knowledge base article kb 546589 prior to performing Install.

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 7 of 165
RecoverPoint/SE 5.1 SP4 P3 Installation
Mandatory EMC Knowledge Solutions
Note: A list of Mandatory EMC Knowledgebase articles will be provided with your approved RecoverPoint
Change Control. It is very important that anyone participating in this activity review and understand each
article before proceeding.

CAUTION: If Replication Manager is used in the environment, please be aware of compatibility

requirements between different versions of RecoverPoint and Replication Manager. Please consult the
RecoverPoint Support Matrix and Replication Manager Support Matrix for details.

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 your 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 your installed networks and storage systems. It is also necessary to ensure
that the LUNs needed by RecoverPoint are available on your storage. EMC Global Services will assist
you with these pre-deployment activities:
• RecoverPoint connectivity
• Zoning

Fibre Channel (RecoverPoint/SE)

RecoverPoint/SE supports the following network topologies, all of which ensure high availability:
Dual fabric
Direct attach

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.

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 8 of 165
 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

Task 1: Unpacking and racking RPAs

Use these instructions to unpack RPAs and install them in their racks.
Before you begin
Verify that each RPA package contains:
• 1 EMC RecoverPoint Appliance
• 1 standard EMC rackmount kit
• 1 EMC bezel
• 2 country-specific power cables

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 9 of 165
If items are missing from the package, promptly notify EMC Customer Support.
Procedure
1. [ ] From https://support.emc.com, obtain the hardware guide for your RPAs:

RPA version Hardware guide

Gen6 RecoverPoint Gen6 Hardware Guide
See rear panel and description in topic "Rear panel description."
Gen5 SRV-I1U-1208 Server Installation and Maintenance Guide
Gen4 SRV-D1U-R610 Installation and Replacement Guide

2. [ ] Install all RPAs in cabinet before proceeding to "Connecting RPAs."

Rear panel description

This section describes the rear panel controls and indicators
Rear panel view

Item Control/Indicator/Port Purpose

A 1 Gbe BMC Management Dedicated BMC service port
B 1 Gbe/NCSI port #3 1000Base T network port
C 1 Gbe/NCSI port #1 1000Base T network port
D USB 2.0 port USB port
E Dual-stacked DB-9 ports COM 1 (top), COM 2 (lower)
F Reset/Power Button The Reset/Power button has the following function:
1) System is off:

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 10 of 165
 Item Control/Indicator/Port Purpose
• Action: Any duration button press
• Result: System powers on
2) System is on:
• Action: Short button press (less than 10 seconds).
• Result: System reset.
• Action: Long power button press (longer than 10
seconds)
• Result: System powers off
G I/O Module, Slot 0 Houses I/O module
H I/O Module, Slot 1 Houses I/O module
I Power supply 0 Supplies power to a CPU module and system
components
J Power supply LEDs (top to bottom)
• AC power good (green)
• DC power good (green)
• Fault (amber)
K Power supply 1 Supplies power to a CPU module and system
components
L I/O module power/service LED • Green (good)
• Amber (fault)
M 1 Gbe/NCSI port #0 1000Base T network port
N 1 Gbe/NCSI port #2 1000Base T network port

SP system LEDs
Top to bottom:
• Do not remove - White
• System power applied - Blue
• SP service - Blue (good)/Amber (fault)

Gen5 and Gen4 RPA interfaces

Figure 1 Gen5 network interfaces

Figure 2 Gen4 network interfaces

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 11 of 165
Task 2: Connecting RPAs
Procedure
1. [ ] Connect the RPA Fibre Channel ports.
• Dual-fabric topology– Connect one RPA Fibre Channel port to Fabric A and a different RPA
Fibre Channel port to Fabric B on each RPA.
• Direct attach topology to EMC mid-range storage arrays– Connect one RPA Fibre Channel
port to Storage Processor A, and a different RPA Fibre Channel port to Storage Processor B.
Connect the remaining RPA Fibre Channel ports to the remaining RPA Fibre Channel port of
the other RPA in the cluster.
• Direct attach topology to XtrermIO– A RecoverPoint cluster can support up to two Xbricks.
The RecoverPoint cluster must have exactly two RPAs.
Every RPA must be connected to all storages controllers.

Note: A dual fabric configuration is required at all clusters for RPA, host, and storage connectivity.

2. [ ] For each RPA, connect an Ethernet cable from the:

a. Management (LAN) interface to the eth1 port.

b. WAN to eth0 port.
3. [ ] Connect a country-specific electrical power cable to each of the two power plugs on each RPA.
4. [ ] Connect each RPA to a monitor and keyboard or via a KVM. If these options are not available
(Gen6 does not support KVM and does not have a VGA port), use one of the following options:
• 1– Attach an external computer using an EMC console cable to the RPA’s serial port.
• 2– Attach an external computer using an Ethernet crossover cable to the RPA WAN port.
5. [ ] Power up the RPA.
The following prompt appears:
localhost.localdomain login:
Password:

If the login prompt does not appear, press Enter until it does.
6. [ ] Log in to the RPA using boxmgmt credentials.
You will be prompted for a temporary, subnet, and gateway IP addresses. If DHCP is configured for
all RPAs in the cluster, these IP addresses are optional. When the configuration is completed, the
boxmgmt main menu will appear.
The IP addresses you assigned will be used throughout the deployment process. Verify that a single
workstation can access all IP addresses assigned to RPAs at all clusters. As an alternative, you may
install one site at a time, in which case, it is necessary only to be able to reach the RPAs of one
cluster at a time.
Java™ 8 is required on the workstation that will be running the installation wizard. It is highly
recommended to have the latest version of Java installed.

NTP server
Network Time Protocol (NTP) synchronizes the clocks across all of the machines that are attached to a
given installation.
Best practice is to configure an external NTP server, running on Linux machines, for use by the
RecoverPoint system prior to RecoverPoint installation.

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 12 of 165
When an external NTP server is configured at a site, the first RPA in a cluster at that site will synchronize
to the external NTP server. All other RPAs in all clusters of the RecoverPoint system will synchronize to
the first RPA. To increase the accuracy of the time, you may enter 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 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, 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
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 will
observe only minor differences in performance and availability. However, initiator-target separation is
not supported when:
• Mixing different splitter types in the same site
• Using remote replication over Fibre Channel
• 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 already
exist as part of the SAN implementation. Confirm that these zones exist. EMC requires single-initiator
zoning.
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 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:
• One HBA port of that RPA
• 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 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 be in one zone. Normally, the RPA-to-
storage zone satisfies this requirement.
Zoning for remote replication over Fibre Channel

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 13 of 165
 Create one zone per fabric that includes all of the site 1 RPA ports together with all of the site 2 RPA
ports.
Unity/VNXe/VNX ports with native array-based replication
Best practice is not to share Unity/VNXe/VNX ports between array-based replication technologies and
RecoverPoint. For Unity/VNXe/VNX splitters, not sharing ports between array-based replication
technologies and RecoverPoint is required. Array-based replication technologies should be excluded
from RecoverPoint zones.

Zoning for VNX/CLARiiON splitting

The zoning requirements for RecoverPoint deployment are presented in later sections of this document,
along with the splitter installation instructions.

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).

Overview of vRPA
The RecoverPoint vRPA is a virtual implementation of the RecoverPoint Appliance (RPA). Being a virtual
machine, the vRPA operates with dynamic virtual resources. Reserving and provisioning these resources
is the responsibility of the user. In contrast, in a physical RPA, system resources are locked down by
server capabilities.

The difference between RPA and vRPA

Error! Reference source not found. compares features of the physical RPA with vRPA.

Table 1 Comparison between RPA and vRPA

Feature RPA (Physical) vRPA (Virtual)

Splitting communication Direct SCSI (IP)/Fibre Channel iSCSI (IP)
IP ports LAN, WAN LAN, WAN, iSCSI1, ISCSI2

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 14 of 165
 RecoverPoint license CL/EX/SE RecoverPoint 4.0: SE only
RecoverPoint 4.0.1: /CL, /EX, and
/SE
Support for dynamic resource No Yes
allocation
Deduplication always available minimum 8xCPUs/8GB RAM
configuration required
Replication Asynchronous and synchronous Asynchronous; synchronous only
with 8CPU/8GB configuration
Distributed consistency groups Yes No
Communication between clusters FibreChannel/WAN (IP) WAN (IP)

Planning
Reserving sufficient system resources (CPU, memory, disk space) and network bandwidth is critical to
assuring optimal performance of vRPAs. This chapter discusses planning vRPA deployment and
resource requirements.

IMPORTANT: The current vRPA packaging (OVF) was verified only in the VMware vSphere environment.

The hypervisor (VMware) must be configured and prepared in advance for vRPA deployment. To ensure
that deploying vRPAs is as simple and effortless as possible, vRPAs are provided as OVF (Open
Virtualization Format) package files. The OVF package contains wizards that provide the most secure and
least error-prone way to create vRPAs and configure both the virtual system resources and network
requirements for correct deployment.
The OVF package creates the first virtual machine with pre-defined temporary network settings. The
same process can be repeated to create additional vRPAs, or the first vRPA can be cloned as many
times as necessary. Once the vRPAs have been created, RecoverPoint Deployment Manager can be
used to build a RPA cluster, or to join the vRPAs to an existing cluster.

Prerequisites
Environment
The vRPA requires the following environment components to enable its functionality:
• VNX OE 05.32.000.5.2 or later, preconfigured with at least one iSCSI port per storage processor.
• RecoverPoint Deployment Manager (DM) 2.0 or later
• Fully licensed RecoverPoint 4.0 (or later) cluster
• VMware vCenter 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)
• If there is more than one VNX in the RecoverPoint environment and Challenge-Handshake
Authentication Protocol (CHAP) is used, CHAP credentials must be identical on all VNX arrays in the
environment.
• When not using RecoverPoint/SE installer, virtual iSCSI Qualified Names (IQNs) of each vRPA must
be registered with all VNX arrays in the RecoverPoint environment.

Virtual Resources
For correct and efficient operation of vRPA virtual machines, the following resources are required:

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 15 of 165
 • Reserved quota for virtual system resources (CPU, memory, disk)
• 4 virtual networks (LAN, WAN, iSCSI1, iSCSI2)
When the vRPA is created using the OVF package, the resources required are indicated in
. The vRPA supports dynamic provisioning of these resources, as long as they do not go below the
values in
.

Table 2 The vRPA performance profile matrix

RPA Profile Feature 2xCPU/4GB 4xCPU/4GB 8xCPU/8GB

virtual CPUs 2 4 8
RAM 4GB 4GB 8GB

Deploying
Cluster requirements
RPAs and vRPAs cannot be mixed in one cluster. The cluster must be either all physical RPAs or all
vRPAs. However, replication is supported between any of the following cluster types:
• RPA and RPA
• RPA and vRPA (in either direction)
• vRPA and vRPA
• N:1 topology is supported when multiple RPA clusters replicate to one vRPA cluster. In N:1 topology,
production must be physical RPAs.
• In RecoverPoint/SE installations, the number of RPAs in each of the two clusters must be the same,
regardless of whether they are physical or virtual.

Creating the first or a single vRPA

vRPAs must be created using the OVF package file.
• The OVF package can be used only via the VMware vCenter management, not via the vSphere
management.
• To deploy a vRPA, use Deployment Manager to create a RPA cluster and attach the instance to the
cluster.

Creating multiple vRPAs

Multiple vRPAs can be creating in one of the following ways:
• The best practice is to create each vRPA instance individually from an OVF package (as described in
Creating the first or a single vRPA , page 16).
• It is possible to create multiple vRPAs by cloning or copying an existing vRPA.

IMPORTANT: To deploy vRPAs, use Deployment Manager to create a cluster and attach the instances
to the cluster.

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 16 of 165
Virtualization best practices
Memory reservation
When using 4CPU/4GB or 8CPU/8GB configurations to run vRPA, the best practice is to reserve all RAM
for RecoverPoint.

If multiple vRPAs share same vSphere host:

vRPAs should not share the same ESX server, to allow redundancy in case an ESX server fails. Where
resources are so scarce (temporarily) that vRPAs must run on the same host, sufficient resources must
be made available:
• CPU and memory: total resources available on a shared host must be the sum of resources required
by each of the individual vRPAs on the server.
• Network bandwidth must be sufficient to handle the I/Os of all vRPAs.

Configuring virtual networks for vRPA:

• In low-traffic deployments, all four network cards may be placed on the same virtual network (on a
single vSwitch).
• Where high performance is desired, separate LAN and WAN traffic from iSCSI traffic. For even better
performance, place each network (LAN, WAN, iSCSI1, and iSCSI2) on a separate virtual switch.
• For high-availability deployments, in which clients have redundant physical switches, the best practice
is to route each iSCSI card to a different physical switch. This will usually involve specifying a
different virtual network for each of the iSCSI cards.

Cloning vRPAs:
• The best practice is to create each vRPA instance from the OVF.
• vRPAs can be cloned. Cloning has no effect on the source vRPA. The target vRPA will automatically
reset its configuration when it is booted, to avoid IP collisions. Deployment Manager can then be used
to add the clone to the RPA cluster.

vMotion and storage vMotion

• As is the case for regular RPAs, any online or offline porting of vRPA is supported; except for pause
or resume operations, which can lead to corruption (especially if the vRPA is the cluster leader for the
consistency groups)

High Availability features:

• As is the case for regular RPAs, any online or offline porting of vRPA is supported without affecting
high availability; except for pause or resume operations, which can lead to corruption (especially if the
vRPA is the cluster leader for the consistency groups)

iSCSI bandwidth:
In VNX, either of two types of iSCSI modules may be available:
• 1Gb port cards, which allow bandwidth of 1Gb ,2Gb, 4Gb
• 10Gb port cards, which allows bandwidth of 10Gb, 20Gb
Since the vRPA relies on virtual networks, the bandwidth that the user exposes to the vRPA iSCSI
vSwitches will determine the performance that the vRPA can reach. The user can configure vSphere
hosts with quad port NICs and present them to the vRPAs as single or dual iSCSI networks; or implement
VLAN tagging to logically divide the network traffic among multiple vNICs.

Creating vRPAs using the OVF package

Use the following procedure to deploy a vRPA:

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 17 of 165
 1. [ ] At the vCenter management console, from the File menu, select Deploy OVF Template.

Figure 3

The OVF deployment wizard appears.

2. [ ] Specify the vRPA OVF package location.

Figure 4

The vRPA OVF template details appear, showing the general properties of this OVF template.

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 18 of 165
 Figure 5

3. [ ] To accept, click Next.

4. [ ] The EMC End-User License Agreement appears. If you accept the terms, click Accept and Next.

Figure 6

The Name and Location screen appears.

5. [ ] Enter the name you wish to assign to this vRPA. If you enter the name of an existing vRPA, you
will not be permitted to continue.

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 19 of 165
 Figure 7

6. [ ] Select the desired configuration profile (refer to

7. [ ] , page 16).

Figure 8

8. [ ] (Optional) Select the desired vSphere host resource pool.

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 20 of 165
This step is optional because, in the absence of a resource pool, you can choose the vSphere host, which
should comply with the minimum resources required by the vRPA.

Figure 9

9. [ ] Specify the vRPA Storage (datastore) that will be used to host the vRPA virtual machine files.
The best practice is to select a high-performance datastore. Do not use a datastore that you intend to
replicate with RecoverPoint.

Figure 10

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 21 of 165
10. [ ] Specify the vRPA datastore virtual Disk Format. Select Thin Provision.

Figure 11

11. [ ] Create the Network Mapping to map the four required vRPA Ethernet ports (Source Networks) to
the available vSphere virtual networks (Destination Networks). Do not select the internal VMware
iSCSI network (iSCSI Network option).

Figure 12

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 22 of 165
12. [ ] Specify the desired IP address allocation policy for the vRPA temporary IP, which will later be
used to connect to the Deployment Manager.

Figure 13

13. [ ] If you selected the fixed IP policy, enter the required IP Properties.

Figure 14

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 23 of 165
14. [ ] The Ready to Complete screen summarizes all your selections. Click Finish to create this
instance of the vRPA.

Figure 15

The Deploying vRPA appears, showing the progress.

Figure 16

When the vRPA is created, the vRPA Summary tab shows the vRPA package contents as specified. The
new vRPA virtual machine is ready to be powered on. The selected IP policy will be implemented
automatically when the vRPA is powered up.

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 24 of 165
 Figure 17

15. [ ] Use RecoverPoint Deployment Manager to add this vRPA instance to an RPA cluster:

a. On any computer that has access to the RPA cluster management IP address, run Deployment
Manager.
b. In Deployment Manager, select the RecoverPoint or RecoverPoint/SE Installer Wizard, and follow
directions in the wizard.

Limitations
• The vRPA has ongoing validation algorithms. Any exception causes the vRPA to disconnect from the
RPA cluster (meaning that this vRPA will not function as an active RPA). Validation is performed for
the following metrics:
Does the vRPA have enough system resources (refer to
)?
Cloning of a vRPA that is a member of an RPA cluster generates a failure error (as shown below). It
will cease operate within the cluster.

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 25 of 165
 Figure 18

• The vRPA OVF package can be deployed only from the vCenter management, not via vSphere
management. This is a VMware limitation for vAPP functionality, which is used by the OVF script.
• The vRPA requires a VNX array supporting iSCSI (running firmware described in “Environment,”
page 15).
• Sharing vRPA iSCSI interfaces (iSCSI1 and iSCSI2) with the vRPA regular networks (LAN and WAN)
will result in performance degradation and unexpected behavior of the vRPA.
• Any pause or resume tasks (or hibernation-like functionality) of a running vRPA virtual machine is not
supported and will lead to corruption or failure.
• Collecting vSphere logs from a running vRPA (for instance, using vSphere File > Export > Export
System Logs command) may cause inconsistencies in the datastore or other unexpected behavior.
• Do not use MirrorView-enabled ports for vRPA (iSCSI), because the RecoverPoint splitter is not
supporting MirrorView ports, but instead supports SC (San Copy) ports.
• Distributed consistency groups are not supported when using vRPA.
• Before creating a VMware snapshot of a vRPA, it must be detached from the vRPA cluster.

Comments and getting help

Getting help
EMC support, product, and licensing information can be obtained as follows.
Product information. For documentation and release notes, or for information about EMC products,
licensing, and service, go to EMC Online Support (registration required) at:
http://support.emc.com
Technical support. For technical support, go to EMC Customer Service on EMC Online support. To open
a service request through EMC Online Support, you must have a valid support agreement. Please contact
your EMC sales representative for details about obtaining a valid support agreement or to answer any
questions about your account.

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 26 of 165
Your comments
Please include the title, part number, and revision of the document.
If you have issues, comments, or questions about specific information or procedures, include the relevant
page numbers and any other information that will help us locate the information you are addressing.
• [email protected]

Pre-installation Requirements
Before installing RecoverPoint software:
• Ensure that a secure shell (SSH) client is installed on your PC.
If your PC runs Microsoft Windows, use an SSH client such as PuTTY. If your PC runs Linux or UNIX,
use the SSH client that comes with the operating system.
• EMC provides RecoverPoint software on EMC Online Support to those individuals that are authorized
to handle it. If the software is not available on EMC Online Support, contact Customer Service.
• For local installations, have the ISO image available on a disc:

1. [ ] Verify the checksum against the md5sum listed on http://support.emc.com.

Note: If running Microsoft Windows, use the md5sum.exe utility

2. [ ] Burn the ISO image onto a DVD.

IMPORTANT: Installing RecoverPoint software on an RPA for the first time requires a new software
installation and not a software upgrade.

Install software on each RPA

To install the RPA software:
1. [ ] Load the ISO image from an ftp server or from a DVD.
Wait until the software loads and the disc automatically ejects.
2. [ ] Repeat step 1. [ ] for all RPAs.

Login to RPA and set IP address

3. [ ] Connect to an RPA using one of the following options:
• Connect an Ethernet crossover cable between a PC and the WAN Ethernet segment to which the
RPA is connected:

a. Assign the PC the IP address: 10.77.77.50 with subnet mask: 255.255.255.0

b. Access the RPA using an SSH client, such as PuTTY or ssh, to connect to the default
(unrouted) IP address of the RPA: 10.77.77.77
• Connect a KVM (keyboard, video, mouse) to the RPA.
If the login prompt does not appear after the start process, press Enter (several times, if
necessary) until it does.
4. [ ] Log in to RPA. At the prompt, login as boxmgmt with the password boxmgmt.
You will be asked to configure a temporary IP address, subnet mask, and gateway. You should enter
management IP address.
When you do the Main menu appears.

Installing a new cluster

Customers may use this procedure to install RecoverPoint on an RPA cluster, physical or virtual.

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 27 of 165
 About this task
This wizard installs RecoverPoint with Unity, VNXe, or VNX arrays and a RecoverPoint/SE license. These
RecoverPoint systems can contain one or two clusters. The Installer wizard installs one cluster at a time.
Run again to install a second cluster.
RecoverPoint/EX and /CL licenses support systems with more than two clusters. Contact customer
support to arrange installation by support personnel.
Procedure
1. [ ] Ensure that you have the latest version of the RecoverPoint_DM.exe application file. Launch
Deployment Manager by opening RecoverPoint_DM.exe. Follow instructions on screen.
2. [ ] Select the RecoverPoint version to install.
3. [ ] On the login screen, select Customer installation and click Login.
4. [ ] On the RecoverPoint Deployment Manager wizard screen, select RecoverPoint with VNX
Installer or RecoverPoint with Unity/VNXe Installer.
5. [ ] On the Prerequisites screen, if any of the conditions are not fulfilled, close the wizard, fulfill the
conditions, and run the wizard again.
6. [ ] On the Configuration file screen, select an installation mode:
• Create a new installation configuration file–
To save your settings to a file in case you need to repeat this installation.
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 an installation from a saved configuration file– If you previously saved a
configuration file, to load the saved settings as defaults for this installation.
7. [ ] On the Environment settings screen, specify the settings.
Configuration
Select WAN and LAN traffic on separate network adapters (default) or on the same network adapter.
• RecoverPoint 5.0 and later supports more than one network traffic type on a network adapter.
• The network adapter topology must be the same for every RPA in the cluster and for every
cluster in the RecoverPoint system.
• To modify an existing network adapter topology, change it for every RPA in every cluster in the
RecoverPoint system. To change, detach the RPA, use boxmgmt to change the network
adapter topology, and reattach the RPA to the cluster. Repeat for all RPAs in all clusters.
WAN and LAN
• If the WAN and LAN are on the same network adapter, they may be on the same subnet.
• If the WAN and LAN are on different network adapters, they must be different subnets.
• All WAN interfaces in a cluster must reside on the same subnet.
• All LAN interfaces and the cluster IP address in a cluster must reside on the same subnet.
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

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 28 of 165
 The cluster domain name is optional.
8. [ ] On the RPA discovery screen, select discovery options.
9. [ ] On the IP and connectivity settings screen, specify IP and connectivity settings.
RecoverPoint 5.0 and later allows you to select Dynamic Host Configuration Protocol (DHCP) to
assign IP addresses to RPAs.
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.
Click Add route to add additional gateways.
10. [ ] On the Login credentials screen, enter the RecoverPoint boxmgmt login credentials.
11. [ ] When all statuses appear OK (green check mark), click Next to continue. You must resolve any
error on the Connectivity results screen before you can proceed. When ready, click Retry.
12. [ ] The Cluster iSCSI settings screen appears only if you are replicating virtual machines. On the
storage array, register the IQNs of both initiators of each vRPA. Map LUNs to the IQNs of the vRPAs
that need to access those LUNs.
13. [ ] On the Cluster iSCSI settings screen, select the network adapter topology for iSCSI traffic.

Note: If the RecoverPoint iSCSI traffic is on a different network adapter from the LAN and WAN, it is
recommended to put the iSCSI traffic on a different subnet from the LAN and WAN, to avoid iSCSI
communication errors.

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:
• If you have Internet connectivity…– Enter EMC Online Support login credentials.
• If you do not have Internet connectivity…– Select Use an offline Change Management XML file
and browse to a local version of the file. To obtain an up-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.
17. [ ] On the Update RecoverPoint Release screen, select an option.

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 29 of 165
 If you select Update with an ISO image available locally, select the download source on the ISO file
information screen.
18. [ ] On the Installation Change Management procedures screen, follow the instructions.
19. [ ] The Apply Configuration results screen shows the installation progress on each RPA. When
installation has completed, press Next.
20. [ ] On the Security configuration screen, select the RPA communication security level for
communication between RPAs and RPA clusters.
• Not authenticated, not encrypted– Communication between RPAs is not authenticated nor
encrypted.
• Authenticated and encrypted– RPAs use certificates to authenticate each other before
communicating, and all communication between RPAs is encrypted.
21. [ ] On the Security configuration screen, select the Local users' security level.
• 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.
• Automatic– Only for:
Cisco fabric switches with an active zoneset
or
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.
Enter the required information. The system creates an RPA-to-storage zone for each new RPA
at the site, where each zone includes:
One HBA port of that RPA
One port for each midrange storage processor
• Semi-automatic– Only for Brocade and Cisco fabric switches.
Enter the required information. The RPA creates a script that can be used to create the zoning.
To export the script, click Export to clipboard. Paste the script into the CLI of the fabric switch.
• Manual– Zone and map LUNs using the RPA port WWNs displayed in the RPA WWNs tables
and the midrange storage array port WWNs displayed in the Array table.
To create RPA-to-storage zones:

a. On each fabric, create a zone for each RPA, which includes:

One RecoverPoint Fibre Channel port of that RPA. If the RecoverPoint FC port has virtual
WWNs, include all of them in the zone.

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 30 of 165
 One port for each VNX storage processor.
b. Add the new RPAs to the RPA-to-RPA zone containing all local RPA FC ports that are not
used in RPA-to-storage zones (best practice).
• Direct-attach Storage– Select this option if each RPA is directly connected to SP A and SP B of
the midrange storage array.
For manual zoning, use the following example for reference.
Fabric A entities Fabric B entities
Storage Port (SPA): Storage Port (SPA):
[pwwn 50:06:01:64:3d:e0:0a:99] [pwwn 50:06:01:65:3d:e0:0a:99]
Storage Port (SPB): Storage Port (SPB):
[pwwn 50:06:01:6c:3d:e0:0a:99] [pwwn 50:06:01:6d:3d:e0:0a:99]
RPA 1, Port 0: RPA 1, Port 2:
[pwwn 50:01:24:82:00:92:4a:86] [pwwn 50:01:24:82:01:b2:4a:86]
RPA 2, Port 2: RPA2, Port 0:
[pwwn 50:01:24:82:00:89:9a:c2] [pwwn 50:01:24:82:01:a9:9a:c2]
Zoning: Zoning:
RPA 1, Port 0 to Storage Port (SPA, SPB): RPA 1, Port 2 to Storage Port (SPA, SPB):
zone name RP_London_0_0 vsan 25 zone name RP_ London _0_0 vsan 55
[pwwn 50:01:24:82:00:92:4a:86] [pwwn 50:01:24:82:01:b2:4a:86]
[pwwn 50:06:01:64:3d:e0:0a:99] [pwwn 50:06:01:65:3d:e0:0a:99]
[pwwn 50:06:01:6c:3d:e0:0a:99] [pwwn 50:06:01:6d:3d:e0:0a:99]
RPA2, Port 2 to Storage Port (SPA, SPB): RPA2, Port 0 to Storage Port (SPA, SPB):
zone name RP_ London _1_0 vsan 25 zone name RP_ London _1_0 vsan 55
[pwwn 50:01:24:82:00:89:9a:c2] [pwwn 50:01:24:82:01:a9:9a:c2]
[pwwn 50:06:01:64:3d:e0:0a:99] [pwwn 50:06:01:65:3d:e0:0a:99]
[pwwn 50:06:01:6c:3d:e0:0a:99] [pwwn 50:06:01:6d:3d:e0:0a:99]
RPA 1, Port 0 to RPA2, Port 2: RPA 1, Port 2 to RPA2, Port 0:
zone name RP_London_COMMON_0 vsan 25 zone name RP_London_COMMON_0 vsan 55
[pwwn 50:01:24:82:00:89:9a:c2] [pwwn 50:01:24:82:01:b2:4a:86]
[pwwn 50:01:24:82:00:92: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.
• Automatic– In step 28, you will select a resource pool. Minimum size of a repository volume
automatically provisioned is 5.72 GB.
• Manual– In step 28, you will select a LUN. Minimum size is 2.86 GB.
28. [ ] On the Repository volume screen, select a resource pool or LUN.

Note: The RPA formats the repository volume. Ensure that the LUN is new and does not contain any
valuable data.
Note: The repository volume must be highly available.

Note: Capacity beyond 5.72 GB (automatic) or 2.86 GB (manual) is not used. Configure a repository
volume on Unity or VNXe storage manually.
Note: The repository volume may be provisioned on a thin or non-thin LUN.

Note: 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

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 31 of 165
 To… Do…
Install a second cluster Repeat this procedure.
Connect two clusters Proceed to the Connect Cluster wizard.
To begin local replication (on a single cluster) Use the link on the Summary screen to open
Unisphere for RecoverPoint management GUI.

Task 3: Changing the root password

For best system security, it is recommended that you replace the default password for the root user with a
strong password that is unique to your system.
About this task
Beginning with RecoverPoint 5.1.2, your admin user password serves also as the root password, Follow
your organization's password policy to set a strong password for these users.

Task 4: Change Password

About this task
Select Admin > Users and Security > Change Password to change the password of the currently logged-
in user.

Procedure
1. [ ] Enter your current password.

2. [ ] Enter the new password in the New Password and Confirm Password fields according to the
password rules of your user's security level.
3. [ ] Click OK.

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.

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 32 of 165
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)
4. [ ] Verify that the ntp_server name has an asterisk.
If there is an asterisk, proceed to step 5. [ ].
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.
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.

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 33 of 165
 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.

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 any 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).

Site 1 Splitter Installation

This section describes the installation for Site 1

RecoverPoint Splitter Requirements

Table 1 identifies VNX OE for Block releases that provide RecoverPoint Splitter support.

Table 1 RecoverPoint Splitter Driver VNX Series Support

RP Version VNX OE for Block Releases

v3.4.x VNX OE for Block 05.31
VNX OE for Block 05.32.000.5.008 and later (no Splitter Driver needed)
V3.5.x VNX OE for Block 05.31
VNX OE for Block 05.32.000.5.008 and later (no Splitter Driver needed)
VNX OE for Block 05.33.000.5.015 and later (no Splitter Driver needed)
V4.0.x VNX OE for Block 05.31

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 34 of 165
 VNX OE for Block 05.32.000.5.008 and later (no Splitter Driver needed)
VNX OE for Block 05.32.000.5.204 and higher contains the 4.0 Splitter.
VNX OE for Block 05.33.000.5.015 and later (no Splitter Driver needed)
V4.1.x VNX OE for Block 05.31
VNX OE for Block 05.32.000.5.011 and later (no Splitter Driver needed)
VNX OE for Block 05.32.000.5.204 and higher contains the 4.0 Splitter.
Snap Based Replication required 05.32.000.5.215 or higher.
VNX OE for Block 05.33.000.5.015 and later (no Splitter Driver needed)

Upgrading the VNX Operating Environment

This document describes how to upgrade the EMC® VNX™ Operating Environment (OE) on a system
using the Unisphere™ Service Manager (USM). With the USM you can:
• Update the operating environment to a new major version on VNX, VNX for Block, and VNX for File
• Apply a patch to the existing operating environment version

Before you start

The system comes pre-installed with the latest version of VNX OE software available at the time of
shipment. To see if any patches or newer releases have been made available since shipment, or to install
any enabler software that you ordered with your system, you can use the procedures described in this
document to:
• Download and install the Unisphere Service manager (USM)
• Select and download the software that you want to install
• Launch the software wizard to install any available patches, software, or enablers
To upgrade the operating environment on a system, you need:
• A Windows host or Windows virtual machine that is:
• Running a supported operating system version. For supported versions, refer to the EMC Unisphere
Service Manager Release Notes, which is available on the EMC Online Support website. We
recommend that you install the latest version of the USM.
• Connected to the internet if you need to install the USM, download software, or both.
• Running Java Runtime Environment (JRE). For supported JRE versions, refer to the EMC Unisphere
Service Manager Release Notes.
• An account on the EMC Online Support website.
• Read knowledgebase articles emc261652 and emc261310. Knowledgebase article emc261652 will
inform you of the steps you need to take before upgrading the VNX OE. Knowledgebase article
emc261310 will outline the compatible block and file software combinations. To locate these articles,
1. Log in to the EMC Online Support website.
2. Select the Search Support tab.
3. Enter the knowledgebase article number or text from the warning message and click Search.

Updating the VNX operating environment

Use the wizards in the Software > System Software section of the Unisphere Service Manager (USM) to
upgrade the file or block operating environment. If you are not running the latest version of USM, it is
recommended that you download and install the latest version.
The USM offers several ways to upgrade your VNX. You can:

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 35 of 165
 • Install VNX OE USM installs the VNX for file software first and then installs the VNX for block
software on a VNX. This is the default selection and recommended method for installing new file and
block software.
• Install VNX OE for File USM installs the VNX for file software on either a file-only system or unified
system. The VNX for block software on the system remains unchanged. This option, for example,
could be used for a file-only upgrade when you want to keep the current block software.
• Install VNX OE for Block and/or enablers USM installs the VNX for block software on either a block-
only or unified system. The VNX for file software on the system remains unchanged. This option, for
example, would be used for a block-only upgrade and when you want to keep the current file
software.

CAUTION: You must first verify that the current file software will be compatible with a block upgrade before
selecting the Install VNX OE for Block and/or enablers option. To verify this, refer to knowledgebase article
emc261310 for information about compatible file and block software combinations.

CAUTION: During the software installation procedure:

- The system must not have any faulted or transitioning components.

You can view the current state of the system components using Unisphere.

- You must not power down or reboot the system, power down an SP, or remove any components. Doing
so may put the system in a state from which you cannot restart it.

- A dual Control Station does not support a VNX for file upgrade using the USM software wizards prior to
file version 7.0.50.2.

• After the block software installation is complete on the secondary SP, that SP reboots. When the SP
comes back up, the primary SP is updated, and then reboots.

Create an account with EMC Online Support

If you do not currently have an account with EMC Online Support, create one by going to the EMC Online
Support website and following the instructions for creating an account.

Installing system software

To install system software (a new operating environment version, software enablers, or language packs)
using the USM’s software wizards, follow the instructions on this section:
• Use the Unisphere Server Utility to validate the environment of any servers connected to the storage
system.
• Install the Unisphere Service Manager (USM).
• Copy any enablers or language packs that you are installing to the software repository.
• Run the software wizards
Download VNX software update
Prepare for Installation wizard
Install Software wizard

Validating the server environment and installing the Unisphere Service Manager (USM)
You must install the USM on a Windows host that is connected to the Internet and on the same network
as the management ports on the system.

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 36 of 165
 1. [ ] Use the Unisphere Server Utility to validate your server environment for High Availability before
making any changes.
2. [ ] Install the USM on the Windows server or host from which you will install the system software.
e. Accept the license agreement.
The installation wizard verifies that the server is running the supported Java Runtime Environment
(JRE) version.
• If the server is running an earlier version of the JRE, select Yes when asked if you want to
continue with the installation. The installation wizard prompts you to download and install the later
version of the JRE from the Sun website.
• If the server is running a later version of the JRE, the installation wizard asks if you want to
continue with the installation.
Select Yes to continue or No to cancel the installation.

IMPORTANT: Important: If you select Yes, the USM may not work properly with a later JRE version. If you
select No, and manually remove the later version of the JRE, other applications that require this version
may not work properly.

Copying enablers and/or Unisphere language packs into the system software repository
Read this section if you have enablers or Unisphere language packs to install on the system. To copy
enablers or language packs into the software repository:

1. [ ] For each enabler that you want to install on the system:

a. Locate each enabler CD that shipped with your order, and insert it into the CD drive on the
Windows server or host running the USM.

Note: This Windows server or host must be on the same network as the system management ports.

b. Copy the enabler (.ena) file from each CD into the C:\emc\repository\Downloads\VNX folder on
the Windows server or host on which you installed the USM.

Note: The USM installation process creates a C:\emc\repository\Downloads folder as the default
repository for the USM’s system software to use. If this folder does not exist, you must create it.

c. Remove the CD from the CD drive.

2. [ ] For each Unisphere language pack that you want to install, download the language pack from the
“Software Downloads and Licensing” section of the EMC Online Support website into the
c:\emc\repository\Downloads folder.

Downloading VNX Software Updates

USM offers two options for downloading the latest VNX software to your system from the EMC Online
Support website.
If you are connected to a system, the VNX Download wizard determines the hardware model, file
software version, and block software version of the selected system. The wizard then walks you through
the steps to select the correct software updates and downloads them to a repository on a laptop or
workstation. If your system is already running the latest software, the VNX Download wizard will not make
a recommendation.
You also have the option of downloading the appropriate file and block software manually without being
connected to the system. This option is useful if you want to download the software and perform the
installation at a later time.
Block software uses a file extension of .pbu,while File software uses extensions of .tar and .iso.
• Block must be downloaded to the following location:

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 37 of 165
 C:\EMC\repository\Downloads\VNX\date\xxxx.pbu
where:
date = the date in the format of year, month, day (2011-01-02) xxxx = block software bundle name
(CX5-Bundle-05.31.000.4.012.pbu)
• File must be downloaded to the following location:
C:\EMC\repository\Downloads\VNX\date\7.0.11.1.upg\xxxx.tar and xxxx.iso
where:
date = the date in the format of year, month, day (2011-01-02) xxxx = version of the file download
(7.0.11.1.tar)

Note: The name of the download directory must match the version of the release that you are
downloading. For example, if the version that you are downloading is 7.0.11.1, the download directory
must be named 7.0.11.1.upg.

To download VNX software updates:

1. [ ] After launching the USM, select Downloads > Download VNX Software Updates and choose:
• This selection is available only if you have selected a VNX system if you are logged in to a system
and want to accept the default software selection, or
• I will enter the storage system information if you want to manually select the system software
whether or not you are logged in to a system. Use the drop down list to make your software
selection.
2. [ ] For the Storage System Type, select:
• VNX or VNX for File to download updates for both file and block components, or
• VNX for Block to download Block updates only.

Note: Enablers and language packs reside on the Block side of your VNX system. Select the VNX
for Block option to install these on your VNX or File system.

3. [ ] Follow the remaining steps in the wizard to complete the software download.

CAUTION: If you manually download the File software, verify the size and checksum of the .tar
before continuing with the software upgrade.

Running the System Software wizards

1. [ ] Start the Unisphere Service Manager (USM) by doing either of the following:
• Click the Unisphere Service Manager icon on your desktop, or
• Select Start > All Programs or Start > Programs, then select EMC > Unisphere > Unisphere
Service Manager > Unisphere Service Manager
2. [ ] Log in to your system.

Note: You must first download the software packages using the USM Downloads wizard. Then, use
the Prepare for Installation and Install Software wizards to complete the installation of the software
packages.

3. [ ] For block upgrades, from the System screen, select Software > System Software > Prepare for
Installation.
Follow the recommended steps in the Prepare for Installation wizard.

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 38 of 165
 Note: The Prepare for Installation wizard applies ONLY for Block upgrades—it is not intended for File
upgrades.

4. [ ] Once the Prepare for Installation wizard has run, or if upgrading VNX for File software only,
proceed with the Install Software wizard to install enablers, language packs, block or file software.
Select Software > System Software > Install Software.
5. [ ] Follow the instructions to install the desired software packages.
• Install VNX OE
• Install VNX for File
• Install VNX for Block
After the software installation is complete, the system reboots automatically. After the block upgrade,
the secondary SP reboots. When that SP comes back up, the primary SP is updated and then
reboots. For a file upgrade, the Control Station may also reboot.
If the USM logs out during a block upgrade, the upgrade continues. If this happens, log in to USM and
check the status of the upgrade by selecting Software > System Software. Under the Tools list, select
Software Maintenance Status.
You cannot start Unisphere on the system until the reboot is complete, which could take
approximately 45 minutes for each SP. The reboot is complete when the SP status lights on each SP
are in the on state steadily. Wait until both reboots are complete before continuing.
A health check is performed after the file software is upgraded. Note that the number and content of
the post-upgrade health checks may differ from those performed before the upgrade. Be sure to
review the results of the health check, and if any problems are detected, resolve them before using
your system.
6. [ ] When the installation is complete, select Notify your service provider with updated storage
system configuration information, and click Finish.

Note: If the newly-installed software requires a commit, the last step in the wizard provides the option
to make the commit.

7. [ ] Close the USM.

Additional steps to perform after the upgrade

1. [ ] Look for any fault lights on the system components and resolve these issues before proceeding.
2. [ ] Restart all SAN Copy sessions and any other replication software activities that were stopped
prior to this upgrade.
3. [ ] Confirm the cache settings are properly configured. If new replication software was added, cache
settings may not be able to be set as they previously were.
4. [ ] If there are any unowned private LUNs, the ownership will revert to the status of "owned" once
the clones, mirrors, or snapshots start up. Alternately, you can try deallocating/reallocating LUNs from
the CPL, WIL, or reserved LUN pool.
5. [ ] If there is a VMware server attached to the system, read knowledgebase article emc190865 on
how to trespass LUNs back to their default owners on VMware servers.

Verifying the VNX for Block software installation with Unisphere

4. [ ] Start Unisphere for the system by entering the IP address of an SP in the system in a browser
window.
5. [ ] Select All Systems > System List.
6. [ ] Right-click the system and select Properties. The Storage System Properties window appears.

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 39 of 165
 7. [ ] Select the Software tab.
8. [ ] Verify that the list contains an entry for each software package that you installed and that each
entry is listed as Active and does not require a commit.
9. [ ] If an entry for a software package that you installed requires a commit, select the entry and click
Commit.

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.

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 desired option:
• Prepare new cluster for connection– To prepare the new cluster for connection to an existing
RecoverPoint system. Continue to step 4
• Connect new cluster to an existing system– To connect the new prepared cluster to an existing
RecoverPoint system. Continue to step 7
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, log in with boxmgmt credentials.
6. [ ] On the Connect Now or Later screen, select the desired option:
• Connect the new cluster to an existing RecoverPoint system– Select this option only if you are
able to communicate with the existing RecoverPoint system. Click Next. Continue to step 7.
• Connection the new cluster at a later time– Select this option if you are unable to communicate
with the existing RecoverPoint system, or you do not want to connect the new cluster now. Be
sure to copy the internal cluster name (only displayed if preparing a new physical RPA cluster)
and RPA WAN IP address and use them to connect later. Click Finish to exit the wizard. When
you rerun the wizard to connect the new cluster to the existing system, in step 3, select
Connect new cluster to an existing system.
Do not install a license in, or modify the settings of, the new cluster before connecting it to the existing
system.
7. [ ] On the Connection prerequisites screen, if any of the conditions are not fulfilled, close the wizard,
fulfill the conditions, and run the wizard again.
8. [ ] In the Existing cluster login credentials screen, enter the cluster management IP address or the
IP address of RPA 1 or RPA2; and enter boxmgmt credentials.
9. [ ] On the Cluster connection settings screen, if you are connecting a new cluster to an existing
system, enter the Internal cluster name and RPA WAN IP address. These values were displayed on
the Connect now or later screen.
If you select IP, you can add an additional WAN gateway. 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 or if no WAN gateway is specified. Otherwise, this section can be left
blank.
10. [ ] 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.

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 40 of 165
11. [ ] When the Summary screen appears, you have completed the connection of the new cluster, and
you can start using Unisphere for RecoverPoint.
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.

Register RecoverPoint
Select the Register RecoverPoint menu to fill out or update your
RecoverPoint post- deployment form and automatically send it to the
EMC Install Base Group, registering your RecoverPoint product.

Register your RecoverPoint system

Register your RecoverPoint system after:
• installing a RecoverPoint system
• connecting RPA clusters in a RecoverPoint system
• upgrading a RecoverPoint system
The RecoverPoint registration process will fail if you do not first configure your SMTP address on page
227.
The registration process will be incomplete if valid values are not provided for every field in the post-
deployment form.
When a new RPA cluster is added to the system, it is automatically added to the post- deployment form
with empty parameter values. Ensure you have entered the values for all new RPA clusters before
sending the post-deployment form to the IB group.

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 41 of 165
2. Select Admin > Register RecoverPoint to display the RecoverPoint Post-Deployment Form.
3. Click Update Form to display the Update Post-Deployment Form Details dialog box.

4. In the Update Post-Deployment Form Details dialog box:

1. Select the relevant RPA cluster from the RPA Cluster drop-down.
2. Update the form information according to the instructions in the following table.

Field Description For Example

Activity Type Enter the type of activity you are Upgrade

performing (upgrade,
installation)
Location The city, state and country New York, New York, USA
where the customer is located.

Field Description For Example

Upgrade/ Enter the role of the Customer

Installation person performing this
Performing upgrade or installation
Resource activity

Sales The customer or Customer 62276566

Order Engineer should provide
Number this information

VCE Indicate whether or not this Selected=Yes

RecoverPoint implementation
Unselected=N
is operating within a VCE
(Vblock) environment. o or Unknown
VCE = VMware+Cisco+EMC

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 42 of 165
 Connect Home The method used to send Software: ESRS (preferred), E-
configuration reports and alerts mail, Not Allowed
to EMC. Enabling this feature is
Hardware: Not Applicable
recommended as it allows EMC
to pro-actively address issues
within your RecoverPoint
environment, should they arise.

Configure System Reports and

Alerts on page 226” to establish
connectivity for your
RecoverPoint environment.

Connect In The method used to allow Software: ESRS (preferred),

remote connectivity to your WebEx, or Not Allowed
RecoverPoint environment.
Hardware: ESRS (preferred,
Enabling this feature is
WebEx, or Not Allowed
recommended as it allows
secure access to your
RecoverPoint environment to
gather logs and resolve issues
as expeditiously as possible.

If you already have an ESRS

Gateway servicing other EMC
products, simply use the ESRS
Config Tool (refer to the EMC
Secure Remote Support
Gateway Operation Guide for
further instructions on Config
Tool usage) to add your
RecoverPoint devices (or have
your gateway administrator do it
for you) to the list of ESRS
monitored environments. Once
the device is added, click the
request update button to send
the new device information to
EMC and contact

Field Description For Example

your local EMC Customer

Engineer to approve the update.

If you do not have an ESRS

Gateway at your site, contact
your EMC Account Manager to
find out more about the benefits
of ESRS.

3. Click Apply to save each change to the form, without closing the dialog box.
4. Click OK to save all changes and close the dialog box.
If your company does not have SyR connectivity, and therefore, you cannot Configure system
reports and alerts on page 227, you can skip the rest of the steps in this procedure, Export the
post-deployment form to a CSV file on page 186 and Registering RecoverPoint by email or phone
on page 186 now.

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 43 of 165
 5. Click Send Form to automatically send the post-deployment form to the EMC Install Base group. The
Send Form dialog box is displayed.

6. In the Send Form dialog box, enter the email address of the person at your company that is in charge
of RecoverPoint maintenance and operation.

Note: Call home event 8000 is sent to EMC with your updated registration information and an email is sent
to the specified email address from EMC Customer Support to verify that your registration details were
updated successfully in the EMC Install Base.

7. Wait a couple of minutes.

8. Select Dashboard > System Events and look for events 8000 “Calling home”Calling home”. If event
8000 is logged; the registration details were successfully sent to the EMC Install Base.
The following information is automatically sent along with the information that you entered into the post-
deployment form, per RPA cluster:
• Software serial ID
• Hardware serial IDs for RPAs 1-8
• RecoverPoint software version
• Cluster namelLicense type
• Connect home method
• The System ID (identical for all RPA clusters in a RecoverPoint system)

Export the post-deployment form to a CSV file

You can save your RecoverPoint registration information or Registering RecoverPoint by email or phone
on page 186 by exporting the RecoverPoint post-deployment form and allof its contents as a comma-
delimited file () that can be opened in MS Excel or any*.csvother reader of CSV files. The Activity Date
field in the exported CSV file contains the date and time that the file was exported.

1. Select Admin > Register RecoverPoint.

2. Click the Export button at the top right corner of the screen.
3. In the Export dialog box:

1. Select the desired export options and click Next.

2. Click Download to download the file to your computer, select a location on your computer to store
the file, and click Save.
4. Open the exported file:

1. Open MS Excel.
2. Open the *.csv file from the location you selected in the previous step. The Excel Text Import
Wizard is displayed to help you set the import options.
3. In the Excel dialog box, select Delimited, and click Next.
4. In the Delimiters field, select Comma, and click Next.
5. Click Finish.

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 44 of 165
Licensing RecoverPointRegistering RecoverPoint by email or phone
Registers RecoverPoint if your company does not have external connectivity, and therefore you cannot
register your RecoverPoint system online.
Register your RecoverPoint system after:
• installing a RecoverPoint system
• connecting RPA clusters in a RecoverPoint system
• upgrading a RecoverPoint system
The registration process will be incomplete if valid values are not provided for every field in the post-
deployment form.

1. Access https://support.emc.com
2. Search for the term Post-Deployment Form
3. Download and fill out the EMC RecoverPoint and RP for VMs Post-Deployment Form
4. Send the information to the EMC Install Base group:
EMC customers and partners: Email the post-deployment form to the Install Base group at
[email protected].
EMC employees:
(Preferred) Use the IB Portal at http://emc.force.com/BusinessServices.
Call in the information to the Install Base group at 1-866-436-2411 – Monday to Friday (regular Eastern
Time Zone working hours).

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 45 of 165
AudienceThis guide describes the EMC® RecoverPoint 4.0 ordering and licensing process. It details the
Overview
ordering rules and options, licensing rules and processes, typical use cases, terminology and
FAQs.
Note: The complete end-to-end process is detailed in pages 51 to 87. The rest of this
document contains the use cases, reference materials, and FAQs to provide all of the
information that you should need during the procedures.

This guide is intended for use by EMC sales, professional services and support teams, and RecoverPoint
partners, who are responsible for ordering, licensing and installing RecoverPoint software.
Readers of this document are expected to be familiar with EMC RecoverPoint technology and
components, as listed in Appendix I: RecoverPoint Ordering and Licensing Terminology on page 155.

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 46 of 165
The RecoverPoint 4.0 System Architecture and Terminology
This section illustrates the new RecoverPoint system architecture and gives a high-level overview of key
factors in the new RecoverPoint terminology.

Figure 1 RecoverPoint system

Figure 1 illustrates the new RecoverPoint system architecture and the new terminology that is related to it.
Note: Since RecoverPoint now supports up to 5 RPA clusters, the RecoverPoint terminology
has changed from previous RecoverPoint versions. See Appendix I: RecoverPoint
Ordering and Licensing Terminology for the complete list of new RecoverPoint
terminology.

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 47 of 165
Table 1 RecoverPoint 4.0 terminology

Term Description
RecoverPoint system All of the RecoverPoint components that are used to
replicate and protect data, at all sites, including all RPA
clusters. There can be up to five RPA clusters in a
RecoverPoint system.
Account / System ID The unique identifier of all RPA clusters in a RecoverPoint
system.
Note: In RecoverPoint 4.0 and later version, the Account
ID is used to display the System ID.
RPA cluster A group of 2-8 physical (or virtual) RPAs at the same
geographic location, that work together to replicate and
protect data are called an RPA cluster. There can be up to
five RPA clusters in a RecoverPoint system.
The number of RPA clusters and the number of RPAs in
an RPA cluster is set during RecoverPoint system
deployment.
The number of RPAs in an RPA cluster must be the same
at all RPA clusters in a RecoverPoint system.
Each RPA cluster is identified by a unique RPA cluster ID.
The RecoverPoint/CL license model is enforced to the
RPA cluster ID.
Also known as: RecoverPoint cluster
Local copy/Local Note: The previous term “CDP” has been replaced by the
replication new term “local replication”.
RecoverPoint entities are prefixed with the word “local”
with relation to the geographical location of the
production. For example, a local copy, local storage, local
host, local site, or local RPA cluster are the
copy/storage/site that are local to the (or in other words,
are situated in the same) geographical location, as the
production.
Similarly, “local replication” means that you are replicating
to a copy that is in the same geographical location as the
production.
Remote copy/Remote Note: The previous term “CRR” has been replaced by the
replication new term “remote replication”.
RecoverPoint entities are prefixed with the word “remote”
with relation to the geographical location of the
production. For example, a remote copy, remote storage,
remote host, remote site, or remote RPA cluster are the
copy/storage/site that are remote to the (or in other words,
situated in a different) geographical location of the
production. Similarly, “remote replication” means that you
are replicating to a copy that is in a different geographical
location than the production.

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 48 of 165
Phase 4321 - Reporting
Licensing
Installing
Ordering

The RecoverPoint 4.0 Ordering and Licensing Process

The ordering and licensing process for the new RecoverPoint system consists of four phases;
ordering, activating, installing, and reporting.

RecoverPoint ordering is performed by EMC Sales (through Direct Xpress) or the EMC partner
(through Channel Xpress). The order is submitted and processed, and the customer receives
email notification of his entitlements. The eLicensing-enabled software details are made
available through the EMC Online Support (NGOE) website (support.emc.com).
Note: This phase is detailed in Phase 1 – Ordering RecoverPoint on page 51.

Activate entitlements by logging into EMC Online Support and generating a license file for each
entitlement. As part of this process, for RecoverPoint/EX and RecoverPoint /SE entitlements
you will have to provide all array serial numbers, and for RecoverPoint/ CL entitlements you will
have to provide RPA cluster IDs. Activation turns your entitlements into license files
recognizable by the RecoverPoint system.
Note: This phase is detailed in Phase 2 – Licensing RecoverPoint 4.0 on page 56.

Install the license files in the RecoverPoint system.

Note: This phase is detailed in Phase 3 - Installing License Files in Unisphere for
RecoverPoint on page 82.

Report back to the EMC back office. In RecoverPoint, set up system notifications and test
connectivity to enable support and automatically report back to the EMC back office, by sending
a Call Home event to SyR.
Note: This phase is detailed in Phase 4 – Reporting Back to EMC via Unisphere for
RecoverPoint on page 84.

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 49 of 165
End-to-end process diagramThe following diagram illustrates the end-to-end ordering and licensing
process.

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 50 of 165
How to order RecoverPointPhase 1 – Ordering RecoverPoint via Direct
Xpress or Channel Xpress

The following guidelines were created to assist you when deciding which RecoverPoint licensing
model to offer to a customer.
Choosing the right RecoverPoint option
RecoverPoint licensing is performed based on where you want to replicate from (or in other words, the
array on which the RecoverPoint splitter resides).
For example, if the splitting is performed on a VNX array, then a RecoverPoint/SE or RecoverPoint/EX
license is required. If the splitting is performed on a VMAX or VPLEX array, a RecoverPoint/EX license is
required.
Note: For non-EMC storage arrays, RecoverPoint/EX for VPLEX is recommended.

RecoverPoint license types

Following are the types of licenses offered by RecoverPoint, and the scenario in which you would choose
each:
• RecoverPoint/SE for replicating from VNX series, CLARiiON CX3 and CX4, and Celerra
Unified storage environments.
• RecoverPoint/EX for replicating across EMC storage including; Symmetrix VMAX™
Series (VMAX, VMAX 10K, VMAX 20K, VMAX 40K), VPLEX™ Local and Metro, VNX™
Series, and CLARiiON® CX3 and CX4 Series.
Note: RP/SE and RP/EX are array/platform-based licensing.

• RecoverPoint/CL for replicating across EMC and non-EMC storage platforms.

Note: RP/CL is cluster-based licensing.

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 51 of 165
 RecoverPoint ordering and licensing basics
Table 2 describes the general guidelines for RecoverPoint ordering and licensing.
Table 2 RecoverPoint licensing guidelines

RecoverPoint/SE RecoverPoint/EX RecoverPoint/CL

Where To • RecoverPoint/SE for • RecoverPoint/EX frame- Sold via the

Order VNX is orderable as part based for VNX/CX/NS RecoverPoint Ordering
of the VNX software CLARiiON arrays is path
suites /packs orderable via the
• RecoverPoint/SE for RecoverPath Ordering
CLARiiON/ Celerra NS path
is orderable via the • Existing RP/SE
RecoverPoint Ordering customers with
path – Upgrade Solution VNX/CX/NS can upgrade
path from RP/SE to RP/EX in
the RecoverPoint
Ordering license upgrade
solution path
• RecoverPoint/EX
registered capacity for
VMAX and VPLEX is
orderable via the
RecoverPoint Ordering
path or via the specific
array ordering path
• RP/EX RAW capacity is
orderable only via the
VMAX10K ordering path
• RecoverPoint/EX for
VPLEX with frame-based
VNX is orderable via the
RecoverPoint Ordering
path or the VPLEX
solution path

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 52 of 165
 RecoverPoint/SE RecoverPoint/EX RecoverPoint/CL

How to Order • Local replication, RP/EX frame-based for VNX/CX • Local replication,
remote replication, CLARiiON arrays remote replication,
or local and remote • Local replication, remote or local and remote
replication1 replication, or local and replication
• Local replication and remote replication • Local replication and
remote replication • Local replication and remote remote replication
are sold separately replication are sold separately are sold separately
RP/EX registered capacity for • Ordered according
VMAX arrays to replicated
capacity (total
• Local replication and remote capacity replicated
replication are sold separately via the RP Cluster)
• Registered capacity is • Support all
ordered according to VMAX RecoverPoint
array registered capacity, so splitters
only the specified (partial)
capacity of a given array can
be licensed for replication
RP/EX RAW capacity for VMAX
10K
• SATA and Non-SATA
capacities are sold separately
RP/EX registered capacity for
VPLEX
• Local replication and remote
replication are sold separately
RP/EX for VPLEX with frame-
based VNX
• Local replication and remote
replication are sold separately
• VPLEX with VNX frame-
based is ordered based on
the VNX array
Note: CX/NS arrays are not
supported with this option.
• RAW capacity for VMAX10K
is licensed according to total
SATA and Non-SATA
capacity of the array

1 p/o VNX protection suites/packs

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 53 of 165
 RecoverPoint/SE RecoverPoint/EX RecoverPoint/CL

Supported Limited to single VNX, Multiple EMC arrays (block) per Multiple heterogeneous
configurations VNX2, CX3, CX4 or NS site arrays per site, per ESM
(Unified) to a single Notes:
VNX, CX3, CX4 or NS
(Unified) Non-EMC arrays are
supported via VPLEX or
VMAX with FTS
Any storage behind
VPLEX/VMAX (FTS)
with RP/EX is also
supported.
Supported • VNX/VNX2 Series • Symmetrix VMAX Series Heterogeneous (per
arrays (VMAX, VMAX 10K, VMAX ESM)2
• CLARiiON CX3/CX4
Series 20K, VMAX 40K) Notes:
• VPLEX Local and Metro Non-EMC arrays are
• Celerra NS Unified
storage • VNX Series supported via VPLEX
• CLARiiON CX3/CX4 Series Any storage behind
VPLEX/VMAX (FTS)
with RP/EX is also
supported.
Number of Limited to single array • Multiple EMC arrays4 • Multiple arrays5
arrays per site for local replication and
• Unlimited number of array per • Unlimited number of
up to two arrays (one
sites arrays per site
per site) for remote
replication.3 • License is not tied to
arrays
License Per array, Local Per array, Local replication and Sold per RP Cluster,
replication and remote remote replication are licensed Local replication and
replication are licensed separately remote replication are
separately licensed separately
Capacity Not required Additional capacity can be Additional capacity can
Upgrade purchase via the RecoverPoint be purchase via the
Ordering path – Upgrade solution RecoverPoint ordering
path or via the specific path – Upgrade solution
VMAX/VPLEX ordering paths. path
Note: no capacity upgrade is
required for RecoverPoint/EX for
VNX/CX arrays

2 Array type and quantity is ignored

3 Array quantity is enforced x 1 array per site
4 Array quantity is enforced
5 Array quantity is ignored

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 54 of 165
The RecoverPoint order summary
The RecoverPoint order summary will include either three models (base + license + LS) or two
models (license + LS).
• 457 model: A 457 model number is considered the 'parent' of the 456s ordered with it.
The 457 carries the base price and will show only in the order summary.
• 456 model: The 456 models are the capacity tiers and carry the RecoverPoint license
and a price.
• License solution: The function of a license solution is to ensure that the ELM models
interface correctly in EMC back office systems. The RecoverPoint license solution is
called RP-LS.
Note: The RecoverPoint license solution (RP-LS) is required for all RecoverPoint eLicensing
offerings.

The RecoverPoint standalone ordering path

The following screenshot is of the new RecoverPoint standalone ordering path.

Figure 2 RecoverPoint standalone ordering path

Note: When entering the information in the order form, select the RPA in the first row. In a
mixed array configuration, always start in the following order: VPLEX, VMAX40K/VMAX
20K, VMAX, VAX10K, and VNX/CX. RecoverPoint/EX raw for VMAX 10K is orderable
only in the VMAX 10K path.

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 55 of 165
 The new RecoverPoint standalone ordering path includes the following
Licensing guidelinesenhancements:
•Order multiple arrays through the same order screen
• Order local replication and remote replication through the same order screen
• Add RPAs through the same order screen
• Select the RPA type and quantity through the same order screen
• Order RecoverPoint/EX for VNX directly, without going through the VNX ordering path

Phase 2 – Licensing RecoverPoint 4.0

Licensing options at-a-glance

Table 3 describes the RecoverPoint licensing options.
Table 3 RecoverPoint 4.0 licensing options

RecoverPoint/SE RecoverPoint/EX RecoverPoint/CL

Use cases Limited to replication Support all EMC arrays ▪ Customer has
between two VNX/CX heterogeneous
arrays storage
▪ License is not
tied to arrays
▪ Survives storage
refresh
Rules ▪ Tied to specific VNX ▪ VMAX and VPLEX: ▪ License is not
▪ Supports full VNX/CX Capacity-based, tied to any array
array capacity License is tied to a and can be
VMAX/VPLEX array, transferred to
▪ Limited to replication Licensed per array different arrays
between VNX/CX and survives
arrays VNX: Frame-based
capacity License is tied array refresh
Limited to one array per to a VNX array. Not
site limited to two VNX/CX
arrays for remote
replication (one array
per site)
What is ▪ Array type ▪ Array type ▪ Capacity
enforced
▪ Array quantity ▪ Registered capacity, ▪ RPA Cluster ID
▪ Array S/N as purchased
▪ Raw SATA and non-
SATA total capacity
▪ Array S/N
Locking ID ▪ VNX/CX array serial VNX/CX, VPLEX or RPA Cluster ID
number Symmetrix array serial
number

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 56 of 165
 When to ▪ More than two N/A N/A
upgrade VNX/CX arrays are
required
▪ More than two RPA
clusters are required
▪ Replicating from
VNX/CX to
VMAX/VPLEX
▪ Hardware refresh to
VMAX (all arrays in
the clusters need to
upgrade to
RecoverPoint/EX
license)

Table 4 describes RecoverPoint 4.0 licensing guidelines.

Table 4 RecoverPoint 4.0 licensing guidelines

Licensing Model Licensing Rules License capacity

• Licensed per array (See Appendix G: How to • Total Capacity
Find Locking IDs) of array up to 2
• Local replication and remote replication are PB
RecoverPoint/SE licensed separately • Frame-based
• The license is non-transferable (does not capacity
(P/O VNX/VNX2
Protection Packs) survive array tech
• refresh)
• The license is tied to the VNX/CX array serial
number
RP/EX for VNX/CX arrays • Total capacity
• Licensed per array (See Appendix G: How to of the array
Find Locking IDs) • Frame-based
• Local replication and remote replication are capacity
licensed separately
• The license is non-transferable (does not
survive array tech refresh)
• The license is tied to the VNX/CX array serial
number
RP/EX registered capacity for VMX
RecoverPoint/EX
• Licensed per array (See Appendix G: How to
Find Locking IDs)
• Licensed per tier TB capacity
• Local replication and remote replication are
licensed separately
• License is tied to the Symmetrix ID (SymmID)
• License is non-transferable and does not
survive array tech refresh
• Additional capacity requires the purchase of a
new license

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 57 of 165
Licensing Model Licensing Rules License capacity
RP/EX for VMX (RAW)
• RecoverPoint raw capacity licensing is
available only for the VMAX 10K
• Licensed per VMAX 10K array
• SATA and non-SATA are licensed separately
• VMAX 10K array (See Appendix G: How to
Find Locking IDs)
• License is non-transferable and does not
survive array tech refresh
RP/EX registered capacity for VPLEX
• The RecoverPoint/EX for VPLEX license is per
VPLEX array/cluster
• Licensed per tier TB capacity
• Additional capacity requires the purchase of
additional licenses
• Local replication and remote replication are
licensed separately
• License is tied to the VPLEX array serial
number
• License is non-transferable but it does survive
back-end array tech refresh
Note: A RecoverPoint local replication license with
a capacity of 40 TB is bundled with the VPLEX
Metro Express (for a total local replication capacity
of 80 TB).

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 58 of 165
Licensing Model Licensing Rules License capacity
RP/EX for VPLEX with frame-based VNX
• License is per VNX array model
• Local replication and remote replication are
licensed separately
• License is based on the VPLEX splitter
• License is tied to the VPLEX array serial
number and lasts for the entire VNX array
lifetime
• The full VNX array capacity is supported
• License is non-transferable and does not
survive array tech refresh
• Upgrading the VNX array requires the
purchase of a new license
• There is no capacity enforcement; customers
are entitled to replicate the entire array through
the VPLEX splitter, using one or more
RecoverPoint clusters, as required.
• Not available for CLARiiON arrays
• Existing RecoverPoint/SE or RecoverPoint/EX
for VNX customers cannot convert their license
to this option
Notes:
▪ A separate RecoverPoint/SE or RecoverPoint/EX
license is required to replicate VNX arrays (using
VNX splitter)
▪ RecoverPoint/EX for VPLEX with VMAX and
non-EMC arrays should continue to purchase the
RecoverPoint/EX registered capacity for VPLEX
license (per TB capacity)
▪ The VNX frame-based license with the full VNX
capacity does not count towards
RecoverPoint/EX for VPLEX tier capacities

• License is per RecoverPoint cluster Licensed by

Replicated
• Local replication and remote replication are
Capacity
licensed separately
• License is per tier TB of replicated capacity
• Additional capacity requires the purchase of
RecoverPoint/CL
additional licenses
(Classic)
• The license is tied to the RPA cluster ID
• License is non-transferable but it does survive
array tech refresh
• Third party arrays are supported when arrays
support VPLEX, or VMAX with FTS

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 59 of 165
Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 60 of 165
Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 61 of 165
Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 62 of 165
Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 63 of 165
Licensing process overviewThe RecoverPoint licensing terminology is presented in Appendix I:
RecoverPoint Ordering and Licensing Terminology.
RecoverPoint licensing is performed through Powerlink Licensing.
Note: Powerlink Licensing has moved from Powerlink at
http://www.powerlink.emc.com to EMC Online Support at
http://support.emc.com. Since Powerlink Licensing is an application
portal, it is still referred to as Powerlink Licensing even though it is now accessed
through EMC Online Support.

Licensing process at-a-glance

The RecoverPoint eLicensing process can be summarized as follows:
1. Immediately upon submission of your sales order, a LAC email is sent to the address provided during
order entry, containing a new License Authorization Code (LAC) for all of your purchased
entitlements. A sales order can contain multiple LACs. In this case, a separate LAC email is sent for
each LAC contained in the sales order.
2. Click the Click here link in the LAC email to automatically access the RecoverPoint licensing area of
the EMC Online Support site and display all of the entitlements associated with your LAC.
3. In the RecoverPoint licensing area of the EMC Online Support site, activate and generate a License
File for each entitlement.
You will install your license files on the RecoverPoint system in Phase 3 - Installing License Files in
Unisphere for RecoverPoint on page 82.

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 64 of 165
 Table 5 describes additional licensing guidelines.
Table 5 Additional licensing guidelines

Existing License
License Solutions
New RP Customer
None RP VPLEX/EX VPLEX/EX RP/CL replicated
VNX behind
VNX frame- registered capacity
VPLEX
based license capacity
RP VPLEX/EX VPLEX/EX RP/CL replicated
VNX frame- registered capacity
based for VNX capacity
VNX + VMAX,
Behind VPLEX VPLEX EX
registered
capacity for
VMAX
VPLEX/EX VPLEX/EX RP/CL replicated
frame-based registered capacity
VNX+ non EMC for VNX capacity
VPLEX EX for
non-EMC
VPLEX/EX VPLEX/EX RP/CL replicated
VMAX + non
License registered capacity
EMC
capacity
Existing RP Customer
Protection ▪ Purchase RP VPLEX/EX RP/CL replicated
Pack VPLEX/EX registered capacity
frame-based capacity
license for
VNX behind VNX
VPLEX
▪ Purchase
VPLEX VNX
frame-based
license

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 65 of 165
 Existing License
License Solutions
Protection ▪ Purchase RP VPLEX/EX RP/CL replicated
Pack + VPLEX/EX registered capacity
VMAX/EX frame-based capacity
license for
VNX
▪ Purchase
VPLEX VNX
frame-based
VNX + VMAX, license for
Behind VPLEX VNX
▪ Purchase
VPLEX/EX
for VMAX
▪ Purchase
VPLEX
registered
capacity for
VMAX
Classic or ▪ Will require RP/CL replicated
Classic + continuing capacity
Protection using the
Pack RP/CL
replicated
capacity
▪ Unable to
mix license
models
VNX+ non-EMC ▪ Purchase
VPLEX VNX
frame-based
license for
VNX
▪ Purchase
VPLEX
registered
capacity for
the non-EMC
array

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 66 of 165
 Existing License
License Solutions
Classic or ▪ Will require RP/CL replicated
Classic + continuing capacity
VMAX/EX using the
RP/CL
replicated
capacity
▪ Cannot mix
VMAX+ non- license
EMC models
▪ Purchase
VPLEX
registered
capacity for
VMAX the
non-EMC
array

Note: The table assumes using VPLEX-splitter for all options.

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 67 of 165
Licensing illustrations
The following diagram illustrates the connection between RecoverPoint licensing models, sales orders
and licensed entities.

Note: Depending on the RecoverPoint licensing model, a separate license is required for each
unique array or RPA cluster.

Licensing examples
The following figure illustrates a RecoverPoint/SE environment with a VNX7500 at the production site
replicating data both locally and remotely to a VNX5300.

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 68 of 165
Since RecoverPoint/SE is frame-based and not capacity-based, the amount of data being replicated is
not limited or capped when determining the proper licensing for this environment. The only licenses that
are required are a RecoverPoint/SE local and remote replication license for the VNX7500 and a
RecoverPoint/SE remote replication license for the VNX5300.
The following diagram illustrates a RecoverPoint/CL environment with a VNX5700, a VMAX 40K, and a
VPLEX fronting two non-EMC storage arrays at the production site and a VNX5500 and a VPLEX fronting
two non-EMC arrays at the remote site.

In this illustration, both sites are protecting 150 TB locally, and the remotely replicated data between both
sites is 100 TB. In this case, you would have a RecoverPoint/CL local replication license for 150 TB and a
RecoverPoint/CL remote replication license for 100 TB.
Note: For RecoverPoint 4.0 there is no need to split the total RecoverPoint/CL capacity
between the two sites. Each site is licensed for the total capacity it will replicate.

Before you begin

Before you begin, note the following rules that apply to the Licensing process in Unisphere for
RecoverPoint:
• All RecoverPoint licenses are per array or RPA cluster. RPA cluster and storage array
licensing is enforced using the Locking ID in the license file.
• If a license Locking ID contains an array serial number that is not recognized by
RecoverPoint, you can install the license in RecoverPoint but it will not be tied to an RPA

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 69 of 165
 cluster and the license will not be activated until
How to license new RecoverPoint purchasesthe array is mapped and zoned to an RPA
cluster.
• You cannot add a volume that resides on an unlicensed array to a replication set. Only
volumes that reside on licensed arrays are displayed in the volume list. This limitation
does not exist for journal volumes or repository volumes.
• For consistency groups containing both a local copy and a remote copy: If you select to
fail over to the remote copy and the remote RPA cluster does not have enough licensed
replication capacity for two times the capacity of the remote copy, the failover will fail and
you will be prompted to remove the local copy for the failover to succeed.
• When removing a license, a warning is issued if removing the license may cause the
system to exceed the allowed replication capacity (for example, when an array license is
removed but an existing consistency group contains volumes that reside on the removed
array).
• When adding or modifying a group, copy or replication set, the licenses of all relevant
arrays and RPA clusters are checked and the action will fail if it causes any of the arrays
or RPA clusters in the system to exceed their maximum licensed replication capacity. If
an array or RPA cluster exceeds its licensed replication capacity, replication continues,
and the removal of groups, copies and replication sets is allowed.
• Installing a RecoverPoint/CL license will fail if:
o The Locking ID contains an RPA Cluster ID that is not recognized.
o A RecoverPoint/SE license already exists.
o A RecoverPoint/EX license already exists (the RecoverPoint/EX license is disabled until the
RecoverPoint/CL license is removed).
• In RecoverPoint/SE, only RecoverPoint/SE licenses can be installed.
• Installing a RecoverPoint/EX license will fail if a RecoverPoint/SE license already exists
on the same cluster, or if a RecoverPoint/CL license already exists (the
RecoverPoint/EX license is disabled until the RecoverPoint/CL license is removed).

Before starting this process, ensure that you have:

• Read Licensing on page 64, and Before you begin on page 69.
• The customer’s LACs (or sales order numbers).
Note: Once the customer’s RecoverPoint sales order is approved, a LAC (License
Authorization Code) email is automatically sent to the email addresses provided during
order entry. If the customer does not have their LAC emails on hand, ask them to search
their email inboxes for any email(s) containing the text ‘EMC License Authorization’ in
the subject line. If they still cannot find their LAC email(s), ask them to contact EMC
Customer Support or call for support (see Appendix H: Where to Get Support on page
155).

• Access to the customer’s entitlements in the Powerlink Licensing portal on EMC Online
Support (see Search for entitlements by navigating to Powerlink Licensing on page 72).
The licensing process contains two main steps:
1. Accessing a customer’s entitlements.
There are two ways to do this:
• By clicking the deep link in the LAC email (if you have it)

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 70 of 165
 • By navigating to the Manage Licenses section of the EMC Online Support site (if you do not have
a LAC email, but you do have the customer’s LACs or sales order numbers).
2. Activating entitlements in Powerlink Licensing
Accessing entitlements via LAC email(s) or EMC Online Support
A customer will need to create a new RecoverPoint purchase order if they are a new RecoverPoint 4.0
customer, or if they want to:
• Add replication capacity in RecoverPoint/CL.
• Add registered capacity in RecoverPoint/EX.
• Upgrade from RecoverPoint/SE to RecoverPoint/EX.
• Upgrade from RecoverPoint/EX to RecoverPoint/CL.
• Add storage arrays in RecoverPoint/EX.
• Add RPAs to your RecoverPoint system.
• Add an RPA cluster to your RecoverPoint system.
• Add raw capacity (for RecoverPoint/EX customers with VMAX 10K arrays with registered
capacity).
• Add back-end array replication (for RecoverPoint/EX customers with VPLEX) No license
is required unless additional capacity is to be added.
• Dynamically change capacity allocations on RPA clusters (for ELA).

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 71 of 165
In all of these cases, the customer will need to make a purchase with EMC Sales or an EMC partner, and
obtain a sales order. As soon as the sales order is approved, the Licensing Ops team feeds the
information into Powerlink licensing and a LAC email is automatically sent to the email addresses
provided during order entry, containing the LAC (License Authorization Code) issued to the customer.
A unique LAC is usually generated and emailed to the customer for each purchase, but this is not always
the case for evaluation licenses or purchases of certain products. Also, in some cases (such as the
addition of multiple arrays in RecoverPoint/EX), multiple LACs will be generated and multiple LAC emails
will be emailed to the customer.
Note:The customer must turn their LACs into license files before they can use them to license their
RecoverPoint system.
To start the licensing process, you can:
• Click the link in the LAC email
• Navigate to Powerlink Licensing on EMC Online Support and search for entitlements by
entering the customer’s LACs or their sales order numbers.
Search for entitlements by clicking the link in the LAC email
In the LAC email, click the Click here link to automatically access Powerlink Licensing on the EMC Online
Support site, and search for the entitlements associated with the LAC.

Note: Quantity is generic in the LAC email for RecoverPoint models. Depending on the
RecoverPoint model, the amount of terabytes for each replicated/protected capacity is
also included in the LAC email.

Search for entitlements by navigating to Powerlink Licensing on support.emc.com

You can also manage all active and inactive licenses in Powerlink Licensing by performing the following
steps:
1. Access and log into EMC Online support at http://support.emc.com
2. Select Service Center from the main menu.

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 72 of 165
 Figure 3 EMC Online Support > Service Center

3. Select Get and Manage Licenses.

Figure 4 Get and Manage Licenses

4. Select RecoverPoint Family.

Figure 5 RecoverPoint Family

5. Click the Activate link in the RecoverPoint version 4.0 and later section to access the
Powerlink Licensing portal.

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 73 of 165
6. In the LAC Request screen, either:

• Enter the customer’s LAC and click the Activate button to search for all inactivated
entitlements associated with a customer’s profile.

• Access all of the features of the Powerlink Licensing site by clicking the Manage
Entitlements button.

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 74 of 165
Note: You can select Activation > Activate Licenses to display all of the inactivated
entitlements associated with a customer profile, from anywhere in the Powerlink
Licensing site.

7. When you have displayed a customer’s inactivated entitlements, you can activate the
entitlements by performing the procedure described in Activating entitlements in
Powerlink Licensing below.

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 75 of 165
Activating entitlements in Powerlink Licensing
After clicking the deep link in the LAC email, or navigating to the RecoverPoint Powerlink Licensing portal
on EMC Online Support and searching for a customer’s active entitlements, the Search Entitlements to
Activate screen is displayed. The Search Entitlements to Activate screen is the first screen of a five
screen wizard that will guide you, step-by-step, through the process of turning the LACs into license files
(redeeming the entitlements).
1. In the Search Entitlements to Activate screen:
The link in the LAC email pre-populates the LAC field and searches for all entitlements
associated with the specified LAC. All relevant entitlements are displayed.

a. Select ONE entitlement to activate. Each entitlement must be selected and activated
separately. There can be multiple RecoverPoint models listed under each entitlement.
b. Click Start Activation Process. The Search Machines dialog box pops-up on top of the
screen.

c. In the Search Machines dialog box, click Add a Machine. The Add Machine dialog box is
displayed.

d. In the Add Machine dialog box, enter a new machine name, and click Save.

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 76 of 165
Note: A machine name is like a folder, it is used to group items together logically. A unique
machine name must be specified for each entitlement. Machine names can be whatever
unique name you choose but it is best practice to relate the machine name to the
Locking ID. For example, in RecoverPoint/SE and RecoverPoint/EX, the Locking ID is an
array serial number. Therefore, the machine name should be RP-APM00120701240 if
APM00120701240 is the array serial number used for the Locking ID. In
RecoverPoint/CL, the Locking ID is the RPA Cluster ID, so the machine name should be
the RPA Cluster ID.

2. In the Register screen, verify the machine name, and click Next.
3. In the Activate screen, enter the Locking ID, and click Next.

The Locking ID is the field that is displayed under the Machine Information column; its value
is whichever entity the license is enforced to.
Depending on the entitlement, the Locking ID can be either an RPA Cluster ID (in
RecoverPoint/CL), or an array serial number (in RecoverPoint/SE and RecoverPoint/EX).
Click the Locking ID help link to display how to find your RPA Cluster IDs and array serial
numbers. Alternatively you can find out how to find your RPA Cluster IDs or array serial
numbers by reading Appendix G: How to Find Locking IDs on page 153.
4. In the Confirm screen, enter the email addresses of the recipients of the license file in the
Email to field of the Additional Email Options section, and click Finish.
By default, the customer contact provided during order entry and the user performing the
entitlement activation are automatically emailed an activation certificate containing the
license file as an attachment. You can enter multiple email addresses in the Email to field.
Separate multiple email addresses with commas. You can also include optional comments
which will be displayed in the certificate e-mail in the Email comments field, or add optional
notes which can only be viewed online in Powerlink Licensing in the Notes for this
transaction section.

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 77 of 165
Upgrading to RecoverPoint 4.0 from previous RecoverPoint versions (LCT)

5. In the Complete screen, click Save to File to download the license file and save the file
locally. The resulting license file has a *.lic extension and is in plain text format (can be
opened in any text editor).

6. Redo this procedure for all inactive entitlement in each LAC email.
7. After you have turned all of your entitlements into license files:
a. Ensure that your license file(s) contain the required information according to Appendix E:
RecoverPoint 4.0 License File Example on page 148.
b. Physically transfer the license file(s) to the computer from which you will be running
RecoverPoint.
c. Install the license files in RecoverPoint according to the instructions in Phase 3 -
Installing License Files in Unisphere for RecoverPoint on page 82.

When upgrading to RecoverPoint 4.0 from previous RecoverPoint versions (legacy licenses), the process
is called a Legacy Customer Transition (LCT).

Legacy Customer Transition process overview

In the LCT process:
• Existing RecoverPoint customer under valid maintenance agreements can upgrade to
RecoverPoint 4.0 using the legacy license (non-ELMS). The upgrade process is a Non-
Disruptive Upgrade (NDU).
Note: After upgrade to RecoverPoint 4.0, the legacy licenses will automatically be converted
to a new temporary license and be valid for 90 days from the upgrade date

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 78 of 165
 • After software upgrade, customers have a 90 days grace period to upgrade the legacy
RecoverPoint license to a RecoverPoint 4.0 license.
Note: Warning messages about temporary licenses will be displayed in RecoverPoint GUI.
Post 90-days, no new actions will be allowed in the RecoverPoint environment, but
RecoverPoint replication will continue as usual.

• License upgrade is a manual process and is performed by opening of a service request

through EMC Support Zone > Manage my Licenses.
• The Licensing Ops team will create new entitlements and will e-mail the License file to
the customer.
Note: The account team and partners will be notified in case of any discrepancies.

Legacy Customer Transition process rules

When upgrading to RecoverPoint 4.0 from previous RecoverPoint versions:
• The process is non-disruptive (NDU) and has no impact on production operations.
• Previous licenses will automatically be converted to the new license format. The new
licenses are temporary and valid for 90 days from the date of upgrade. After that, you
must have installed one or more permanent license files to replicate with RecoverPoint
appliances.
• Warning messages will be displayed in RecoverPoint starting 90-days prior to the
temporary licenses expiration date.
• Post 90-days no new actions will be allowed in the RecoverPoint environment, but
RecoverPoint replication will continue as usual.
• The upgrade process necessitates the opening of a service request, in the service
request; you will need to provide the following information:
• The sales order numbers of all RecoverPoint sales orders in your customer’s possession.

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 79 of 165
 • The customer’s Account/System ID. To display the Account/System ID in any RecoverPoint
version, run the get_account_settings CLI command and look for the Account ID. The Account ID
is the System ID in RecoverPoint 4.0 and later versions.
• All of the array serial numbers of the EMC arrays (VNX, VMAX, VPLEX, etc.) that require
RecoverPoint protection. To obtain your array serial numbers in RecoverPoint 4.0, see Appendix
G: How to Find Locking IDs on page 153.
• The required replication types (local replication, remote replication).
• The required replication capacities.
• The required configuration details (splitter type, splitter sharing, stretch CDP, etc.).
• Any other relevant information.

Legacy Customer Transition process

To upgrade to RecoverPoint 4.0 from previous RecoverPoint versions:
1. Read Before you begin on page 69.
2. Open a Service Request with EMC Customer Support:
To have an EMC representative open the Service Request for you, call 24/7 License Key Live
Support for:
• North America at +1-800-782-4362 > Option 4 > Option 4
• EMEA at +353 (0) 21 487-9862 > Option 1
• APJK at +353 (0) 21 487-9883
To open the Service Request yourself:
a. Access the EMC Support site at http://support.emc.com.
b. In EMC Online Support, click Service Center in the main toolbar, and then click Create a
Service Request.
c. Fill out the fields in the service request according to the instructions in Table 6.

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 80 of 165
Table 6 Submitting an SR for upgrades

Field Instructions
Service Select Technical Problem/Question from the drop-down.
Request Type
Company and Product Information
Search by Site This is the geographical location for which you are requesting the
ID license. If you know the site ID, enter it in this field.
If you do not know the site ID:
1. Expand the Advanced Site Search.
2. Enter your company name and details.
3. Click Search.
4. Select the relevant site ID in the Search Results table.
If you do not see your company’s site ID in the list, contact EMC
Customer Support.
Product Details Select the Choose from all EMC Products radio button.
Start typing the product name into the field to bring up all of the
relevant EMC products, and select the EMC product for which you are
requesting an upgrade from the search results.
Version Select the version number of the EMC product that you want to
Number upgrade from the drop-down.
Contact Information
Initial Contact Select Email.
is Best Made If you select Online, all communication regarding your RecoverPoint
By license key will be through the SR tracking system on EMC Online
Support.
Primary Your license will be emailed to the email address specified here.
Contact Name Select the name of the primary contact person at your company for
RecoverPoint management.
If the email address/es listed under the primary contact name are
incorrect or missing, edit them to update the contact information.
Phone Enter the phone number as an alternative contact method.
If the phone numbers listed under the primary contact name are
incorrect or missing, edit them to update the contact information.
Problem Details
Problem Enter a problem severity of 4.
Severity
Problem Enter the following text into the problem summary field:
Summary License Upgrade Request for SO#: <The Sales Order Number(s) of
Customer’s Latest RecoverPoint Purchase(s)>

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 81 of 165
Installing your license files using the Getting Started wizard
Field Instructions
Problem Enter the following:
Description • Your current RecoverPoint Account/System ID
• All of the array serial numbers of the EMC arrays (VNX, VMAX,
VPLEX, etc.) that require RecoverPoint protection.
• Your required replication types (local replication, remote
replication)
• Your required replication capacity
• Your required configuration details (splitter type, splitter sharing,
Stretch CDP, etc.)

d. Click the Submit button. An SR Tracking number is displayed. Write this number down and
save it for future reference.
Note: In most cases, within 48 hours after submitting the SR, the RecoverPoint license files
are emailed to the email addresses specified in the SR. If you have not received your
RecoverPoint licenses within a month from the time you submitted the SR, contact EMC
Customer Support.

3. Install your RecoverPoint license(s) in RecoverPoint according to the instructions in Phase

3 - Installing License Files in Unisphere for RecoverPoint on page 82.

Phase 3 - Installing License Files in Unisphere for RecoverPoint

Before starting this process, ensure that you have RecoverPoint 4.0 installed all of the RPAs in your
RecoverPoint system. If you do not have RecoverPoint 4.0 installed, see the EMC RecoverPoint
Installation and Deployment Guide for installation instructions, and install RecoverPoint before starting
this procedure.
You can install your license files on the RecoverPoint system through:
• The Unisphere for RecoverPoint Getting Started wizard, when Unisphere for
RecoverPoint loads for the first time.
• The Unisphere for RecoverPoint Admin > Manage Licenses screen, every subsequent
time that Unisphere for RecoverPoint loads.

When Unisphere for RecoverPoint loads for the first time, the RecoverPoint Getting Started wizard is
displayed. The Getting Started wizard guides you, step-by-step, through the process of installing your
license file(s) in the RecoverPoint system and enabling RecoverPoint support (as performed in Phase 4 –
Reporting Back to EMC via Unisphere for RecoverPoint on page 84).
To start protecting your data with RecoverPoint, in the Welcome screen of the Getting Started wizard,
click Next Add Licenses to go on to the Add Licenses screen.
Note: The settings in the Add Licenses screen are displayed both through the Getting Started
wizard (the first time you launch Unisphere for RecoverPoint), and also in the Admin >
Manage Licenses screen, each subsequent time that Unisphere for RecoverPoint is
launched (see Installing your license files using Admin > Manage Licenses on page 84).
In the Add Licenses screen, for each license file:
1. Click Add to display the Add License dialog box.

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 82 of 165
 2. Click Browse... and select a license file.
3. Click OK to add the license file to the RecoverPoint system.
Verify that the information that is displayed in each row and column of the Licenses table contains the
correct information, according to Appendix E: RecoverPoint 4.0 License File Example on page 148, and
then proceed to Phase 4 – Reporting Back to EMC via Unisphere for RecoverPoint on page 84.

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 83 of 165
Installing your license files using Admin > Manage LicensesTo install your license file(s) through
the main Unisphere for RecoverPoint
interface:
1. Select Admin > Manage Licenses.

2. For each license file:

a. Click Add to display the Add License dialog box.

b. Click Browse... and select a license file.

c. Click OK to add the license file to the RecoverPoint system.
Verify that the information that is displayed in each row and column of the Licenses table contains the
correct information, according to Appendix E: RecoverPoint 4.0 License File Example on page 148, and
then proceed to Phase 4 – Reporting Back to EMC via Unisphere for RecoverPoint on page 84.

Phase 4 – Reporting Back to EMC via Unisphere for

RecoverPoint
Configure System Notifications to set up the RecoverPoint system reports mechanism (SyR) and provide
one-way communication between a RecoverPoint installation and the EMC System Reports database
(ESRS).
The following parameters are sent to the system report database after system notifications are
configured:
• Account/System ID
• SSID
• Location/Site ID

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 84 of 165
 Note: See Appendix I:
Configure system notifications using the Getting Started wizardRecoverPoint Ordering and
Licensing Terminology on
page 155 for descriptions of each of these terms. Note that the definitions of
Account/System ID and SSID (Software Serial ID) have changed from previous
RecoverPoint versions.
You can configure system notifications in the RecoverPoint system through:
• The Unisphere for RecoverPoint Getting Started wizard, when Unisphere for
RecoverPoint loads for the first time.
• The Unisphere for RecoverPoint Admin > System Notifications > Configure System
reports and Alerts screen, every subsequent time that Unisphere for RecoverPoint loads.

To configure system notifications using the Getting Started wizard, in the Enable Support screen:
1. Ensure that the Enable System Notifications checkbox is selected, and the radio button
is set to System alerts and system reports.
2. Ensure that the Compression and Encryption checkboxes are selected.
3. Define the transfer method.
• To transfer system notifications through an SMTP server:
a. In the Transfer Method section, ensure the SMTP radio button is selected.
b. In the SMTP server address field, specify the IP address or DNS name of your dedicated
SMTP server, in IPv4 or IPv6 format.
c. In the Sender email field, specify the email address from which the system notifications
will be sent.
d. Click Apply.

• To transfer system notifications through RecoverPoint’s built-in FTPS server:

e. In the Transfer Method section, select the FTPS radio button.
f. Click Apply.

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 85 of 165
 •To transfer
Configure system notifications using Admin > Configure System Notificationssystem
notifications
through an ESRS gateway:
g. In the Transfer Method section, select the ESRS radio button.
h. In the ESRS gateway IP address field, specify the IP address of your ESRS gateway in
IPv4 format.
i. Click Apply.
4. Click the Finish button to close the wizard and apply your changes.
5. Select Admin > System Notifications > Configure System Reports and Alerts.
6. Click the Test Connectivity button.
7. In the dialog box that is displayed, enter the email address to which EMC Customer
Support can send a verification email.
Note: The connectivity test, if successful, opens a service request containing call home
event number 30999 and sends an email to the specified verification email address from
EMC Customer Support to verify that the system reports mechanism (SyR) has been
successfully configured.
8. Wait ten minutes.
9. Select Dashboard > System Events and look for event 1020 “Failed to send system
report”.
• If this event does not appear in your event logs, the system notifications mechanism has been
properly configured.
• If you do receive this event; check whether there is an issue with your selected method of
transfer. If a problem exists, fix it and then, perform the connectivity test again by clicking the Test
Connectivity button the System Reports tab of the System Settings dialog box. If problem persists
contact EMC Customer Support.

To configure system notifications through the main Unisphere for RecoverPoint interface:
1. Select Admin > System Notifications > Configure System Reports and Alerts.
2. Ensure that the Enable System Notifications checkbox is selected, and the radio button
is set to System alerts and system reports.
3. Ensure that the Compression and Encryption checkboxes are selected.
4. Define the transfer method.
• To transfer system notifications through an SMTP server:
a. In the Transfer Method section, ensure the SMTP radio button is selected.
b. In the SMTP server address field, specify the IP address or DNS name of your dedicated
SMTP server, in IPv4 or IPv6 format.
c. In the Sender email field, specify the email address from which the system notifications
will be sent.
d. Click Apply.

• To transfer system notifications through RecoverPoint’s built-in FTPS server:

e. In the Transfer Method section, select the FTPS radio button.
f. Click Apply.

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 86 of 165
 •To transfer system notifications
RecoverPoint/SE replication from VNX7500 to VNX5500through an ESRS gateway:
g. In the Transfer Method section, select the ESRS radio button.
h. In the ESRS gateway IP address field, specify the IP address of your ESRS gateway in
IPv4 format.
i. Click Apply.
5. Click the Finish button to close the wizard and apply your changes.
6. Click the Test Connectivity button.
7. In the dialog box that is displayed, enter the email address to which EMC Customer
Support can send a verification email.
The connectivity test, if successful, opens a service request containing call home event
number 30999 and sends an email to the specified verification email address from EMC
Customer Support to verify that the system reports mechanism (SyR) has been
successfully configured.
8. Wait ten minutes.
9. Select Dashboard > System Events and look for event 1020 “Failed to send system
report”.
• If this event does not appear in your event logs, the system notifications mechanism has been
properly configured.
• If you do receive this event; check whether there is an issue with your selected method of
transfer. If a problem exists, fix it and then, perform the connectivity test again by clicking the Test
Connectivity button the System Reports tab of the System Settings dialog box. If problem persists
contact EMC Customer Support.

Appendix A: Ordering and Licensing Examples by Use Case

This section presents examples of the common ordering and licensing use cases.

The following diagram contains the ordering and licensing output you can expect when a customer wants
to replicate from VNX7500 to VNX5500.

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 87 of 165
Figure 6 RecoverPoint/SE replication from VNX7500 to VNX5500

Additional notes:
• Available as part of the VNX Software Suites/Packs
• Local replication is available in the VNX Local Protection Suite (LPS)
• Remote replication is available in the VNX Remote Protection Suite (RPS)
• Local replication and remote replication are available in the VNX Protection Pack
(PPAK) or the Efficiency Protection Pack (EPAK)
• License is tied to the VNX array serial number
• RecoverPoint/SE can replicate only to another RecoverPoint/SE cluster
• RecoverPoint/SE does not support up to five RPA clusters
• Refer to the Scalability section of the EMC RecoverPoint Release Notes for the number
of RPAs supported when using splitter sharing

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 88 of 165
RecoverPoint/EX replication from VNX7500 (L+R) and VMAX 10K to VMAX 10KThe following
diagram
contains the ordering and licensing output you can expect when a customer wants to replicate from
VNX7500 (L+R) and VMAX 10K to VMAX 10K.

Figure 7 RecoverPoint/EX replication from VNX7500 (L+R) and VMAX 10K to VMAX 10K

Additional notes:
• Local replication is performed on the same array or between arrays at the same site.
Remote replication is performed between sites.
• RecoverPoint/EX for VMAX and VNX can be purchased in the RecoverPoint standalone
ordering path.
• RecoverPoint/SE licenses (Local + Remote) for the VNX7500 must be upgraded to
RecoverPoint/EX for VNX7500.
• RecoverPoint/EX for VMAX registered capacity is based on the total capacity replicated
from the VMAX array to the VMAX array.
• RecoverPoint/EX for VMAX and RecoverPoint/EX for VNX licenses are tied to the array
serial number
• Unlimited arrays can be added per site. Each array is licensed separately.

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 89 of 165
• Supports up to five RPA clusters

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 90 of 165
Replication from two CX-120s to a VNX5300The following diagram contains the ordering and
licensing output you can expect when a customer
wants to replicate from two CX-120s to a VNX5300.

Figure 8 Replication from two CX-120s to a VNX5300

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 91 of 165
Replication from VNX7500 (local and remote) and VNX5300 (local only) to VNX5700The
following diagram contains the ordering and licensing output you can expect when a customer wants to
replicate from VNX7500 (local and remote) and VNX5300 (local only) to VNX5700.

Figure 9 Replication from VNX7500 (local and remote) and VNX5300 (local only) to
VNX5700

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 92 of 165
Replication of 50 TB from VMAX 20K and 30 TB from VMAX 10K to VNX5700The following
diagram
contains the ordering and licensing output you can expect when a customer wants to replicate 50 TB from
VMAX 20K and 30 TB from VMAX 10K to VNX5700.

Figure 10 Replication of 50 TB from VMAX 20K and 30 TB from VMAX 10K to VNX5700

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 93 of 165
Replication from VNX7500 to VNX5500 with splitter sharingThe following diagram contains the
ordering and licensing output you
can expect when a customer wants to replicate from VNX7500 to VNX5500 with splitter sharing.

Figure 11 Replicating from VNX7500 to VNX5500 with splitter sharing

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 94 of 165
Replication from VNX7500 (local and remote) and VMAX 10K to VMAX 10KThe following
diagram contains
the ordering and licensing output you can expect when a customer wants to replicate from VNX7500
(local and remote) and VMAX 10K to VMAX 10K.

Figure 12 Replicating from VNX7500 (local and remote) and VMAX 10K to VMAX 10K

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 95 of 165
Replication from two CX4-120s to a VNX5300The following diagram contains the ordering and
licensing output you can expect when a customer
wants to replicate from 2 CX4-120s to a VNX5300.

Figure 13 Replicating from 2 CX4-120s to a VNX5300Note the following:

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 96 of 165
Replication from VNX7500 to an existing RecoverPoint/SE clusterThe following diagram
contains the ordering and
licensing output you can expect when a customer wants to add an array to an existing configuration, and
replicate from a VNX7500 to an existing RecoverPoint/SE cluster.

Figure 14 Replication from a VNX7500 to an existing RecoverPoint/SE cluster

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 97 of 165
Add VMAX 10K with 50 TB to an existing local RecoverPoint/SE clusterThe following diagram
contains the ordering
and licensing output you can expect when a customer wants to add a VMAX 10K with 50 TB to an
existing local RecoverPoint/SE cluster.

Figure 15 Add VMAX 10K with 50 TB to an existing local RecoverPoint/SE cluster

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 98 of 165
Replication of 50 TB from VPLEX to VMAX 10KThe following diagram contains the ordering and
licensing output you can expect when a customer
wants replicate 50 TB from VPLEX to VMAX 10K.

Figure 16 Replication of 50 TB from VPLEX to VMAX 10K

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 99 of 165
Replication of 150 TB from non-EMC arrays to VMAX 20KThe following diagram contains the
ordering and licensing output you can
expect when a customer wants replicate 150 TB from non-EMC arrays to VMAX 20K.

Figure 17 Replication of 150 TB from non-EMC arrays to VMAX 20K

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 100 of 165

Replication from one site to two different sites (example 1)The following diagram contains the
ordering and licensing output you can
expect when a customer wants to replicate from one site to two different sites.

Figure 18 Replicating from one site to two different sites (example 1)

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 101 of 165

Replication from one site to two different sites (example 2)The following diagram contains the
ordering and licensing output you can
expect when a customer wants replicate from one site to two different sites.

Figure 19 Replication from one site to two different sites (example 2)

Additional notes:
• All RecoverPoint/SE licenses at Site A, B and C MUST be upgraded to RecoverPoint/EX
licenses
• Existing customers using RecoverPoint/SE with splitter sharing should upgrade their
license to RecoverPoint/EX

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 102 of 165

Replication of multiple VNXs for new purchases and upgrade scenariosThe following diagram
contains the ordering
and licensing output you can expect when a customer wants replicate of multiple VNXs after a new
purchase or an upgrade scenario.

Figure 20 Replication of multiple VNXs for new purchases and upgrade scenarios

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 103 of 165

Additional use cases

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 104 of 165

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 105 of 165

Appendix B: RecoverPoint Ordering FAQs and Getting Help
Question: What is a 457 model?
Answer: A 457 model is considered the ‘parent’ of the 456s ordered with it. The 457 carries
the base price and will show only on the Direct Express or Channel Express order
summary page (not in ELMS).

Question: What is a 456 model?

Answer: 456 models are the capacity tiers and carry the RecoverPoint license and a price.

Question: What is License Solution?

Answer: License Solution is used to ensure that the ELMS models interface correctly in
EMC Back Office systems.

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 106 of 165

Answer: Note:The RecoverPoint License Solution (RP-LS).

Question: In the model description, what does the equal sign (=) followed by two (2)
capitalized alphabetic letters mean?
Answer: The equal sign (=) followed by two (2) capitalized alphabetic letters (the “UOM
Code”), describe the unit-of-measure for that model (such as registered capacity,
raw capacity, frame-based, and so on)

Question: How do I find the Array ID/Locking ID for RecoverPoint?

Answer: See the instructions in this document or call EMC Licensing support for the steps to
locate the Array ID/Locking ID for RecoverPoint.

Question: What are the ordering changes that have been made to RecoverPoint 4.0?
Answer: RecoverPoint 4.0 has implemented an EMC-standard electronic licensing scheme
that will simplify the implementation for our customers and field team. Upon
ordering a license, the customers will receive an email with the code and
information that will allow them to obtain a license file directly from the NGOE
website, with no need for opening a service request or other manual intervention.
Starting with release version 4.0, RecoverPoint software will only support this new licensing
scheme (eLicensing). Model codes are changed to reflect that, and the configurator paths
are updated accordingly.
Note:When ordering RecoverPoint (pre-4.0 releases), the "older" ordering path in Direct
Express or Channel Express will continue to be available in the RecoverPoint Ordering
Path, until the end of 2013.

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 107 of 165

Question: Are existing RecoverPoint customers required to purchase RecoverPoint 4.0??
Answer: No, RecoverPoint customers with a current software maintenance contract can
upgrade to RecoverPoint 4.0 and use these new features at no charge.
Note:License upgrades require submitting a service request (SR).

Question: If I only replicate a portion of my array with RecoverPoint/EX, must I license the
entire storage capacity of my array?
Answer: No, With RecoverPoint/EX, every storage platform has a registered capacity, and
this registered capacity can be smaller than the capacity of your storage platform.

Question: Is the upgrade to RecoverPoint 4.0 or higher a non-disruptive process?

Answer: Upgrading from RecoverPoint 3.1 or higher to RecoverPoint 4.0 or higher is non-
disruptive and can be performed without impact to consistency groups and without
losing journal data or requiring a full sweep.

Question: Is upgrading to RecoverPoint 4.0 or higher mandatory?

Answer: No, EMC will continue to support customers who are running RecoverPoint 3.4x
and 3.5.x.
Answer: Note:RecoverPoint 3.3 and earlier were End of Service Life (EOSL) and are no
longer supported by EMC. Customers should move to the latest recommended
version in order to get the latest functionality and fixes.
RecoverPoint/SE
Question: What is RecoverPoint/SE?
Answer: The RecoverPoint/SE offering allows remote replication of a single VNX/CLARiiON
array to a single VNX/CLARiiON array, or local replication from a single
VNX/CLARiiON array onto itself.

Question: How do I order RecoverPoint/SE for VNX?

Answer: RecoverPoint/SE for VNX arrays can be ordered in the VNX ordering path with the
appropriate VNX software bundle (VNX suites/packs) that includes the appropriate
RecoverPoint/SE license (LPS for local replication and/or RPS for remote
replication).
Answer: Note:Both the LPS and RPS are included in the Protection Pack and in the
Efficiency Pack.

Question: I have a customer with a VNX5300 and a VNX5500 for their production workload.
They are planning out a DR site and plan to go with a single VNX5700 at the DR
site. They will fan in the replication from the VNX5300 and the VNX5500 to the
single VNX5700. Total replicated capacity is less than 300 TB. Will
RecoverPoint/SE licensing cover this scenario?
Answer: In order to fan in the replication from the VNX5300 and the VNX5500 to the single
VNX5700, RecoverPoint/EX license is required for all three VNX arrays.

Question: How do I order RecoverPoint/SE for CLARiiON?

Answer: You can order RecoverPoint/SE for the CLARiiON arrays in the RecoverPoint
standalone ordering path – Upgrade solution path.
Note:Moving forward, only the CLARiiON frame-based RecoverPoint/SE can be
ordered for those CLARiiON arrays (local or remote).

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 108 of 165

Question: I have the Total Protection Pack for my VNX, but I only want local replication for my
VNX arrays. Must I purchase the local and remote conversion models for my VNX?
Answer: No, you need to upgrade only the replication types that you actually deployed. If
you want to perform local replication, then you only need to purchase RP/EX-local
upgrade. If you want to perform only remote replication, then purchase RP/EX
remote-upgrade. If you want to perform local and remote replication, then you must
purchase both (local and remote).

Question: My customer has an existing RecoverPoint/SE remote configuration that includes

replication between two CLARiiON arrays. After they migrate one of the CLARiiON
arrays to a VNX series array, can they reuse their existing RecoverPoint/SE license
for the new VNX?
Answer: No, RecoverPoint/SE licenses are associated with specific arrays. Any migration to
a different array, in this example from a CLARiiON to a VNX series array, requires
that the RecoverPoint license be repurchased for the new VNX array.

Question: Which versions of RecoverPoint support NAS replication?

Answer: NAS replication is supported by VNX arrays using RecoverPoint 3.4 or higher (only
with RecoverPoint/SE license). RecoverPoint/EX and RecoverPoint/CL do not
support NAS replication.
Note:While RecoverPoint supports NAS replication, it is not as complete as
Replicator. You should lead with Replicator for file system replication and lead with
RecoverPoint for block-based replication.

Question: Can my customer upgrade their RecoverPoint/SE remote configuration from 4 TB

to 16 TB?
Answer: No, they will need to acquire two one-time conversion models, one for each array
at each site. These models will convert their RecoverPoint/SE remote license from
a capacity-based license to a frame-based license tied to each frame of their
arrays.

Question: Does RecoverPoint/SE support multipathing products other than EMC PowerPath?
Answer: Yes, refer to the EMC Online Support for the full list.

Question: My customer wants to purchase an additional RecoverPoint/SE license. Can they

order it as a capacity-based license?
Answer: No, new RecoverPoint/SE local licenses ordered will ask for the array model for the
single array. New RecoverPoint/SE remote licenses ordered through the
configurator will ask for the array models for both arrays. A frame-based model will
be generated for the appropriate arrays.

Question: Is the conversion from RecoverPoint/SE to RecoverPoint/EX a non-disruptive

event?
Answer: Yes, upgrading from a RecoverPoint/SE license to a RecoverPoint/EX license is a
non-disruptive upgrade, when using the Conversion Wizard in the RecoverPoint
Deployment Manager.

Question: What will I lose if I convert RecoverPoint/SE to RecoverPoint/EX?

Answer: You will be unable to manage RecoverPoint/EX through Unisphere for VNX or
replicate NAS file systems.

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 109 of 165

Question: What is the difference between RecoverPoint/EX registered capacity and
RecoverPoint/CL replicated capacity-based licensing that we have previously
used?
Answer: RecoverPoint/EX registered capacity is licensed per array and supports only EMC
array splitters, so you are allowed to use the capacity you purchased to replicate
only for the array for which it was purchased. A RecoverPoint/EX registered
capacity license cannot be moved to another array and a new RP/EX license
should be purchased if the array is replaced (such as, if the array ID is changed).
RecoverPoint/CL (RP Classic) replicated capacity licensing is per RecoverPoint
cluster. It allows you to replicate the capacity you purchased from any array
connected to RecoverPoint cluster with full flexibility to add or remove arrays.
RecoverPoint/CL supports all splitter types (array-based splitter, Intelligent Fabric
based splitter, or host-based splitters).

Question: My customer wants to upgrade an existing RecoverPoint/SE configuration to

RecoverPoint/EX. Can this be done?
Answer: Yes, it can be done in the RecoverPoint standalone path – Upgrade Solution path
– License Upgrade.
Note:Unisphere integration and file system replication will not be supported. A new
RecoverPoint license will be issued, and the RecoverPoint appliances can be
reused.

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 110 of 165

RecoverPoint/SE Ordering FAQ
Question: Has something changed where the Local/Remote Protection Suites (or Total
Protection Pack) no longer entitles the buyer to RP/SE licenses? Is
RecoverPoint/SE 4.0 not included in the VNX Local/Remote Protection Suite?
Answer: The RecoverPoint/SE license continues to be included with the VNX local/remote
suites/packs. However, because VNX local/remote suites/packs are not ELMS, the
system needs to create ELMS models for RP/SE, outside of the VNX bundles for
the electronic licensing process. The 456 RP/SE models are $0 and used to trigger
the LAC email for the electronic licensing process.
Note: The RP/SE 456 models will always show on the VNX suites/pack Order
Summary.

RecoverPoint for VNX and CLARiiON

Question: How does RecoverPoint/EX for VNX or CLARiiON compare with RecoverPoint/SE?
Answer: RecoverPoint/SE allows replication between a single CLARiiON or VNX to another
single CLARiiON or VNX array. RecoverPoint/EX allows full RecoverPoint
capabilities without the limitation of the number and type of arrays used.

Question: How do I order RecoverPoint/EX for VNX/CLARiiON?

Answer: This requires several steps as follows:
• If the CLARiiON is not replicated already with RecoverPoint/SE, then in the RecoverPoint
ordering path, order an array-based RecoverPoint/SE for that array (local, remote, or
both, as needed).
• If the CLARiiON is already licensed for RecoverPoint/SE (either the old "capacity-
based" license or the new array-based license), proceed to next step (RPEX
upgrade). Note that there is no need to upgrade a "capacity-based" license to
array-based before ordering/applying the RecoverPoint/EX upgrade.

Question: Once I have performed the conversion, can I add a VNX series array to my
RecoverPoint/EX configuration?
Answer: Yes, but every similar array should have a RecoverPoint/EX license as previously
described.

Question: I have a VNX series with RecoverPoint/SE local and remote replication. I want to
convert the local replication to RecoverPoint/EX so that I can perform local
replication onto another array. Do I have to convert the remote replication to
RecoverPoint/EX as well?
Answer: Yes, you cannot convert only local or only remote replication if both are used with
this array.

Question: The Total Protection Pack for my VNX comes with EMC Replication Manager and
EMC Data Protection Advisor. Can I use these with a VMAX attached to my
RecoverPoint/EX configuration?
Answer: No, however you can continue to use these with the original VNX array.

Question: Can I locally replicate my VNX-7500 using RecoverPoint/EX and remotely replicate
my VNX-7500 using RecoverPoint/SE?

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 111 of 165

Answer: No, when you attach the VNX series to your RecoverPoint/EX configuration you
cannot use the RecoverPoint/SE software contained in the suites or packs. You
need to upgrade both (RecoverPoint/SE local and remote licenses to RP/EX).

Question: I have RecoverPoint/SE between two VNX arrays. I want to virtualize some of the
VNX array LUNs with VPLEX. Can I use the same RecoverPoint/SE cluster to
replicate the virtualized LUNs (through VPLEX write splitter) along with non-
virtualized LUNs (using the VNX splitter)?
Answer: No, because a RecoverPoint system must use a single type of license, you must
first convert both arrays from using RecoverPoint/SE to using RecoverPoint/EX for
VNX. After that, add to the cluster a RecoverPoint EX for VPLEX license with the
appropriate capacity and replicate the virtualized LUNs through the VPLEX write
splitter.

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 112 of 165

RecoverPoint/EX
Question: What is RecoverPoint/EX?
Answer: RecoverPoint/EX is a licensing option that enables customers to purchase a
license to replicate an EMC array (or a certain capacity of an array), using an array
splitter to any other supported and licensed array.

Question: What types of capacity licenses are available for RecoverPoint/EX?

Answer: RecoverPoint/EX is offered in the following options:
• Registered capacity - for Symmetrix VMAX, Symmetrix VMAXe, Symmetrix VMAX 10K,
Symmetrix VMAX 20K, Symmetrix VMAX 40K, and VPLEX
• Frame-based - for CLARiiON and VNX series (after upgrading from RP/SE to RP/EX)
• Raw capacity - for Symmetrix VMAX 10K

Question: What is RecoverPoint/EX registered capacity?

Answer: Registered capacity is the recommended option for using array splitters for the
EMC Symmetrix VMAX 40K, Symmetrix VMAX 20K, Symmetrix VMAX, Symmetrix
VMAX 10K, or VPLEX (local or metro). It allows you to specify the amount of data
you want to replicate to/from the storage array. RecoverPoint registered capacity is
licensed separately for RecoverPoint local replication and RecoverPoint remote
replication. Customers who want RecoverPoint local and remote replication must
purchase both.

Question: How do I calculate registered capacity for remote replication?

Answer: Registered capacity for RecoverPoint/EX for an array is the total of the source
volumes (replicated from that array) and target volumes (replicated to that array).

Question: What is RecoverPoint/EX raw capacity licensing?

Answer: RecoverPoint/EX raw capacity licensing is available on the Symmetrix VMAX 10K
series only, and may be beneficial for customers who plan to replicate more than
60-70% (approximately) of their VMAX 10K array. It is calculated based on the
number of terabytes of physical drives inside the array (SATA and non-SATA).
With raw capacity licensing, you always purchase both local and remote replication
and you pay according to the array raw capacity, regardless of how much you
actually replicate from the array.

Question: How do I order RecoverPoint/EX?

Answer: It varies. You can order RecoverPoint/EX in the RecoverPoint standalone ordering
path or according to the array type. For additional information for each array, refer
to Table 10.

Question: Must I purchase RecoverPoint local replication and remote replication separately?
Answer: Yes. If you want to perform both local and remote replication, then you must
purchase both the local and remote separately. Please note that for VNX, the local
protection suite (LPS) for a VNX series includes RecoverPoint/SE local license and
the remote protection suite (RPS) for a VNX series includes RecoverPoint/SE
remote license. The protection packs (PPAL and EPAK) for the VNX series contain
both LPS and RPS.

Question: For RecoverPoint/EX, how is the physical storage licensed?

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 113 of 165

Answer: For the VPLEX and Symmetrix VMAX 40K, VMAX 20K, VMAX 10K and VMAX
arrays, RecoverPoint/EX is licensed by "registered capacity", such as, the number
of terabytes that you want to replicate to/from each array. For the Symmetrix
VMAX 10K, RecoverPoint can also be licensed for "raw capacity", based on the
size and types of all physical volumes inside the frame.

Question: What license types does RecoverPoint offer?

Answer: The RecoverPoint family includes three types of licenses:
• RecoverPoint/SE is a license that is associated with a VNX/CX array and provides
continuous data protection and replication for the EMC VNX series and CLARiiON CX4
and CX3. It is limited to support a single array to a single array.
• RecoverPoint/EX is a license that is associated with an array and provides continuous
data protection and replication for the VMAX 10K, VMAX 20K, VMAX 40K, VPLEX, VNX,
and CLARiiON CX3 and CX4.
• RecoverPoint/CL is a license associated with the RecoverPoint cluster and
allows replication of all array types supported by RecoverPoint.

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 114 of 165

RecoverPoint for VMAX 10K
Question: How do I order RecoverPoint/EX for VMAX 10K?
Answer: Go to the RecoverPoint standalone ordering path in Channel Express or Direct
Express, where you can order either the RecoverPoint/EX with the VMAX 10K
array (New Solutions), or separately as an upgrade (Upgrade Solutions).

Question: How do I order RecoverPoint raw for VMAX 10K

Answer: RecoverPoint raw capacity can be ordered in the VMAX 10K ordering path

Question: When should I use registered capacity licensing instead of raw?

Answer: For most customers, registered capacity would be a better option. However, if you
plan to replicate more than 60-70% of the raw capacity of your VMAX 10K array,
then the RecoverPoint/EX raw model will be more cost effective.

Question: My customer has a Symmetrix VMAX 10K and a VNX series array. Can
RecoverPoint/SE be used?
Answer: RecoverPoint/SE licensing supports VNX/CX arrays. Either RecoverPoint/EX or
RecoverPoint/CL must be used.

Question: My customer has two VNX series arrays with RecoverPoint/SE replicating them. My
customer plans to convert one of the VNX series arrays to a Symmetrix VMAX 10K.
Can RecoverPoint/SE continue to be used?
Answer: No, your customer must convert/upgrade RecoverPoint/SE to RecoverPoint/EX for
the remaining VNX, and purchase a RecoverPoint/EX for VMAX 10K for the new
VMAX 10K.

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 115 of 165

RecoverPoint for the VMAX 20K and VMAX
Question: How do I order RecoverPoint/EX for Symmetrix VMAX 20K or VMAX?
Answer: Go to the RecoverPoint standalone ordering path, or to the Symmetrix VMAX 20K
ordering path, or to the VMAX ordering path (New Solutions) in Channel Express
or Direct Express.

Question: How do I order RecoverPoint/EX for an existing Symmetrix VMAX 20K array?
Answer: You can order RecoverPoint/EX for an existing VMAX 20K from the RecoverPoint
standalone ordering path or in the Symmetrix VMAX 20K ordering path in Channel
Express or Direct Express. You then select RecoverPoint/EX in the Upgrade
Solutions path to add to an existing system. It is listed in the path on the Software
Components screen as an option.
Answer: Note:Any additional items that are optional can be removed by deselecting them
under Additional Options. This includes customer education services and
maintenance. Power cords are only added by Configurator if they are mandatory. A
$0 VMAX PS model (PSUPG-VMAX) may be added, but it can be ignored.
RecoverPoint for the Symmetrix VMAX 40K
Question: How do I order RecoverPoint/EX for VMAX 40K?
Answer: Go to the RecoverPoint ordering path or to the VMAX 40K ordering path in
Channel Express or Direct Express.

Question: I have various arrays connected to my VMAX series arrays using FTS. Can I
replicate those arrays with RecoverPoint?
Answer: Storage that is virtualized by FTS is viewed by RecoverPoint as Symmetrix VMAX
volumes, and is therefore replicated the same as any other VMAX volumes.
Therefore, order the capacity you need to replicate as if this storage is VMAX
storage.

Question: Does RecoverPoint support multiple clusters to the same VMAX series array?
Answer: Yes, you can have multiple clusters attached to one VMAX series array. For a
RecoverPoint/EX license, since it is associated with the array, a single license
needs to be purchased.

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 116 of 165

RecoverPoint for VPLEX
Question: How do I order RecoverPoint/EX for VPLEX?
Answer: Go to the RecoverPoint standalone ordering path or to the VPLEX ordering path in
Channel Express or Direct Express.

Question: What do I need to order to replicate with RecoverPoint, using the VPLEX splitter?
Answer: RecoverPoint replicates the virtual volumes presented by VPLEX. Therefore, when
ordering RecoverPoint/EX for VPLEX, order the amount of RecoverPoint/EX TBs
of virtual volumes you need to replicate. When you replicate at the VPLEX level,
you benefit from VPLEX flexibility, so if you move your data between back-end
arrays under the same VPLEX, you do not need to change your RecoverPoint
license. Note that you need to have a VPLEX license for the amount of virtual
volumes for the production copy, and also any local copy, repository and journal
volumes, if those reside on virtual volumes.

Question: If I replicate a virtual volume licensed by RecoverPoint/EX for VPLEX, do I also

need a RecoverPoint license for this volume at the array level?
Answer: No, you license only once, at the point of replication.

Question: I have an array with VPLEX virtualizing some of its volumes. I want to replicate
some volumes through VPLEX and some unvirtualized volumes directly from the
array. Can I do it?
Answer: Yes, you should order RecoverPoint/EX for VPLEX for the amount of TB you
replicate through the VPLEX splitter and RecoverPoint/EX for the array for the
capacity you want to replicate directly from the back-end array splitter.

Question: I have a VPLEX Metro and I replicate locally or remotely with RecoverPoint, using
RecoverPoint VPLEX splitter on one site. Do I have to order RecoverPoint/EX for
both Metro sites?
Answer: No, you order RecoverPoint/EX license for the site where you are replicating from
and for that VPLEX only.

Question: What is the RecoverPoint local, which is bundled with the VPLEX Metro Express
Edition?
Answer: A 40 TB RecoverPoint local is bundled with VPLEX Metro Express Edition (total of
80 TB local for the VPLEX Metro Express Edition).
Answer: Note:The RecoverPoint local, bundled with VPLEX Metro Express Edition, is free.

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 117 of 165

Ordering FAQs

Question: Why are RecoverPoint for VPLEX with frame-based licenses being offered?
Answer: To offer a consistent and user friendly way to price and purchase RecoverPoint for
VPLEX when VPLEX is being purchased with VNX.

Question: What about existing VNXs attached to VPLEX with RecoverPoint?

Answer: Your existing RecoverPoint for VPLEX licensing for the VNX arrays already
attached to VPLEX are not affected by the new frame-based VPLEX licenses. You
have the option of either continuing with the existing registered capacity licenses or
purchasing the new frame-based licenses. There is no upgrade path from the
existing registered capacity-based licenses to the frame-based licenses.

Question: Do I now have to order RecoverPoint for VPLEX frame-based licenses?

Answer: You have a choice between the traditional RecoverPoint for VPLEX registered
capacity-based licenses and the new RecoverPoint for VPLEX frame-based
licenses.

Question: Is the pricing different from the registered capacity pricing?

Answer: Yes, RecoverPoint for VPLEX registered capacity-based licenses are priced based
on the capacity to be virtualized by VPLEX and RecoverPoint for VPLEX frame-
based licenses are priced by the VNX frame type with the ability to virtualize
unlimited capacity.

Question: Do I have to convert my current RecoverPoint for VPLEX quotes?

Answer: No, you have a choice between the traditional RecoverPoint for VPLEX registered
capacity-based licenses and the new RecoverPoint for VPLEX frame-based
licenses. You only have to convert a current quote if you wish to utilize the new
RecoverPoint for VPLEX frame-based licenses.

Question: Is there a rebate for RecoverPoint for VPLEX capacity that will be taken up by VNX
frame?
Answer: No, you may apply your existing RecoverPoint for VPLEX capacity-based licenses
to another storage array that is not covered by a frame-based license.

Question: When will this be available on Channel Express and Direct Express?
Answer: RecoverPoint for VPLEX frame-based licenses will be available, via RecoverPoint
standalone, in Channel Express and Direct Express, in September 2013.

Question: How do I create a quote today?

Answer: Prior to the RecoverPoint for VPLEX frame-based licenses becoming available in
Channel Express and Direct Express, you can create quotes for these licenses
manually through Product Catalog with instructions available from the
RecoverPoint Deal Support Desk.

Question: How do I place an order today?

Answer: Prior to the RecoverPoint for VPLEX frame-based licenses becoming available in
RecoverPoint path of Channel Express and Direct Express in September, you can
order these licenses manually through Product Catalog with instructions available
from the RecoverPoint Deal Desk.

Question: Does this offering use the standard RecoverPoint and VPLEX hardware?

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 118 of 165

Answer: Yes, the RecoverPoint for VPLEX frame-based licenses are licenses only and
apply to all current RecoverPoint and VPLEX hardware.

Question: Does this use the standard RecoverPoint and VPLEX software?
Answer: Yes, the RecoverPoint for VPLEX frame-based licenses are licenses only and
apply to RecoverPoint version 4.0 (or higher) and all current VPLEX software.

Question: Are there any changes regarding the migration licensing change?
Answer: No, the provision that allows RecoverPoint for VPLEX licenses to be used for
migration capacities apply to both frame-based and capacity-based licenses.

Question: Are there RecoverPoint for VPLEX Geo frame-based licenses available?
Answer: No, currently there are no RecoverPoint for VPLEX Geo frame-based licenses
available, but EMC is considering offering them in the future.

Question: Can RecoverPoint for VPLEX frame-based licenses co-exist with RecoverPoint
capacity-based licensing?
Answer: RecoverPoint for VPLEX registered capacity-based and frame-based licenses can
co-exist on the same RecoverPoint for VPLEX splitter.

Question: Are there plans to add RecoverPoint for VMAX frame-based licensing?
Answer: No, because VMAX is also sold via capacity-based pricing, there are no plans to
offer RecoverPoint/EX frame-based licenses for VMAX.

Question: Should I use the VPLEX, VNX, or both splitters for RecoverPoint?
Answer: If you have VPLEX, you should use the VPLEX splitter for RecoverPoint.

Question: Can a customer upgrade from a RecoverPoint/SE frame-based RecoverPoint

license (with VNX splitter) to the VPLEX frame-based?
Answer: No, there is no upgrade from RP/SE frame-based license to RP/EX frame-based
for VNX on VPLEX.

Question: Would I still need the VNX frame-based license (or capacity-based license) for
VPLEX (Local/Metro)?
Answer: Yes, VPLEX and RecoverPoint need to be licensed.

Question: If I have a VPLEX for VNX frame-based license with some additional capacity for a
third-party array VPLEX license, can I have RP/EX licensed in both ways (frame for
VPLEX for VNX and capacity for the VPLEX used for the third-party arrays)?
Answer: Yes, RecoverPoint for VPLEX registered capacity-based and frame-based licenses
can co-exist on the same RecoverPoint for VPLEX splitter.

Question: Is it a requirement to have frame-based licensing for VPLEX, to leverage

RecoverPoint for VPLEX, on VNX licensing?
Answer: Yes, it is a requirement to have frame-based licensing for VPLEX, to leverage
RecoverPoint for VPLEX, on VNX licensing?

Question: Can I replicate some of my LUNs, via VPLEX, and other LUNs, via the VNX array?
Answer: Yes, you can, but you would need to purchase two licenses, RP/EX for VPLEX
frame-based and RP/EX for VNX.

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 119 of 165

Question: Can customer upgrade from RP/EX for VPLEX capacity-based to RP/EX for
VPLEX frame-based?
Answer: No, there is no upgrade from RP/EX for VPLEX capacity-based to RP/EX for
VPLEX frame-based.
RecoverPoint for VPLEX with Frame-Based VNX
Question: Why are RecoverPoint for VPLEX frame-based licenses being offered?
Answer: To offer a consistent and user friendly way to price and purchase RecoverPoint for
VPLEX when VPLEX is being purchased with a VNX.

Question: What about existing RecoverPoint for VNX/VNX2 licenses attached to VPLEX?
Answer: Your existing RecoverPoint/SE and RecoverPoint/EX licenses for VNX/VNX2
arrays are not affected by the new RecoverPoint/EX for VPLEX frame-based
VNX/VNX2 licenses. You have the option of either continuing with the existing
licenses or purchasing the new frame-based licenses. There is no upgrade path
from the existing capacity-based licenses to the frame-based licenses.

Question: What about existing RecoverPoint for VPLEX licenses with VNX attached to the
VPLEX?
Answer: Your existing RecoverPoint for VPLEX licensing with VNX arrays already attached
to VPLEX are not affected by the new RecoverPoint for VPLEX with frame-based
VNX licenses. You have the option of either continuing with the existing licenses or
purchasing the new frame-based licenses. There is no upgrade path from the
existing capacity-based licenses to the frame-based licenses.

Question: Do I now have to order RecoverPoint 4.0 for VPLEX frame-based licenses?
Answer: No, you have a choice between the traditional VPLEX capacity-based licenses and
the new frame-based licenses. The rule is that you must use RecoverPoint frame-
based VNX if the VPLEX capacity purchased is also frame-based.

Question: Is the pricing different from the RecoverPoint for VPLEX capacity pricing?
Answer: Yes, RecoverPoint for VLPEX capacity-based licenses are priced based on the
capacity to be virtualized by VPLEX. RecoverPoint for VPLEX frame-based
licenses are priced by the VNX frame type with the ability to virtualize the full VNX
array capacity.

Question: Do I have to convert my current VPLEX quotes?

Answer: No, you have a choice between the traditional RecoverPoint for VPLEX capacity-
based licenses and the new RecoverPoint for VPLEX frame-based VNX licenses.
You only have to convert a current quote if you wish to utilize the new frame-based
licenses.

Question: Is there a rebate for RP/EX for VPLEX capacity that will be taken up by VNX/VNX2
frame?
Answer: No, you may apply your existing RecoverPoint for VPLEX capacity-based licenses
to another storage array that is not covered by a RecoverPoint for VPLEX frame-
based license.

Question: When will this be available on Channel Express and Direct Express?

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 120 of 165

Answer: RecoverPoint for VPLEX frame-based licenses will be available manually, via
Product Catalog in July 2013 and VNX Channel Express and Direct Express in
August 2013.

Question: Who can help me to create a quote?

Answer: Contact the RecoverPoint Deal Support Desk:
[email protected].

Question: Do RecoverPoint for VPLEX frame-based licenses use the standard RecoverPoint
and VPLEX hardware?
Answer: Yes, the RecoverPoint for VPLEX frame-based licenses are packaging/license
offerings and apply to all current RecoverPoint and VPLEX hardware.

Question: Do RecoverPoint for VPLEX frame-based licenses use the standard RecoverPoint
and VPLEX software?
Answer: Yes, the RecoverPoint for VPLEX frame-based licenses are licenses only and
apply to all current RecoverPoint and VPLEX software.

Question: Is there a policy change to migration licensing?

Answer: No, the provision that allows RecoverPoint for VPLEX licenses to be used for
migration capacities apply to both frame-based and capacity-based licenses.

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 121 of 165

Question: Can RecoverPoint for VPLEX frame-based licenses co-exist with RecoverPoint for
VPLEX capacity-based licensing?
Answer: Yes, RecoverPoint/EX for VPLEX capacity-based and RecoverPoint/EX for VPLEX
frame-based licenses can co-exist on the same RecoverPoint or VPLEX cluster.

Question: Are there plans to add VMAX frame-based licensing?

Answer: No, because VMAX series arrays are sold via capacity-based pricing, there are no
plans to offer frame-based licenses for VMAX series arrays.

Question: Should I use the VPLEX, VNX, or both splitters for RecoverPoint?
Answer: If you have VPLEX, you should use the VPLEX splitter for RecoverPoint.

Question: Why is there no enhanced maintenance option for RecoverPoint for VPLEX?
Answer: Premium Maintenance is the only option available for RecoverPoint for VPLEX.

Question: If a customer owns a RecoverPoint for VPLEX frame-based local/base license, can
they purchase a capacity-based Metro license or do they have to purchase the
frame-based Metro license?
Answer: Customers with frame-based local/base licenses must also purchase frame-based
Metro licenses and must also use RecoverPoint/EX VPLEX frame-based license
for those VNX/VNX2 arrays. Likewise, customers with capacity-based must
purchase capacity-based licenses.
The following diagram illustrates the licensing option for VPLEX arrays with VPLEX and RecoverPoint.

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 122 of 165

RecoverPoint/CL
Question: Can I convert RecoverPoint/CL to RecoverPoint/EX?
Answer: No.

Question: My customers have RecoverPoint/CL. Do they also have a right to use

RecoverPoint/Cluster Enabler?
Answer: Yes, starting with RecoverPoint 4.0, the RecoverPoint/Cluster Enabler is included
with all RecoverPoint offerings, including RecoverPoint/CL.

Question: Can a VNX splitter (or more generally, any splitter) be shared by two totally
separate RP/CL (or EX) RPA clusters, running dissimilar releases? Can
RecoverPoint 4.0 work with previous RecoverPoint versions?
Answer: No, because RecoverPoint 4.0 will not work with previous RecoverPoint versions,
RecoverPoint 4.0 or higher is required.
RPA Questions
Question: What are the advantages of RPA Gen 5 over previous generations?
Answer: The Gen5 advantages over Gen4 are:
• Higher compression rates at all compression levels
• More memory in the RPA enables longer short peaks (that fit into the RPA's memory)
• Preliminary testing shows that the stronger CPU increases the distribution speed
at about 10%-15%

Question: Q: What is the minimum hardware required for RecoverPoint 4.0?

Answer: RecoverPoint 4.0 requires RPA Gen 4 or higher.

Question: Is it possible to buy only RPA Gen 5 hardware, while keeping their existing
RecoverPoint software licensing (they have a valid maintenance contract)?
Answer: Yes, they would need to upgrade the RPAs to RPA Gen 5 in order to support
RecoverPoint 4.0. However, please note that SANTap splitter was EOL and the
customer would not be able to upgrade beyond 3.5.x. Therefore, RecoverPoint 4.0
will not support SANTap splitters. The recommendation is to migrate the customer
to a VPLEX-splitter or one of EMC’s array splitters, depending on the overall
requirements and if third party arrays are utilized.

Question: I am running RPA Gen 3 appliances. Can I upgrade to RecoverPoint 4.0 or higher?
Answer: No.

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 123 of 165

vRPA Questions
Question: What is vRPA?
Answer: The RecoverPoint vRPA is defined as the virtual edition and implementation of
traditional RecoverPoint Appliance (RPA) and offers a cost-effective alternative to
the physical RPA.
As a virtual machine, the vRPA operates in a virtual environment. Any previous physical
limitations (system and performance) are no longer valid as the entire virtual eco system
has transformed from strict physical resources into dynamic virtual resources. In addition,
the entire responsibility for reserving and provisioning these resources are now in the
control of the virtualization administrators (as opposed to previous physical RPA, where
system resources were locked down by server capabilities and not by the user).

Question: What are the benefits of the vRPA?

Answer: The benefits are that it eliminates dependency on hardware and it provides a
solution for environments where the cost of the physical RPA is considered
significant.

Question: What are the differences between RPA and vRPA?

Answer: Table 7 shows a basic comparison between RPA and vRPA:
Table 7 Comparison between RPA and vRPA

Features RPA (Physical) vRPA (Virtual)

RP Code Identical Identical
Splitting Direct SCSI/FC iSCSI
communication
Replication over Identical Identical
Ethernet
Required # of networks 2 (LAN/WAN) 4
(LAN/WAN/iSCSI1/iSCSI2)
RecoverPoint license RP/SE, RP/EX and RP/CL RP/SE
De-duplication With a minimum 4 GB RAM With a minimum 8 CPUs/8
GB RAM
Replication Type Asynchronous and Asynchronous only
synchronous
Support for dynamic No Yes
resource allocation

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 124 of 165

Question: What are the pre-requisites for the vRPA?
Answer: To enable its functionality, the vRPA requires the following environment
components:
• VNX Inyo MR1 SP1 or later, preconfigured with at least one iSCSI port per storage
processor
• RecoverPoint Deployment Manager (DM) 2.0 or later
• Fully licensed RecoverPoint/SE 4.0 (or later) cluster
• VMware vCenter 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 1 GB/10 GB)
• The vSphere host and the existing RPA cluster networks (LAN and WAN)
• VNX Requirements: 1 Gb Quad Card or 10 Gb Dual Card
Answer: For correct and efficient operation of vRPA virtual machines, the following
resources are required:
• Reserved quota for virtual system resources (CPU, memory, disk)
• Four virtual networks (LAN, WAN, iSCSI1, iSCSI2)

Question: What is the vRPA performance profile matrix?

Answer: The following table shows the vRPA performance profiles
RPA Profile Features 2xCPU/4 GB 4xCPU/4 GB 8xCPU/8 GB
Virtual CPUs (cores) 2 cores 4 cores 8 cores
Memory RAM 4 GB 4 GB 8 GB
WAN + LAN Bandwidth 1 Gb E Ethernet 1 Gb E Ethernet 1 Gb E Ethernet
iSCSI1 + iSCSI2 2 Gb E Ethernet 8 Gb Ethernet 16 Gb Ethernet
Bandwidth

Question: What are the iSCSI options supported by vRPA?

Answer: In VNX there are two types of iSCSI modules:
• 1 Gb port cards – which allows bandwidth of 1 Gb, 2 Gb, and 4 Gb
• 10 Gb port cards – which allows bandwidths of 10 Gb and 20 Gb
Answer: As the vRPA relays on virtual networks, the bandwidth which the user will expose
to the vRPA iSCSI v switches will determine the performance that the vRPA can
reach (the user can configure its vSphere hosts with quad port NICs and present
them as single or dual iSCSI networks for the vRPA requirements).

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 125 of 165

Question: What are the supported configurations of RPA and vRPA?
Answer: The following table shows the supported configurations of RPA and vRPA.
Source Site RPA type Remote Site RPA type Support Statement
RPA RPA
RPA vRPA
Supported
vRPA RPA
vRPA vRPA
vRPA or RPA vRPA+RPA Not supported

Question: What are the best practices to deploy multiple vRPAs?

Answer: When deploying multiple vRPAs, the following are several best practices:
• No redundancy in the event of disaster/maintenance to: vSphere host and network
connectivity
• Provisioning of system resources must be guaranteed for more than a single vRPA – use
resource pools to evenly share these resources; the formula to assure that the shared
host has enough system resources to carry multiple vRPAs should reflect equal/higher
output of: (Single vRPA system values) x (number of shared vRPA)
• Avoid sharing same iSCSI physical NICs among vRPAs to avoid possible
degradation of performance (always ensure to measure performance for both idle
and peak bursts before consolidating vRPAs)
When consolidating multiple (vRPA) networks into single vSwitch or physical NIC:
• The vRPA is exposed to performance degradation, I/P conflicts and eventually, corruption
• You may share WAN and LAN on the same vSwitch or physical NIC as they consume
minor bandwidth (no more than 1 Gb)
• Sharing iSCSI1 and iSCSI2 on the same vSwitch or physical NIC is possible with
the price of performance (unless the iSCSI utilized bandwidth on peak bursts has
been validated)

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 126 of 165

Question: Can I Clone vRPAs?
Answer: Cloning of vRPAs will be safe when the cloned vRPA is not part of a RecoverPoint
cluster (disjoint vRPA).
Any clone action to an active RecoverPoint cluster vRPA will cause shutting down of this
vRPA. A vRPA VM can be copied as a VMware template. However, due to that a vRPA is
already shipped with the RecoverPoint code, you might be required to perform an upgrade
when the existing RecoverPoint cluster will have newer code than the template vRPA.

Question: Does vRPA support vMotion?

Answer: Yes, vMotion is supported.

Question: What arrays are supported with vRPA?

Answer: The following arrays are supported with vRPA:
• RecoverPoint 4.0
• Single VNX per site (targeting the low end VNXs)
• Vblock models that have VNX
• RecoverPoint 4.0.1
• Multiple VNXs arrays
• Vblock models that have multiple VNX arrays

Question: Does the vRPA require a license?

Answer: No, vRPA does not require a license.

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 127 of 165

General Licensing QuestionsAppendix C: RecoverPoint Licensing FAQs
and Getting Help

Question: What is a LAC?

Answer: A LAC is a unique 11 to 20 character alphanumeric code used to obtain a license
electronically. A LAC is the primary identifier of the entitlement(s) used by the
customer or partner to locate and activate licenses. The LAC is emailed to the
customer after the order is placed in Direct Express or Channel Express.

Question: How do I find my LAC?

Answer: When a customer’s software order is fulfilled, an email or letter that includes the
LAC and instructions for the entitlement activation process will be sent to the
customers. Customers can also access the LAC online on NGOE. If a customer
has misplaced a LAC, they can obtain assistance by contacting Worldwide
Licensing Support.

Question: How to activate a LAC for RecoverPoint?

Answer: LAC activation is performed in the NGOE Support Zone->Manage My Licenses.
Answer: Note:For RecoverPoint/SE and RecoverPoint/EX license activations, customers
are required to provide the array serial number and for RecoverPoint/CL license
activations customers are required to install the RecoverPoint software first and
provide the RPA Cluster ID.
Answer: Go to Activation path -> Activate licenses -> enter the LAC# - Select the licenses
that need to be activated - enter the array serial number - Finish the process.

Question: Can license support send me a copy of the LAC email for SO#?
Answer: License support can send out a request to the Fulfillment team to provide the
customer with a copy of their LAC email.

Question: What is NGOE?

Answer: NGOE is EMC's online self-service tool for customers, partners, and EMC
employees to activate new software entitlements and manage existing
entitlements/license files.

Question: What is license activation?

Answer: License activation is an online process by which customers and partners access
NGOE to generate license file(s) or key(s) from their entitlements. License
activation occurs after customers and/or partners receive a LAC (License
Authorization Code) letter and the LAC number listed on their LAC email is
redeemed.

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 128 of 165

Question: How do I know if my entitlements are part of an Enterprise License Agreement
(ELA)?
Answer: If the License Authorization Code (LAC) begins with ELA, then the entitlement
associated with the LAC is subject to an ELA between your company and EMC.

Question: How does a legacy RecoverPoint customer upgrade their license to ELMS?
Answer: Legacy Customer Transition (LCT) is done by submitting a service request and the
license(s) will be manually converted by EMC’s licensing team.

Question: What is frame-based licensing?

Answer: RecoverPoint for VNX series and for CLARiiON arrays are licensed for replicating
the frame-based capacity (locally or remotely). This entitles the customer to
replicate as much as they want from the array, even if they need more than one
RecoverPoint cluster. Note that CLARiiON arrays that were licensed under the
previous, per-TB RecoverPoint/SE capacity licensing scheme, should be upgraded
to frame-based.

Question: I have ordered the wrong RecoverPoint license. Can I correct my order?
Answer: If the order has already been processed, then the account rep needs to place a
new order in the system to replace the incorrect order and to decommission the
incorrect licenses.

Question: We have an issue while installing/configuring RecoverPoint. Can Licensing Support

assist us?
Answer: License support directs customers to contact technical support for further
assistance.

Question: We are planning to purchase additional RecoverPoint software, could license

support let us know if it is compatible?
Answer: Any question related to customer configuration on their existing environment,
should be directed to presales or technical consultants. Call 1-866-EMC-7777,
Option #2 or (508) 435-1000, ext. 54777, Option #2.

Question: The customer is not able to manage/activate licenses. Who could help?
Answer: Any question related to customer configuration on their existing environment,
should be directed to presales or technical consultants. Call 1-866-EMC-7777,
Option #2 or (508) 435-1000, ext. 54777, Option #2.

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 129 of 165

Question: Can I transfer all of the entitlements from one site to another site of the same global
company?
Answer: Yes, customers can transfer all the licenses from one site to another as long as it is
under the same parent company.

Question: Can you merge all of the licenses from company A to company B?
Answer: This is done on a case-by-case basis. If there was a legal, merging, or acquisition
of companies, then EMC needs the legal proof in order to merge the licenses.
Merging of licenses is a manual process and requires further research.

Question: I am not able to locate some of my licenses in the NGOE portal, although I have
purchased the permanent licenses. What should I do?
Answer: EMC seeks additional information such as a list of licenses that the customer is
unable to locate in NGOE. The EMC licensing team will research and open a ticket
(if required) with NGOE to remedy the issue.

Question: Could the license team assist us to apply the license keys that we received from
the support team?
Answer: Customers should contact technical support, as it is not a licensing issue.

Question: Does license support offer support for licensing related queries?
Answer: Refer to Table 9 elsewhere in this document.

Question: How to handle customers with an expired, cancelled maintenance agreement or the
customer has received RecoverPoint shipped without a maintenance agreement?
Answer: Create a case for the customer. In the meantime, inform the customer that the
maintenance agreement expires in the system and someone from EMC will contact
them to remedy the issue.

Question: How do I obtain RecoverPoint licensing support?

Answer: Refer to Table 9 elsewhere in this document.

Question: Whom should I call for licensing support?

Answer: Refer to Table 9 elsewhere in this document.

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 130 of 165

Question: How do I find my Symmetrix VMAX serial number?
Answer: There are three ways to can obtain a VMAX serial number:
• Located on the Symmetrix VMAX LAC for the initial VMAX hardware purchase
• From the Symmetrix VMAX system Bay – see the blue tag located at the top of the
system bay
• Utilize the Symmetrix VMAX ID found on the Unisphere Management Console –
open command prompt on the server running the Solution Enabler application
and at the prompt type “Symcflist” and press enter

• Run “Get System Setting” from admin GUI

Answer: Note:The SYMMID column contains the Symmetrix serial numbers.

Question: How do I find my VNX/VNX2 serial number?

Answer: Your VNX serial number can be cut and pasted from the "Manage Licenses"
screen of your VNX management console. You can also find it on the tag hanging
from the back of your VNX in the "SN:" field.
Answer: Note:Each VNX comes with a unique serial number/product ID located on the tag
attached to the DPE at the back of the VNX system.

Question: How do I find my VPLEX serial number?

Answer: For VPLEX arrays, this is the VPLEX serial number that contains 5 alphanumeric
characters, followed by 9 numeric characters. You can find the VPLEX serial
number, via the VPLEX CLI or, via the RP CLI command.

Question: I have two VNX5300s with 15 TB each. I have a dual engine VPLEX VS2 Local. I
want to use RecoverPoint through the VPLEX. What licensing do I need for both
the VNX and VPLEX to replicate the full capacity (30 TB) through VPLEX?
Do I still need the remote protection suite for the VNXs? Am I still required to have RP/EX
for VPLEX if the only capacity I have is the 2 VNXs? I want to do the VNX Frame-based
licensing.
Answer: You need a license for RecoverPoint where the splitter is used. In your case, you
use the VPLEX splitter, so you only need a RecoverPoint/EX VPLEX license. No
need for any VNX Remote Protection Suite.

Question: If you are using the VPLEX frame-based for VNX, you can use the appropriate
RecoverPoint frame-based for VPLEX – you'd need two of those, one for each VNX
(same as you need two VPLEX frame-based license). This will allow you to
replicate the full VNX frames.
Answer: The RecoverPoint frame-based gives you the ability to replicate the full VNX. Since
VPLEX frame-based also allows virtualizing the whole VNX, it does not matter how
much you replicate/virtualize.

Question: Is there a reason that the VNX Frame Licensing is showing up in the VPLEX path
then? I was able to see and select the frame-based licenses when I was in CXP?
Answer: Yes, VPLEX and RecoverPoint are licensed separately. The frame-based license
you see in CXP only covers the VPLEX. The only RecoverPoint option in the
VPLEX path today is RP/EX capacity-based. This will change to RP/EX or frame-
based VNX, starting in July 2013.

Question: Why is the RP/EX for VNX with VPLEX price twice the cost of RP/EX for VNX?

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 131 of 165

Answer: The EX for VPLEX frame-based is a VPLEX license, not a VNX license. Therefore,
you do not purchase the VNX bundle (RP/SE) and upgrade from it, you purchase
the EX VPLEX FB. So the comparison should be:
o For VNX splitter – RPS + EX VNX UG

o For VPLEX splitter – EX VPLEX FB

Frequently Asked Questions: VPLEX frame-based Licenses for VNX

Question: Why are VPLEX frame-based licenses being offered?
Answer: To offer a consistent and user friendly way to price and purchase VPLEX when
VPLEX is being purchased with VNX.

Question: What about existing VNXs attached to VPLEX?

Answer: Your existing VPLEX licensing for VNX arrays already attached to VPLEX are not
affected by the new frame-based VPLEX licenses. You have the option of either
continuing with the existing licenses or purchasing the new frame-based licenses.
There is no upgrade path from the existing capacity-based licenses to the frame-
based licenses.

Question: Do I now have to order frame-based licenses?

Answer: No, you have a choice between the traditional VPLEX capacity-based licenses and
the new frame-based licenses.

Question: Is the pricing different from the capacity pricing?

Answer: Yes, capacity-based licenses are priced based on the capacity to be virtualized by
VPLEX and frame-based licenses are priced by the VNX frame type with the ability
to virtualize unlimited capacity.

Question: Do I have to convert my current VPLEX quotes?

Answer: No, you have a choice between the traditional VPLEX capacity-based licenses and
the new frame-based licenses. You only have to convert a current quote if you wish
to utilize the new frame-based licenses.

Question: Is there a rebate for VPLEX capacity that will be taken up by VNX frame?
Answer: No, you may apply your existing VPLEX capacity-based licenses to another
storage array that is not covered by a frame-based license.

Question: When will this be available on CX/DX?

Answer: VPLEX frame-based licenses will be available via VPLEX CX/DX in May 2013 and
VNX CD/DX in July 2013.

Question: How do I create a quote today?

Answer: Prior to the VPLEX frame-based licenses becoming available in CX/DX in May you
can create quotes for these licenses manually through instructions available from
the VPLEX Deal Support Desk: [email protected]

Question: How do I place an order today?

Answer: Prior to the VPLEX frame-based licenses becoming available in CX/DX in May you
can order these licenses manually through instructions available from the VPLEX
Deal Desk.

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 132 of 165

Question: Does this use the standard VPLEX hardware?
Answer: Yes, the VPLEX frame-based licenses are licenses only and apply to all current
VPLEX hardware.

Question: Does this use the standard VPLEX software?

Answer: Yes, the VPLEX frame-based licenses are licenses only and apply to all current
VPLEX software.

Question: Is there any change regarding the migration licensing change?

Answer: No, the provision that allows VPLEX licenses to be used for migration capacities
apply to both frame-based and capacity-based licenses.

Question: Are there VPLEX Geo frame-based licenses available?

Answer: No, currently there are no VPLEX Geo frame-based licenses available but we are
considering offering them in the future.

Question: Can VPLEX frame-based licenses co-exist with VMAX capacity-based licensing?
Answer: Yes, VPLEX capacity-based and frame-based licenses can co-exist on the same
VPELX cluster.

Question: Are there plans to add VMAX frame-based licensing?

Answer: No, because VMAX is also sold via capacity-based pricing there are no plans to
offer frame-based licenses for VMAX.

Question: Should I use the VPLEX, VNX or both splitters for RecoverPoint?
Answer: If you have VPLEX you should use the VPLEX splitter for RecoverPoint.

Question: Why is there no Enhanced Maintenance Option for VPLEX?

Answer: Only Premium Maintenance is available for VPLEX.

Question: If a customer owns a frame-based Local/Base License can they purchase a

capacity-based Metro license or do they have to purchase the frame-based Metro
license?
Answer: Customers with frame-based Local/Base licenses must also purchase frame-based
Metro licenses. Likewise, customer with capacity-based Local/GeoSynchrony
Licenses must purchase capacity-based licenses.

Question: How is RecoverPoint pricing affected?

Answer: Presently, you will need to purchase RP-EX licensing for VPLEX on RecoverPoint.
Both teams are working towards creating frame-based licensing for RP with
VPLEX on VNX. We do not currently have an ETA on when that can happen.

Question: How do I find my RPA cluster ID?

Answer: Run the CLI command get_internal_cluster_uids. Enter the cluster name, or
alternately, press "Enter" to see a list of all clusters.

Question: How many clusters are required for local and for remote? How many arrays can be
attached to a local/remote cluster?
Answer: Remote replication involves two RPA clusters and replication goes through two
clusters.

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 133 of 165

Answer: Local replication involves one RPA cluster and replication goes through one
cluster.
• Local replication can involve more than one array on a cluster
• Remote replication involves arrays attached to two clusters. This can be one or more
arrays per cluster.

Question: EMC has EOL Brocade SAN splitters. SAN splitters are mandatory for
RecoverPoint for non-EMC arrays. I am having two opportunities that are all
designed around RecoverPoint over IBM DS8000. What should I do?
Answer: The SAN splitters were EOL and cannot be ordered for new customers. The
Brocade AP7600 is no longer available from the manufacturer. They will not be
supported by the upcoming release of RecoverPoint 4.0.
Answer: EMC encourages you to consider the VPLEX option. VPLEX Local, used as a
replacement for SAN splitters is competitive in price and in some cases it is less
expensive than the SAN options. It also provides other significant values and
benefits to the customers (such as migration, data mobility, and high availability).

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 134 of 165

RecoverPoint/SE
Question:Does RecoverPoint/SE license support up to five RPA clusters?
Answer: No, the RecoverPoint/SE license does not support this new RecoverPoint 4.0
feature.

Question: What are the typical use cases for upgrading from a RecoverPoint/SE license to a
RecoverPoint/EX license?
Answer: There are three major use cases:
• If you want to replicate between a CLARiiON/VNX and another type of array (VMAX
series arrays or VPLEX)
• If you want to replicate between more than two sites, including up to five RPA clusters
• If you want to use more than one VNX/CX array in either location

Question: How do I upgrade my RecoverPoint/SE license to a RecoverPoint EX license?

Answer: You first need to order a local and/or remote RecoverPoint/SE license for the
VNX/CLARiiON. You then order, via the RecoverPoint standalone path, a
RecoverPoint/SE to RecoverPoint/EX (local and/or remote) upgrade, based on a
VNX/CLARiiON array model.
Answer: For new purchases, you can order RecoverPoint/EX for VNX/CX directly from the
RecoverPoint standalone ordering path.

Question: What local or remote replication capacity do I receive when I purchase a frame-
based RecoverPoint/SE license for VNX/CLARiiON or when I convert from
RecoverPoint/SE to RecoverPoint/EX?
Answer: You receive the right to replicate the full VNX/CX array capacity from the licensed
array.

Question: A customer has VNX5700 systems and is using RecoverPoint/SE. How can we
license the VPLEX in Direct Express to include RecoverPoint replication? Do they
upgrade RecoverPoint on the VNX to the EX version?
Answer: The license is based were the splitter exists. If the splitting is done at the VNX,
then a RP/SE upgrade to RP/EX is required. If the splitting is done at the VPLEX, it
requires RP/EX capacity-based for the VPLEX.

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 135 of 165

RecoverPoint/CL
Question:Can I combine products/licensing options (for example, combining
RecoverPoint/SE, RecoverPoint/EX, or RecoverPoint/CL) within one RecoverPoint
configuration (within one side or between the two sides)?
Answer: RecoverPoint/SE can only work with RecoverPoint/SE. You cannot combine
RecoverPoint/SE with other RecoverPoint RecoverPoint/CL can only work with
RecoverPoint/CL. RecoverPoint/EX can only work with RecoverPoint/EX.

Question: If I have a VMAX 10K license, using raw capacity, can I use the registered model
for an additional VMAX 10K array?
Answer: Yes, every array is licensed individually.

Question: I have a VMAX 10K licensed with RecoverPoint/EX using the raw license. Can I
convert to a registered license?
Answer: No.

Appendix D: RecoverPoint 4.0 Models

The following table describes the RecoverPoint 4.0 software models and associated RecoverPoint legacy
models.
• 457 model: A 457 part number is considered the 'parent' of the 456 models ordered with
it. The 457 carries the base price and will show only in the order summary.
• 456 model: The 456 models are the capacity tiers and carry the RP license and a price.
Note: The function of a license solution is to ensure that the ELM models interface correctly in
EMC Back Office systems. The RecoverPoint License Solution (RP-LS) is required for
all RecoverPoint eLicensing offerings.

RecoverPoint software models

License Model Description Legacy Model
Number
457-101-141 RP/CL LOC BASE = CA RP-CDP-BASE
456-104-495 RP/CL LOC REP CAP (0-14 TB)= CA RP-CDP-R01
RecoverPoint Classic (RP/CL)

456-104-496 RP/CL LOC REP CAP (15-25 TB) =CA RP-CDP-R02

456-104-497 RP/CL LOC REP CAP (26-40 TB) = CA RP-CDP-R03
456-104-498 RP/CL LOC REP CAP (41-60 TB) =CA RP-CDP-R04
456-104-499 RP/CL LOC REP CAP (61-100 TB) =CA RP-CDP-R05
456-104-500 RP/CL LOC REP CAP (101-150 TB) =CA RP-CDP-R06
456-104-501 RP/CL LOC REP CAP (151-250 TB) =CA RP-CDP-R07
456-104-502 RP/CL LOC REP CAP (251-400 TB) =CA RP-CDP-R08
456-104-503 RP/CL LOC REP CAP (401-600 TB) =CA RP-CDP-R09

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 136 of 165

 License Model Description Legacy Model
Number
456-104-504 RP/CL LOC REP CAP (601-1 PB) =CA RP-CDP-R10
456-104-505 RP/CL LOC REP CAP (1 PB+) =CA RP-CDP-R11
457-101-142 RP/CL LOC REP CAP UG =CA RP-CDP-UPG
457-101-143 RP/CL REM BASE =CA RP-RR-BASE
456-104-506 RP/CL REM REP CAP (0-14 TB) =CA RP-RR-R01
456-104-507 RP/CL REM REP CAP (15-25 TB) =CA RP-RR-R02
456-104-508 RP/CL REM REP CAP (26-40 TB) =CA RP-RR-R03
456-104-509 RP/CL REM REP CAP (41-60 TB) =CA RP-RR-R04
456-104-510 RP/CL REM REP CAP (61-100 TB) =CA RP-RR-R05
456-104-511 RP/CL REM REP CAP (101-150 TB) =CA RP-RR-R06
456-104-512 RP/CL REM REP CAP (151-250 TB) =CA RP-RR-R07
456-104-513 RP/CL REM REP CAP (251-400 TB) =CA RP-RR-R08
456-104-514 RP/CL REM REP CAP (401-600 TB) =CA RP-RR-R09
456-104-515 RP/CL REM REP CAP (601-1 PB) =CA RP-RR-R10
456-104-516 RP/CL REM REP CAP (1 PB+) =CA RP-RR-R11
457-101-164 RP/CL REM REP CAP UG =CA RP-RR-UPG
RPEXM-CDP-
457-101-144 RP/EX LOC BASE FOR VMAX =CA
BAS
RPEXM-CDP-
456-104-517 RP/EX LOC REG CAP VMAX (0-14TB)
T1
RP/EX LOC REG CAP VMAX (15-25TB) RPEXM-CDP-
456-104-518
=CA T2
RP/EX LOC REG CAP VMAX (26-40 TB) RPEXM-CDP-
456-104-519
=CA T3
RP/EX for VMAX

RP/EX LOC REG CAP VMAX (41-60 TB) RPEXM-CDP-

456-104-520
=CA T4
RP/EX LOC REG CAP VMAX (61-100 TB) RPEXM-CDP-
456-104-521
=CA T5
RP/EX LOC REG CAP VMAX (101-150 TB) RPEXM-CDP-
456-104-522
=CA T6
RP/EX LOC REG CAP VMAX (151-250 TB) RPEXM-CDP-
456-104-523
=CA T7
RP/EX LOC REG CAP VMAX (251-400 TB) RPEXM-CDP-
456-104-524
=CA T8
RP/EX LOC REG CAP VMAX (401-600 TB) RPEXM-CDP-
456-104-525
=CA T9

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 137 of 165

 License Model Description Legacy Model
Number
RP/EX LOC REG CAP VMAX (601-1 PB) RPEXM-CDP-
456-104-526
=CA T10
RPEXM-CDP-
456-104-527 RP/EX LOC REG CAP VMAX (1 PB+) =CA
T11
RP/EX LOC REG CAP UG FOR VMAX RPEXM-CDP-
457-101-145
=CA UG
RPEXM-CRR-
457-101-146 RP/EX REM BASE FOR VMAX =CA
BAS
RP/EX REM REG CAP VMAX (0-14TB) RPEXM-CRR-
456-104-528
=CA T1
RP/EX REM REG CAP VMAX (15-25TB) RPEXM-CRR-
456-104-529
=CA T2
RP/EX REM REG CAP VMAX (26-40 TB) RPEXM-CRR-
456-104-530
=CA T3
RP/EX REM REG CAP VMAX (41-60 TB) RPEXM-CRR-
456-104-531
=CA T4
RP/EX REM REG CAP VMAX (61-100 TB) RPEXM-CRR-
456-104-532
=CA T5
RP/EX REM REG CAP VMAX (101-150 RPEXM-CRR-
456-104-533
TB) =CA T6
RP/EX REM REG CAP VMAX (151-250 RPEXM-CRR-
456-104-534
TB) =CA T7
RP/EX REM REG CAP VMAX (251-400 RPEXM-CRR-
456-104-535
TB) =CA T8
RP/EX REM REG CAP VMAX (401-600 RPEXM-CRR-
456-104-536
TB) =CA T9
RP/EX REM REG CAP VMAX (601-1 PB) RPEXM-CRR-
456-104-537
=CA T10
RPEXM-CRR-
456-104-538 RP/EX REM REG CAP VMAX (1 PB+) =CA
T11
RP/EX REM REG CAP UG FOR VMAX RPEXM-CRR-
457-101-147
=CA UG
RPEX2-CDP-
457-101-148 RP/EX LOC BASE FOR VMAX20 =CA
BAS
RP/EX for VMAX 20K

RP/EX LOC REG CAP VMAX20 (0-14 TB) RPEX2-CDP-

456-104-539
=CA T1
RP/EX LOC REG CAP VMAX20 (15-25 TB) RPEX2-CDP-
456-104-540
=CA T2
RP/EX LOC REG CAP VMAX20 (26-40 TB) RPEX2-CDP-
456-104-541
=CA T3
RP/EX LOC REG CAP VMAX20 (41-60 TB) RPEX2-CDP-
456-104-542
=CA T4

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 138 of 165

License Model Description Legacy Model
Number
RP/EX LOC REG CAP VMAX20 (61-100 RPEX2-CDP-
456-104-543
TB) =CA T5
RP/EX LOC REG CAP VMAX20 (101-150 RPEX2-CDP-
456-104-544
TB) =CA T6
RP/EX LOC REG CAP VMAX20 (151-250 RPEX2-CDP-
456-104-545
TB) =CA T7
RP/EX LOC REG CAP VMAX20(251-400 RPEX2-CDP-
456-104-546
TB) =CA T8
RP/EX LOC REG CAP VMAX20 (401-600 RPEX2-CDP-
456-104-547
TB) =CA T9
RP/EX LOC REG CAP VMAX20 (601-1 PB) RPEX2-CDP-
456-104-548
=CA T10
RP/EX LOC REG CAP VMAX20 (1 PB+) RPEX2-CDP-
456-104-549
=CA T11
RP/EX LOC REG CAP UG FOR VMAX20 RPEX2-CDP-
457-101-149
=CA UG
RPEX2-CRR-
457-101-150 RP/EX REM BASE FOR VMAX20 =CA
BAS
RP/EX REM REG CAP VMAX20 (0-14 TB) RPEX2-CRR-
456-104-550
=CA T1
RP/EX REM REG CAP VMAX20 (15-25 RPEX2-CRR-
456-104-551
TB) =CA T2
RP/EX REM REG CAP VMAX20 (26-40 RPEX2-CRR-
456-104-552
TB) =CA T3
RP/EX REM REG CAP VMAX20 (41-60 RPEX2-CRR-
456-104-553
TB) =CA T4
RP/EX REM REG CAP VMAX20 (61-100 RPEX2-CRR-
456-104-554
TB) =CA T5
RP/EX REM REG CAP VMAX20 (101-150 RPEX2-CRR-
456-104-555
TB) =CA T6
RP/EX REM REG CAP VMAX20 (151-250 RPEX2-CRR-
456-104-556
TB) =CA T7
RP/EX REM REG CAP VMAX20 (251-400 RPEX2-CRR-
456-104-557
TB) =CA T8
RP/EX REM REG CAP VMAX20 (401-600 RPEX2-CRR-
456-104-558
TB) =CA T9
RP/EX REM REG CAP VMAX20 (601-1 RPEX2-CRR-
456-104-559
PB) =CA T10
RP/EX REM REG CAP VMAX20 (1 PB+) RPEX2-CRR-
456-104-560
=CA T11
RP/EX REM REG CAP UG FOR VMAX20 RPEX2-CRR-
457-101-151
=CA UG

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 139 of 165

 License Model Description Legacy Model
Number
RPEXM2-CDP-
457-101-152 RP/EX LOC BASE FOR VMAX40 =CA
BA
RP/EX LOC REG CAP VMAX40 (0-14 TB) RPEXM2-CDP-
456-104-561
=CA T1
RP/EX LOC REG CAP VMAX 40(15-25 TB) RPEXM2-CDP-
456-104-562
=CA T2
RP/EX LOC REG CAP VMAX40 (26-40 TB) RPEXM2-CDP-
456-104-563
=CA T3
RP/EX LOC REG CAP VMAX40 (41-60 TB) RPEXM2-CDP-
456-104-564
=CA T4
RP/EX LOC REG CAP VMAX40 (61-100 RPEXM2-CDP-
456-104-565
TB) =CA T5
RP/EX LOC REG CAP VMAX40 (101-150 RPEXM2-CDP-
456-104-566
TB) =CA T6
RP/EX LOC REG CAP VMAX40 (151-250 RPEXM2-CDP-
456-104-567
TB) =CA T7
RP/EX LOC REG CAP VMAX40 (251-400 RPEXM2-CDP-
456-104-568
TB) =CA T8
RP/EX for VMAX40K

RP/EX LOC REG CAP VMAX40 (401-600 RPEXM2-CDP-

456-104-569
TB) =CA T9
RP/EX LOC REG CAP VMAX40 (601-1 PB) RPEXM2-CD-
456-104-570
=CA T10
RP/EX LOC REG CAP VMAX40(1 PB+) RPEXM2-CD-
456-104-571
=CA T11
RP/EX LOC REG CAP UG FOR VMAX40 RPEXM2-CDP-
457-101-153
=CA UG
RPEXM2-
457-101-154 RP/EX REM BASE FOR VMAX40 =CA
CRR-BA
RP/EX REM REG CAP VMAX40 (0-14 TB) RPEXM2-
456-104-572
=CA CRR-T1
RP/EX REM REG CAP VMAX40 (15-25 RPEXM2-
456-104-573
TB) =CA CRR-T2
RP/EX REM REG CAP VMAX40 (26-40 RPEXM2-
456-104-574
TB) =CA CRR-T3
RP/EX REM REG CAP VMAX40 (41-60 RPEXM2-
456-104-575
TB) =CA CRR-T4
RP/EX REM REG CAP VMAX40 (61-100 RPEXM2-
456-104-576
TB) =CA CRR-T5
RP/EX REM REG CAP VMAX40 (101-150 RPEXM2-
456-104-577
TB) =CA CRR-T6
RP/EX REM REG CAP VMAX40 (151-250 RPEXM2-
456-104-578
TB) =CA CRR-T7

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 140 of 165

 License Model Description Legacy Model
Number
RP/EX REM REG CAP VMAX40 (251-400 RPEXM2-
456-104-579
TB) =CA CRR-T8
RP/EX REM REG CAP VMAX40 (401-600 RPEXM2-
456-104-580
TB) =CA CRR-T9
RP/EX REM REG CAP VMAX40 (601-1 RPEXM2-CR-
456-104-581
PB) =CA T10
RP/EX REM REG CAP VMAX40 (1 PB+) RPEXM2-CR-
456-104-582
=CA T11
RP/EX REM REG CAP UG FOR VMAX40 RPEXM2-
457-101-155
=CA CRR-UG
RPEXE-CDP-
457-101-156 RP/EX BASE LOC FOR VMAX10 =CA
BAS
RPEXE-CDP-
456-104-583 RP/EX LOC REG CAP 1TB VMAX10 =CA
1TB
RPEXE-CDP-
457-101-340 RP/EX LOC REG CAP UG VMAX 10 =CA
UG
RP/EX for VMAX 10K

RPEXE-CRR-
457-101-157 RP/EX BASE REM FOR VMAX10 =CA
BAS
RPEXE-CRR-
456-104-585 RP/EX REM REM CAP 1TB VMAX10 =CA
1TB
RPEXE-CRR-
457-101-341 RP/EX REM REG CAP UG VMAX10 =CA
UG
456-104-587 RP/EX RAW 1TB SATA VMAX10 = CB RPEX-1TBS
456-104-589 RP/EX RAW 1TB NSATA VMAX10 = CB RREX-1TBN
457-101-158 RP/EX RAW BASE VMAX10 = CB RPEX-BASE
456-104-591 RP/EX FTS EXT CAP 1TB VMAX10 = CB RP-FTS-EXT
457-101-159 RP/EX RAW CAP UG VMAX10 = CB RPEX-UPG
RPEXV-CDP-
457-101-160 RP/EX LOC BASE FOR VPLEX =CA
BAS
RP/EX LOC REG CAP VPLEX (0-14TB) RPEXV-CDP-
456-104-592
=CA T1
RP/EX for VPLEX

RP/EX LOC REG CAP VPLEX (15-25TB) RPEXV-CDP-

456-104-593
=CA T2
RP/EX LOC REG CAP VPLEX (26-40 TB) RPEXV-CDP-
456-104-594
=CA T3
RP/EX LOC REG CAP VPLEX (41-60 TB) RPEXV-CDP-
456-104-595
=CA T4
RP/EX LOC REG CAP VPELX (61-100 TB) RPEXV-CDP-
456-104-596
=CA T5

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 141 of 165

License Model Description Legacy Model
Number
RP/EX LOC REG CAP VPLEX (101-150 RPEXV-CDP-
456-104-597
TB) =CA T6
RP/EX LOC REG CAP VPLEX (151-250 RPEXV-CDP-
456-104-598
TB) =CA T7
RP/EX LOC REG CAP VPLEX (251-400 RPEXV-CDP-
456-104-599
TB) =CA T8
RP/EX LOC REG CAP VPLEX (401-600 RPEXV-CDP-
456-104-600
TB) =CA T9
RP/EX LOC REG CAP VPLEX (601-1PTB) RPEXV-CDP-
456-104-601
=CA T10
RP/EX LOC REG CAP T11 VPLEX (1 PB+) RPEXV-CDP-
456-104-602
=CA T11
RPEXV-CDP-
457-101-161 RP/EX LOC REG CAP UG VPLEX =CA
UG
RPEXV-CRR-
457-101-162 RP/EX REM BASE FOR VPLEX =CA
BAS
RP/EX REM REG CAP VPLEX (0-14TB) RPEXV-CRR-
456-104-603
=CA T1
RP/EX REM REG CAP VPLEX (15-25TB) RPEXV-CRR-
456-104-604
=CA T2
RP/EX REM REG CAP VPLEX (26-40 TB) RPEXV-CRR-
456-104-605
=CA T3
RP/EX REM REG CAP VPLEX (41-60 TB) RPEXV-CRR-
456-104-606
=CA T4
RP/EX REM REG CAP VPLEX (61-100 TB) RPEXV-CRR-
456-104-607
=CA T5
RP/EX REM REG CAP VPLEX (101-150 RPEXV-CRR-
456-104-608
TB) =CA T6
RP/EX REM REG CAP VPLEX (151-250 RPEXV-CRR-
456-104-609
TB) =CA T7
RP/EX REM REG CAP VPLEX (251-400 RPEXV-CRR-
456-104-610
TB) =CA T8
RP/EX REM REG CAP VPLEX (401-600 RPEXV-CRR-
456-104-611
TB) =CA T9
RP/EX REM REG CAP VPLEX (601-1 PB) RPEXV-CRR-
456-104-612
=CA T10
RP/EX REM REG CAP VPLEX (1 PB+) RPEXV-CRR-
456-104-613
=CA T11
RPEXV-CRR-
457-101-163 RP/EX REM REG CAP UG VPLEX =CA
UG
456-104-614 RP/SE LOC FOR LPS V51= IC LPS-V51
R

N
P

S
E

X
o

2
r
/

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 142 of 165

 License Model Description Legacy Model
Number
456-104-615 RP/SE LOC FOR LPS V53/V54= IC LPS-V53/V54
456-104-616 RP/SE LOC FOR LPS V55/V56= IC LPS-V55/V56
456-104-617 RP/SE LOC FOR LPS V57/V58= IC LPS-V57/V58
456-104-618 RP/SE LOC FOR LPS V75/V76= IC LPS-V75/V76
456-104-626 RP/SE LOC FOR LPS V80= IC LPS-V80
456-104-619 RP/SE REM FOR RPS V51= IC RPS-V51
456-104-620 RP/SE REM FOR RPS V53/V54=IC RPS-V53/V54
456-104-621 RP/SE REM FOR RPS V55/V56= IC RPS-V55/V56
456-104-622 RP/SE REM FOR RPS V57/V58= IC RPS-V57/V58
456-104-623 RP/SE REM FOR RPS V75/V76= IC RPS-V75/V76
456-104-627 RP/SE REM FOR RPS V80 = IC RPS-V80
RPEX-CDP51-
456-104-637 RP/SE TO RP/EX LOC UG V51, CX = IC
UG
RPEX-CDP53-
456-104-638 RP/SE-RP/EX LOC UG V53, CX120=IC
UG
RP/SE TO RP/EX LOC UG V55,CX240 = RPEX-CDP55-
456-104-639
IC UG
RP/SE TO RP/EX LOC UG V57,CX480 = RPEX-CDP57-
456-104-640
IC UG
RP/SE UG to RP/EX

RP/SE TO RP/EX LOC UG V75,CX960 = RPEX-CDP75-

456-104-641
IC UG
RPEX-CRR51-
456-104-642 RP/SE TO RP/EX REM UG V51, CX = IC
UG
RPEX-CRR53-
456-104-643 RP/SE-RP/EX REM UG V53,CX120=IC
UG
RP/SE TO RP/EX REM UG V55,CX240 = RPEX-CRR55-
456-104-644
IC UG
RP/SE TO RP/EX REM UG V57,CX480 = RPEX-CRR57-
456-104-645
IC UG
RP/SE TO RP/EX REM UG V75,CX960 = RPEX-CRR75-
456-104-646
IC UG
456-104-628 RP/SE TO RP/EX LOC UG V80= IC N/A
RP/SE UG to RP/EX

456-104-629 RP/SE TO RP/EX REM UG V80=IC N/A

456-105-068 RP/SE TO RP/EX LOC UG V52 = IC N/A
VNX2

456-105-069 RP/SE TO RP/EX LOC UG V54 =IC N/A

456-105-070 RP/SE TO RP/EX LOC UG V56 = IC N/A
456-105-071 RP/SE TO RP/EX LOC UG V58 = IC N/A

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 143 of 165

 License Model Description Legacy Model
Number
456-105-072 RP/SE TO RP/EX LOC UG V76 = IC N/A
456-105-073 RP/SE TO RP/EX REM UG V52 = IC N/A
456-105-074 RP/SE TO RP/EX REM UG V54 =IC N/A
456-105-075 RP/SE TO RP/EX REM UG V56 = IC N/A
456-105-076 RP/SE TO RP/EX REM UG V58 = IC N/A
456-105-077 RP/SE TO RP/EX REM UG V76 = IC N/A
456-104-647 RPSE LOC ARRY LIC - CX1 and CX2 = IC RPSE-CDP-L2
RPSE LOC ARRY LIC - CX3-10, AX4-5 =
456-104-648 RPSE-CDP-L3
IC
RPSE LOC ARRY LIC - CX3-20, CX4-120
456-104-649 RPSE-CDP-L4
= IC
RPSE LOC ARRY LIC- CX3-40, CX4-240 =
456-104-650 RPSE-CDP-L5
RP/SE FRAME BASED FOR CX

IC
RPSE LOC ARRY LIC - CX3-80, CX4-480
456-104-651 RPSE-CDP-L6
= IC
456-104-652 RPSE LOC ARRY LIC - CX4-960 = IC RPSE-CDP-L7
456-104-653 RPSE REM ARRY LIC- CX1 and CX2 = IC RPSE-CRR-L2
RPSE REM ARRY LIC - CX3-10, AX4-5 =
456-104-654 RPSE-CRR-L3
IC
RPSE REM ARRY LIC - CX3-20, CX4-120
456-104-655 RPSE-CRR-L4
= IC
RPSE REM ARRY LIC - CX3-40, CX4-240
456-104-656 RPSE-CRR-L5
= IC
RPSE REM ARRY LIC - CX3-80, CX4-480
456-104-657 RPSE-CRR-L6
= IC
456-104-658 RPSE REM ARRY LIC - CX4-960 = IC RPSE-CRR-L7
RPSE-CRR-
456-104-659
RP/SE CAP UG TO FRAME BASED

RP/SE REM UG FOR CX1 and CX2 = IC L2C

RPSE-CRR-
456-104-660 RP/SE REM UG FOR CX3-10, AX4-5 = IC
L3C
RP/SE REM UG FOR CX3-20,CX4-120 = RPSE-CRR-
456-104-661
FOR CX

IC L4C
RP/SE REM UG FOR CX3-40, CX4-240 = RPSE-CRR-
456-104-662
IC L5C
RP/SE REM UG FOR CX3-80 CX4-480 = RPSE-CRR-
456-104-663
IC L6C
RPSE-CRR-
456-104-664 RP/SE REM UG FOR CX4-960 = IC
L7C

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 144 of 165

 License Model Description Legacy Model
Number
RPSE-CDP-
456-104-665
RP/SE LOC UG FOR CX1 and CX2 = IC L2C
RPSE-CDP-
456-104-666 RP/SE LOC UG FOR CX3-10, AX4-5 = IC
L3C
RP/SE LOC UG FOR CX3-20, CX4-120 = RPSE-CDP-
456-104-667
IC L4C
RP/SE LOC UG FOR CX3-40, CX4-240 = RPSE-CDP-
456-104-668
IC L5C
RP/SE LOC UG FOR CX3-80 CX4-480 = RPSE-CDP-
456-104-669
IC L6C
RPSE-CDP-
456-104-670 RPSE LOC UG FOR CX4-960 = IC
L7C

CUSTOM ELA RECOVERPOINT-CL

456-104-675 ELA-RP-CDP
LOCAL =CA
ELA

CUSTOM ELA RECOVERPOINT-CL

456-104-676 ELA-RP-RR
REMOTE =CA

456-104-928
RP/EX LOC FRAME BASED V51 FOR VPLEX =IC N/A
RP/EX for VPLEX with FRAME BASED

456-104-929
RP/EX LOC FRAME BASED V53 FOR VPLEX =IC N/A
456-104-930
RP/EX LOC FRAME BASED V55 FOR VPLEX =IC N/A
456-104-931
RP/EX LOC FRAME BASED V57 FOR VPLEX =IC N/A
456-104-932
RP/EX LOC FRAME BASED V75 FOR VPLEX =IC N/A
VNX

456-104-933
RP/EX REM FRAME BASED V51 FOR VPLEX =IC N/A
456-104-934
RP/EX REM FRAME BASED V53 FOR VPLEX =IC N/A
456-104-935
RP/EX REM FRAME BASED V55 FOR VPLEX =IC N/A
456-104-936
RP/EX REM FRAME BASED V57 FOR VPLEX =IC N/A
456-104-937
RP/EX REM FRAME BASED V75 FOR VPLEX =IC N/A
456-104-938
RP/EX LOC FRAME BASED V52 FOR VPLEX =IC N/A
RP /EX for VPLEX with FRAME BASED

456-104-939
RP/EX LOC FRAME BASED V54 FOR VPLEX =IC N/A
456-104-940
RP/EX LOC FRAME BASED V56 FOR VPLEX =IC N/A
456-104-941
RP/EX LOC FRAME BASED V58 FOR VPLEX =IC N/A
456-104-942
RP/EX LOC FRAME BASED V76 FOR VPLEX =IC N/A
VNX2

456-104-943
RP/EX LOC FRAME BASED V80 FOR VPLEX =IC N/A
456-104-944
RP/EX REM FRAME BASED V52 FOR VPLEX =IC N/A
456-104-945
RP/EX REM FRAME BASED V54 FOR VPLEX =IC N/A
456-104-946
RP/EX REM FRAME BASED V56 FOR VPLEX =IC N/A
456-104-947
RP/EX REM FRAME BASED V58 FOR VPLEX =IC N/A

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 145 of 165

License Model Description Legacy Model
Number
456-104-948
RP/EX REM FRAME BASED V76 FOR VPLEX =IC N/A
456-104-949
RP/EX REM FRAME BASED V80 FOR VPLEX =IC N/A

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 146 of 165

RecoverPoint physical appliances
RPA Model (TAA) Model Description
CLS-RPHW-G5T RPA GEN5-TAA FOR RP CLASSIC
VME-RPHW-G5T RPA GEN5-TAA FOR VMAX 10K
RPA GEN5-TAA FOR VMAX V1 and VMAX
VMX-RPHW-G5T
V2
VPLX-RPHW-
RPA GEN5-TAA FOR VPLEX
G5T
VNX-RPHW3-
RPA GEN5 TAA FOR VNX L1
G5T
VNX-RPHW5-
RPA GEN5-TAA FOR VNX L2
G5T

RecoverPoint virtual appliances

RPA Model Model Description
456-104-624 VIRTUAL RPA FOR RP/SE =IC

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 147 of 165

 Appendix E: RecoverPoint 4.0 License File Example
A RP License File is a set of parameters and values recognized by the RecoverPoint system
(unlike a LAC) that contain multiple licenses for the same Locking ID. In a license file, each
license instance starts with the word INCREMENT.
• RecoverPoint Offering
• RecoverPoint Type (Local + Remote)
• License Type (permanent/expiring)
• Capacity entitlements
• Locking ID (array S/N or RPA cluster ID)
• Creation timestamp
• Digital signatures

The RecoverPoint 4.0 License File contains the following information:

INCREMENT RP {Type} {Replication} {Prod} EMCLM {Version} {Expiration}
VENDOR_STRING=LOCKING_ID= {LockingID}; Capacity= {Capacity};
CAPACITY_HOSTID=ANY dist_info= ”{Customer}” ISSUER=EMC \
ISSUED= {Issued} NOTICE= ”{Site_info}” \
SN= {SN} TS_OK SIGN=”{Sign}”

Table 8 describes the variables in the license file, and their possible values.
Table 8 License file variables

Variable Description Comments Examples

The RecoverPoint license model.

RecoverPoint/CL: Uses the • RP.CL.xxx.xx
RecoverPoint/CL licensing model.
Valid values are:
• CL for RecoverPoint/CL
RecoverPoint/EX: Uses the • RP.SE.xxx.xx
Type
RecoverPoint/EX licensing model.
• EX for RecoverPoint/EX
RecoverPoint/SE: Uses the • RP.EX.xxx.xx
• SE for RecoverPoint/SE
RecoverPoint/SE licensing model.

The RecoverPoint license model. The license supports replication to RP.xx.REM.xx

Valid values are: a local copy.
Replication
• LOC for local replication The license supports replication to RP.xx.LOC.xx
a remote copy.
• REM for remote replication

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 148 of 165

 Variable Description Comments Examples
The array model. Valid values are: RP.xx.xx.VNX5700
• 00 - for RecoverPoint/CL
licenses
• ELA - for licenses based on
Enterprise License
Agreements (see Table 80 on
page 347)
• VNX5100, VNX5200,
VNX5300, VNX5400,
Prod VNX5500, VNX5600,
VNX5700, VNX5800,
VNX7500, VNX7600,
VNX8000,
• VMAX, VMAX 10K, VMAX
20K, VMAX40K
• VPLEX
• CX, CX4-120, CX4-240, CX4-
480, CX4-960, AX4-5, AX4-
120

The license schema version Note: The only valid value in 1.0
Version
RecoverPoint 4.0 is 1.0.

The license expiration date. Note: Warnings will appear before • 15-Dec-2014
RecoverPoint licenses can be: an expiring license is about to
• Permanent
expire.
• Permanent (The license does
Note: Valid values are:
not have an expiration date)
• Permanent
• or
Expiration • A date in the format day-
• Expiring (The date on which
month-year
the license expires):
▪ Evaluation: Up to 90 days
▪ Temporary: Up to 365 days
▪ Emergency: Up to a few days

The unique identifier of the entity The serial number of the licensed Array serial numbers
that the license is tied to. storage array. are in the format:
Valid values are: • RecoverPoint/SE and • VNX:
• Array serial number in RecoverPoint/EX: An array APM0012080124
RecoverPoint/SE and serial number 0
RecoverPoint/EX • RecoverPoint/CL: RPA • VMAX:
• An RPA cluster ID in Cluster ID 000194910874
Locking ID
RecoverPoint/CL • Note: To find a RPA Cluster • VPLEX:
ID, in the RecoverPoint CLI, FNM0010550051
run the 1
get_internal_cluster_uids RPA cluster IDs are
command and enter the in the format:
cluster name or press “Enter”
to display all of the RPA 77546439875555408
Cluster IDs. 54

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 149 of 165

 Variable Description Comments Examples
The number of terabytes licensed A value of zero means that the • 100 (for 100 TB)
for replication at a given site. replication capacity is unlimited. • 0 (for unlimited
• RecoverPoint/SE: Full VNX/CX capacity)
array (unlimited)
• RecoverPoint/EX: Full VNX/CX
Capacity
array
• RecoverPoint/CL: As
purchased, per RPA cluster
All other arrays: As purchased
per array.

The capacity of data being 100 TB

Unit
replicated.

The customer’s name and physical EMC, MyStreet,

Customer address, as entered in the Hopkinton, MA
RecoverPoint sales order.

Issued The license creation date. 15-Dec-2014

The geographical location of the In RecoverPoint, this SiteID ACTIVATED TO

customer site. (received from licensing) is called SiteID:
Site_info Location ID and it is sent to the 112207055
system report mechanism (SyR)
for support purposes.

The Activation ID, a uniquely Every time a license is activated, 2055509

generated value specific to the the SN changes. This value is
SN activation. sent to the system report
mechanism (SyR) for support
purposes.

An encrypted hash segment 0004 0EAA 52A0

containing the license information, F74E 6EG4 BE6A
which is used by RecoverPoint to 6CF0 1400\
Sign validate the license and ensure its 10E3 A333 704C
uniqueness. 11E1 9DAF DA5B
1C0B

Active The license is active.

Expired The expiration date of the license

has passed.

Inactive The license is not active. This can

happen when:
• If a licensed array is not
Status mapped and zoned to the
RPA.
• If a RecoverPoint/EX license
and a RecoverPoint/CL
license are both added at the
same RPA cluster, and the
RecoverPoint/EX license
becomes inactive.

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 150 of 165

The following figure contains some common examples of RecoverPoint 4.0 licenses.
One license file can include multiple licenses for the same Locking ID. Each license starts with the word
INCREMENT.

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 151 of 165

Appendix F: Rules for Expiring Licenses
RecoverPoint has the following expiring licenses:
• Temporary licenses
• Evaluation licenses
• Emergency Licenses

Temporary licenses
Temporary licenses can be used by both internal and external customers for the purpose of special
services engagements, demonstrations, testing, and so on.
• Temporary licenses must have duration of either 30, 90, or 365 days
• Temporary licenses must be extendable in 30, 90, or 365 day increments
• Temporary licenses are available by submitting a change request, via NGOE

Evaluation licenses
Evaluation licenses allow external customers to evaluate the RecoverPoint software on a trial basis,
before deciding whether to make the purchase.
• Evaluation licenses duration is either 30 or 90 days
• Evaluation licenses must be extendable in either 30 or 90 day increments
• Evaluation licenses are orderable through CXP/DXP

Emergency licenses
Emergency licenses provide external customers with a temporary RecoverPoint software license that can
be used when EMC support is experiencing issues with the creation of non-expiring license files.
• Emergency licenses duration is 30 days
• Emergency licenses are extendable in 30 day increments
• Emergency Licenses are available by submitting a change request, via NGOE

Notes:

• When running RecoverPoint with expiring licenses, multiple warnings will be issued
before an expiring license is about to expire. After license expiration, replication
continues but no further operations will be allowed on the RecoverPoint system.
• Adding a new expiring license with the same Locking ID as an existing expiring license
replaces the existing expiring license

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 152 of 165

How to find your array
RPA cluster
serial numbers
IDs Appendix G: How to Find Locking IDs
A Locking ID is the unique identifier of the entity that the
license is enforced to.
Depending on the entitlement, the Locking ID can be either an RPA Cluster ID (in RecoverPoint/CL), or
an array serial number (in RecoverPoint/SE and RecoverPoint/EX).
Array IDs may be obtained by using the “Get System Setting” command from the admin GUI. The array
ID will appear in the “Array Serial” field.

To find RPA Cluster IDs (in RecoverPoint 4.0 only):

1. Run the CLI command get_internal_cluster_uids
2. Enter the cluster name, or alternately, press Enter to see a list of all cluster internal uids.
3. Note the output:
Internal cluster uids:
Cluster1: 123123123123123123
Cluster2: 345345345345345345
Cluster3: 456456456456456456

The RPA cluster ID contains 1 to 20 alphanumeric characters.

The procedures for finding your array serial numbers differ per array type.
• For VNX/VNX2 models enter the VNX/VNX2 Serial Number as NNNNN999999999 (5
alphanumeric, 9 numeric)
• For VMAX based models enter the Symm ID as 9999999999999 (12 numeric). Note that
the Symm ID is not the same as the Symm Serial Number.
• For VPLEX based models enter the VPLEX Serial Number as NNNNN999999999 (5
alphanumeric, 9 numeric)

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 153 of 165

For VNX arrays
For VNX/VNX2 Series arrays, use the Naviseccli getagent command to find the array serial number. Note
that spaddress is the address of SPA or SPB, not the control station. For example:
naviseccli -Scope 0 -user <username> -password <password> -address <spaddress> getagent

Agent Rev: 7.32.0 (5.2)

Name: K10
Desc:
Node: A-APM00120701240
Physical Node: K10
Signature: 2998645
Peer Signature: 2998612
Revision: 05.32.000.4.007
SCSI Id: 0
Model: VNX7500
Model Type: Rackmount
Prom Rev: 8.10.00
SP Memory: 24576
Serial No: APM00120701240
SP Identifier: A
Cabinet: SPE5

For Symmetrix arrays

For Symmetrix arrays, you can display the array serial number on the Symmetrix array or through
RecoverPoint.
On the Symmetrix array, run the SYMCLI command to find the array serial number. Note that the
Symmetrix locking ID is the SYMM ID.
For example:
# symcfg list
S Y M M E T R I X

Mcode Cache Num Phys Num Symm

SymmID Attachment Model Version Size (MB) Devices Devices
000194900874 Local VMAX-1SE 5876 28672 32 695

In RecoverPoint, run the get_splitter_states CLI command to display the array serial number.
For example:
SiteC > get_splitter_states cluster=SiteC
Cluster:
SiteC:
Splitters:
SYMM- 000194900874
Status: OK

For VPLEX arrays

For VPLEX arrays, you can display the array serial number on the VPLEX array or through RecoverPoint.
On the VPLEX, for example, type:
VPlexcli:/> ls -t /engines/*::top-level-assembly

/engines/engine-2-1:

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 154 of 165

 Name Value
------------------ --------------
top-level-assembly FNM00104500511

/engines/engine-1-1:
Name Value
------------------ --------------
top-level-assembly FNM00104500511

In RecoverPoint, run the get_splitter_states CLI command to display the array serial number.
ClusterA> get_splitter_states cluster=ClusterA

Cluster:
ClusterA:
Splitters:
FNM00104500511
Status: OK

Appendix H: Where to Get Support

The following table contains the support contacts that you may need when ordering and licensing.
Table 9 Contact information

Contact Americas EMEA APJ

Legacy Tel: 1-508-249-5401 +1-508-249-5401 +1-508-249-5401
Customer Support hours: 24/7 Support hours: 24/7 Support hours: 24/7
Transition
(Upgrade)

Enterprise Distribution Deal Desk North America EMEA Deal Desk APJ Pricing Distribution
License Support hours: 24/7 Support hours: 24/7 list
Agreement
Support hours: 24/7
s

Web URL: TS Pre Sales Support Center URL: http://emc.force.com/PresalesCase Creation

Tel: 1-866-EMC-7777, Option +1-508-435-1000, ext. 54777, Option #2

#2 (Staffed during EMC US work days)
Ordering
Support hours: Monday –
Friday (Business hours)

Email: [email protected]

SR:* http://support.emc.com > Service Center > Create Service Request

Tel: 1-800-782-4362 353 (0) 21 487-9862 353 (0) 21 487-9883

License
Activation • Option #4 then Option #1 Support hours: 24/7
or Support hours: 24/7
Installation • Option #4
• Support hours: Fax: 353 (0) 21 487- Fax: 353 (0) 21 487-9701
9701
24/7
Other Web URL support.emc.com support.emc.com support.emc.com
support
issues

*SRs replace email support for Core Software.

Appendix I: RecoverPoint Ordering and Licensing Terminology

The following table describes the RecoverPoint eLicensing terminology.

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 155 of 165

Term Description
System / Account ID The unique identifier of all RPA clusters in a RecoverPoint
system.
Note: In RecoverPoint 4.0 and later version, the Account ID
is used to display the System ID.
In RecoverPoint 4.0 and later versions, the Account/System
ID:
• Is generated for the first RPA cluster that is added to
the system during RecoverPoint deployment. When
adding additional RPA clusters to the system, the
additional RPA clusters receive the Account ID of the
first RPA cluster.
• Does not change with upgrades. When upgrading to
RecoverPoint 4.0 from previous RecoverPoint versions,
the Account ID value is taken from the value of Account
ID in the previous RecoverPoint version.
• Can only be displayed by the user (using the
get_account_settings CLI command), and can only be
modified by EMC Customer Support.
Array serial number A unique identifier of a storage array that is registered (and
therefore enabled) for replication.
• For VNX/VNX2 arrays, this is the VNX/VNX2 Serial
Number. It contains 5 alphanumeric characters followed
by 9 numeric characters.
• For VMAX arrays, this is the VMAX Symm ID. It
contains 12 numeric characters. Note that the SYMM ID
is not the same as the SYMM Serial Number.
• For VPLEX arrays, this is the VPLEX Serial Number. It
contains 5 alphanumeric characters followed by 9
numeric characters.
To find your array serial number, see Appendix G: How to
Find Locking IDs on page 153.
CDP See: Local replication
CLR Replaced by the terms “local replication” and “remote
replication”.
Cluster See: RPA Cluster

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 156 of 165

Term Description
Copy A logical RecoverPoint entity that constitutes all of the
volumes of a consistency group that are configured for
replication at a given RPA cluster, including the journal
volumes.
• A maximum of one production copy and up to four non-
production copies can be configured per consistency
group.
In local replication, there can be only one production copy
and one local copy.
In remote replication:
• If a local copy exists there can be up to three remote
copies.
• If a local copy does not exist, there can be up to four
remote copies.
• There can be a maximum of two copies per consistency
group, per RPA cluster.
CRR See: Remote replication
Deep link The Click here link in the LAC email that automatically
navigates to RecoverPoint Powerlink Licensing, opens the
entitlements search page, enters the associated LAC into
the LAC field, and searches for all inactive entitlements
associated with the LAC.
ELA Enterprise License Agreement. A license agreement with a
customer that provides non-standard license terms.
In RecoverPoint/CL, ELA license types provide unlimited
replication capacity. RecoverPoint ELA licensing is based
on RecoverPoint/CL licensing. All ELA orders are converted
to RecoverPoint/CL licenses. Local replication and remote
replication are licensed separately. The license is tied to the
RPA cluster ID. The license is non-transferable but it does
survive array tech refresh.
Note: Call the North America, EMEA or APJ deal desk for
help with ELA orders, see Appendix G: Where to Get
Support.
ELMS See: Powerlink Licensing
EMC Online Support EMC’s new Web site for all support-related issues.
Access EMC Online Support by navigating to
support.emc.com.
Entitlement An electronic record representing the type, version, and
quantity of the software to which you have purchased a
license. When an entitlement is activated an electronic
license key or license file is generated.
Note: Some entitlements may contain two licensing models.
Frame-based capacity The total available capacity of the array.

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 157 of 165

Term Description
LAC License Authorization Code. An 11 to 20 character alpha-
numeric code that is associated with an eLicensing-enabled
software order and delivered to the customer as the primary
identifier of his entitlement(s). It is used to locate and
activate licenses via Powerlink Licensing.
A LAC is like a coupon for a license. Each LAC entitles you
to a license, but you must turn the LAC into a license file
(redeeming the coupon) in order to enable your license
capabilities.
When EMC issues new license entitlements to a customer
based on a purchase, evaluation or other event, the
entitlements are associated to a unique LAC.
• At the time a LAC is generated it is usually emailed to
the customer, but this is not always the case for
evaluation licenses or for purchases of certain products.
• RecoverPoint models for a given sales order should all
be on one LAC but there may be multiple LACs on a
sales order based on configurator ordering rules.
• There may be non-RP models on the same LAC.
LAC email License Authorization Code email. An email that is sent to
customers during order processing and fulfillment. The LAC
email contains your software license authorization code
(LAC), and instructions for downloading software binaries
and activating your entitlements.
If you do not have your LAC email, go to EMC Worldwide
Licensing Support at:
https://powerlinklicensing.emc.com/poeticWeb/session/licen
se_request_emc.jsp
Immediately after a RecoverPoint sales order is approved,
a LAC email is automatically sent to the email addresses
provided during order entry. If you do not have your LAC
email and want to activate your RecoverPoint product,
contact EMC Customer Support.
A sales order can contain multiple LACs. In this case, a
separate LAC email is sent for each LAC contained in the
sales order.
License A set of parameters and values recognized by the
RecoverPoint system (unlike a LAC). The RecoverPoint
license describes the licensing model and replication
capabilities purchased by the user.
Users enter LACs into the licensing site at support.emc.com
to generate a license for each LAC. There can be multiple
licenses in one license file but not two license with the
same feature name (See also: Feature). If there are
multiple licenses in a license file, each license instance
starts with the word INCREMENT.
Licenses are added to the RecoverPoint system through
the Getting Started wizard or the Admin > Manage Licenses
screen of Unisphere for RecoverPoint, using the
add_license CLI command.

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 158 of 165

Term Description
License activation An online process by which customers and partners access
Powerlink Licensing to generate license file(s) from their
entitlements. License activation occurs after customers
and/or partners receive a LAC (License Authorization Code)
letter and the LAC number listed on their LAC email is
redeemed.
License file The output of activation used to determine authorization for
software usage. Helps customers manage their compliance
with EMC´s end user license agreement (EULA).
A set of parameters and values recognized by the
RecoverPoint system (unlike a LAC) that contain multiple
licenses but not two license of the same feature.
Note: In a license file, each license instance starts with the
word INCREMENT.
License files are added to the RecoverPoint system through
the Getting Started wizard, or using the add_license CLI
command.
License key A numeric code generated by EMC for a specific customer
license signature used to authenticate a license. A License
key can be installed on a specific RPA (an un-served
license) or a on a license server that manages floating
licenses and counts metrics for certain license models.
The license key generation process takes place after
receipt of the LAC email.
License management A general term to describe all of the processes and systems
used to interface to our customers concerning purchase of
Licensed Products, distribution and activation of License
Keys and Entitlement.
License model One of several EMC approved methodologies of measuring
and controlling the use of software products. Usually, the
license model also correlates to the pricing and packaging
of the software product. It includes metrics which define the
way EMC implements and counts the compliance with the
right to use. Examples of entitlement metrics are capacity,
concurrent user, and so on.
License type Identifies if a product is a base product or an-add-on
product, also called a License Feature.
Licensing site An area of the EMC Online Support web site at
www.support.emc.com, through which users turn their
LACs into licenses.
Local Throughout the documentation, RecoverPoint entities are
prefixed with the word “local” with relation to the
geographical location of the production. For example, a
local copy, local storage, local host, local site, or local RPA
cluster are the copy/storage/site etc. that are local (or in
other words, are situated in the same) geographical
location, as the production. Similarly, “local replication”
means that you are replicating to a copy that is in the same
geographical location as the production.

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 159 of 165

Term Description
Local replication Replaces CDP.
See: Local
Location ID The Site ID used in various EMC global processes. A
unique identifier of the physical location of an RPA cluster.
The Location ID:
• Contains the value of the <Site_Info> parameter that is
generated from the first installed license for an RPA
cluster, see Appendix E: RecoverPoint 4.0 License File
Example on page 148 for the value of <Site_Info>.
• If no license was added for an RPA cluster, the Location
ID of that RPA cluster will be empty.
• Can only be displayed by the user (using the
get_system_settings CLI command), and can only be
modified by EMC Customer Support.
• Does not change even if the <Site_Info> from which it
was generated no longer exists in any of the installed
licenses.
Locking ID To ensure an unambiguous association between the
license and the system, a key attribute of the system is
identified and encoded into the license as the locking ID.
This prevents the license from being inadvertently copied or
moved to other systems and helps the customer maintain
compliance with their license agreement.
In RecoverPoint, the Locking ID is the unique identifier of
the entity that the license is enforced to:
• In RecoverPoint/SE and RecoverPoint/EX, a
VNX/VNX2, VPLEX or Symmetrix array serial number.
The serial number that is registered (and therefore
enabled) for replication.
• In RecoverPoint/CL, an RPA Cluster ID; a unique
identifier of an RPA cluster in a RecoverPoint system.
Machine name A unique name that must be specified for each entitlement.
Machine names can be whatever unique name you choose.
However, the recommendation is to relate it to the Locking
ID.
For example: In RecoverPoint/SE and RecoverPoint/EX,
the Locking ID is an array serial number. Therefore,
machine name=RP-APM00120701240, where
APM00120701240 is the array serial number used for the
Locking ID. In RecoverPoint/CL, the Locking ID is an RPA
Cluster ID, so the machine name should also be an RPA
Cluster ID.
Production The source of replication for a given consistency group.

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 160 of 165

Term Description
Powerlink Licensing EMC’s online customer self-service portal for activation and
administration of eLicensing enabled license entitlements.
Also known as: ELM (Electronic License Management)
The EMC back-office infrastructure supporting EMC’s roll-
out and ongoing support of electronic license management.
The ELMS infrastructure distributes Licensing Authorization
Codes (LACs), a unique code that is associated with the
order and enables customers to redeem them for licenses,
tracks the distribution of licenses, and integrates with sales
order and customer support systems.
Raw capacity The sum of all capacities of all SATA and non-SATA Drives
in the array (RecoverPoint/EX VMAX 10K), excluding
spares. Raw capacity licensing is available on the
Symmetrix VMAX 10K series only, and may be beneficial
for customers who plan to replicate more than
(approximately) 60-70% of their array. It is calculated based
on the number of terabytes of physical drives inside the
array (SATA and non-SATA). With raw capacity licensing,
you always purchase both local and remote replication
(CLR) and you pay according to the array raw capacity,
regardless of how much you actually replicate from the
array.
RecoverPoint model See: License model
RecoverPoint site The geographical location where an RPA cluster is located.
There may be more than one RPA cluster at a site, either
from the same RecoverPoint system or a different
RecoverPoint system.
Important: The term “site”, which was previously used to
refer to a group of RPAs at a specific location, has been
replaced by the term “RPA cluster”.

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 161 of 165

Term Description
RecoverPoint splitter The RecoverPoint splitter is proprietary software that is
installed on storage subsystems, and is built-into the VNX,
Symmetrix, and VPLEX storage systems. The
RecoverPoint splitter is used to access volumes that
contain data to be replicated, and “split” the application
writes so that they are sent to their normally designated
storage volumes and the RecoverPoint appliance
simultaneously.
The splitter carries out this activity efficiently, with little
perceptible impact on host performance, since all CPU-
intensive processing necessary for replication is performed
by the RPA.
The RecoverPoint splitter can be bundled with the VNX's
FLARE or a splitter enabling package, and can be non-
disruptively upgraded.
Multiple splitters can be attached to one RPA cluster. See
the EMC RecoverPoint Release Notes for the limitation on
the maximum number of splitters that can be attached to a
cluster.
Refer to the EMC support matrix on EMC Online Support
for exact support statements including supported OS
versions, and other caveats in supported and unsupported
configurations.
RecoverPoint system All of the RecoverPoint components that are used to
replicate and protect data, at all sites, including all RPA
clusters and RecoverPoint splitters.
Registered capacity The capacity of the array that is actually protected
(protected capacity can be partial) in RecoverPoint/EX.
Registered capacity is the licensed capacity that is
registered for a specified storage array in a RecoverPoint
system, under the RecoverPoint/EX licensing model.
In the RecoverPoint/EX licensing model, each storage array
is licensed per a specified capacity and the full storage
array capacity is not necessarily used or licensed for
replication. Therefore, the capacity is referred to as
registered as opposed to replicated (as in
RecoverPoint/CL).
Remote Throughout the documentation, RecoverPoint entities are
prefixed with the word “remote” with relation to the
geographical location of the production. For example, a
remote copy, remote storage, remote host, remote site, or
remote RPA cluster are the copy/storage/site etc. that are
remote (or in other words, situated in a different)
geographical location, than the production. Similarly,
“remote replication” means that you are replicating to a
copy that is in a different geographical location than the
production.
Remote replication Replaces CRR.
See : Remote

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 162 of 165

Term Description
Replicated capacity The capacity that is protected through an RPA cluster in
RecoverPoint/CL.
In the RecoverPoint/CL licensing model, each RPA Cluster
in the RecoverPoint system is licensed to replicate a
particular amount of data. Therefore, the capacity is
replicated as opposed to registered (as in
RecoverPoint/EX).
RPA The RecoverPoint appliance (RPA) is RecoverPoint's
intelligent data protection appliance. RPAs manage all
aspects of reliable data replication and they can be physical
or virtual (see the EMC RecoverPoint Deploying
RecoverPoint with VMware Technical Notes). RPAs are
used to attain availability. If an RPA fails, another RPA will
pick up the workload.
The RPAs in a RecoverPoint system are connected to each
other through either a Local Area Network (LAN), a Wide
Area Network (WAN), or by Fibre Channel (FC).
Each RPA has the following dedicated interfaces:
• Fibre Channel. Used for data exchange with local host
applications and storage subsystems. The RPA
supports a dual-port configuration to the Fibre Channel,
providing redundant connectivity to the SAN-attached
storage and the hosts.
• WAN. Used to transfer data to other RPAs (Ethernet).
• Management. Used to manage the RecoverPoint
system (Ethernet).
You can access each RPA directly through an SSH
connection to the RPA’s dedicated IP address.
RPA cluster A group of 2-8 physical (or virtual) RPAs at the same
geographic location, that work together to replicate and
protect data are called an RPA cluster. There can be up to
five RPA clusters in a RecoverPoint system. To scale-up
and support a higher throughput rate, you can add
additional RPAs to your RPA clusters.
The number of RPA clusters and the number of RPAs in an
RPA cluster is set during RecoverPoint system deployment
(see the EMC RecoverPoint Installation and Deployment
Guide).
The number of RPAs in an RPA cluster must be the same
at all RPA clusters in a RecoverPoint system. You can
access all RPAs in an RPA cluster through a floating cluster
Management IP address. In other words, once
RecoverPoint is configured, you can manage the entire
installation from a single IP address.
RPA cluster ID A unique identifier of an RPA cluster in the RecoverPoint
system. The ID contains between 1 and 20 alphanumeric
characters. You can find the value by running the
get_internal_cluster_uids command from the RecoverPoint
CLI and providing a cluster name.
Site See: RecoverPoint site

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 163 of 165

Term Description
SSID The Software Serial ID. The unique identifier of an RPA
cluster in the RecoverPoint system. The SSID is the
identification used by the install base to support EMC
equipment installed at customer sites, through the system
reporting and ESRS mechanisms.
Note that the definition of the SSID has changed from
previous RecoverPoint versions.
The SSID is in the format <SN>EID<RPA Cluster ID>, see
Table 4 on page 118 for the value of <SN> and Table 2 on
page 103 for the value of <RPA Cluster ID>. Its length can
be no more than 22 characters, and therefore, the RPA
Cluster ID will be truncated as required.
In RecoverPoint 4.0 and later versions, the SSID:
• Is generated for each RPA cluster when the first license
related to the RPA cluster is added to the system. When
additional licenses are added to the system, the SSID of
the RPA cluster does not change.
• If no license was added for an RPA cluster, the SSID of
that RPA cluster will be empty.
• Can only be displayed by admin users (using the
get_system_settings CLI command), and can only be
modified by SE users.
• Does not change with upgrades. When upgrading to
RecoverPoint 4.0 from previous RecoverPoint versions,
the SSID value is taken from the value of the SSIDs in
the previous RecoverPoint version.
• Does not change even if the SSID SN from which it was
generated no longer exists in any of the installed
licenses.

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 164 of 165

Appendix J: The RecoverPoint Ordering Path
The following table describes where to order RecoverPoint.
Table 10 RecoverPoint ordering paths

Ordering path RecoverPoint/S RecoverPoint/S RecoverPoint/E RecoverPoint/C

E for CLARiiON E for VNX X for EMC L
arrays arrays
RecoverPoint
standalone X6 X7 X
ordering path
VNX ordering
X8
path
VMAX ordering
X9
path
VMAX 10K
X10
ordering path
VMAX 20K
X11
ordering path
VMAX 40K
X12
ordering path
VPLEX
X13
ordering path

Starting Replication
Once RPAs and splitters are installed and configured, you define what you want to replicate and how.
You will need to add splitters, create new consistency groups, create replication sets and define their
volumes, enable the consistency groups and start transfer.

6 Through the upgrade solution path

7 VMAX/VPLEX, by registered capacity; VNX, by frame-based capacity
8 Through VNX suites/packs by frame-based capacity
9 VMAX only by registered capacity
10 VMAX 10K only, by registered and raw capacity. Note that the VMAX 10K ordering path will be updated

in July with RecoverPoint 4.0 models. For RecoverPoint 4.0 registered capacity for VMAX 10K, use to the
RecoverPoint standalone path. For RecoverPoint raw for VMAX10K, order the model as non-ELMS and
open a service request to request license upgrades.
11 VMAX 20K only, by registered capacity
12 VMAX40K only, by registered capacity
13 VPLEX only, by registered capacity

Dell Technologies – Customer’s Internal Use Only – Confidential & Subject to NDA

Page 165 of 165