RecoverPoint 4.4 Release Notes

Release Notes
RecoverPoint
Version 4.4
Release Notes
P/N 302-002-496
REV 06
July 2016
l
l
l
l
l
l
l
l
l
l
Preface...................................................................................................................... 2
Product description....................................................................................................3
New features and changes....................................................................................... 10
Fixed issues............................................................................................................. 12
Environment and system requirements.................................................................... 21
Known issues and limitations.................................................................................. 22
Technical notes........................................................................................................36
Documentation........................................................................................................ 37
Software media, organization, and files................................................................... 37
Installation and upgrade.......................................................................................... 37
Release Notes
Preface
As part of an effort to improve its product lines, EMC periodically releases revisions of its
software and hardware. Therefore, some functions described in this document might not
be supported by all versions of the software or hardware currently in use. The product
release notes provide the most up-to-date information on product features.
Contact your EMC technical support professional if a product does not function properly
or does not function as described in this document.
Note
This document was accurate at publication time. Go to EMC Online Support (https://
support.emc.com) to ensure that you are using the latest revision of this document.
Where to get help
EMC support, product, and licensing information can be obtained as follows:
Product information
For documentation, release notes, software updates, or information about EMC
products, go to EMC Online Support at https://support.emc.com.
Technical support
Go to EMC Online Support and click Service Center. You will see several options for
contacting EMC Technical Support. Note that to open a service request, you must
have a valid support agreement. Contact your EMC sales representative for details
about obtaining a valid support agreement or with questions about your account.
Your comments
Your suggestions will help us continue to improve the accuracy, organization, and overall
quality of the user publications. Send your opinions of this document to
techpubcomments@emc.com.
Revision History
The following table presents the revision history of this document.
Table 1 Revision History
Revision
Date
Description
06
July 2016
Release 4.4.1.1. Added new

feature. Added fixed bugs.
05
April 2016
Release 4.4.1. Added new

features. Added known bugs.
Added fixed bugs.
04
February 2016
Corrected build number. Added

known bug. Edited upgrade
information.
03
January 2016
Release 4.4.0.1. Added known

bugs. Added bug fixes.
02
December 2015
Added upgrade information.

Added known bug. Fixed
documentation bugs.
RecoverPoint 4.4 Release Notes
Release Notes
Table 1 Revision History (continued)
Revision
Date
Description
01
November 2015
First release of RecoverPoint 4.4
Product description
The EMC RecoverPoint product family provides a comprehensive data protection solution
for enterprise and commercial customers, providing integrated continuous data
protection and continuous remote replication to recover applications to any point in time.
RecoverPoint systems enable reliable replication locally with one RPA cluster, and over
any distance to up to four remote RPA clusters. RecoverPoint systems support replication
of data that applications are writing to SAN-attached storage using existing Fibre Channel
(FC) and iSCSI infrastructure to integrate seamlessly with existing host applications and
data storage subsystems. For remote replication, the systems use existing connections to
send the replicated data over FC and WAN, and uses FC and IP infrastructure to replicate
data asynchronously or synchronously. The systems provide failover of operations to
another cluster in the event of a disaster at the production cluster.
The RecoverPoint family consists of three licensing offerings:
l
RecoverPoint/CL for EMC and non-EMC storage platforms.
RecoverPoint/EX for EMC storage platforms (Block), licensed by storage array.
RecoverPoint/SE for XtremIO, Unity/VNXe/VNX series, and CLARiiON CX4 series.
Note
An EMC Simple Support Matrix (ESSM) on E-Lab Navigator https://

elabnavigator.EMC.com serves the RecoverPoint product family. After logging in,
selectData Protection option on the Simple Support Matrices.
This table identifies the build and size of the RecoverPoint ISO image associated with the
4.4 release. The build also appears in the Unisphere for RecoverPoint login screen, in
response to the get_versions CLI command, and in the Installation Manager (boxmgmt)
header.
Table 2 RecoverPoint release, build, and ISO image size
Release Build
ISO image size
4.4.1.1
rel4.4SP1_P1_h.154 1.19 GB
4.4.1
rel4.4SP1_h.138
1.13 GB
4.4.0.1
rel4.4.P1_d.180
1 GB
4.4
rel4.4_d.176
1 GB
Notes on performance
Performance information is provided in the EMC RecoverPoint Performance Guide, available
on EMC Online Support.
Product description
Release Notes
Configuration limits
RecoverPoint is supported on virtual RPA (vRPA) platforms in environments that include
VMware vCenter. For important information about vRPA deployment, best practices, and
limitations, refer to the EMC RecoverPoint vRPA Technical Notes. RPA clusters consisting of
physical RPAs require either a dual fabric or a direct attach network topology.
This table lists RPA hardware supported by the current releases of RecoverPoint. EMC will
continue to support existing configurations of RPA hardware platforms running earlier
versions of RecoverPoint
Table 3 RPA hardware supported by RecoverPoint
RPA hardware
4.4 and later
EMC Europa 1U (Gen6)
Supporteda
Intel R1000 (Gen5)
Supportedb
Dell PowerEdge R610 (Gen4)
Supportedc
Dell PowerEdge 1950 phase 3 (Gen3) or Dell PowerEdge 2950 phase 3 Not supported
Dell PowerEdge 1950 phase 2 (Gen1) or Dell PowerEdge 2950 phase 2 Not supported
Legacy hardware (such as the IBM xSeries 336)
a.
b.
c.
Not supported
All supported RPAs may be mixed in the same cluster. Best practice is to configure the latest
hardware type as RPA 1 and RPA 2 (cluster control RPAs).
Break/fix support
EMC will handle break/fix activity for Gen4, Gen5 and Gen6 RPA hardware platforms
purchased through Direct Express and Channel Express.
SAN support
This table lists Fibre Channel support across RPA hardware types. When using virtual
RPAs, iSCSI is supported in 1 Gb/s and 10 Gb/s network infrastructure.
Table 4 Fibre Channel support across RPA hardware types
RPA
hardware
1 Gb/s
2 Gb/s
4 Gb/s
8 Gb/s
16 Gb/s
Gen4
Not
supported
Supported
Supported
Supported
Not supported
Gen5
Not
supported
Supported
Supported
Supported
Not supported
Gen6
Not
supported
Not
supported
Supported
Supported
Supported
Release Notes
General
The tables in this section present the general configuration limits and scalability limits for
the RecoverPoint system. Unless otherwise stated, RecoverPoint refers to all three
family products (RecoverPoint/CL, RecoverPoint/EX, and RecoverPoint/SE).
Table 5 General configuration limits
Parameter
RecoverPoint 4.4 and later
Supported operating systems
RecoverPoint/CL: Heterogeneous
RecoverPoint/EX: Heterogeneous
RecoverPoint/SE: Heterogeneous with VNX/

CLARiiON splitter and with XtremIO
Refer to the EMC Support Matrix for details.

Supported storage arrays
RecoverPoint/CL: Heterogeneous (EMC and

non-EMC)
RecoverPoint/EX: EMC (block)
RecoverPoint/SE: Unity platform, VNX series,

CLARiiON CX4 series, Celerra unified, and
XtremIO
Refer to the EMC Support Matrix for details.

Supported splitter types
Maximum capacity
Maximum number of arrays
Maximum number of RPA clusters in a

system
Journal compression
RecoverPoint/CL: Symmetrix, VPLEX, and

Unity/VNX/VNXe/CLARiiON
RecoverPoint/EX: Symmetrix, VPLEX,

Unity/VNX/VNXe/CLARiiON, and XtremIO
splitter-less replication
RecoverPoint/SE: Unity/VNX/VNXe/CLARiiON,
and XtremIO splitter-less replication
RecoverPoint/CL: Per license (maximum 2 PB)
RecoverPoint/EX: Per license (maximum 2 PB)
RecoverPoint/SE: 2 PB
RecoverPoint/CL: Unlimited
RecoverPoint/EX: Unlimited
RecoverPoint/SE: One per RPA cluster
RecoverPoint/SE with XtremIO: Multiple arrays

are supported.a
RecoverPoint/CL: 5 (3 for XtremIO)
RecoverPoint/EX: 5 (3 for XtremIO)
RecoverPoint/SE: 2
RecoverPoint/CL: Supported
RecoverPoint/EX: Supported
RecoverPoint/SE: Supported
Release Notes
Table 5 General configuration limits (continued)
Parameter
Maximum number of open RecoverPoint CLI

connections per RPA cluster
100
Maximum number of open RecoverPoint CLI

connections being set up concurrently
12
Maximum number of concurrent

RecoverPoint GUI sessions per RPA cluster
20
Minimum Adobe Flash Player for

RecoverPoint GUI
Minimum supported web browser for
RecoverPoint GUI
10.2
Internet Explorer 9.0
Mozilla Firefox 3.0
Google Chrome 2.0
Safari for Mac 5.0
Minimum supported screen (display)

resolution for RecoverPoint GUI
1024x768
Number of RPAs in a cluster
2-8
Maximum number of SAN entities (WWNs)

seen by an RPA
256
Maximum number of paths per RPAb
200K
Recommended minimum repository volume

size
2.86 GB
Minimum journal size
10 GB (non-distributed consistency group)
40 GB (distributed consistency group)
Maximum journal sizec
1.0910.00 TB
Maximum number of distributed

consistency groups
Maximum number of journal volumes per

consistency group copy
128
RPA MTU packet size
1,000 - 9,000 bytes for IPv4
1,280 - 9,000 bytes for IPv6
Maximum size of replicated LUNs
32 TB
In virtual access, maximum offset of image

in journal
1.2 TB
In virtual access, maximum writes per RPA
40 GB
Maximum number of consistency groups in

system
128 (not recommended to configure more than 64

per RPA)d
Maximum number of copies per consistency 5 (includes production copy)

group
Release Notes
Parameter
Maximum number of local copies per

consistency group
2 (includes production copy)
Maximum number of copies for a

consistency group with a single remote RPA
cluster
Total of 3 copies (not including production),

including:
l
1 local copy
2 remote copies (on the same cluster)
RecoverPoint/SE supports one remote copy.

Maximum number of consistency groups in
group set
Maximum number of replicated production
volumes in system
Maximum number of replication sets per
consistency group
32 (with parallel bookmarking)
128 (without parallel bookmarking)
8192 (when using physical RPAs)
2048 (when using virtual RPAs)
8192 (when using physical RPAs)
2048 (when using virtual RPAs)
Maximum number of production and nonproduction replication volumes per system
16384
Maximum number of ESX servers in

discovery per RPA cluster
100e
Total number of LUNs that are visible to ESX 2048f

servers per RPA cluster
Total number of VMs that are visible to ESX
servers per RPA cluster
3000 g
Maximum number of vCenter servers in

discovery per RPA cluster
4h
Minimum bandwidth for replication
3 Mb/s
Asynchronous replication over FC distance

limit
Per topology as supported by eLab
Asynchronous replication over IP latency

and packet loss limitsi
Latency of 200 ms, with packet loss of 1%
Note: Latency values are full round trip time.
Synchronous replication over FC distance

limit
200 km (full round trip)
Synchronous replication over FC latency

limit
4 ms (full round trip time)
Synchronous replication over IP latency and 10 ms (full round trip time)

packet loss limits
Packet loss: 1%
Maximum number of synchronous
replication links per consistency group
1 local (FC)
1 remote (FC or IP)
Release Notes
Parameter
Stretch cluster distance limit (on the stretch 30 km

side)
a.
b.
c.
The SE (Basic) license with XtremIO supports multiple arrays as per the XtremIO splitter
limitations.
Where path is a LUN WWN seen by an RPA port. The same LUN WWN seen from different RPA
ports is counted multiple times.
The maximum journal size is three times the initial journal size, subject to the following
exceptions:
l
If three times the initial journal size is less than 1.09 TB, then use 1.09 TB as the max
journal size.
If three times the initial journal size is greater than 1.09 TB, then use 10.00 TB as the max
journal size.
A single RPA cannot be configured to have more than 64 consistency groups. However, in the
event of RPA failure, groups on one RPA will move to other RPAs in the cluster. In such a case,
an RPA can temporarily hold up to 128 groups, and the data of all the groups will continue to
be transferred between clusters. This state is temporary, however, as an RPA with more than 64
groups may run into high loads, and you may not be able to meet your group policies.
Relevant only to vCenter discovery in RecoverPoint and does not affect replication.
A single RPA cannot be configured to have more than 64 consistency groups. However, in the
event of RPA failure, groups on one RPA will move to other RPAs in the cluster. In such a case,
an RPA can temporarily hold up to 128 groups, and the data of all the groups will continue to
be transferred between clusters. This state is temporary, however, as an RPA with more than 64
groups may run into high loads, and you may not be able to meet your group policies.
RecoverPoint performance and ability to meet replication policies cannot be guaranteed if WAN
latency or packet loss exceeds the stated limit.
l
d.
e.
f.
g.
h.
i.
Scalability
VNX/CLARiiON scalability
Table 6 VNX/CLARiiON scalability limits
Parameter
Maximum number of attached
LUNs per splitter
Maximum number of RPA clusters

connected to splitter
Maximum number of splitters per

RPA cluster
Limit
l
2K when using VNX OE for Block 05.32.000.5.201 or

earlier
8K when using VNX OE for Block later than

05.32.000.5.201
4 when using VNX OE for Block 05.32.000.5.201 or

earlier
6 when using VNX OE for Block later than

05.32.000.5.201
Release Notes
VNXe scalability
Table 7 VNXe scalability limits
Parameter
Limit
Maximum number of attached LUNs per splitter
500
Maximum number of RPA clusters connected to splitter 1

Maximum number of splitters per RPA cluster
10
Symmetrix scalability
Table 8 Symmetrix scalability limits
Parameter
Limit
4096 in VMAX 10K, 20K, 40K arrays
Maximum number of RPA clusters connected to splitter 6

VPLEX scalability
Table 9 VPLEX scalability limits
Parameter
Limit
2K when using GeoSynchrony 5.1
8K when using GeoSynchrony 5.2 and later
4 when using GeoSynchrony 5.1
6 when using GeoSynchrony 5.2 and later
Maximum number of RPA clusters connected to

splitter
10
Maximum number of directors for VPLEX Local
Maximum number of directors for VPLEX Metro
16
XtremIO scalability
Table 10 XtremIO scalability limits
Parameter
Limit
Maximum number of volumes in a consistency group
256
Maximum number of replicated consistency groups per array
128
Maximum number of snapshots per array (when number of volumes is at maximum) 8000
Max number of replicated volumes for:
l
a single XtremIO array connected to one or more RPA clusters
a single RPA cluster connected to one or more XtremIO arrays
500
Release Notes
Table 10 XtremIO scalability limits (continued)
Parameter
Limit
Maximum number of RecoverPoint clusters supported by array
Maximum number of arrays which can be replicated by a RecoverPoint cluster
Number of XtremIO snapshot sets per consistency group on target
500
Splitter interoperability
RecoverPoint/CL and RecoverPoint/EX support the mixing of Unity/VNXe/VNX/CLARiiON,
Symmetrix, and VPLEX splitters between different RPA clusters and within the same RPA
cluster. A consistency group copy can span both Symmetrix and VNX/VNXe/CLARiiON
splitters, but not VPLEX splitters. For XtremIO platforms, RecoverPoint supports
replicating from XtremIO to XtremIO, from XtremIO to other arrays, and from other arrays
to XtremIO.
New features and changes

This section lists new features and changes supported in RecoverPoint 4.4 and later.
New features and changes for release 4.4.1.1

This section lists new features and changes in RecoverPoint 4.4.1.1.
Enhanced recovery with XtremIO
The behavior during an XtremIO HA event has been enhanced to allow faster
recovery and to give the production workload higher priority over the replication
process. During the HA event, if the RPO of one or more RecoverPoint Consistency
Group Copies is less than 10 minutes, then that RPO is automatically lengthened to
10 minutes, as long as the metadata prefetch process is in progress.
New features and changes for release 4.4.1

This section lists new features and changes in RecoverPoint 4.4.1.
Gen6 support
The Gen6 RecoverPoint appliance supports all of the functionality supported by the
Gen5 appliance. Gen6 appliances support:
l
Improved system performance
Flexible configuration of I/O modules
10 Gb Ethernet environments
Customer replacement of disk drives and power supplies
Unity Support
RecoverPoint now supports the Unity Midrange platforms.
Online help
Online help has been added for ProtectPoint users. ProtectPoint users can now
select Help > ProtectPoint for XtremIO Help to open the ProtectPoint help. Clicking
10
Release Notes
the help icon of a specific GUI element while a group with a Data Domain copy is
selected will display the ProtectPoint-specific help.
Java 8
RecoverPoint Appliances now run on Java 8.
CCA.xml download page
System installations and upgrades for customers without Internet connectivity are
simplified now that the customer can download the Installation Change
Management XML file.
Axxana end of service life
As of RecoverPoint 4.4.1, the Axxana Phoenix system is not supported.

This section lists new features and changes in RecoverPoint 4.4.0.1.
There are no new features in this release.
Table 13 on page 18 lists the issues fixed in this release.
New features and changes for release 4.4

This section lists new features and changes in RecoverPoint 4.4.
ProtectPoint 3.0 readiness
RecoverPoint now contains the infrastructure required to support ProtectPoint 3.0
when it becomes generally available. This readiness enables ProtectPoint 3.0 to
support the protection of data located on XtremIO arrays. See the ProtectPoint 3.0
Solutions Guide and the ProtectPoint 3.0 Primary and Protection Storage Configuration
Guide when they become available for more information on the RecoverPoint
integration in ProtectPoint.
Volumes can be added to groups without journal loss
When adding replication sets to an existing consistency group, the journal history is
retained.
New security features
RecoverPoint 4.4 introduces new security features:
Key management
Random SSH keys are generated during a new RecoverPoint installation and
regenerated every time the regenerate_encryption_keys command is
run.
Authentication secrets management
During RecoverPoint installation, you will be prompted for the local users'
security level. There is no default value. When Security Level is set to High,
passwords of predefined users (admin, security-admin, and boxmgmt) must be
changed immediately. LDAP authentication is not affected.
Session inactivity timeout
By default, a RecoverPoint GUI session will time out after 10 minutes. After
timeout, user will need to log on with password to access GUI again. Session
timeout can be changed by user with security role privilege.
11
Release Notes
IPv6
RecoverPoint 4.4 has been qualified for use with IPv6 addressing. IPv6 is supported
for all endpoints on the LAN, the WAN, gateways, subnets, VNX arrays, CX4 arrays,
and XtremIO arrays.
EMC WAN Optimization Components (EWOC)
EWOC is not supported in RecoverPoint 4.4. If EWOC was enabled in a RecoverPoint
version prior to 4.4, it will be automatically disabled during upgrade to RecoverPoint
4.4.
Multiple array support for XtremIO
The RecoverPoint/SE license now supports multiple XtremIO arrays per cluster.
Allow RecoverPoint to Manage Volume Access
Since XtremIO replica volumes are not managed by a RecoverPoint splitter, they are
normally accessible, even when image access is disabled. External hosts accessing
replica volumes can cause data corruption. From XtremIO 4.0.2 and later,
RecoverPoint manages the access state of these volumes, and blocks write access to
hosts, unless the volumes are in Image Access mode.
Auto-registration enhancements
Many enhancements have been added to the RecoverPoint automatic registration
mechanism. Among them, a call home event is now automatically sent to the EMC IB
group whenever a cluster removed from or added to the system, and whenever a
change is made to one of the details in the registration form.
Improvements in system feedback during image access
When accessing, failing over to, or recovering production from an image to a point in
time that does not contain all of the replication sets that exist at the current point in
time, new messages (and alerts) are now displayed to help users better understand
the implications of image access.
Fixed issues
Table 11 on page 12 lists the issues fixed in RecoverPoint 4.4.1.1.
Table 12 on page 13 lists the issues fixed in RecoverPoint 4.4.1.
Table 13 on page 18 lists the issues fixed in RecoverPoint 4.4.0.1.
Table 14 on page 18 lists the issues fixed in RecoverPoint 4.4.
Issues fixed in RecoverPoint 4.4.1.1

Table 11 Issues fixed in RecoverPoint 4.4.1.1
Issue number
Product Feature
Problem summary
129289
Deduplication
When deduplication is enabled and compression is set to high, an RPA may

reboot resulting in a short initialization.
130480
Disk Manager
A faulty second hard drive might result in RPA failure.
129612
Gen6
Fixed Gen 6 RPA performance issue.
130899
ProtectPoint
If you want to register a Data Domain array which runs on Data Domain
Operating System 6.0, you must first upgrade the RPs to version 4.4.1.1.
12
Release Notes
Table 11 Issues fixed in RecoverPoint 4.4.1.1 (continued)
Issue number
Product Feature
Problem summary
130953
Replication
Inconsistency found due to a race condition between new I/O and initialized
I/O.
129598
Security
Possible security vulnerability
129674
Security
129863
Security
130402
Security
131084
Security
131486
Security
131515
Security
129874
Upgrading
In RecoverPoint 4.4.1, meta devices are not visible by the RPAs and consistency
groups enter a state of Error.
130903
vRPA
Fixed vRPA performance issue.
129202
XtremIO
If the XtremIO array has a high availability (HA) problem, replication may stop
for around 40 minutes.
130362
XtremIO
Old snapshots that were created due to a "failure of init" or a "user bookmark"
are not removed from the XtremIO production array when there are multiple
links from the production array to the replica array (local or remote).
130431
XtremIO
When a very large amount of diff intervals (more than 2M) occur in a single
Recover Production operation, inconsistencies may occur.
130731
XtremIO
Changed the behavior to reduce the snapshot frequency in RecoverPoint after

the XtremIO array in Production encounters an HA event. Snapshot frequency
will return to its original configuration after the XtremIO array has fully
recovered from the event.
130756
XtremIO
There is an inconsistency between the production and replica XtremIO copies

after adding a volume to the replica XtremIO copy if a link to this copy is not
configured in Snapshot Based Replication mode.
Issues fixed in RecoverPoint 4.4.1

Table 12 Issues fixed in RecoverPoint 4.4.1
Issue number
Product Feature
Problem summary
126179
CLI
You may not be able to failover a group set using the CLI.
123342
VPLEX
When a copy is in virtual access mode, the splitter and firmware may crash on
all hosts in the cluster.
123171
Events
Event IDs may display the incorrect event message.
36574
VNX
Punch commands may not be replicated to the disaster recovery site, and
therefore un-used blocks will not be reclaimed.
13
Release Notes
Table 12 Issues fixed in RecoverPoint 4.4.1 (continued)
Issue number
Product Feature
Problem summary
128897
VNX RecoverPoint/SE
The /var directory maybe full, causing boxmgmt to crash. You may not be able
to log into the RPA withuser SE.
125971
CLI
The CLI command get_group_statistics may return the incorrect link

state.
124280
Credentials
You may not be able to edit you boxmgmt password, role or groups from GUI &
CLI.
124438 (124532)
Data Domain
RecoverPoint replication process stops functioning when recovering production

using a copy on a Data Domain system.
36173
GUI
After changing the language of the GUI, the GUI texts may not display in the new
language.
125105
GUI
The GUI may not display the vCenter servers. The CLI may display vCenter
servers that are no long relevant.
123054
IPv6
When using IPv6, the RPA cannot send syslog messages.
128467
KVSS
KVSS will always fail with the following error: Due to: HTTP/1.1 404
Not Found Could not connect to given RPA .
127790
NDU
Upgrading from RecoverPoint/CE 4.1.x to RecoverPoint 4.4 may fail.
121237
NDU
Performing an Non-disruptive upgrade to RecoverPoint 4.4 may fail with the

following error: Failed to save the current setup
settings.
127092
NDU with VNX splitter
When upgrading to RecoverPoint 4.1.2.3, the Deployment Manager may freeze,

and the RPAs may enter reboot regulation.
128344
ProtectPoint
If the Fibre Channel connection between the RPA and the Data Domain array is
disconnected for an extended period of time, the control process may crash.
123927
ProtectPoint
In ProtectPoint, when creating a Data Domain group, if the user clicks the Edit
Replication Set link, the Edit Replication Set dialog box displays an Attach as
Clean checkbox, although this option is not supported for Data Domain groups.
124551
ProtectPoint
You may not be able to change the Data Domain connection from Fibre Channel
to IP connection or from IP connection to Fibre Channel.
124549
ProtectPoint
Adding a replication set to a consistency group with a Data Domain

immediately after changing the Data Domain connection from Fibre Channel to
IP connection may cause replication to be paused by system.
123843
ProtectPoint
If connectivity is lost between the local RPA cluster and a Data Domain copy
during replication, transfer is paused for 20 minutes and a short initialization
occurs when transfer re-starts to synchronize the group copies with their
production sources .
121886
ProtectPoint
In the GUI and the CLI, when registering a Data Domain, Data Domains are not
displayed in the list of available arrays, even if they have been zoned and
masked to the RPA cluster.
124417
ProtectPoint
When using the CLI to create a consistency group with Data Domains, even if
you do not enable the consistency group the BK license volume capacity will be
consumed.
14
Release Notes
Issue number
Product Feature
Problem summary
123918
ProtectPoint
If a Data Domain vDisk service is disabled, although the connectivity status

continues to appear valid, some vDisk operations may fail.
123816
ProtectPoint
Your first attempt at registering a Data Domain over Fibre Channel may fail with
the following error message: Failed to connect to the
specified array or vCenter Server. Check

credentials and connectivity and try again.
123645
123904
ProtectPoint
In rare cases, when replicating to, or recovering production from a Data Domain,
the "Internal process restarted" event may be logged and a short initialization
of some consistency groups may occur.
122909
ProtectPoint
In ProtectPoint, you cannot recover production to a snapshot created before

replication sets were added.
123952
ProtectPoint
Recovering production from Data Domains will cause a full sweep.
125013
ProtectPoint
When a large number, or rarely, a small number of consistency groups are on

one Data Domain, replication may be paused by system.
126302
ProtectPoint
On a Data Domain, when testing a copy of all consistency groups in a group set,
if you select a specific snapshot, only one consistency group will access the
correct snapshot. The other consistency groups will access an incorrect
snapshot. Workaround: N/A
126610
REST API
If you call the REST command addGroupAnd Copies() (or SOAP commands
addConsistencyGroupAndCopies and validateAddConsistencyGroupAndCopies)
in a FAPI version earlier than 4.4, the command will fail.
126506
RecoverPoint/SE
When upgrading a RecoverPoint/SE environment from 4.1.2 or earlier to 4.4.x, if

you previously upgraded from 4.0.x to 4.1.2 or earlier, communication with the
VNX splitter may fail.
128573
SRM
The Site Recovery Manager (SRM) fails in RecoverPoint configurations with VNX
and XtremIO storage, when consistency groups are configured to replicate in
snap-based replication mode.
127524
Security
A stack-based buffer overflow was found in the glibc library (CVE-2015-7547). A

remote attacker could, theoretically exploit this vulnerability to execute code
with the permissions of the user running the library. The vulnerable library has
been replaced.
123965
Security levels
SSH connections may be lost when changing the security level of an RPA.
125174
Symmetrix
The splitter may crash repeatedly, causing the it to be uncontrollable.
128984
System
The auth.log file causes the /var directory to fill up, resulting in problems with
login and boxmgmt function.
128801
System
Selecting an image to access using the advanced search function may take up
to ten minutes.
128842
System
Snapshot consolidation fails, and the user is unable to access desired images
by specifying a time or bookmark name to search in the advanced search
options.
123981
15
Release Notes
Issue number
Product Feature
Problem summary
122380
System
If the message WARNING: Snap based replication for group
{consistency_group_id} is allocating resources on

storage. Links {source_name} > {target_name} will
stay paused until this stage is completed. and
replication is paused or consistency group creation fails, contact EMC Customer
Service.
118756
System
After installing the ISO, the RPA may enter a reboot regulation and cannot be
attached to the cluster.
119162
System
In rare cases consistency group transfer status may be paused by system.
121383
System
The GUI and CLI may be slow or unresponsive.
123776
System
When adding volumes to a consistency group during the initialization, there

may be journal loss and a full sweep.
126243
System
If you have not defined a primary or secondary DNS, you may not be able to
modify settings.
124465
System
In a multi-cluster environment, after enabling or disabling image access, you

may experience a setting conflict.
124673
System
Arrays that were registered in a cluster will be lost after formatting a repository
volume on that cluster. Consistency groups on the affected arrays will be
paused by system. You must re-register any arrays that were lost.
124445
System
If a consistency group contains a larger number of volumes, creating

bookmarks may fail with no error or warning message.
124795
System
You will not be able to recover production from XtremIO to an array with snapbased replication disabled. You will receive the following error: Error:
Cannot use copy with XtremIO volume(s) as source

copy when snap-based replication is disabled.
Enable snap-based replication in the group's link
policy.
124038
System
After enabling image access on a specific copy, you will not be able to disable
image access if you detached the copy from splitter via the GUI.
120579
System
You may not be able to add a new RPA cluster to the system with a Fibre
Channel connection. You will receive the following error: Unable to
execute command. Contact customer support.

41164
System
You may not be able to enable image access on an old image; the GUI reports
No access, space full during image access. The recovery activities
show journal capacity at 100%.
125779
System
When running config_io_throttling, if you run save_settings to

save all settings, you may receive the following error: Error: Maximum
custom value is 9999.

127623
System
You may not be able to convert a consistency group to a distributed consistency

group.
127578
System
You may not be able to use a VMAX3 device as a journal.
16
Release Notes
Issue number
Product Feature
Problem summary
127355
System
After resizing a volume in a replication set, recovering production to point-intime before the volume was resized may cause all non-production copies to
enter error state.
123436
System
If, in a RecoverPoint version earlier than 4.1, a journal volume was bigger than
10TB, after upgrading to 4.1 or later, replication may stop or a fatal error may
occur.
126392
System
In rare cases, the system will show that a bookmark was created but the
bookmark will not replicate to the non-production copy. The bookmark will be
cancelled on both production and non-production copies without notification.
122976
Unisphere for RecoverPoint/

Getting Started Wizard
After a session time out, any pop-up still open from the previous session
appears behind the new session log-in. It is possible to modify the pop-ups
from the session before the time out.
122571
41327, 41742,
42404, 44062,
116747, 119049,
119434, 122037,
123393, 125148,
127093
VNX
In rare cases, after a lot of IO cancellations, the storage processors may reboot
repeatedly, causing the splitter will fail.
36574
VNX
127883
VPLEX
In a system with 4.1.x and 4.4.x version co-existence, creating a new

consistency group in the 4.1.x cluster always cause a settings conflict. If
consistency groups existed before upgrading to 4.4.x, a conflict may occur the
first times settings are changed after the upgrade.
123498,
125049
XtremIO
When migrating an XtremIO cluster from one XMS to another, replication may be
paused by system.
Workaround: In the cluster where registration was edited, restart the RPAs
sequentially.
123099
XtremIO
Replicating XtremIO may fail with SCSI error when host applies SCSI-3
reservation to production volumes. When upgrading from a version with this
bug to a version without this bug, change the preferred RPA after the upgrade,
to clear the error. It that does not help, disable and then enable the relevant
consistency group.
123227
XtremIO
When configuring the protection window for XtremIO copies to more than 28
days, you will receive the following error: Error: Minimum value for
protection_window parameter in XtremIO copy is 2

hours and maximal value is 1 month.
Workaround: Contact EMC Customer Support to increase the maximum
protection window to 30 days.
125289
XtremIO
Creating a consistency group containing an XtremIO volume with SCSI-2

reservation will fail. The size of the reserved volume will be reported as 0.
17
Release Notes
Issue number
Product Feature
Problem summary
Note
This is scheduled to be fixed in an upcoming XtremIO release; refer to XtremIO

documentation for latest updates.
123369
boxmgmt
Using boxmgmt on cluster control to change the iSCSI IP addresses of multiple

vRPAs in the cluster may fail.
Workaround: Use boxmgmt on each vRPA separately to change the iSCSI IP
address.
117061
boxmgmt
After changing the web server mode in boxmgmt (Setup > Advaced options >
Security options > Change web server mode) the web server automatically
restarts with a false error message Connection to server failed
even though the change was applied.
As of RecoverPoint 4.4.1, there will be a delay after changing the HTTP mode.
The following message will be displayed before the user performed the action:
Do you want to enable/disable the HTTP server?

Please note that this operation takes
approximately 1 minute.
Issues fixed in RecoverPoint 4.4.0.1

Table 13 Issues fixed in RecoverPoint 4.4.0.1
Issue number Problem summary

124796
When the XtremIO Management Server (XMS) is not responsive, the RPA tries to regain connectivity by repeatedly
sending messages to the XMS. These tries may consume substantial RPA resources and may delay requests to the
SYM, causing replication to pause. This may affect consistency groups not related to the specific non-responsive
XMS.
125411
After upgrading to RecoverPoint 4.4, you will not have keyboard, video and mouse control.
126243
System If you have not defined a primary or secondary DNS, you may not be able to modify settings.
Issues fixed in RecoverPoint 4.4

Table 14 Issues fixed in RecoverPoint 4.4
Issue
number
Description
116555
When all VPLEX directors but one are dead, replication is paused and all links move to paused by system.
117957
In the rare case that an XtremIO copy uses almost all of the physical capacity available and the copy is very different
from production, a full sweep or initialization snapshot may appear to be larger than the capacity of the copy. This is
according to design.
18
Release Notes
Table 14 Issues fixed in RecoverPoint 4.4 (continued)
Issue
number
Description
118580
When creating a consistency group, volumes do not automatically attach to the splitter and cannot be attached
using the GUI.
119258
The systems events table updates with the newest event at the top of the table. If you have scrolled down in the
table to view an older event, the table will jump back to the top each time a new event is recorded.
119321
Using the CLI to enable image access and search for a point in time image may take up to ~12 minutes.
119766
In rare cases, replication of the RPAs containing replica copies is unresponsive for up to 20 minutes. The likelihood
of this bug increases in image access mode or during TSP write.
119800
You may not be able to edit link policy templates. You will receive one of the following errors: MgmtAction:
setPolicyTemplates() Local Link Policy returning: Error: Received policy

templates which do not contain the default template. MgmtAction:
setPolicyTemplates() Remote Link Policy returning: Error: Received policy
templates which do not contain the default template.
119949
After a fatal journal error, it is possible that the RPA will enter reboot regulation. In this case, the only solution is to
disable the consistency group and then to enable it again. This will cause a full sweep, but after the full sweep,
replication should continue normally, and the copy should be fully synchronized with the source.
120336
After restarting the primary vRPA, you may receive the following error: RPA1 in Cluster1 can't access
repository volume.
120408
In a Symmetrix environment, when the link policy is set to synchronous mode, during failover the link may become
stuck in ready state. You will receive the following message: Group <groupname> Running on Mismatched RPAs.
120575
After a long initialization, if more data is received than the vRPA can handle replication will be paused by system.
When replication resumes there will be a short initialization.
120667
In rare cases, after an initialization of more than one consistency group, the replication process may be paused by
system.
120672
Failing over and setting production to the remote copy on a grid consistency group with at least three links you may
result in a fatal error and journal corruption.
121017
If, during a long resynchronization, an RPA restarts, this may cause a full sweep of the consistency group. After the
full sweep, the system should recover without errors.
121388
During an upgrade, in the Manage Protection screen, consistency groups may be displayed as disabled, when really
they are in error state.
121494
After the first successful recover production on an array with snap based replication is performed, all further
attempts to recover production will fail. There will be no warning or error message displayed.
121770
You may not be able to convert the RecoverPoint system from RecoverPoint/EX to RecoverPoint/SE.
122232
If transfer is paused during the initialization of a synchronous replication link, the system may restart the entire
initialization 0%.
122274
After recovering production and unselecting start replication to all copies in groups after recovery in the GUI,
or answering no to Do you want to begin data transfer from the new source copy in CLI, the consistency group
status is paused by system. You will not be able to begin transfer.
122576
When attempting to remove a replication set from a consistency group, where the replication set contains a volume
that cannot be seen by RecoverPoint, the consistency group will enter an error state and replication will be paused
by system.
Issues fixed in RecoverPoint 4.4
19
Release Notes
Table 14 Issues fixed in RecoverPoint 4.4 (continued)
Issue
number
Description
123438
All consistency groups in a preferred RPA may enter reboot regulation.
30367
When creating an LDAP type user, the new user cannot be limited to a specified consistency group.
35292
When running Gen4 or Gen5 RPAs in a scaled environment, user may encounter memory problems, indicated by
event Internal process restart.
35614
When loading and saving settings for one cluster group, you may receive and error message "Settings context
obsolete." This happens when there is an automatic settings change on another cluster between the loading and
saving of the initial cluster, causing your new settings to be obsolete.
37076
Loading system settings may fail with this error: Error: Cannot commit action. System is
currently committing some other action. Please try again later. Some of the
system settings may be updated. This issue is rare, but is more likely to occur in scaled environments with many
consistency groups and many volumes.
37227
When deduplication is enabled and compression is set to high on all RPAs, you may experience a short initialization
after rebooting an RPA.
37494
GEN5 RPA does not boot up due to BIOS misconfiguration.
40235
You cannot remove a link between two clusters as long as a consistency group copy on that cluster is linked to a
copy of the same consistency group on any other cluster.
41401
After the security level is set to high using the CLI command set_security_level, you try to log in to the GUI. A
dialog box appears forcing you to change your password to comply with the high-level password requirements. After
performing the password change, the GUI is stuck on the login screen.
43797
When you change the link policy on a protected consistency group through the GUI, and you select Synchronous Dynamic by Latency, you cannot manually enter the number of milliseconds for start async replication above and
start sync replication below if the required number of milliseconds contains a decimal point. When you scroll
through the numbers to select the required number of milliseconds and click apply, the system automatically
rounds the numbers.
43914
When using journal provisioning, you select a resource pool and change its parameters. The system switches the
selected resource pool to the default resource pool.
44201
After upgrading the RecoverPoint system from 4.0 to 4.1, CLI commands performed on existing consistency groups
or copies with a space in their name will fail. Workaround: Rename the consistency group or copy, removing the
empty space.
44230
When running a VNX-only environment, the storage process may crash periodically.
44323
After removing VPLEX Metro volumes from one RPA cluster, the GUI still displays the MetroPoint group checkbox
when creating or editing a consistency group.
44328
When replicating to a VNX array later than R32.MR1SP4 and snapshot enabler is not installed on the array, a
consistency group that is configured with snap-based replication will be in error state. This will pause replication.
Workaround: Disable snap-based replication policy on the consistency group. Go back to asynchronous replication
policy.
44657
When the RPA communication security level is set to Authenticated or to Authenticated and Encrypted ,
RecoverPoint's WAN limitation is ignored and RecoverPoint may use up all of the customer's bandwidth.
20
Release Notes
Environment and system requirements

Description
Requirements
EMC RecoverPoint
4.4.1
RecoverPoint Appliance Hardware Gen4, Gen5 or Gen6

Network Infrastructure
Fibre Channel, LAN, WAN
Software Infrastructure
Java 8 update 72. It is highly recommended to have the latest

Java 8 update installed.
End of service dates and extended support

EMC has a standard software support duration policy which specifies that a major version
will reach End of Service Life (EOSL) a minimum of 36 months following the General
Availability (GA). EOSL may be followed by an Extended Support period during which
customers may elect to pay an additional fee to extend their support coverage rather than
migrate to a current software version.
Once a software product reaches EOSL, EMC Technical Support is no longer available
under base support/maintenance agreements. Customers interested in uninterrupted
support must upgrade to a current release or contract for Extended Support.
EMC Online Support site contains a list of documents that provide end-of-service and
extended support information for EMC software and hardware products.
To access these documents on EMC Online Support:
Procedure
1. To access these documents on EMC Online Support:
1. Go to EMC Online Support, at http://support.emc.com.
2. Go to Support by Product pages and search for RecoverPoint.
3. In the product page, scroll down the left and click Release and End of Life Dates.
4. Find the EMC Software Release and End of Service Life Notifications document in the
results. This document provides EOSL dates for EMC software products.
5. Open the document and search for your product and version.
Results
This policy is in effect for select releases and will be phased in as new versions are made
available. In cases where a software release is not eligible for Extended Support, the
previous policy, which specifies product support and maintenance under Continuous
Coverage Product Maintenance (CCPM), terms still apply.
Environment and system requirements
21
Release Notes
Known issues and limitations

This section lists the limitations and known problems in the current RecoverPoint release.
All information regarding interoperability limitations is available on E-Lab Navigator.
Limitations
RecoverPoint 4.4 releases have the following limitations:
22
For a full list of snap-based replication limitations, see the EMC RecoverPoint 4.4
Administrators Guide.
The VPLEX splitter supports fake sizingthat is, that a volume attached to the
VPLEX splitter at a copy does not need to be exactly the same size as its
corresponding volume at productionwhen using GeoSynchrony 5.2 or later, but not
when using GeoSynchrony 5.1.
All RPA clusters in a system must have the same number of RPAs.
Virtual RPAs can be deployed with Unity, VNXe or VNX storage only.
To remove and disconnect an RPA cluster, you must use Installation Manager
(boxmgmt).
Gen6 (Europa 1U) RPAs support BMC and Phobos. Gen5 (Intel) RPAs support BMC
and RMM4. Gen4 RPAs support Dell iDRAC, OMSA, and the Dell MIB.
When setting a consistency group as distributed, the capacity of the group's copy
journals should not be less than the minimum journal size required for distributed
groups. Adding journal volumes for such groups necessitates a disabling and reenabling of the consistency group, which causes a full sweep.
There is a small improvement in performance when a distributed group is run on

three RPAs. A steep improvement in performance is experienced when the group is
run on four RPAs.
All IP addresses in the RecoverPoint system (that is, RPA, Management (LAN), and
WAN/Private IP addresses) must be unique within the RecoverPoint system, even if
they are not on the same subnet and there is no routing between them.
To avoid damage to data when changing the configuration (LUN mapping, LUN
number or GUID, or storage group) of any LUN that has been exposed to
RecoverPoint, follow the procedures in the EMC RecoverPoint Changing LUN Mapping
Technical Notes.
The RecoverPoint multi-WWN (virtual ports) feature requires that the fabric switch
supports arbitrated loop capability.
RecoverPoint is supported in environments that utilize VLAN tagging (802.1q). RPAs

do not tag the traffic that they send.
RecoverPoint is not supported in environments that utilize IP L2 prioritization

(802.1p).
RecoverPoint is not supported in environments that utilize Differentiated Services

Code Point (DSCP) Quality of Service (QoS).
RecoverPoint does not support Network Address Translation (NAT) between RPAs.
RPAs require that each other RPA in the system be accessible using the configured IP
addresses.
Network Address Translation (NAT) is not supported between the machine that runs
Unisphere for RecoverPoint and the RPAs.
Release Notes
In a RecoverPoint environment with Windows Server 2003 Enterprise running

Exchange 2007 Cluster Continuous Replication with Majority Node Set Quorum,
RecoverPoint VSS utilities (KVSS) will fail to install due to a known MSDTC limitation
in a non-shared Quorum configuration (MNS). This limitation is resolved in Windows
Server 2008 and later releases.
The number of snapshots that can be taken is unlimited. However, when selecting an
image from the list in the Enable Image Access dialog box (RecoverPoint GUI), 1013
snapshots (images) are displayed.
RecoverPoint volumesrepository, journal, and replicationshould not be

configured on CLARiiON CX4 disk drives with FLARE 29 or later installed that have
spin-down capability.
Normally, RecoverPoint will prevent volumes protected by RecoverPoint from spinning
down; however, if a volume does spin down, an error will be raised until the volume
spins up again.
It is recommended to run only a single consistency group in virtual image access

mode using the same RPA.
RecoverPoint does not currently support WAN accelerators, unless the device is
specifically supported in the EMC Support Matrix with RecoverPoint. EMC is aware of
configurations in which performance is degraded when using WAN accelerators in
conjunction with RecoverPoint, such as when enabling compression on both
RecoverPoint and the WAN accelerator.
When replicating a Microsoft VSS image, attempting to access an image on the targetside image when there is an MSCS cluster at the target side, and the replication
volumes are resources in the target cluster, the replicated disk on the target side will
not be visible to the MSCS cluster.
During short initialization when using the Symmetrix splitter, RecoverPoint statistics
may show incoming traffic rate that is greater than what the host is actually sending.
The Predicted Protection window feature is not supported when the current protection
window is less than 24 hours.
The CLI script converter (the convert_script CLI command) does not support the
conversion of measure_lag_to_box parameter from 3.4 or earlier scripts. When
loading the converted CLI script into the new environment, each consistency group
will be created with value of Yes for all group links, unrelated to the value of this
parameter in the old environment.
CLI batch mode processing, where square brackets are used to demarcate multiple
instances of the add_volume, attach_splitter, or
create_replication_set commands, is not supported. Instead, the
edit_group_settings command can be used with the
apply_group_settings command to batch add_journal_volume,
add_replication_volume, or create_replication_set commands. The
attach_splitter command has been replaced by automatic splitter attachment.
RecoverPoint does not support Digital Signature Algorithm (DSA).
With XtremIO arrays

l
During XtremIO cluster expansion, upgrade, or when replacing a device in the cluster
processes which may take several hours. During this time do not take any proactive
action, such as to disable a consistency group.
Disabling and re-enabling multiple distributed consistency groups in a short period of

time may cause unexpected service interruption.
Replicating a high throughput replication set with a small snapshot cycle may
increase the latency temporarily.
Limitations
23
Release Notes
When the copy is on XtremIO and restoring production to a specific point in time, all
snapshots created at the target site after that point in time are deleted.
After failing over to an XtremIO array and changing the replication direction, history
snapshots at the new production copy are deleted.
Resize must currently be done manually (remove volume from RecoverPoint, resize on
array, add volume on RecoverPoint. This will cause a volume sweep.)
The recommended snapshot replication mode for XtremIO replication is Periodic.

For sizing guidelines when using Continuous snapshot replication mode, consult
EMC Customer Support.
RecoverPoint supports 512-byte block XtremIO volumes only.
With VNX/CLARiiON splitters

l
Due to a known issue in VNX OE for Block running 05.32 or later, during image
access, any punch command (regardless of size) will be turned into zeros by vCenter
rather than reclaimed.
In certain configurations, consistency groups cannot include Solaris-based hosts

replicating data on heterogeneous arrays. Refer to the ESM for supported
configurations.
Note
Consistency groups can include Solaris-based hosts replicating data on

heterogeneous arrays when the Solaris-based hosts use VxVM.
l
RecoverPoint replication and MirrorView replication cannot concurrently operate on

the same volume.
If MirrorView is installed on a VNX/CLARiiON array, RecoverPoint cannot utilize the

ports reserved by MirrorView. MirrorView must be disabled before the RecoverPoint
splitter driver can be enabled.
To complete the installation, the RPAs must be able to access two SP ports per
controller that are not used by MirrorView.
When multiple RPA clusters share a VNX/CLARiiON splitter pair, and are running on
the same array, each RPA cluster must have a unique name.
Each storage group can support a maximum number of volumes, based on the
storage system and the storage operating environment. RecoverPoint can replicate
more volumes per VNX/CLARiiON array by using virtual WWNs.
Known issues
Where a problem is only relevant to a specific RecoverPoint release, it is noted in the
problem summary
Known problems are sorted alphabetically by product feature and by issue number within
each product feature.
Table 15 Known issues found in RecoverPoint 4.4 and later
Issue Number
Product Feature
Problem Summary
122379
Adding volumes
without journal loss
When adding or editing a replication set, the added or replaced volumes are
missing from the image list in the distributed consistency group copy journal, and
system bookmarks are not created.
Workaround: Create a bookmark after you add or edit replication sets.
24
Release Notes
Table 15 Known issues found in RecoverPoint 4.4 and later (continued)
Issue Number
Product Feature
Problem Summary
120519
Array splitter specific
In a VNX RecoverPoint/SE environment with snap based replication, you may

receive error messages without errors actually occurring.
Workaround: N/A.
123613
CHAP
If you upgrade from RecoverPoint 4.1 to RecoverPoint 4.4 and RecoverPoint 4.1
has CHAP credentials configured, RecoverPoint may not be able to decrypt the
CHAP passwords. You will receive the following error: ERROR: While
trying to register RPA initiators with the storage

system the RPA encountered the following errors:
Failed to decrypt the CHAP password.
Workaround: Re-enter the CHAP configuration.
123085
CHAP
After changing CHAP credentials and regenerating keys, the system may not be
able to decrypt the new CHAP password. You will receive the following error:
ERROR: While trying to register RPA initiators with

the storage system the RPA encountered the following
errors: Failed to decrypt chap password.
Workaround: Delete CHAP configuration and reconfigure CHAP.
123904 (123979)
Data Domain
When replicating to a copy on a Data Domain system, replication may restart and a
short initialization of some consistency groups may occur.
Workaround: None. The system will recover automatically.
128924
Data Domain
In Data Domain configurations, when editing a link policy template previously

created with a Snap Replication setting of Periodic, and an Interval of 30
minutes, the Interval selection box does not appear in the Edit Policy Template
dialog. Clicking OK in this window may result in an error message:Error:Snap
shipping interval is less than the minimum required

for Data Domain (360 minutes). ( p->r: time interval
minimum: 360requested interval: 30 )
Workaround: To force the Interval selection box to appear, set the Snap
Replication mode off and then back to Periodic.
126392
Data Domain
When the copy is on a Data Domain system, in rare cases, when the user clicks
Create Bookmark the system will show that the snapshot was created but the
snapshot will not replicate to the non-production copy.
Workaround: N/A
128873
Data Domain
In Data Domain configurations, when you create a link policy template a Snap
Replication setting of Periodic, and an Interval of 360 minutes, and then select
that template to load it to the Data Domain group link policy, the Interval units
are displayed in hours (360 hours) instead of minutes (360 minutes).
Workaround: Edit the policy using the Protection > Policy Templates screen to
correct the Interval before applying the changes.
129328
Data Domain
If, during replication over the LAN, the system loses connectivity with a copy on a
Data Domain system, replication may be paused by system, and may not re-start
for 30 minutes.
Workaround: None
Known issues
25
Release Notes
Issue Number
Product Feature
Problem Summary
129161
Data Domain
Following an RPA disconnection from a Data Domain array, Consistency Groups

will fail over to another RPA; however, in rare cases, replication can take up to 3
hours to resume based on an array timeout setting. This condition will cause the
transfer status (visible in the Consistency Group Transfer Status widget) to
alternate from Snap Idle to Paused by System until the timeout
expires.
Workaround: None
124748
Deployment Manager
With release 2.4 of the Deployment Manger, you cannot download the ISO file
directly from the tool. To download the ISO file, go to EMC Online Support, select
the appropriate ISO file and save it locally.
123898
Deployment Manager
When using the Deployment Manager RPA Replacement Wizard, the wizard may
fail to check the connectivity of the new RPA.
Workaround: Retry the connectivity test after about 10 minutes.
122242
Deployment Manager
When performing an installation or an upgrade with the Deployment Manager, if

the ISO does not copy properly and becomes corrupted, the Deployment Manager
will not override the corrupted ISO and you will be unable to upload the ISO.
Workaround: Manually delete the corrupted ISO.
128450
Deployment Manager
When using the Deployment Manager Converter Wizard to convert an RP/SE

license to an RP/EX license, this error (found in the log files) may be encountered:
"Internal error. Error: Action cannot be committed

because the system is in maintenance mode. Wait for
the system to exit maintenance mode, and try again"
The conversion fails because Deployment Manager allows the user to retry while
still in maintenance mode.
Workaround: Exit maintenance mode and retry the conversion. To exit
maintenance mode, run these CLI commands:
35911
26
GUI
1.
resume_rpa_from_maintenance
2.
finish_maintenance_mode
When all of the following conditions are true, you may receive the following error
as a false positive in the GUI. "System Limitations exceeded":
l
Asynchronous links
Remote links WAN over FC/IP
Time-based RPO definitions
No apparent WAN connectivity issues
No burst in the application traffic
No misconfiguration of the load on the RPA
No highloads for an extended period time
Measure-lag-to-kbox=true
Without application-regulation
System limitation warning remains for a significant amount of time without

intermittently disappearing/reappearing
Release Notes
Issue Number
Product Feature
Problem Summary
Workaround: Ignore the warning. You may change the default RPO to
data=500MB. You may also pause and then resume transfer.
123921
GUI
In ProtectPoint, when creating a Data Domain group, if the user clicks the Edit
Replication Set link, the Edit Replication Set dialog box displays an Attach as
Clean checkbox, although this option is not supported for Data Domain groups.
122771
GUI
When protecting a large number of volumes, GUI performance may be very slow or
the GUI may crash.
Workaround: Use the CLI to protect volumes.
122360
GUI
After an RPA restores from a disaster while the browser session is open, the
RecoverPoint GUI may not able to re-connect to the tomcat server after.
Workaround: Open a new GUI session in the browser.
129064
Gen6
Once your operating system has loaded, you may not be able to use the virtual
KVM for Gen6 RPA hardware.
Workaround: Use serial-over-LAN (SOL).
123053
IPv6
RecoverPoint will not email events notifications if the SMTP server is configured
with an IPv6 address.
Workaround: Configure the SMTP server with an IPv4 address.
129326
Installation
After installation, SSH keys are not automatically generated per RPA and all of the
keys in all of the RPAs are identical.
Workaround: After installation, directly connect to each RPA in your system via
SSH, log in as a security-admin user, and run the
regenerate_encryption_keys CLI command.
128310
Installation Manager
When using the Installation Manager (boxmgmt) to perform a vRPA upgrade, the
Auto Upgrade step fails with the error message:

SAN view is empty: Check LUN masking, zoning, network
connections, and storage configuration.
Workaround: Use the Deployment Manager to perform the vRPA upgrade.

123050
LDAP
LDAP over SSL does not work with a certificate. If LDAP over SSL is configured with
a certificate, you will receive the following error: Unable to connect to
primary LDAP server.

Workaround: Use LDAP over SSL without a certificate or use LDAP.
127168
LDAP
In the CLI or GUI, if the LDAP server is not responsive, loging into a local user with
incorrect credentials, login my fail with the following error: Unexpected
error. Please contact system administrator.

Workaround: Disable LDAP.
129238
Localization
After uploading a language pack for RecoverPoint 4.4.1, the version may display
as 4.4.0 in the login dialog and in help.
Workaround: In the CLI, run the get_version cli command to verify which
version you are running.
Known issues
27
Release Notes
Issue Number
Product Feature
126534
NDU
Problem Summary
RPAs may be down after performing an NDU. The following error is displayed:
Applying upgrade failed. It is highly recommended to

retry upgrading again. Upgrade will initiate auto
retry in 2 minutes.
Workaround: Ensure that there is a repository configured before re-trying the
upgrade.
123523
Non disruptive
upgrade
After upgrading to RecoverPoint 4.4, if your security credentials were set to

Authenticated in 4.1.x, the admin use may be blocked from logging in even with
correct credentials.
Workaround: In the CLI, run unlock_user for admin users and
acquire_management_ip for RecoverPoint SE users.
126585
Policy Templates
It is possible to load a policy template with invalid settings, and an error message
may be displayed when clicking Apply in the Link Policy dialog box after loading
such a policy template.
Workaround: Edit the policy settings manually after loading the template.
121886
ProtectPoint
In the GUI and the CLI, when registering a Data Domain, Data Domains are not
displayed in the list of available arrays, even if they have been zoned and masked
to the RPA cluster.
124369
ProtectPoint
In an environment with a large number of Data Domains, if the environment is

running for an extended period of time, the replication process or the RPA may
crash.
Workaround: N/A
123569 (123593)
ProtectPoint
When creating a Data Domain consistency group, if the capacity of the added
volumes exceeds the replication capacity allowed by your RecoverPoint/BK
license, the new consistency group is removed by RecoverPoint but its device
group is not removed from the Data Domain.
Workaround: Manually delete the leftover device group from the Data Domain.
131551
Security
121991
Security credentials
After changing security levels from basic to high, when you log into the RPA via the
CLI, you will not be requested to change your password.
Workaround: Log into Unisphere for RecoverPoint with the boxmgmt user
credentials.
121534
Unisphere for RecoverPoint and the Deployment Manager support passwords

consisting of non- ascii characters. However, the CLI does not support passwords
consisting of non-ascii characters. If your password consists of non-ascii
characters, you will not be able to log into the CLI. Workaround: Passwords must
consist of ascii characters only.
127862
Splitters
If a single storage processor contains a large number of protected volumes, and

the number of IOs arriving at that storage processor is very high (>400,000 in a few
seconds), there may be a full sweep on the protected volumes that received the
IOs.
Workaround 1: Re-balance the load of the protected volumes between the storage
processors.
28
Release Notes
Issue Number
Product Feature
Problem Summary
Workaround 2: Lower the number of IOs to <50,000 per second per storage
processor.
123694 128344
System
If the Fibre Channel connection between the RPA and the Data Domain array is
disconnected for an extended period of time, the control process may crash.
Workaround: Contact EMC Customer Support.
128420
System
Changing multiple settings on the same object (such as a group or splitter) at the
same time or in rapid succession may cause the Resolve Conflicts dialog to be
displayed.
Workaround: In the Resolve Conflicts dialog box, choose the settings of one of
the RPA clusters by clicking the radio button for that cluster. All settings changes
made on the other cluster will be discarded. Alternatively, you can use the
resolve_settings CLI command to perform this action.
128835
System
In the Collect System Information wizard, if the user selects the Copy the output
file(s) to an FTP server check box, completes the remaining FTP text boxes but
leaves the Remote Path text box blank, and then clicks the Next Test
Connectivity button, a popup appears with this error message: Failed
getting collection results: Exception caught in

server [ java.lang.IllegalArgumentException ]
Workaround: Close the error message popup and enter the required FTP server
path in the Remote Path text box using the format: /<FTP server path>
128915
System
In the Collect System Information wizard, if the user enters an illegal character
in the Remote Path edit box in the Output Settings area and clicks the Next
Test Connectivity button, a popup warns the user that an illegal character was
entered. When the user clicks Close (to close the popup), the Back and the Next
Test Connectivity buttons are disabled and the user cannot continue.
Workaround: Click the Cancel button and restart the wizard.
124029
System
When using the Deployment Manager to add new RPAs to an RPA cluster, you will
not be able to use a saved configuration file. You will receive the following error:
Internal Error. Cannot register RPA WWNs.

registerInitiatorsInternal failed. You may have to complete
the Deployment Manager session, or you may be able to start a new session
without loading a configuration file.
123847
System
After replication is paused by system, the RPA may enter a reboot regulation and
detach from the cluster.
Workaround: Reboot the RPA at the production site
127587
System
If two RPAs in your system are set to different times (e.g. one to local time and one
to GMT), the Connect clusters wizard may fail with the following error: Failed
to get cluster into maintenance mode. Operation

failed. Error: Password has expired.
Workaround: Reset passwords on both RPAs .
129362
VNX
The following error message can appear when:
Known issues
29
Release Notes
Issue Number
Product Feature
Problem Summary
l
Choosing a snapshot from the image list on a Group Set - the error message
appears although the snapshot is still in the list
Requesting Image Access based on a given time (approximate query) - the

error message appears although the snapshot was not even selected from the
list
Error message: "ERROR: Specified image removed from
journal."
In both cases, the image that is selected might not be the best point-in-time image
available.
Workaround: None.
128897
VNX RecoverPoint/SE
The /var directory maybe full, causing boxmgmt to crash. You may not be able to
log into the RPA withuser SE.
125985
VPLEX
When a virtual machine VMDK is on a LUN replicated with the VPLEX splitter
without SRM, before failing or accessing an image on a copy, shut down the
production virtual machine. When shutting down the virtual machine is not
possible (for instance, when an unexpected disaster occurs at the production
copy), the recovery will be similar to recovering from an unexpected disaster, such
as a power outage, of a physical server.
127846
XtremIO
If you move an XtremIO cluster with active consistency groups to a different

XtremIO Management Server (XMS), commands will fail with the following error:
One or more links of group CG5 are set to replicate

snaps and an error occurred in the snap-based
replication process. The following errors were
received from the storage: Link = c1->d1, error =
[RPC failed at server. unauthorized_user].
Workaround: N/A. To recover your setup, move the cluster back to the original
XMS.
Table 16 Known issues found earlier than RecoverPoint 4.4
Issue Number
Product Feature
Problem Summary
120519
In a VNX RecoverPoint/SE environment with snap based replication, you may

receive error messages without errors actually occurring.
Workaround: N/A.
41234
In VNX environments, when running the load_settings command in the CLI, if

the CLI script you are loading contains more than one instance of
register_resource_pools per VNX array, an error is displayed and the script
does not load.
Workaround: None
37874
When replicating with the Symmetrix splitter, a failure of the repository volume
may cause the reboot of a cluster leader.
30
Release Notes
Table 16 Known issues found earlier than RecoverPoint 4.4 (continued)
Issue Number
Product Feature
Problem Summary
37456
In CLARiiON splitter environments, when a RecoverPoint 3.4, 3.5,or 4.0 CLI script is
converted to RecoverPoint 4.1, the converted script cannot be loaded in
RecoverPoint 4.1 if there are any instances of
config_splitter_login_credentials in the old script that contain refer
to CLARiiON splitter.
During conversion, the old config_splitter_login_credentials
command is translated to the new register_storage command. If the
config_splitter_login_credentials command contains a value for SPB_IP, the type of the register_storage command is set to VNX, even if the
storage type is actually CLARiiON.
Workaround: Before loading the converted script, open it in a text editor and
replace any instances of register_storage that have a type=VNX where the
actual type of the storage is CLARiiON.
37089
In some cases, volumes are not attached to Symmetrix splitter, and can also not
be attached manually.
Workaround: Contact EMC Customer Service.
43913
CHAP
When using CHAP, you may not be able to use the Deployment Manager to replace
RPAs.
Workaround: Turn off CHAP, perform HWR, and turn CHAP back on.
38562
CLI
When using the CLI to load settings, if the RecoverPoint system contains more
than two RPA clusters, a settings conflict message is displayed and the system
does not allow any further settings modification until the settings conflict is
resolved.
Workaround: When the system issues a settings conflict notification, select the
RPA cluster from which the settings were loaded.
43547
Changing web server

certificates
When changing the web server certificate, the private key generated is in PKCS#8
format. Importing keys in PKCS#8 format fails.
Workaround: Convert the private key to PKCS#1 format before importing it to
RecoverPoint.
44405
Cluster Security
After formatting a repository volume, security levels may be different for different
clusters.
Workaround: Enable cluster isolation mode (via boxmgmt:Setup > Advanced
options > Security options > Enable/disable cluster isolation, change the
RPA communication security level to be the same for all clusters (via
boxmgmt:Setup > Advanced options > Security options > Enable/disable
cluster isolation > Change appliance communication security level, then
disable cluster isolation mode.
120058
Converting licenses
When the conversion from a RecoverPoint/EX license to a RecoverPoint/SE license

fails, the retry command fails.
120047
Converting licenses
Converting from a RecoverPoint/EX license to a RecoverPoint/SE license fails.

Known issues
31
Release Notes
Issue Number
Product Feature
Problem Summary
117970
Converting licenses
When trying to convert from RecoverPoint/EX to RecoverPoint/SE, you may receive

the following errors in the GUI: ERROR: While trying to create
storage group on the storage system, system

encountered the following errors: An internal error
has occurred. Please contact Customer Support.
Workaround 1: Rename the storage group of the RPA.
Workaround 2: Manually remove the old storage group name, and rename them to
fit RecoverPoint conventions
43898
Converting to
RecoverPoint/SE
You will not be able to convert to RecoverPoint/SE if you have not upgraded all
clusters in the system.
Workaround: Ensure that all clusters are upgraded to RecoverPoint 4.1 or later.
120698
Deployment Manager
In the Deployment Manager, after successfully performing a non-disruptive

upgrade, you may receive the following invalid warning message: Failed to
get group settings. The group states were not

validated.
Workaround: N/A.
120203
Deployment Manager
When using the Deployment Manager to upgrade multiple RPAs from 4.0 SP1 to
4.1 SP2, the upgrade will fail, and the RPAs will enter reboot regulation.
Workaround: Reboot one RPA, and run the upgrade again.
118415
Deployment Manager
If when using Deployment Manager to perform a non-disruptive upgrade, you are

unable to attach RPAs to the cluster and you receive the message Internal
error; or when rebooting RPAs, you are unable to reattach them to the cluster,
reboot the RPA.
118151
GUI
When you chose the Automatically provision journal volume option

in the Define production journal step of the Protection Wizard, full resource
pools are displayed. You cannot use them for provisioning your journal volume.
117704
GUI
When rebooting RPAs, after the GUI is disconnected, multiple pop-ups appear one
on top of the other with the error message: Error: Connection with
RPA was lost. Please check RPA and network settings.

The screen gradually becomes darker.
Workaround: N/A
42665
Image access
During Image Access, if the journal becomes full or is in an error state, the
replication process of a consistency group may be unresponsive for about 20
minutes. Other consistency groups on the same RPA may also become
unresponsive. After about 20 minutes, the replication process restarts
automatically. A short initialization occurs to ensure that no writes are lost. After
that, replication restarts. This may occur in any version of RecoverPoint, but in
RecoverPoint 4.1.1.0 and later, it occurs only with distributed consistency groups.
Workaround: Disable image access. To prevent recurrence, consider increasing
journal capacity.
39765
LDAP
When using LDAP (rather than LDAPS) over port 636 to authenticate users or test
settings, the RPA crashes.
32
Release Notes
Issue Number
Product Feature
Problem Summary
Workaround 1: For secure LDAP access, use LDAPS instead of LDAP (over port
636).
Workaround 2: For unsecure LDAP access, refrain from using the reserved LDAPS
port.
41410
RecoverPoint GUI
If you use the CLI to reset the security level to high, while the Unisphere for
RecoverPoint GUI is open, the GUI prompts you for a new password. After you enter
the new password, Unisphere for RecoverPoint closes. If you attempt to re-open
Unisphere for RecoverPoint immediately, it may not recognize your (new)
password.
Workaround: After setting the new password, wait two minutes before you log in
again to Unisphere for RecoverPoint.
41418
RecoverPoint Installer Occasionally, navigation from the "Zoning and LUN masking" step may be
Wizard
blocked, accompanied by the error message, Unhandled exception.
Workaround: Restart the wizard, using a saved configuration file to avoid re-entry
of all the settings.
44429
RecoverPoint/SE
When installing or upgrading RecoverPoint/SE, and you have more than one IP
address per physical storage port, the installation or upgrade may fail. The
following error message appears: Cannot add path, could not
find port numbers for all supplied remote IPs.

Workaround: Make sure Virtual Port 0 is configured correctly: The port should be
Enabled. The correct IP should be configured.
119888
SRM/SRA
If a consistency group contains a bad volume, the SRM discoverDevices

command will fail and the SRA reports an empty consistency group and causes an
error.
125981
System
You may only be able to access statistics from the last few days of replication. This
is particularly relevant to scaled environments.
123135
System
When system settings differ between RPAs, the Deployment Manager may fail to
add additional RPAs to the cluster.
Workaround: Contact EMC Customer Support
123049
System
In a scaled environment with a large number of volumes, if the system runs into a
conflict in settings (which can occur as a result of simultaneous changes made to
different clusters or running configuration scripts on environment with 3 or more
clusters), system processes will crash continuously and eventually the RPAs will
be in reboot regulation.
Workaround: N/A. To avoid this, it is recommended to format a repository on all
clusters.
121383 (123526)
System
The GUI and CLI may be slow or unresponsive.

Workaround: Disable snapshot consolidation on all consistency groups.
42217
System
One or more RPA may reboot, which may cause a watchdog timeout in other RPAs
41191
System
After creating many new links across multiple clusters, RPAs may experience
connection failures.
Workaround 1: Remove any unnecessary links.
Known issues
33
Release Notes
Issue Number
Product Feature
Problem Summary
Workaround 2: Reboot the RPA(s).
41094
System
When applying LDAP settings on environments with multiple clusters, an error may
occur and LDAP settings are not changed.
Workaround: Reappy the LDAP settings.
41022
System
In some cases, a short initialization begins for all of the consistency groups
running on a given RPA.
Workaround: None.
40871
System
When replicating VMware virtual machines on a VPLEX Metro distributed volume

using VMware Site Manager Recovery, some virtual machines on production may
not shut down. When Recovery is rerun after fixing the fracture, SRM assumes all
virtual machines are powered down, which may not be the case. As a result,
Recovery will fail.
Workaround: After fixing the fracture, power down all production virtual machines
before running Site Recovery Manager Recovery again.
40652
System
After failing over to a target RPA cluster using SRM, if there is no communication
between the RPA clusters, a settings conflict is displayed after communication
between clusters is restored.
Workaround: Resolve the settings conflict by selecting to apply the settings of the
target RPA cluster.
40291
System
In some cases, consistency groups will not be enabled after the journal is auto
provisioned.
Workaround: Manually enable the consistency group once the journal is
provisioned.
35911
System
When all of the following conditions are true, you may receive the following error
as a false positive in the GUI, "System Limitations exceeded":
l
Asynchronous links
Remote links WAN over FC/IP
Time-based RPO definitions
No apparent WAN connectivity issues
No burst in the application traffic
No misconfiguration of the load on the RPA
No highloads for an extended period time
Measure-lag-to-kbox=true
Without application-regulation
System limitation warning remains for a significant amount of time without

intermittently disappearing/reappearing
Workaround: Ignore the warning. You may change the default RPO to
data=500MB. You may also pause and then resume transfer.
39803
34
System
When there is a back-end storage disaster at the VPLEX winner site and at least
one volume in the back-end storage is not available, the data transfer status of the
RecoverPoint consistency group will appear as init.
Release Notes
Issue Number
Product Feature
Problem Summary
34015
System
If you have two clusters with the same WAN and LAN subnet you will not be able to
add a third cluster if it has only the default gateway configured.
Workaround: Configure additional gateways besides the default gateway to allow
connectivity between the cluster WAN IPs.
33024
System
When a user adds volumes to the same copy of the same consistency group, but
from different clusters, and the volumes are added simultaneously or when the
WAN is disconnected, the number of volumes can exceed the maximum number
supported by the splitter. Cluster control attempts to add the volumes to the
splitter until the consistency group is regulated.
Workaround: Detach volumes from the splitter until the number is within the
maximum allowed.
26393
System
Defining info level filtering for syslog notification only shows info event logs and
does not display higher level event logs (such as errors and warnings).
Workaround: Define filters for warning and error levels.
44374
VPLEX
When running RecoverPoint 4.1.1 with the VPLEX splitter, collecting logs from a
remote VPLEX splitter may fail. Workaround: Connect directly to the remote cluster
and collect logs from that cluster only.
43994
VPLEX MetroPoint
In a VPLEX MetroPoint configuration, when VPLEX fails to access a DR1 production

volume, the links do not enter an error state and a production switch over does not
occur. Instead, the local link remains stuck at Init (0%) and the standby link
remains stuck at 'On Standby'.
119397
Virtual ports
Using many virtual ports may cause RPAs to reboot repeatedly or fail.
Workaround: Use no more than three virtual ports per RPA.
121991
After changing security levels from basic to high, when you log into the RPA via the
CLI, you will not be requested to change your password.
117037
System
During long-term statistics collection or bottleneck detection, WAN statistics are

only collected for one direction for each pair of RPAs.
122785
GUI
When creating a new consistency group, after selecting copy volumes and clicking
Next Review Replication Sets, the wizard may be stuck and the GUI may be
unresponsive.
36574
VNX
123171
Events
Event IDs may display the incorrect event message.
123342
VPLEX
When a copy is in virtual access mode, the splitter and firmware may crash on all
hosts in the cluster.
Known issues
35
Release Notes
Technical notes
This section contains important information for the current release.
Re-installing RecoverPoint 4.4

Before you begin
Ensure that you have the current (old) values for the Account ID and for the SSID for
each RPA cluster.
l
If you have the completed Post-Deployment Form from your last installation, you can
find these values there.
If not, run the following commands from the CLI (user=admin), and write down the
old Account ID and SSIDs:
When the old RecoverPoint installation is 4.0 and later, run:

get_account_settings to display the Account ID
get_licenses to display the licenses
get_system_settings to display the SSIDs for all clusters
Follow this procedure to guarantee continued high-quality service from EMC Technical
Support.
If, for any reason, you perform a full install of RecoverPoint 4.1, or later, on top of a
previous RecoverPoint installation, carefully follow these instructions:
Procedure
1. Install RecoverPoint 4.4 or later version.
During installation, your RecoverPoint system may assign new values for the Account
ID and the SSIDs.
2. Re-enter the old values for the Account ID and for the SSID for each cluster in place of
any new values. To do so, run the following commands from the CLI (user=admin):
l
set_account_id to enter the old Account ID.
config_cluster_ids to enter an old SSID. Run the command once for each
RPA cluster. In the context of this procedure, you can disregard the note to not
modify this setting.
Upgrading to the latest RecoverPoint 4.4 release

Upgrade to the latest RecoverPoint 4.4 release in order to resolve the issues listed in
Fixed issues on page 12. Upgrades are performed using the latest RecoverPoint
Deployment Manager.
It is recommended to upgrade all relevant splitting technologies only after all RPAs have
been upgraded to the latest 4.4 release.
Instructions for upgrading are detailed in the EMC RecoverPoint Installation and
Deployment Guide. Information about Deployment Manager 2.4.x can be found in the EMC
RecoverPoint Deployment Manager Release Notes.
36
Release Notes
Documentation
The following documents, available on EMC Online Support, provide additional
information about RecoverPoint:
l
EMC RecoverPoint 4.4 Documentation Set
l
EMC RecoverPoint Installation and Deployment Guide
l
EMC RecoverPoint 4.4 Product Guide
l
EMC RecoverPoint 4.4 Administrators Guide
l
EMC RecoverPoint 4.4 Security Configuration Guide
Documentation Name Changes
Name changes have been made to the following EMC RecoverPoint documents:
Old document name New document name
Notes
RecoverPoint Installation
and Deployment Guide
This document is a new version of the

Installation and Deployment Guide, and
describes how to install, upgrade and
maintain RecoverPoint systems 4.0 and later.
This document is release agnostic.
RecoverPoint 3.x
Installation and
Deployment Guide
This legacy document describes how to

install, upgrade and maintain RecoverPoint
systems earlier than 3.5.x.
RecoverPoint boxmgmt
Guide
This document was previously a chapter in the

Installation and Deployment Guide. This
document is release specific.
RecoverPoint VNX/
CLARiiON Technical
Notes
RecoverPoint Deploying
EMC Midrange Storage
Technical Notes
Includes information for Unity, VNXe, VNX and

CLARiiON arrays
RecoverPoint 4.4 Quick

Start Customer
Installation Guide
This document combines the Customer

Installation Guide and the Customer Upgrade
RecoverPoint 4.4
Customer Installation and Guide. This document is release specific.
Upgrade Guide
RecoverPoint
Installation and
Deployment Guide
RecoverPoint Customer
Upgrade Guide
Software media, organization, and files

GPL-licensed code is included herewith. If you would like source code for any such GPLlicensed code, please send a written request to: EMC Legal, 176 South Street, Hopkinton,
MA 01748, ATTN: Open Source Program Office. In your request, please indicate the EMC
Software Package or EMC Product which included an offer for GPL-licensed source code.
Installation and upgrade

RecoverPoint 4.4, RecoverPoint with VNX and RecoverPoint with Unity/VNXe RPA clusters,
with RecoverPoint/SE licenses, are fully customer installable. RecoverPoint/SE is also
fully customer-installable.
RecoverPoint with VNX and RecoverPoint with VNX, with SE licenses, and
RecoverPoint/SE are designed to be upgraded by the customer. However, EMC
Documentation
37
Release Notes
engineering periodically reviews this feature and may disable it remotely. When this
happens, the RecoverPoint Deployment Manager will issue an error message. If you
cannot wait for the feature to be enabled again, open a service request with EMC
Customer Service.
RecoverPoint/CL and RecoverPoint/EX hardware and software components are installed
and upgraded by EMC personnel.
RecoverPoint for XtremIO hardware and software components are installed and upgraded
by EMC personnel.
In all cases, specific requirements by both EMC and the customer are expected to be
addressed before the equipment is shipped to the customer site.
Instructions for installing and upgrading RecoverPoint are presented in the EMC
RecoverPoint Installation and Deployment Guide.
For upgrading to RecoverPoint 4.4 use the Cluster Upgrade Wizard.
The RecoverPoint/SE Installation Kit, available from EMC Online Support, contains
software and documentation to support customer installation of RecoverPoint/SE 4.4.
The RecoverPoint/SE Upgrade Kit, available for EMC Online Support, contains software
and documentation to support customer upgrades of RecoverPoint/SE.
If you previously upgraded an RPA cluster from 4.0.x to 4.1.2.0 or earlier, upgrading to
any version of 4.4 may cause communication between RPA clusters to fail. First, upgrade
to the 4.1 recommended minor version, and then to 4.4.
Deploying RecoverPoint with VNX/CLARiiON splitter
The EMC Midrange Storage arrays (Unity, VNXe, VNX, CLARiiON) support a RecoverPoint
array-based splitter. Special instructions for deploying RecoverPoint with midrange
storage arrays and splitters are presented in the EMC RecoverPoint Deploying with EMC
Midrange Storage Technical Notes.
Deploying RecoverPoint with Symmetrix splitter
The Symmetrix splitter is available for VMAX Series arrays. Special instructions for
deploying RecoverPoint with Symmetrix arrays and the Symmetrix splitter are presented
in the EMC RecoverPoint Deploying with Symmetrix Arrays and Splitter Technical Notes.
Deploying RecoverPoint with VPLEX splitter
EMC VPLEX storage virtualization platform supports a RecoverPoint array-based splitter
when using RecoverPoint 4.1 and later. This splitter is commonly referred to as the VPLEX
splitter. Special instructions for deploying RecoverPoint with VPLEX are presented in the
EMC RecoverPoint Deploying with VPLEX Technical Notes.
Deploying RecoverPoint with XtremIO arrays
RecoverPoint supports the XtremIO all-flash storage array as both a source and a target of
replication. RecoverPoint supports snap-based replication for XtremIO. For more
information, refer to the EMC RecoverPoint XtremIO Technical Notes.
38
Release Notes
Copyright 2015-2016 EMC Corporation. All rights reserved. Published in the USA.
Published July 2016
EMC believes the information in this publication is accurate as of its publication date. The information is subject to change without
notice.
The information in this publication is provided as is. EMC Corporation makes no representations or warranties of any kind with
respect to the information in this publication, and specifically disclaims implied warranties of merchantability or fitness for a
particular purpose. Use, copying, and distribution of any EMC software described in this publication requires an applicable software
license.
EMC, EMC, and the EMC logo are registered trademarks or trademarks of EMC Corporation in the United States and other countries.
All other trademarks used herein are the property of their respective owners.
For the most up-to-date regulatory document for your product line, go to EMC Online Support (https://support.emc.com).
Installation and upgrade
39

RecoverPoint 4.4 Release Notes

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

RecoverPoint 4.4 Release Notes

Uploaded by

Copyright:

Available Formats

Release Notes

Release 4.4.1.1. Added new

Release 4.4.1. Added new

Corrected build number. Added

Release 4.4.0.1. Added known

Added upgrade information.

RecoverPoint 4.4 Release Notes

Table 1 Revision History (continued)

First release of RecoverPoint 4.4

RecoverPoint/CL for EMC and non-EMC storage platforms.

RecoverPoint/EX for EMC storage platforms (Block), licensed by storage array.

RecoverPoint/SE for XtremIO, Unity/VNXe/VNX series, and CLARiiON CX4 series.

An EMC Simple Support Matrix (ESSM) on E-Lab Navigator https://

ISO image size

4.4 and later

EMC Europa 1U (Gen6)

Intel R1000 (Gen5)

Dell PowerEdge R610 (Gen4)

RecoverPoint 4.4 Release Notes

RecoverPoint 4.4 and later

Supported operating systems

RecoverPoint/SE: Heterogeneous with VNX/

Refer to the EMC Support Matrix for details.

RecoverPoint/CL: Heterogeneous (EMC and

RecoverPoint/EX: EMC (block)

RecoverPoint/SE: Unity platform, VNX series,

Refer to the EMC Support Matrix for details.

Maximum number of arrays

Maximum number of RPA clusters in a

RecoverPoint/CL: Symmetrix, VPLEX, and

RecoverPoint/EX: Symmetrix, VPLEX,

RecoverPoint/CL: Per license (maximum 2 PB)

RecoverPoint/EX: Per license (maximum 2 PB)

RecoverPoint/SE: One per RPA cluster

RecoverPoint/SE with XtremIO: Multiple arrays

RecoverPoint/CL: 5 (3 for XtremIO)

RecoverPoint/EX: 5 (3 for XtremIO)

Table 5 General configuration limits (continued)

RecoverPoint 4.4 and later

Maximum number of open RecoverPoint CLI

Maximum number of open RecoverPoint CLI

Maximum number of concurrent

Minimum Adobe Flash Player for

Internet Explorer 9.0

Mozilla Firefox 3.0

Google Chrome 2.0

Safari for Mac 5.0

Minimum supported screen (display)

Number of RPAs in a cluster

Maximum number of SAN entities (WWNs)

Maximum number of paths per RPAb

Recommended minimum repository volume

Minimum journal size

10 GB (non-distributed consistency group)

40 GB (distributed consistency group)

Maximum journal sizec

Maximum number of distributed

Maximum number of journal volumes per

RPA MTU packet size

1,000 - 9,000 bytes for IPv4

1,280 - 9,000 bytes for IPv6

Maximum size of replicated LUNs

In virtual access, maximum offset of image

In virtual access, maximum writes per RPA