vRPA RecoverPoint-4.0-Release-Notes PDF

RELEASE NOTES
EMC® RecoverPoint
Release 4.0
Release Notes
P/N 300-015-077
REV 02
June 28, 2013
These release notes contain information about release 4.0 and service pack and patch
releases of the EMC RecoverPoint product family. Topics included in this document are:
◆ Revision history ........................................................................................................ 2
◆ Product description................................................................................................... 2
◆ New features and changes ...................................................................................... 10
◆ Fixed problems ....................................................................................................... 14
◆ Environment and system requirements ................................................................... 19
◆ Known problems and limitations ............................................................................. 20
◆ Technical notes ....................................................................................................... 25
◆ Documentation ....................................................................................................... 26
◆ Software media, organization, and files .................................................................. 26
◆ Installation ............................................................................................................. 26
◆ Troubleshooting and getting help............................................................................ 27
Revision history
Revision history
The following table presents the revision history of this document:
Table 1 Revision history
Revision Date Description
02 June 28, 2013 Release of 4.0.0.P1, see “New features and

changes for release 4.0 P1” on page 10.
01 May 13, 2013 Release of RecoverPoint 4.0, see “New

features and changes for release 4.0” on
page 10.
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:

◆ RecoverPoint/CL for EMC and non-EMC storage platforms.
◆ RecoverPoint/EX for EMC storage platforms (Block), licensed by storage array.
◆ RecoverPoint/SE for VNX series, CLARiiON CX3 and CX4 series, and Celerra unified
storage environments.
Note: Throughout this document, in the context of comparing “RecoverPoint” and

“RecoverPoint/SE”, the term “RecoverPoint” is synonymous with “RecoverPoint/CL and
RecoverPoint/EX”, unless otherwise noted.
Note: An EMC Support Matrix (ESM) on E-Lab™ Navigator https://elabnavigator.EMC.com

serves the RecoverPoint product family. After logging in, select the PDFs and Guides tab
and look for RecoverPoint in the Information Management Software section.
2 EMC RecoverPoint 4.0 Release Notes

Product description
Table 2 on page 3 identifies the build and size of the RecoverPoint ISO image associated
with the 4.0 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.0.P1 4.0.P1_f.231 0.74 GB
4.0 4.0_f.224 0.74 GB
Notes on performance
Additional performance information will be provided in the RecoverPoint 4.0 Performance
Guide, to be available shortly after product release.
Table 3 on page 3 and Table 4 on page 3 present general throughput and IOPS values for
Gen4/Gen5 RPAs and for virtual RPAs (vRPAs). You can use these values to develop
general sizing requirements for your RecoverPoint system. Note, however, that the
following limitations apply:
◆ Values in tables are for non-distributed consistency groups.
◆ Throughput rates were measured using a write size of 64 KB.
◆ The values include writes only.
Note: Reads do not impact performance.
These values are independent of:

◆ Link type (WAN-IP, FC)
◆ Replication mode (async, sync)
Table 3 Average sustained throughput and IOPS per RPA
Throughput (MB/s) IOPS (per splitter type)
RPA 120 VNX/CLARiiON 20000

Symmetrix 22000
VPLEX 24500
Notes:
1. Throughput and IOPS increase linearly with the number of RPAs, provided that the splitter
supports the increased levels of performance.
2. For async replication of distributed consistency groups, RecoverPoint 4.0 supports throughput of
up to 400 MB/s, depending on storage array configuration.
Table 4 Average sustained throughput and IOPS per vRPA
vRPA Profile Throughput (MB/s) IOPS
8 CPU 8 GB RAM 80 10000
4 CPU 4 GB RAM 65 6500
2 CPU 4 GB RAM 50 4500

Note: Each vRPA CPU operates at speed of 2.13 GHz.
EMC RecoverPoint 4.0 Release Notes 3

Product description
For additional information on RecoverPoint 4.0 scale and performance, contact your EMC
sales representative.
Configuration limits
In addition to being supported on 64-bit RPA hardware platforms, RecoverPoint/SE is now
supported on virtual RPA platforms. For 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.
Table 5 on page 4 lists the 4.0 releases supported across RPA hardware types.
EMC will continue to support existing configurations of RPA hardware platforms running
earlier versions of RecoverPoint.
Table 5 RecoverPoint releases support across RPA hardware types
RPA hardware 4.0 and later
Intel R1000 (Gen5) Supported1
Dell PowerEdge R610 (Gen4) Supported1
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) Not supported
1. When using a mix of RPA hardware types (Gen5 and Gen4), it is highly recommended to configure the latest
types as RPA 1 and RPA 2 (cluster control RPAs) to improve system function and performance.
Break fix/support
EMC will handle break/fix activity for Gen4 and Gen5 RPA hardware platforms purchased
through Direct Express and Channel Express.
SAN support
Table 6 on page 4 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 6 Fibre Channel support across RPA hardware types
RPA hardware 1 Gb/s1 2 Gb/s 4 Gb/s 8 Gb/s
Gen4 Not supported Supported Supported Supported
Gen5 Not supported Supported Supported Supported

1. No support for basic connectivity of Gen4 or Gen5 in 1 Gb/s SAN.

Product description
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 7 on page 5 lists the general configuration limits for 4.0 and later releases.
Table 7 General configuration limits (page 1 of 4)
Parameter RecoverPoint 4.0 and later
Supported operating • RecoverPoint/CL: Heterogeneous

systems • RecoverPoint/EX: Heterogeneous
• RecoverPoint/SE: Windows Server 2000/2003/2008/2012 and
heterogeneous with VNX/CLARiiON splitter
Refer to the EMC Support Matrix for details.
Supported storage arrays • RecoverPoint/CL: Heterogeneous (EMC and non-EMC)

• RecoverPoint/EX: EMC (block)
• RecoverPoint/SE: VNX series, CLARiiON CX3 and CX4 series, and
Celerra unified
Refer to the EMC Support Matrix for details.
Supported splitter types • RecoverPoint/CL: Symmetrix, VPLEX, and VNX/CLARiiON

• RecoverPoint/EX: Symmetrix, VPLEX, and VNX/CLARiiON
• RecoverPoint/SE: VNX/CLARiiON
Maximum capacity • RecoverPoint/CL: Per license (maximum 2 PB)

• RecoverPoint/EX: Per license (maximum 2 PB)
• RecoverPoint/SE: 2 PB
Maximum number of arrays • RecoverPoint/CL: Unlimited

• RecoverPoint/EX: Unlimited
• RecoverPoint/SE: One per RPA cluster
Maximum number of RPA • RecoverPoint/CL: 5

clusters in a system • RecoverPoint/EX: 5
• RecoverPoint/SE: 2
Unisphere integration • RecoverPoint/CL: Not supported

• RecoverPoint/EX: Not supported
• RecoverPoint/SE: Supported
Journal compression • RecoverPoint/CL: Supported

• RecoverPoint/EX: Supported
• RecoverPoint/SE: Not supported
Maximum number of open 100

RecoverPoint CLI
connections per RPA cluster
Maximum number of open 12

RecoverPoint CLI
connections being set up
concurrently
Maximum number of 20
concurrent RecoverPoint GUI
sessions per RPA cluster

Product description
Minimum Adobe® Flash® 10.2

Player for RecoverPoint GUI
Minimum supported web • Internet Explorer 7.0

browser for RecoverPoint • Mozilla Firefox 3.0
GUI • Google Chrome 2.0
• Safari for Mac 5.0
Minimum supported screen 1024x768

(display) resolution for
RecoverPoint GUI
Number of RPAs in a cluster 2-8
Maximum number of SAN 256

entities (WWNs) seen by an
RPA
Maximum number of paths 200K

per RPA1
Recommended minimum 2.86 GB

repository volume size
Minimum journal size • 10 GB (non-distributed consistency group)

• 40 GB (distributed consistency group)
Maximum journal size per 10 TB

consistency group
Maximum number of 8
distributed consistency
groups
Maximum number of journal 128

volumes per consistency
group copy
RPA MTU packet size • 1,000 - 9,000 bytes for IPv4

• 1,280 - 9,000 bytes for IPv6
Maximum size of replicated 32 TB

LUNs
In virtual access, maximum 1.2 TB

offset of image in journal
In virtual access, maximum 40 GB

writes per RPA
Maximum number of 128 (not recommended to configure more than 64 per RPA)2
consistency groups in
system
Maximum number of copies 5 (includes production copy)

per consistency group
Maximum number of local 2 (includes production copy)

copies per consistency
group

Product description
Maximum number of 2
consistency group remote
copies per RPA cluster
consistency groups in group
set
Maximum number of • 128 - continuous local replication or continuous remote replication

non-production copies in • 256 - continuous local and remote replication
cluster

replicated production
volumes in system
Maximum number of • 8192 (when using physical RPAs)

replication sets per • 2048 (when using virtual RPAs)
consistency group

replication volumes per
system

exposed LUNs per ESX
servers
Maximum number of ESX 100

servers in discovery per RPA
cluster
Total number of LUNs that 2048

are visible to ESX servers per
RPA cluster
Total number of VMs that are 3000

visible to ESX servers per
RPA cluster
Maximum number of vCenter 4

servers in discovery per RPA
cluster
Minimum bandwidth for 3 Mb/s

replication
Asynchronous replication Per topology as supported by eLab

over FC distance limit
Asynchronous replication 200 ms (round trip time)

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

over FC distance limit
Synchronous replication 4 ms (round trip time)

over FC latency limit
Synchronous replication 10 ms (round trip time)

over IP latency limit

Product description
Maximum number of • 1 local (FC)

synchronous replication • 1 remote (FC or IP)
links per consistency group
Stretch cluster distance limit 30 km

(on the stretch side)
Maximum WAN packet loss 1%4

1. Where “path” is a LUN WWN seen by an RPA port. The same LUN WWN seen from different RPA ports is
counted multiple times.
2. 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.
3. More groups can be supported. Consult EMC Customer Support for setting a minimal interval for
bookmarking.
4. RecoverPoint performance and ability to meet replication policies cannot be guaranteed if WAN packet loss
exceeds this limit.
Scalability
The scalability limits when deploying RecoverPoint with the currently available splitter
types are as follows:
VNX/CLARiiON scalability
Table 8 on page 8 lists the VNX/CLARiiON scalability limits:
Table 8 VNX/CLARiiON scalability limits
Parameter Limit
Maximum number of attached LUNs per splitter • 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
Maximum number of RPA clusters connected to splitter • 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
Maximum number of splitters per RPA cluster 10
1. One splitter serves both storage processors of a VNX/CLARiiON array.

Product description
Symmetrix scalability
Table 9 on page 9 lists the Symmetrix scalability limits:
Table 9 Symmetrix scalability limits
Parameter Limit
Maximum number of attached LUNs per splitter 40961 in VMAX 10K2, 20K, 40K arrays
Maximum number of RPA clusters connected to splitter 6
1. In a continuous remote replication configuration.

2. When using RecoverPoint 4.0 and EMC Enginuity release 5876 or later for Symmetrix VMAX 10K. (When not
using both of these products, 2048 LUNs are supported.)
VPLEX scalability
Table 10 on page 9 lists the VPLEX scalability limits.
Table 10 VPLEX scalability limits
Parameter Limit
Maximum number of attached LUNs per splitter • 2K when using GeoSynchrony 5.1
• 8K when using GeoSynchrony 5.2
Maximum number of RPA clusters connected to splitter • 4 when using GeoSynchrony 5.1
• 6 when using GeoSynchrony 5.2
Splitter support for different size volumes1 • No, when using GeoSynchrony 5.1
• Yes, when using GeoSynchrony 5.2
Maximum number of directors for VPLEX Local 8
Maximum number of directors for VPLEX Metro 16

1. Whether or not the VPLEX splitter supports “fake size”, that is, if a replica volume attached to the VPLEX
splitter must be the exact same size as the production volume or not.
Splitter interoperability
RecoverPoint/CL and RecoverPoint/EX support the mixing of VNX/CLARiiON, Symmetrix,
and VPLEX splitters between different RPA clusters and within the same RPA cluster, as
shown in Table 11 on page 9.
Table 11 Splitter interoperability between RPA clusters and within RPA clusters
Splitter type1, 2,3 VNX/CLARiiON Symmetrix VPLEX

VNX/ CLARiiON Supported Supported Supported
Symmetrix Supported Supported Supported
VPLEX Supported Supported Supported
1. Each volume can be attached to only one splitter type.
2. A consistency group copy can span both Symmetrix and VNX/CLARiiON splitters, but not VPLEX splitters.
3. A volume can only be included in one consistency group across all RPA clusters in the case of
multi-cluster (sharable) splitters.

New features and changes

This section lists new features and changes in RecoverPoint 4.0 and later.
New features and changes for release 4.0 P1

There are no new features in this release.
◆ Fixed problems
Table 12 on page 14 lists the problems fixed in this release.
New features and changes for release 4.0

◆ Support for data protection on up to five RPA clusters
RecoverPoint now provides the capability to concurrently protect data to multiple
disaster recovery sites using a single management point. For example, data can be
protected locally on one RPA cluster and concurrently copied to up to four remote RPA
clusters (“fan out”), or replicated from up to four remote RPA clusters to one, central
RPA cluster (“fan in”). For installation and deployment information, refer to the EMC
RecoverPoint Installation and Deployment Guide. For administration and replication
configuration information, refer to the EMC RecoverPoint 4.0 Administrator’s Guide.
◆ Virtual RPA (vRPA) with VNX splitter
vRPA is a virtual RPA that runs as a virtual machine on VMware ESX servers. Almost all
RPA functionality is available in vRPA with little or no additional limitations. Instead of
HBAs and Fibre Channel, the vRPA uses iSCSI over a standard IP network; therefore,
there are no hardware requirements for the vRPA other than a standard ESX server. For
installation, deployment, and operating instructions, refer to EMC RecoverPoint vRPA
Technical Notes.
◆ SRM AnyPIT
SRM AnyPIT enables VMware Site Recovery Manager to access point-in-time images,
not only the latest RecoverPoint image. Use EMC Virtual Storage Integrator 5.5 for
RecoverPoint from within the vCenter to select the image. Refer to Virtual Storage
Integrator documentation for instructions.
◆ Replicating the same device with both SRDF and RecoverPoint
From RecoverPoint 4.0 and later and Symmetrix Enginuity 5876 Q2 2013 SR and later,
it is permitted to replicate the same device with both SRDF and the RecoverPoint
Symmetrix splitter, as long as SRDF and RecoverPoint are replicating to two different
devices, and RecoverPoint is replicating only to a local copy. For details, refer to the
EMC RecoverPoint Deploying with Symmetrix Arrays and Splitter Technical Notes.
◆ Scale and performance improvements
• Maximum replication throughput for a distributed consistency group, over Fibre
Channel or WAN, is now 400 MB/s.
• A RecoverPoint system supports up to 8K production volumes, when using VNX
splitters with VNX OE for Block later than 05.32.000.5.201, and when using VPLEX
splitters with VPLEX GeoSynchrony 5.2.

◆ Intelligent fabric-based splitters (Brocade and SANTap) and host-based splitters are
not supported with RecoverPoint 4.0.
◆ Unisphere for RecoverPoint (new Management Application GUI)
The RecoverPoint GUI, renamed to Unisphere for RecoverPoint, has been completely
re-developed using Adobe Flash technology and simplified to promote ease of use
and a common user experience between RecoverPoint, VNX, VPLEX, and Symmetrix
products.
The new protection and recovery wizards have been streamlined and optimized for a
simpler and more intuitive user experience. User inputs have been reduced, more
default values have been added, preferred RPAs are automatically defined, and a
dashboard has been added to provide an overall view of the system health status.
Furthermore, all of the information displayed in the new GUI is consistently
auto-refreshed and the new GUI is aligned with Unisphere’s internationalization
support. Detailed information can be found in the EMC RecoverPoint 4.0
Administrator’s Guide.
◆ RecoverPoint/SE is now customer upgradable
With the release of Deployment Manager 2.0, RecoverPoint/SE 3.5 and later releases
are now customer upgradable. The upgrade process has been greatly simplified and
customers can now perform the RecoverPoint/SE software upgrades on their own
schedule and without the need to schedule and rely on external resources. To perform
the upgrade, you must download the RecoverPoint/SE Upgrade Kit and follow the
instructions in the RecoverPoint/SE Upgrade Guide contained within the kit.
To download the kit from EMC Online Support (http://support.emc.com), click
“Support by Product” and type “RecoverPoint SE” in the “Find a Product” search field.
On the “RecoverPoint SE” page, the kit is located in the “Recommended Resources”
section.
◆ Deployment Manager 2.0
Deployment Manager 2.0, which replaces Deployment Manager 1.1, introduces a
number of changes and new features, including a new wizard to connect RPA clusters
running release 4.0, the ability to install virtual RPAs, and integration with EMC Online
Support site for upgrades. Furthermore, as of 4.0, deployment operations—such as
installation, upgrade, and modification—are performed per RPA cluster, not per
system. Refer to the RecoverPoint Installation and Deployment Guide and
RecoverPoint Deployment Manager 2.0 Release Notes for more information.
◆ REST API access to the RecoverPoint functional API
The REST API provides a simple-to-use Web interface to the RecoverPoint API that
third-party developers can use to integrate RecoverPoint functionality into their own
applications and to script RecoverPoint operations. The REST API is documented in the
EMC RecoverPoint 4.0 REST API Programming and Reference Guide.
◆ SyR improvements
A new schema has been developed that supports the new RecoverPoint multi-cluster
and eLicensing features, doesn't change whenever a class in the schema changes,
and only contains fields that are required by SyR clients. When testing connectivity,
the user is now prompted for a verification email address. If the connectivity test is

successful, a service request containing call home event number 30999 is opened
and an email is sent to the entered email address from EMC Customer Support to
verify that the system reports mechanism (SyR) has been successfully configured.
◆ Lag Optimizer
Priority of bandwidth allocation for consistency groups has been improved to
substantially minimize any business damages that customers may incur due to data
loss in the case of an actual disaster.
◆ Licensing improvements
This feature introduces eLicensing. For existing RecoverPoint users, this enhances
license tracking and management, improves overall user experience, enables less
complex license upgrades, reduces the risk of non-compliance, eliminates the paper
right-to-use (RTU) cards, and enables self-service license creation. For licensing
information, refer to the EMC RecoverPoint 4.0 Administrator’s Guide.
◆ Journal and repository volumes can now be located on non-licensed arrays
In RecoverPoint/SE and RecoverPoint/EX, journal and repository volumes can now be
located on non-licensed arrays.
◆ Support for sync over IP
RecoverPoint now supports synchronous replication over IP to a remote RPA cluster.
◆ FIPS 140-2 compliance
The following FIPS (Federal Information Processing Standard) 140-2 validated
cryptographic modules are used in RecoverPoint 4.0:
• RSA BSAFE® Crypto-J, JSAFE, and JCE Software Modules
• RSA® BSAFE Crypto-C Micro Edition
• OpenSSL FIPS Object Module
For more information about RecoverPoint security, refer to the EMC RecoverPoint 4.0
Security Configuration Guide.
◆ User experience enhancements
Many improvements have been made to ensure a better overall total customer
experience in RecoverPoint 4.0:
• Splitters residing on licensed arrays are automatically added to the system.
• When recovering production, there is no longer a need to enable image access to
the production and resume production.
• Snapshots now carry a consistency tag that enables the user to mark snapshots
that are known to be application-consistent as such. Snapshots created using
KVSS are automatically marked as application-consistent.
• Image access is now part of the flow of the recovery wizards and is no longer
performed as a separate function. An image access progress indicator and an
image access log capacity indicator have both been added to the recovery wizards.

• Users can now select an event in the event log and click “Collect System
Information” to open the Collect System Information wizard and RecoverPoint will
automatically set the collection start time and end time fields to 10 minutes before
and after the selected event.
• Additional RPA cluster information has been added, including; the RecoverPoint
version, RPA type (physical or virtual), number of RPAs in the cluster, cluster
management (LAN) IPv4 and IPv6, and the time zone of the RPA cluster.
• Bottleneck detection and load balancing analysis are now available from the GUI.
◆ Read access to replication volumes
When using VNX or Symmetrix splitters, 4.0 supports read access to replication
volumes at local and remote copies, without disrupting normal distribution of
replicated data to the same volumes. As a result, the Cluster Shared Volumes feature
is supported for consistency groups managed by RecoverPoint/CE 4.1.3 or later, for
which “read-only” is the default splitter setting. Note that when in read-only mode,
consistency and data integrity of the copy volumes are guaranteed only if the user
does not mount, unmount, or otherwise manipulate those volumes. For other groups,
“fail-all” continues to be the default splitter setting.
◆ Multipathing performance and robustness improvements
In 4.0, multipathing performance and robustness is improved, thereby simplifying the
procedure for changing the mapping of LUNs that have already been exposed to
RecoverPoint. This feature is implemented both with FC and iSCSI protocols.
◆ Fixed problems
Table 13 on page 15 lists the problems fixed in this release.

Fixed problems
Fixed problems
Table 12 on page 14 lists the problems fixed in RecoverPoint 4.0 P1.
Table 13 on page 15 lists the problems fixed in RecoverPoint 4.0.
Fixed problems are sorted alphabetically by product feature and by issue number within
each product feature.
Table 12 Problems fixed in RecoverPoint 4.0 P1
Issue number Product feature Problem summary
35612 Deployment When using the Deployment Manager Add New RPAs Wizard to add an RPA to an existing
Manager RecoverPoint/SE RPA cluster, the addition will fail with the error, “Unable to execute command.”
Workaround: Manually register the new RPA initiators on the VNX/CLARiiON array, and add them
to the relevant storage groups.
35342, Deployment When using the Deployment Manager Upgrade RPAs Wizard to upgrade a system running 3.5.x,
35469 Manager and with no WAN gateway configured, to 4.0, the upgrade will fail.
Workaround: Before the upgrade, configure a WAN gateway.
35003 Deployment When using the Deployment Manager RecoverPoint/SE Installer Wizard to reinstall 4.0 on a
Manager system that was already running 4.0, the installation will fail with an error stating that there is no
IP connection between RPAs and storage.
Workaround: Contact EMC Customer Support for assistance.
35708 System After upgrading a one-cluster (one-site) RecoverPoint system from 3.5.x to 4.0 using Deployment
Manager Upgrade RPAs Wizard, reboot regulation will occur.
35673 System When in physical or virtual image access mode and: a) a flipover occurs, or b) the replication
process crashes, an inconsistency may occur.
35438 System The RecoverPoint getVolumeInformation Functional API method may return an incorrect naaUid,
which may affect users that use this field, which is part of the VolumeInformation object.
35377, System When sending write(16) SCSI commands for some offsets (which usually occurs when working
35430, with LUNs greater than 2 TB in size), you will be unable to replicate consistency groups with
35476 these LUNs (the groups will go into a regulation state).
35079 System When performing an upgrade while throttling level is enabled (high or low), or enabling
throttling level after installation, replication will get stuck during initialization.
Workaround: Disable throttling level.
35684 System After performing an upgrade from 3.5.x to 4.0, one of the following will occur on the remote site:
• When using automatic snapshot consolidation, the RPAs will eventually enter reboot
regulation
• When using manual snapshot consolidation, the replication process will restart.
Workaround: Disable snapshot consolidation.
35690 VMware SRM When using VMware SRM AnyPIT, the SRM test failover feature fails with errors when the
protected and recovery sites are disconnected.
35126 vRPA After cloning a virtual RPA (vRPA), the cloned vRPA does not have a network interface defined,
causing it to spontaneously reboots in a loop every couple of seconds, making it unusable.
Workaround: Use OVF package to deploy a new vRPA.

Fixed problems
Table 13 Problems fixed in RecoverPoint 4.0 (page 1 of 4)
34762 Array splitter Only relevant when using RecoverPoint 4.0 and VPLEX GeoSynchrony 5.1
specific When the RecoverPoint Client calls the VolumeInformation object, getPaths() method, the re-
turned list is always empty. No information is available on VPLEX and RecoverPoint integration.
34301 Array splitter In a Symmetrix splitter environment, when the splitter tries to query the array regarding an ORS
specific state when no ORS session exists on the array, the splitter will crash.
33869 Array splitter When resizing Replication Set while disabling a consistency group, the relevant copy locks in
specific REGULATED state instead of DISABLED state.
Workaround: Remove the Replication Set that is being resized (the problematic RSET).
33244 Array splitter In a RecoverPoint/SE environment, running the get_system_settings CLI command leads to the
specific repository volume information not being displayed properly in the command output. As a result,
when using, for example, the Deployment Manager Converter Wizard, this problem will cause
the conversion to RecoverPoint to fail.
32804 Array splitter In a Symmetrix splitter environment, Open Replicator Sessions do not support LUNs that are ex-
specific posed to more than 32 FAs. If a LUN in a RecoverPoint replication set is attached to the Symme-
trix splitter, and exposed to more than 32 FAs, it will stop the Symmetrix splitter (replication of
the entire consistency group will fail).
32113 Array splitter In a VNX splitter or VMAX splitter environment, during unmapped data (punch) distribution, rep-
specific lication process may constantly crash when only unmapped data is replicated (since the meta-
data pool is entirely consumed), and initialization does not progress.
Workaround: Contact EMC Customer Support for a signed script.
31971 Array splitter In a Symmetrix splitter environment, even though volumes may be detached, generic warnings
specific for the volumes may still appear in the RecoverPoint GUI.
31488 Array splitter In a RecoverPoint/SE environment, due to a CLI issue, the interface with Celerra does not work,
specific leading to a failure to replicate on a file level.
30916 Array splitter In a system converted to RecoverPoint/SE where the array has many storage groups, the user
specific may fail to change system settings (such as creating a new consistency group), indicated by the
UI getting stuck until a timeout occurs. Workaround: Contact EMC Customer Support for a tweak.
30797 Array splitter When performing SRM failover (migration) on multiple consistency groups, RecoverPoint may re-
specific turn conflicting states, causing SRM actions to fail.
Workaround: Resolve the settings conflict manually, and then re-activate SRM.
30767 Array splitter In a Symmetrix splitter environment, when the ACA bit is set on the device, the RPAs will be un-
specific able to see the device. As a result, RecoverPoint will present a configuration error even though
the configuration is OK. Workaround: The error can be ignored.
30709 Array splitter When using a VPLEX splitter, the snapshots, bookmarks, and other features are unavailable
specific when rebuilding a distributed volume on a RecoverPoint protected VPLEX Metro cluster. This is
due to a physical link error or a non-operating VPLEX cluster. The RPA reports the consistency
group is in ERROR instead of INIT state.
Workaround: None: Consistency group returns to INIT or Active state once un-order writes have
completed.
29980, Array splitter VNX/CLARiiON Splitter fails when reading or writing in virtual access or virtual with roll. This
30126 specific causes an SP panic on the VNX/CLARiiON array.
Workaround: Do not use virtual access or virtual with roll.
26768 Array splitter Deployment Manager (DM) cannot upgrade RecoverPoint with consistency groups with names
specific that end with back-slash (\).
Workaround: Rename the consistency groups, removing the back-slash (\).

Fixed problems
34208 System During initialization, if transfer of a consistency group is stopped for some reason (for example,
due to high load), and the group has compression configured, there is a low probability that the
RPA running the consistency group may fail with assertion, and as a result a short initialization
may occur on all the consistency groups running on this RPA.
34152 System When a fatal error occurs during virtual access, the RPA cluster may detach because of RPA repli-
cation processes crashing in a loop.
33946 System There is a low probability that during snapshot consolidation a fatal error may occur and will
cause a full sweep and journal loss.
33815 System If distributing a large-sized image during a pause distribution (the large image may occur during
an initialization), and at the same time the system tries to remove this image due to a lack of
space, the journal may become corrupted and the journal history will be cleared and a full
sweep will occur.
33461 System When I/O throttling is enabled, reboot regulation may occur.
Workaround: Disable I/O throttling if this problem occurs.
33309, System Resizing LUNs may cause errors or loss of journal, returning a “fatal error” or “journal loss” mes-
33336 sage. This may occur when journal space is used up and the journal mus be resized.
Workaround: None. Reduce the chances for error by setting journal lag after the most recent LUN
resize and before a planned reboot or NDU user action.
33219 System When creating a consistency group using the Consistency Group Wizard, together with Auto-pro-
visioning journal, the complete name (cgName + copyName + internalSiteName) cannot be lon-
ger than 64 characters.
Workaround 1: Define short consistency group and copy names, so that the complete name is
up to 64 characters,
Workaround 2: Create journal volumes manually.
32113 System During unmapped data (punch) distribution, replication process may constantly crash when
only unmapped data is replicated (since the metadata pool is entirely consumed), initialization
does not progress.
Workaround: Contact EMC Customer Support for a signed script.
32074 System If a communication disaster occurs during synchronous replication of a distributed consistency
group, and immediately afterwards an FC disaster occurs on the remote site, the replication
process of the primary RPA will get stuck, and after a number of minutes the replication process
will restart. This will result in a short initialization of all consistency groups running on the RPA.
31949 System In a VMAX or VNX splitter environment that support thin LUNs, when a long resynchronization
occurs, the replication process may generate massive amount of logs. These logs probably
cause the replication process to get stuck and to restart after a number of minutes. This action
will result in a short initialization of all consistency groups running on the RPA.
31914, System In a heavily loaded environment, the control process may crash, causing reboot regulation. The
32914, UI temporarily loses connection with cluster control. User initiated operation may fail.
34276 Workaround: Reboot RPAs 2-8 to resolve the problem until the next occurrence.
31845 System When a sudden, small I/O burst occurs (for example, 1.5 GB), a high load may occur.
31546, System In a RecoverPoint system connected over Fibre Channel (not iSCSI), an RPA might get stuck or
34732, suddenly reboot, causing one or more RPAs in the cluster to crash.
34839
31252 System Due to a storage awareness issue, when I/O throttling is enabled, the replication process may
crash, leading to RPA to enter reboot regulation.
Workaround: Contact EMC Customer Support for a tweak.

Fixed problems
31215 System After installation, a settings conflict (probably due to improper installation process) occurred
that was resolved improperly by the user taking the empty settings. This action causes the inter-
nal process to crash and restart. Workaround: Contact EMC Customer Support for a tweak.
31054 System In the following scenario, you will not be able to connect to the RecoverPoint UI, and eventually
the RPAs will enter reboot regulation:
1. Add a new replication set to a consistency group, with no volumes in it.
2. Add a replication volume to the replication set, in the replica copy.
3. Add a replication volume to the replication set, in the production copy.
Workaround 1: Before the issue occurs, add the replication volume of production copy to the
replication set before adding the replication volumes in the replica copy.
Workaround 2: After the issue occurs, remove the relevant consistency group and add its set-
tings according to the order above (production volume first).
30965 System In a RecoverPoint system connected over Fibre Channel (not iSCSI), a high I/O rate may cause
the replication process on the remote site to restart, causing a short initialization.
Workaround: Contact EMC Customer Support for a tweak to reduce the probability of the issue
occurring.
30808 System When integrating a new RPA or replacing a disk in an existing RPA, installation may fail, raising
failure mode (shell). The installation process appears stuck.
Workaround:
1. Reboot and try installing again from the installation DVD.
2. Connect a KVM switch and try installing from another instance of the Installer Wizard.
30673 System In a system with high latency between sites and deduplication is configured for a certain link,
and the transfer over the link is paused and started, replication process may crash and a short
initialization will occur of the consistency groups running on the specific RPA.
30515, System Trying to add a second VMware vCenter Server to the same site will fail and display the error
34666 message "Error: Invalid port or certificate", even when the port and certificate are valid.
Workaround: Reboot RPA or Tomcat to reload the keystore. To add several connections with sev-
eral certificates, first add all the credetials with all the certificates to the keystore, then restart
Tomcat to reload all the new certificates.
30489 System There is a low probability that during snapshot consolidation a fatal error may occur and cause a
full sweep and journal loss.
30365 System When replicating asynchronously over Fibre Channel (FC), and the FC connection is slow, this
may cause transfer to start and pause repeatedly. As a result, the replication process may lose
memory, causing the replication process to crash.
30309 System Using the Installation Manager (boxmgmt), when attaching RPA1 and you enter the current local
time, the input is applied in GMT time. This results in bookmarks appearing in the incorrect time
zone. Workaround: When attaching RPA1, enter the GMT time instead of the local time.
29578 System In a CDP or CRR configuration, if you add a copy to a consistency group when the replication task
is closed, journal loss and a full sweep on the relevant consistency group will occur. Work-
around: Do not add a copy when transfer is in “N/A” state. Fix the problem, wait for transfer to
be in any other state than “N/A” and then add the copy.
29470 System If you try to configure more than 1024 replication sets in a consistency group, RPAs will enter re-
boot regulation.
Workaround: Divide the consistency group with more than 1024 replication sets into two
groups. Do this also before upgrading to 3.5.

Fixed problems
29220 System In an environment with at least 3 RPAs with a distributed consistency group with at least 3 pre-
ferred RPAs, in case of within-site FC connectivity problems between two RPAs, replication will
not start.
Workaround 1: Fix the connectivity problem.
Workaround 2: Define different preferred RPAs.
29205 System In a scaled environment, where SAN Discovery might take some time, if volumes were not ex-
posed to an RPA and then many new volumes were exposed to an RPA just prior to installation,
installation will be blocked and user will see error “SanView is empty”.
Note: In a VPLEX environment, the maximum number of volumes for VPLEX deployment per
VPLEX cluster is 5K.
Workaround 1: Wait until SAN Discovery finishes, then perform installation.

Workaround 2: Avoid exposing many new volumes to RecoverPoint prior to installation.
29128, System In an environment where replica storage is a bottleneck and there is low journal size, a high
29170 write rate may lead to a journal loss in replica and full sweep afterwards. The probability of this
problem occurring increases when there are sync and async links in the same direction. Work-
around: Use a larger journal, or restrict journal lag by some value.
29099 System If a Fibre Channel disaster occurs when a distributed consistency group is replicating synchro-
nously, transfer will go down (display “N/A”) for a number of minutes. Afterwards, the RPA will
automatically recover and an initialization will occur.
26171 System Initialization restarts, high latency for user I/Os, and possibly aborted I/Os may occur in the fol-
lowing scenario:
• Initialization in synchronous replication mode
• “Measure lag when writes reach the target RPA” setting (in Consistency Group Advanced Pol-
icy of the RecoverPoint GUI) or measure_lag_to_box parameter (in the set_policy CLI com-
mand) equals “No”
• relatively high write rate on the production copy
Specifically, near the end of the initialization, host I/Os will not be acknowledged for a consider-
able period of time, which may cause the host to abort an I/O. The abort will cause the system to
stop responding to writes for several seconds, after which an initialization will start again. It is
possible that this behavior will reoccur.
Workaround: Set the “Measure lag when writes reach the target RPA” setting or the
measure_lag_to_box parameter to equal “Yes”.

Environment and system requirements
Environment and system requirements

Generally, RecoverPoint hardware and software components are installed by EMC
personnel. Specific requirements by both EMC and the customer are expected to be
addressed before the equipment is shipped to the customer site. However, as mentioned
in “RecoverPoint/SE is now customer upgradable” on page 11, customers can now access
RecoverPoint software and perform their own upgrades.
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:

◆ Go to EMC Online Support, at http://support.emc.com.
◆ Go to Support by Product pages and search for RecoverPoint CL.
◆ In the product page, scroll down the left and click Release and End of Life Dates.
◆ Find the EMC Software Release and End of Service Life Notifications document in the
results.
◆ Open it and search for your product and version.
This document provides EOSL dates for EMC software products.
Note: 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.

Known problems and limitations

This section lists the limitations and known problems in the current RecoverPoint release.
Note: All information regarding interoperability limitations is available on E-Lab Navigator.
Limitations
RecoverPoint 4.0 and later releases have the following limitations:
◆ To remove an RPA cluster, the Installation Manager (boxmgmt) must be used.
◆ 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
re-enabling 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.
◆ RecoverPoint supports thin provisioning only on all EMC arrays and on Hitachi arrays.
◆ AVT failover mode is not supported on all storage arrays.
◆ 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).
◆ RPAs on one cluster may not be able to communicate with RPAs on another cluster if
there is a network address translation (NAT) firewall between the clusters.
◆ Unisphere for RecoverPoint may not be able to communicate with RPAs if there is a
network address translation (NAT) firewall between the machine that runs the GUI and
the RPAs.
◆ RecoverPoint/CE 4.1.3 and later supports replication for continuous remote
replication consistency groups and continuous local and remote consistency groups.
For the latter groups, however, failover is supported only to a remote copy, and
failback will always be to the original production copy.

◆ 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).
Note: 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), a limit
of 1013 snapshots (images) are presented.
◆ VMware ESX replication capabilities and limitations are specified in EMC RecoverPoint
Replicating VMware Technical Notes.
◆ When using VNX/CLARiiON splitters:
• 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.
• 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.
• When multiple RPA clusters share a VNX/CLARiiON splitter pair (CX3 models
running FLARE 03.26 or later, CX4 models running FLARE 04.29 or later, and VNX
OE for Block models running 05.31 and later), and are running on the same array,
each RPA cluster must have a unique name.
◆ RecoverPoint volumes—repository, journal, and replication—should 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
target-side 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.

◆ For VNX/CLARiiON arrays, 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.
◆ 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.
Known Problems
Table 14 on page 22 lists the known problems found in RecoverPoint 4.0 and later.
Table 15 on page 23 lists the known problems found earlier than RecoverPoint 4.0.
Where a problem is only relevant to a specific RecoverPoint release, it is noted in the

problem summary.
Table 14 Known problems found in RecoverPoint 4.0 and later
Issue Number Product Feature Problem Summary
34637 Array splitter If you try to reinstall a RecoverPoint/SE environment from scratch (including formatting the re-
specific pository volume) without running the clear_settings CLI command beforehand, a generic warn-
ing will appear stating that devices are attached to another cluster, and replication won't start.
Workaround: Contact EMC Customer Support for a procedure to resolve the issue.
33024 Array splitter When a user adds volumes to the same copy of the same consistency group, but from different
specific 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. Control at-
tempts to add the volumes to the splitter until the consistency group is regulated.
Workaraound: Detach volumes from the splitter until the number is within the maximum al-
lowed.
35289 System In a high throughput environment, specifically with large journal lag, replication may stop on all
consistency groups running on the RPA.
34676 System When cluster control comes up, the settings may not yet be loaded when usersystem tries to
useing them, causing control process to crash and restart.
34537 System No warning is issued when configuring RPAs that do not exist in all the copy sitesclusters. As a
result, another RPA, not the preferred RPA, will be used for replication of the group copy.
Workaround: Before configuring the RPAs, verify that the designated RPAs are responding from
all copy sitesclusters. After configuring the RPAs, review RPA settings, verifying all RPAs are ac-
counted, with no missing copy sitesclusters.
32271 VMware VMware ESX Virtual Machine does not shut down when shutting down the RecoverPoint Appli-
ance (RPA) using the “boxmgmt” CLI command.
Workaround: Shut down VMware ESX Virtual Machine and RecoverPoint Appliance manually.
34636 vRPA In a vRPA environment, when the iSCSI IPs of all RPAs are changed at the same time, an unex-
plained reboot may occur.
Workaround 1: Detach all RPAs before changing their iSCSI IPs.
Workaround 2: Change the IPs of each RPA one at a time. For example, verify that RPA 1 is ex-
posed to the repository before changing the IP of RPA 2.

Table 15 Known problems found earlier than RecoverPoint 4.0 (page 1 of 3)
14681 System When Snapshot Consolidation is enabled:

• The Predicted Protection Window information is unavailable.
• The Current Protection Window Status may be incorrect.
23813 System When replicating remotely over Fibre Channel, if you reinstall the environment and change the
RPA roles (such as change R1 to R2 and R2 to R1), the remote RPAs will lose their WAN connec-
tion to the local site.
Workaround: If the RPAs are up and there's no communication between the sites, reboot all RPAs
again. The situation will correct itself after approximately 15 minutes.
23847 System When using the Installation Manager (boxmgmt), running signed scripts that require user input
will cause the system to hang (system will show “Please wait...”) until you end the command.
24326 System When upgrading to a new RecoverPoint version that introduces a change in the system-defined
call home events, the new system-defined events will override the old ones, but any user-defined
call home events will be lost.
Workaround: Save the user-defined call home event rules and add them again after upgrade.
25126 System After performing the following actions, the display in the GUI and CLI is confusing:
1. Detach volumes from a splitter.
2. Remove the splitter.
3. Uninstall the splitter on the host.
4. Connect to add splitter in the GUI.
5. Install splitter (new version) on the host.
The GUI will display the same splitter twice, and the CLI command add_splitter will fail with the
message “Error: Splitter names appear more than once on network”. Workaround: Wait around
30 minutes, after which you will be able to add the splitter successfully.
25483 System When you run CLI commands from RPAs which are not site control RPAs (RPA1 and RPA2), you
may get the wrong output for some commands related to SAN view and to statistics.
Workaround: Run the CLI commands from RPA1 and RPA2.
29504 System If you change several consistency groups (CGs) from distributed to non-distributed, and vice
versa, at the same time, distributed CGs-non-distributed CGs transition will not complete, and
transfer will pause.
Workaround 1: Change CGs to be distributed or non-distributed one at a time.
Workaround 2: Kill all replication processes, one at a time.
Workaround 3: Reboot RPAs one at a time.
30580 System When the Intel Integrated Baseboard Management Controller (BMC) or the Integrated Dell Re-
mote Access Controller (iDRAC) is disabled using the Installation Manager (boxmgmt), only the
Intelligent Platform Management interface over the local area network (IPMI over LAN) access is
actually disabled. It will still be possible to access BMC or iDRAC via its IP address, even when it
is disabled in the Installation Manager.
Workaround: To completely disable access, set all IP addresses that provide access to these
services to 0.0.0.0. For iDRAC, it means setting the LAN IP address to 0.0.0.0. For BMC, it means
setting the LAN, WAN, and BMC port IP addresses to 0.0.0.0. This procedure is not
recommended, as it disables all network access.
15405 Array splitter Working with CLARiiON Splitter and “domino” configuration, a host application performs I/O to
specific RP protected LUNs and the Active CLARiiON SP reboots. After the Active CLARiiON SP restarts, the
host application may experience I/O errors.

25871 Array splitter 3.4 SP1 and later

specific Using a Symmetrix splitter, when replicating synchronously and there is a failover during writes
at the new active site, failover will be followed by a short initialization.
Workaround: Stop writes before performing failover. Start writes after failover completes.
29313, Array splitter In a RecoverPoint/SE environment, changing the site management IP (floating IP) will cause the
29770 specific RecoverPoint plugin in the Unisphere/Navisphere UI to stop working.
Workaround: Manually change the IP address of the RP initiator on the VNX/CLARiiON array. The
initiator ends with 0_0 and contains the previous site management IP.
27796 System Changing a site name does not change the site name seen in volumes list of Configure repository
volume of Installation Manager (in boxmgmt Setup menu). You will always see the site name that
was configured at the moment of installation or upgrade.
26393 System Defining “info” level filtering for syslog notification only shows “info” event logs and does not
display higher level event logs (“errors” and “warnings”). Workaround: Define filters for “warn-
ing” and “error” levels.
33472 System When running a CLI script on a large scale environment (8000 volumes, 128 consistency groups),
the GUI does not open, waiting for the script to complete.
Workaround: Wait for the CLI script to complete, or stop it in the middle to open the GUI.
30367 System When creating an LDAP type user, the new user cannot be limited to a specified consistency
group.
28255 System When the SMTP server is not defined, sending a SyR report fails, returning the error "Failed to
send email".
Workaround: Define the SMTP server.
34834 System When opening multiple GUI sessions on the same computer and browser application, the follow-
ing problems may arise:
1. The RecoverPoint API may reach a different GUI session than the one that called the API.
2. An open session may disconnect for several seconds if another session fails to log on.
3. A non-existing user may succeed logging on to RecoverPoint.
4. A false disconnection error message may appear.
Workaround: When opening several sessions on RecoverPoint from the same computer, use dif-
ferent browser applications.
34181 System When trying to download logs using Microsoft Internet Explorer 8, the following error appears:
“unable to open this internet site..”
Workaround: To download the logs, upgrade Internet Explorer to version 9, or use Firefox or
Google Chrome.
26312 Array splitter When using a VNX/CLARiiON splitter and running the get_splitter_settings CLI command, the
specific output shows SAN information for splitter B as “N/A”, even when splitter B is working fine.
Workaround: See the output of splitter A, since it is identical to splitter B.
28923 Array splitter When using a VPLEX splitter, if the splitter volume state is in target-side processing (TSP) mode
specific and replication reaches TSP full, a full sweep will be triggered. A full sweep will also occur in the
following scenario: If an RPA fails to respond to I/Os from the VPLEX splitter for more than 5 min-
utes (for example, due to a journal error issue).

Technical notes
29069 Array splitter When configuring VPLEX credentials, if you enter a valid username, password, and IP of a VPLEX
specific platform, but the VPLEX platform with the IP you entered is NOT part of the RecoverPoint environ-
ment:
• the credentials validation will incorrectly pass successfully.
• RecoverPoint will not function in the VPLEX UI (disabled in the manager menu).
• RecoverPoint log collection won't collect logs from the correct VPLEX splitter.
• RecoverPoint will filter VPLEX volumes only for the VPLEX platform of that with the incorrectly
entered IP; if there is an additional VPLEX platform on the same site with valid and correct cre-
dentials (that is, the IP address matches the VPLEX splitter), its volumes won't be filtered out.
Workaround: Enter the correct IP of the VPLEX platform in the RecoverPoint environment.
29670 Array splitter VNX/CLARiiON splitter does not support Punch commands, on both virtual and physical image
specific access.
34928 Array splitter When I/O between the Symmetix splitter and the RPA fails, the RPA begins tracking and receiving
specific the backlog from the splitter. Performing a failover before backlog retrieval has completed
causes data data inconsistency between the RPA and splitter.
Workaround: Clear journal markers to initiate a full sweep replication.
35016 System When a user changes a tweak and later the tweak is changed again in a new release, then, after
upgrading to the new release, the user change is ignored and there is no notification that the
change is not applied. Workaround: Reboot site control in production, change the tweak again.
28413 System When an LDAP user has a boxmgmt role, the LDAP user is not fully functional.
Technical notes
This section contains important information for the current release.
Upgrading to the latest RecoverPoint 4.0 release

Upgrade to the latest RecoverPoint 4.0 release in order to resolve the issues listed in
“Fixed problems” on page 14. Upgrades are performed using Deployment Manager 2.0.
It is recommended to upgrade all relevant splitting technologies only after all RPAs have
been upgraded to the latest 4.0 release.
Instructions for upgrading are detailed in the EMC RecoverPoint Installation and
Deployment Guide. Information about Deployment Manager 2.0 can be found in the EMC
RecoverPoint Deployment Manager 2.0 Release Notes.
Licensed features
When upgrading to RecoverPoint 4.0, previous licenses will automatically be converted to
the new license format. However, the new licenses are temporary and valid for 90 days
from the date of upgrade. After that, you must have installed one or more permanent
license files to replicate with RecoverPoint. Instructions for licensing are detailed in the
EMC RecoverPoint 4.0 Administrator’s Guide.
Licensed features in RecoverPoint 4.0 and later: None.

Documentation
Documentation
The following documents, available on the EMC Online Support site,
http://support.emc.com, provide additional information about RecoverPoint:
◆ EMC RecoverPoint 4.0 Documentation Set
◆ EMC RecoverPoint Installation and Deployment Guide
◆ EMC RecoverPoint 4.0 Administrator’s Guide
◆ EMC RecoverPoint 4.0 Security Configuration Guide
Software media, organization, and files

GPL-licensed code is included herewith. If you would like source code for any such
GPL-licensed 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
Instructions for installing RecoverPoint are presented in the EMC RecoverPoint Installation
and Deployment Guide.
Deploying RecoverPoint with VNX/CLARiiON splitter

The EMC VNX series arrays and the CLARiiON CX3 and CX4 Series arrays support a
RecoverPoint array-based splitter. This splitter is commonly referred to as the
VNX/CLARiiON splitter. Special instructions for deploying RecoverPoint with
VNX/CLARiiON arrays and the VNX/CLARiiON splitter are presented in the EMC
RecoverPoint Deploying with VNX/CLARiiON Arrays and Splitter 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.0 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.

Troubleshooting and getting help
Troubleshooting and getting 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.
Copyright © 2006- 2013 EMC Corporation. All rights reserved. Published in the USA.
Published June 2013
EMC believes the information in this publication is accurate as of its publication date. The information is subject to change without
notice.
The information in this publication is provided as is. EMC Corporation makes no representations or warranties of any kind with
respect to the information in this publication, and specifically disclaims implied warranties of merchantability or fitness for a
particular purpose. Use, copying, and distribution of any EMC software described in this publication requires an applicable software
license.
EMC2, EMC, and the EMC logo are registered trademarks or trademarks of EMC Corporation in the United States and other countries.
All other trademarks used herein are the property of their respective owners.
For the most up-to-date regulatory document for your product line, go to EMC Online Support (https://support.emc.com).

vRPA RecoverPoint-4.0-Release-Notes PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

vRPA RecoverPoint-4.0-Release-Notes PDF

Uploaded by

Copyright:

Available Formats

RELEASE NOTES

June 28, 2013

Revision Date Description

02 June 28, 2013 Release of 4.0.0.P1, see “New features and

01 May 13, 2013 Release of RecoverPoint 4.0, see “New

The RecoverPoint family consists of three licensing offerings:

Note: Throughout this document, in the context of comparing “RecoverPoint” and

Note: An EMC Support Matrix (ESM) on E-Lab™ Navigator https://elabnavigator.EMC.com

2 EMC RecoverPoint 4.0 Release Notes

Table 2 RecoverPoint release, build, and ISO image size

Release Build ISO image size

4.0.P1 4.0.P1_f.231 0.74 GB

4.0 4.0_f.224 0.74 GB

Note: Reads do not impact performance.

These values are independent of:

Table 3 Average sustained throughput and IOPS per RPA

Throughput (MB/s) IOPS (per splitter type)

RPA 120 VNX/CLARiiON 20000

Table 4 Average sustained throughput and IOPS per vRPA

vRPA Profile Throughput (MB/s) IOPS

8 CPU 8 GB RAM 80 10000

4 CPU 4 GB RAM 65 6500

2 CPU 4 GB RAM 50 4500

EMC RecoverPoint 4.0 Release Notes 3

Table 5 RecoverPoint releases support across RPA hardware types

RPA hardware 4.0 and later

Intel R1000 (Gen5) Supported1

Dell PowerEdge R610 (Gen4) Supported1

Legacy hardware (such as the IBM xSeries 336) Not supported

Table 6 Fibre Channel support across RPA hardware types

RPA hardware 1 Gb/s1 2 Gb/s 4 Gb/s 8 Gb/s

Gen4 Not supported Supported Supported Supported

Gen5 Not supported Supported Supported Supported

4 EMC RecoverPoint 4.0 Release Notes

Table 7 General configuration limits (page 1 of 4)

Parameter RecoverPoint 4.0 and later

Supported operating • RecoverPoint/CL: Heterogeneous

Supported storage arrays • RecoverPoint/CL: Heterogeneous (EMC and non-EMC)

Supported splitter types • RecoverPoint/CL: Symmetrix, VPLEX, and VNX/CLARiiON

Maximum capacity • RecoverPoint/CL: Per license (maximum 2 PB)

Maximum number of arrays • RecoverPoint/CL: Unlimited

Maximum number of RPA • RecoverPoint/CL: 5

Unisphere integration • RecoverPoint/CL: Not supported

Journal compression • RecoverPoint/CL: Supported

Maximum number of open 100

Maximum number of open 12

EMC RecoverPoint 4.0 Release Notes 5

Table 7 General configuration limits (page 2 of 4)

Parameter RecoverPoint 4.0 and later

Minimum Adobe® Flash® 10.2

Minimum supported web • Internet Explorer 7.0

Minimum supported screen 1024x768

Number of RPAs in a cluster 2-8

Maximum number of SAN 256

Maximum number of paths 200K

Recommended minimum 2.86 GB

Minimum journal size • 10 GB (non-distributed consistency group)

Maximum journal size per 10 TB

Maximum number of journal 128

RPA MTU packet size • 1,000 - 9,000 bytes for IPv4

Maximum size of replicated 32 TB

In virtual access, maximum 1.2 TB

In virtual access, maximum 40 GB