rp3 4 Release Notes 300-012-258 A05

1
These release notes contain information about release 3.4 and service
pack and patch releases of the EMC RecoverPoint product family.
Topics include:
Revision history.................................................................................... 2
Product description.............................................................................. 3
New features and changes ................................................................ 21
Fixed problems ................................................................................... 30
Environment and system requirements .......................................... 49
Known problems and limitations .................................................... 50
Technical notes.................................................................................... 73
Documentation ................................................................................... 73
Software media, organization, and files.......................................... 74
Installation........................................................................................... 74
Troubleshooting and getting help.................................................... 76
EMC

RecoverPoint
Release 3.4
Release Notes
P/N 300-012-258
Rev A05
July 13, 2011
2 EMC RecoverPoint 3.4 Release Notes
Revision history
Revision history
Table 1 on page 2 shows the revision history for this document.
Table 1 Revision history
Revision Date Description
A05 July 13, 2011 Release of Service Pack 1 Patch 1 (SP1 P1)
A04 June 15, 2011 Release of Service Pack 1 (SP1)
A03 May 20, 2011 Release of Patch 1 (P1)
A02 April 4, 2011 Documentation corrections
A01 February 16, 2011 Release of RecoverPoint 3.4
3
Product description
EMC RecoverPoint 3.4 Release Notes
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 the reliable replication of data over any
distance; within the same site (CDP), to another distant site (CRR), or
both concurrently (CLR). Specifically, RecoverPoint systems support
replication of data that applications are writing over Fibre Channel to
local SAN-attached storage. The systems use existing Fibre Channel
infrastructure to integrate seamlessly with existing host applications
and data storage subsystems. For remote replication, the systems use
existing IP connections to send the replicated data over a WAN, or
use Fibre Channel infrastructure to replicate data asynchronously or
synchronously. The systems provide failover of operations to a
secondary site in the event of a disaster at the primary site.
The RecoverPoint family consists of three products:
RecoverPoint/CL for replicating across EMC and non-EMC
storage platforms.
RecoverPoint/EX for VMAXe
, VNX
series, CLARiiON
CX3
and CX4 series, and Celerra
unified storage environments.

RecoverPoint/SE for VNX series, CLARiiON CX3 and CX4 series,
and Celerra unified storage environments.
RecoverPoint/EX and RecoverPoint/SE are optimized for the EMC
storage they support with built-in array-based write splitters.
RecoverPoint/CL is the full-featured offering that adds support for
intelligent fabrics, heterogeneous servers, and heterogeneous storage
platforms.
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: A single consolidated 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.
Product description
Table 2 on page 4 identifies the build and size of the RecoverPoint
ISO image associated with the 3.4 releases. The build also appears in
the RecoverPoint Management Application GUI (Help menu >
About RecoverPoint Management Application), in response to the
get_version CLI command, and in the Installation Manager header.
Performance
Performance statistics are presented for asynchronous and
synchronous remote replication, for both regular and distributed
consistency groups.
The following limitations apply:
Gen3 and Gen4 RPAs were used for testing regular consistency
groups. Only Gen4 RPAs were used for testing distributed
consistency groups and for testing Symmetrix splitters.
Tests of VNX/CLARiiON splitters were conducted on VNX series
arrays.
All tests of asynchronous replication performance were
conducted over IP.
All tests of synchronous replication performance were conducted
over Fibre Channel.
To attain the throughput values presented in the tables, journal
volumes at the remote side must be capable of supporting three
times the specified throughput rates.
For all performance statistics that include compression, the values
were obtained using a compressibility ratio of 1/2 (50%).
Unless otherwise specified, throughput rates were measured
using a write size of 64 KB.
Unless otherwise specified, IOPS were measured using a write
size of 0.5 KB.
Table 2 RecoverPoint release, build, and ISO image size
Release Build ISO image size
3.4 3.4_h.102 971 MB
3.4.P1 3.4.P1_h.122 971 MB
3.4.SP1 3.4.SP1_k.128 965 MB
3.4.SP1.P1 3.4.SP1.P1_k.140 965 MB
5
Product description
All IOPS in SANTap tests were measured using the Cisco
Multilayer Switch Module (MSM).
Asynchronous
replication
This section provides performance statistics for consistency groups
during asynchronous replication.
All performance statistics for asynchronous replication are over
IP. It is assumed that over Fibre Channel, the performance values
would be equal to or slightly greater than those for asynchronous
replication over IP.
WAN accelerators can be used to heighten performance during
asynchronous replication. However, WAN compression should
be disabled if WAN accelerators are used. Refer to the ESM for
devices supported with RecoverPoint.
Deduplication is a consistency group bandwidth reduction policy
that enables users using Gen4 RPAs to eliminate the transfer of
repetitive data to a remote site, saving bandwidth.
Performance of regular groups set to replicate asynchronously
The following performance statistics are available for regular
(non-distributed) groups set to replicate asynchronously:
Average sustained IOPS per RPA, with different splitters
Average sustained and burst IOPS of four groups, per number of
RPAs, for VNX/CLARiiON splitter
Average sustained throughput per RPA (MB/s), with WAN and
journal compression
Table 3 Average sustained IOPS per RPA, with different splitters
KDriver SANTap Brocade VNX/CLARiiON Symmetrix
a
Average sustained 19,500 12,500 20,000 20,000 22,000
a. Results achieved on a VMAXe series array with 8 FAs and 512 devices.
Table 4 Average sustained and burst IOPS of four groups, per number of RPAs,
for VNX/CLARiiON splitter
a
(Sheet 1 of 2)
Burst Average Sustained
1 RPA
with all 4 groups on the same RPA
40,000 20,000
Product description
Performance of distributed groups set to replicate
asynchronously
The following performance statistics are available for distributed
groups set to replicate asynchronously:
Average sustained IOPS per number of RPAs, with different
splitters
Average sustained throughput (MB/s) per number of RPAs,
with journal compression
2 RPAs
with 2 groups on each RPA
51,500 37,000
4 RPAs
with 1 groups on each RPA
53,000 49,000
a. In these tests, there was no difference between the values attained for one
consistency group and four consistency groups.
Table 4 Average sustained and burst IOPS of four groups, per number of RPAs,
for VNX/CLARiiON splitter
a
(Sheet 2 of 2)
Burst Average Sustained
Table 5 Average sustained throughput per RPA (MB/s), with WAN and journal
compression
WAN compression
a
Journal compression High Medium Low None
None 65 70 80 80
Medium 40 50 55 55
High 30 30 30 30
a. Results are the same with or without deduplication (see
Asynchronous replication on page 5).
7
Product description
Average sustained throughput of four RPAs, with WAN
compression
Synchronous
replication
This section provides performance statistics for consistency groups
during synchronous replication over Fibre Channel.
The following limitations apply:
In synchronous replication mode, the host applications initiate a
write, and then wait for an acknowledgment from the remote
RPA and the remote storage before completing the write.
Therefore, in synchronous replication mode, application
performance will be highly impacted if latency is high.
Table 6 Average sustained IOPS per number of RPAs, with different splitters
Total Number of RPAs KDriver SANTap Brocade VNX/CLARiiON Symmetrix
a
2 23,000 13,000 23,000 22,500 24,000
4 26,000 13,500 25,000 22,500 24,000
Table 7 Average sustained throughput (MB/s) per number of RPAs, with journal
compression
Total Number of RPAs
Journal compression 2 4
None 160 250
Medium 110 220
High 60 120
Table 8 Average sustained throughput of four RPAs, with WAN compression
WAN compression
Throughput High Medium Low None
MB/s 200 220 230 250
Product description
As latency increases, the performance (IOPS and throughput)
decreases.
All of the performance tests were performed in environments
with a Bit Error Rate (BER) of 0 and no packet loss.
The term parallelism refers to the number of active I/Os in the
HBA queue. A parallelism value of 128 means that the queue
depth of all host HBA ports is at least 128, and there are 128 I/Os
total in the queues at all times.
Note: Parallelism is similar to queue depth, but not entirely identical.
Although a queue handles I/Os according to its depth, the queue may
not be full at all times. This means that if the queue depth is 128, but the
queue is not full at all times, the throughput and IOPS values will be
lower than when a parallelism of 128 is used. Also, the queue depth
denotes a depth per HBA port and parallelism denotes the sum of all
HBA ports.
In Table 9 and Table 10, a Fibre Channel distance of 100 km
represents 0.5 ms of latency.
Since RecoverPoint uses a SCSI protocol, each write makes two
round trips. Therefore, when replicating to a physical distance
100 km away, a write would experience 1ms of latency in a round
trip, and this would be performed twice to complete a full SCSI
write, meaning 2 ms of latency in a full round trip.
The local storage latency is also a factor in performance. All of the
performance tests were performed on ideal storage. Add
approximately of the storage latency to the latency values for
9
Product description
the exact performance statistics. For example, if the average
storage write latency is 2 ms, add 0.5 ms to the latency values in
Table 9 and Table 10.
I/O accelerators provide a significant improvement in performance
when replicating synchronously. Therefore, their usage is highly
recommended for synchronous replication. Refer to the ESM for
supported I/O accelerators.
Performance of regular groups set to replicate synchronously
The following performance statistics are available for regular
(non-distributed) groups set to replicate synchronously:
Average sustained IOPS per RPA, according to one way latency,
write size, and parallelism
Average sustained throughput (MB/s) per RPA, according to
latency, write size, and parallelism
Table 9 Average sustained IOPS per RPA, according to one way latency, write
size, and parallelism
Write Size (KB) Parallelism
Latency (ms)
0 0.25 0.5 1 2 4
0.5 128 11,500 10,000 9,000 7,500 5,000 3,000
8 128 7,600 7,000 6,400 5,700 4,500 2.500
Table 10 Average sustained throughput (MB/s) per RPA, according to latency,
write size, and parallelism
Write Size (KB) Parallelism
Latency (ms)
0 0.25 0.5 1 2 4
8 128 60 55 50 45 35 20
64 128 80
a
80
a
80
a
80
a
75 45
64 20 80 75 70 65 50 20
a. RPA throughput is limited to 80 Mb/s, and therefore, in some cases, the RPA will be the limiting factor.
For a higher throughput rate, use distributed consistency groups (see Performance of distributed
groups set to replicate synchronously on page 10).
Product description
Performance of distributed groups set to replicate
synchronously
The following performance statistics are available for distributed
groups set to replicate synchronously:
Average sustained IOPS per number of RPAs, with different
splitters
Average sustained throughput (MB/s) per number of RPAs
Configuration limits
RecoverPoint 3.4 and later is supported on 64-bit RPA platforms only.
Table 13 on page 10 lists the RecoverPoint 3.4 releases supported
across RPA hardware types.
EMC will continue to support existing configurations of RPA
hardware platforms running earlier versions of RecoverPoint.
Table 11 Average sustained IOPS per number of RPAs, with different splitters
Total Number of RPAs KDriver SANTap Brocade VNX/CLARiiON Symmetrix
a
2 17,500 11,000 16,500 16,000 17,500
4 17,500 11,000 16,500 16,000 17,500
Table 12 Average sustained throughput (MB/s) per number of RPAs
2 RPAs 4 RPAs
MB/s 130 150
Table 13 RecoverPoint releases support across RPA hardware types
RPA hardware 3.4 and later
Dell PowerEdge 1950 phase 2 (Gen1) or Dell PowerEdge 2950 phase 2 Not supported
Dell PowerEdge 1950 phase 3 (Gen3) or Dell PowerEdge 2950 phase 3 Supported
a
Dell PowerEdge R610 (Gen4) Supported
a
Legacy hardware (such as the IBM xSeries 336) Not supported
11
Product description
Break/fix support EMC will handle break/fix activity for the following RPA hardware
platforms purchased through Direct Express and Channel Express:
Gen1
Gen3
Gen4
Dell will handle break/fix activity for R610 RPA hardware platforms
purchased through EMC Select. Turn to your hardware vendor for
legacy hardware break/fix activity.
SAN support Table 14 on page 11 lists SAN support across RPA hardware types.
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 15 on page 11 lists the general configuration limits for the 3.4
and later releases.
a. When using a mix of Gen4 and Gen3 RPAs, it is highly recommended to
configure Gen4 RPAs as RPA 1 and RPA 2 (site control RPAs) to improve system
function and performance.
Table 14 SAN support across RPA hardware types
RPA hardware 1 Gb/s SAN 2 Gb/s SAN 4 Gb/s SAN 8 Gb/s SAN
Gen3 Supported Supported Supported Not supported
Gen4 Not supported
a
Supported Supported Supported
a. No support for basic connectivity of Gen4 in 1 Gb/s SAN.
Table 15 General configuration limits (Sheet 1 of 5)
Parameter RecoverPoint 3.4 and later
Supported operating
systems
RecoverPoint/CL: Heterogeneous
RecoverPoint/EX: Heterogeneous
RecoverPoint/SE: Windows Server 2000/2003/2008 and
heterogeneous with VNX/CLARiiON splitter
Refer to the EMC Support Matrix for details.
Product description
Supported storage
arrays
RecoverPoint/CL: Heterogeneous (EMC and non-EMC)
RecoverPoint/EX: VMAXe series, VNX series, CLARiiON CX3
and CX4 series, and Celerra unified
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: KDriver, Intelligent fabric (SANTap and
Brocade), Symmetrix (VMAXe only), and VNX/CLARiiON
RecoverPoint/EX: Symmetrix (VMAXe only) and
VNX/CLARiiON
RecoverPoint/SE: VNX/CLARiiON and KDriver (Windows only)
Support for intelligent
fabric switches
a
RecoverPoint/CL: Supported
RecoverPoint/EX: Not supported
RecoverPoint/SE: Not supported
Maximum capacity RecoverPoint/CL: Per license
RecoverPoint/EX: Per license
RecoverPoint/SE: 300 TB
Number of arrays RecoverPoint/CL: Unlimited
RecoverPoint/EX: Unlimited
RecoverPoint/SE: 2 in CRR or CLR (one per site), 1 in CDP
Unisphere integration RecoverPoint/CL: Not supported
RecoverPoint/EX: Supported (only with VNX/CLARiiON
splitter)
RecoverPoint/SE: Supported
Journal compression RecoverPoint/CL: Supported
RecoverPoint/EX: Supported
RecoverPoint/SE: Not supported
Dual fabric Production site - mandatory
Remote site - mandatory
Maximum number of
open RecoverPoint
CLI connections per
site (RPA cluster)
100
13
Product description
Maximum number of
open RecoverPoint
CLI connections being
set up concurrently
12
Maximum number of
concurrent
RecoverPoint GUI
sessions per site
(RPA cluster)
4
Minimum Java (JRE)
for RecoverPoint GUI
Java 6 Update 7 (32-bit)
b
Minimum supported
web browser for
RecoverPoint GUI
Internet Explorer 6.0
Mozilla Firefox 2.0
Minimum supported
screen (display)
resolution for
RecoverPoint GUI
1024x768
RPA nodes in cluster 2-8 RPAs per site
Bandwidth reduction Included
Maximum number of
SAN entities (WWNs)
seen by an RPA
256
Maximum number of
paths
c
64K per site
Recommended
minimum repository
volume size
3 GB
Minimum journal size
d
5 GB (non-distributed consistency group)
20 GB (distributed consistency group)
Maximum journal size 10 TB
Maximum number of
distributed
consistency groups
8
Product description
for distributed
consistency groups
20 GB
for distributed
consistency groups
with snapshot
consolidated enabled
40 GB
Journal configuration
for distributed
consistency groups
One 20 GB volume + optional smaller volumes
Two 10 GB volumes + optional smaller volumes
Three 8 GB volumes + optional smaller volumes
Four 5 GB volumes + optional smaller volumes
RPA MTU packet size 1,300 - 1,500 bytes
Maximum size of
replicated LUNs
2 TB (minus 512 bytes)
32 TB when using VNX/CLARiiON splitter or Symmetrix splitter
In virtual access,
maximum offset of
image in journal
1.2 TB
In virtual access,
maximum writes per
RPA
40 GB
Consistency groups in
cluster
128 (maximum 64 per RPA)
e
Consistency groups in
group set
8
f
Non-production
copies in cluster
128 - CDP and CRR
256 - CLR
Replicated source
LUNs in single cluster
2048
Maximum number of
exposed LUNs per
ESX server
255
g
LUNs per host-based
splitter
256
15
Product description
Hosts running a
splitter connected to a
cluster
60
Minimum bandwidth
for replication
3 Mb/s
RecoverPoint/CE Supported
Asynchronous
replication over FC
distance limit
Per topology as supported by eLab
Asynchronous
replication over FC or
IP latency limit
200 ms
Synchronous
replication over FC
distance limit
200 km (full round trip)
Synchronous
replication over FC
latency limit
4 ms (full round trip)
Stretch cluster
distance limit (on the
stretch side)
30 km
Maximum WAN
packet loss
1%
h
a. The Connectrix MDS-9000 family that supports SANTap running on SAN-OS
and NX-OS, and the Connectrix B-Series (AP-7600B and PB-48K-AP4-18) that
supports SAS running on FOS.
b. It is highly recommended to install the latest update for your Java version.
c. Where path is a LUN WWN seen by an RPA port. The same LUN WWN seen
from different RPA ports is counted multiple times.
d. To prevent the possible loss of all journal snapshots during a group
resynchronization, the recommended minimum journal size is 10 GB for a
non-distributed consistency group, or 40 GB for a distributed consistency
group.
e. 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
sites. 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.
Product description
SANTap scalability Table 16 on page 16 and Table 17 on page 18 list the SANTap
scalability limits for the Storage Services Interfaces (SSIs) supported
by the current platforms. SSM and MSM platforms are supported
with the same RPA cluster when both platforms are running the same
SSI and NX-OS combination. Additional information on the
parameters is available from EMC RecoverPoint Deploying
RecoverPoint with SANTap and SAN-OS Technical Notes and the EMC
RecoverPoint Deploying RecoverPoint with SANTap and NX-OS Technical
Notes.
f. More groups can be supported. Consult EMC Customer Service for setting a
minimal interval for bookmarking.
g. Number of exposed LUNs per ESX server is:
HBAs * RPAps * LUNs
where:
HBAs = number of HBA ports on one ESX server
RPAps = number of RPA ports in the host-to-RPA zone
LUNs = number of RDMP virtual disks to be replicated.
It is only relevant when replicating VMware volumes with host-based splitters
(KDrivers) running on the virtual machines.
h. RecoverPoint performance and ability to meet replication policies cannot be
guaranteed if WAN packet loss exceeds this limit.
Table 16 SANTap scalability limits on SSM (Sheet 1 of 2)
a

b
Parameter SSI
c
Notes
Hosts per DVT 64
LUNs per host
(for single DVT)
256
LUNs per DVT 3K
DVTs per SSM 64
Replicated host ITLs
(sessions) per SSM
2K All ITLs to be replicated using the SSM.
LUN ID address size
(bits)
32 Even though the LUN ID field in the Fibre Channel
protocol command frame is 8 bytes, most arrays use
the single-level peripheral device addressing
method, which means that 8 to 16 bits are significant.
DVT LUNs per SSM 16K
17
Product description
ITLs per DPP 3K There can be several types of ITLs on a DPP, and
multiple ITLs can be created for each triple of host
initiator port, storage target port, and storage LUN.
The technical notes referred to above contain
information that may be useful in planning your
configuration so that it adheres to the ITL limit.
ITLs per SSM 8K
d
12K
e
16K
f
These values are the sum of all ITLs, including host,
discovery, reservation, and control ITLs.
SSMs per RPA cluster
per fabric
4
Minimum replication
volume size
8 MB
a. Multiple SSMs per MDS director are supported, however there can only be one
CVT per back-end VSAN. Multiple CVTs per single VSAN are not supported.
b. RPA clusters can share the same SSM module, however each RPA cluster must
have its own back-end VSAN, and such a configuration requires an RPQ for
final approval.
c. 3.2(3m), 3.2(3r), 3.2(3s), 3.2(3t), 3.2(3v), 4.1(1j), 4.1(3i), 4.1(3j), 4.1(3m), 4.2(3i),
5.0.4i, 5.0.4j.
d. When using SSI 3.2(3m)/(3r) with the supported SAN-OS.
e. When using SSI 3.2(3s)/(3t)/(3v) with the supported SAN-OS.
f. When using SSI 4.1(1j), SSI 4.1(3i)/(3j)/(3m), 4.2(3i),and 5.0.4i with the
supported NX-OS.
Table 16 SANTap scalability limits on SSM (Sheet 2 of 2)
a

b
Parameter SSI
c
Notes
Product description
Table 17 SANTap scalability limits on MSM-18/4 and 9222i (Generation 2)
Parameter SSI
a
Notes
Hosts per DVT 64
LUNs per host per DVT 256
LUNs per DVT 3K
DVTs per ILC 128
Replicated host ITLs
(sessions) per ILC
2K All ITLs to be replicated using the SN.
LUN ID address size
(bits)
32 Even though the LUN ID field in the Fibre Channel
protocol command frame is 8 bytes, most arrays use
the single-level peripheral device addressing method,
which means that 8 to 16 bits are significant.
DVT LUNs per SN 16K
Host ITLs per ILC 16K
ITLs per ILC 16K These values are the sum of all ITLs, including host,
discovery, reservation, and control ITLs.
SNs per RPA cluster
per fabric
4
Minimum replication
volume size
8 MB
a. 4.1(1j), 4.1(3i), 4.1(3j), 4.1(3m), 4.2(3i), 5.0.4i, 5.0.4j.
19
Product description
Connectrix AP-7600B
and PB-48K-AP4-18
scalability
Table 18 on page 19 lists the Connectrix AP-7600B and
PB-48K-AP4-18 limits per device for the current release. Additional
information on the parameters is available from EMC RecoverPoint
Deploying with the Brocade Splitter Technical Notes.
Table 18 Connectrix AP-7600B and PB-48K-AP4-18 scalability limits for
supported SASes
Parameter
Supported
SAS
a
Notes 3.4.2
Host initiator-target
nexuses per DPC
1000 (2000)
Total virtual entities 496 (992) This value includes:
Virtual targets 1 per storage target
Virtual initiators 1 per host initiator
AVTs When reservations are
supported, 1 per each host initiator port
that has access to reserved LUNs
System VI 1 total
Replicated LUNs 2048 From among all LUNs that are exposed by
all target ports, those that represent volumes
that are attached to the splitter.
ITLs 12000 (24000) ITLs = Host ITLs + AVT ITLs
where:
Host ITLs = number of LUNs to which a
host initiator has access
AVT ITLs = RPA initiator ports x Host
ITLs (for which LUNs support
reservations)
a. When working in Frame Redirect mode, with RecoverPoint release 3.4 and
later, use of two DPCs is supported on the AP-7600B and PB-48K-AP4-18; the
values in parentheses are the limits for two DPCs. Otherwise, values are for
the use of a single DPC only. The value for Replicated LUNs is not dependent
on the number of DPCs used.
Product description
Splitter scalability The scalability limits when deploying RecoverPoint with the
currently available splitter types are as follows:
Host-based splitter (KDriver) scalability
The following limitations apply to host-based splitters:
VNX/CLARiiON splitter scalability
The following limitations apply to VNX/CLARiiON splitters:
Symmetrix splitter scalability
The following limitations apply to Symmetrix splitters:
SANTap splitter scalability
The following limitations apply to SANTap splitters:
Table 19 Host-based splitter scalability limits
Splitter type Attached LUNs per splitter
Number of splitters per RPA
cluster per site limit
Host-based (KDriver) 256 60
Table 20 VNX/CLARiiON splitter scalability limits
VNX/CLARiiON 2048 10
a
a. One splitter serves both storage processors of a VNX/CLARiiON array.
Table 21 Symmetrix splitter scalability limits
Symmetrix 2048
a
4
a. In a CDP configuration, each replication set consumes two LUNs (production
and local copy).
Table 22 SANTap splitter scalability limits
SANTap Refer to Table 16 on page 16
and Table 17 on page 18
8
a
21
New features and changes
Brocade splitter scalability
The following limitations apply to Brocade splitters:
This section lists new features and changes in RecoverPoint 3.4 and
later.
New features and
changes for
3.4 SP1 P1
There are no new features in this release.
Fixed problems
Table 30 on page 30 lists the problems fixed in this release.
New features and
changes for 3.4 SP1
RecoverPoint 3.4 SP1 includes the following features and changes:
Target product qualifications for this RecoverPoint release:
VNX series: VNX OE for Block 31 with embedded
RecoverPoint 3.4 SP1 splitter driver.
Cisco SSI 5.0.4j with NX-OS 5.0.4b
For a complete list of compatibilities, refer to the ESM.
Symmetrix splitter
RecoverPoint now supports an array-based splitter for the
Symmetrix VMAXe series platform. The Symmetrix splitter
supports all RecoverPoint functionality, except virtual image
access and virtual access with roll, and replica LUNs that are
larger than production LUNs. On every site that uses the
Symmetrix splitter, the site control RPAs (RPA 1 and RPA 2) must
be Gen4 RPA hardware platforms.
a. Maximum of 4 splitters per fabric, as long as each target port (represented by
DVT) is either handled exclusively by a single splitter or handled by several
splitters, each on a different VSAN.
Table 23 Brocade splitter scalability limits
Brocade Refer to Table 18 on page 19 8
a
a. Maximum of 4 splitters per fabric, as long as each target port is handled
exclusively by a single splitter.
Support for the VMAXe
RecoverPoint now support the Symmetrix VMAXe series
platform for local, remote, and bi-directional replication of all
block LUN types. The support includes a RecoverPoint write
splitter for the VMAXe that runs inside the Enginuity operating
environment.
Refer to the EMC RecoverPoint Deploying with Symmetrix Arrays
and Symmetrix Splitters Technical Notes, available on Powerlink, for
more information on the usage and limitations of the above two
features.
New Deployment Manager feature - Converter Wizard
Using Deployment Manager 1.0 SP3, you can now
non-disruptively convert a 3.4 SP1 or later environment to a
RecoverPoint/SE or RecoverPoint (RecoverPoint/CL and
RecoverPoint/EX) configuration.
Refer to the EMC RecoverPoint Deployment Manager Release Notes,
available on Powerlink, for more information on the usage and
limitations of this feature.
SANTap Immediate Appliance Recovery Log
The new, faster Appliance Recovery Log (ARL) mechanism
significantly reduces the number of incidents of hosts receiving
busy messages from the switch, quiescing the host. More time
may be required to resynchronize regions marked dirty by ARL
than before.
Support for RecoverPoint Adapter for VMware vCenter SRM
releases 1.0 SP3 and 1.0 SP2 P1
For more information, refer to the EMC RecoverPoint Adapter for
VMware vCenter Site Recovery Manager Release Notes.
New CLI commands
Table 24 on page 23 presents the new CLI commands in
RecoverPoint 3.4 SP1.
Modified CLI commands
Table 25 on page 23 presents the CLI commands that have been
modified in RecoverPoint 3.4 SP1.
23
Changes to RecoverPoint Management Application GUI
Table 26 on page 23 presents the changes that have been made to
the RecoverPoint GUI in 3.4 SP1.
Fixed problems
New features and
changes for 3.4 P1
There are no new features in this release.
Fixed problems
Table 24 New CLI commands in RecoverPoint 3.4 SP1
New CLI Command Feature
get_access_ids_for_symmetrix Symmetrix splitter
show_symmetrix_gate_keepers Symmetrix splitter
Table 25 Modified CLI commands in RecoverPoint 3.4 SP1
Modified CLI Command Feature CLI Modification
set_policy Symmetrix splitter Added Allow replication with
self-mirroring parameter.
Table 26 Changes to the Management Application in RecoverPoint 3.4 SP1
Element/Process Description Location
Number of exposed
LUNs
Parameter in Installation
Manager changed to Number
of VMware ITLs
Setup menu > Modify
settings > Site details
New features and
changes for 3.4
RecoverPoint 3.4 includes the following features and changes:
Target product qualifications for this RecoverPoint release:
VNX series: VNX OE for Block 31 with embedded
RecoverPoint 3.4 splitter driver.
CLARiiON series:
CX4 series: Latest CX4 FLARE 30 bundle with the latest
CX3 series: Latest CX3 FLARE 26 bundle with the latest
Brocade SAS 3.4.2 with FOS 6.4.1a.
Cisco SSI 5.0.4i with NX-OS 5.0.4
Cisco SSI 3.2(3v) with SAN-OS 3.3(4a).
For a complete list of compatibilities, refer to the ESM.
Support for file systems replication
RecoverPoint/SE now provides cabinet-level continuous remote
replication for file systems (NAS) on EMC VNX Series. See the
EMC RecoverPoint Administrators Guide for a detailed explanation
of cabinet-level replication. Refer to the Using RecoverPoint/SE
with VNX for File for Disaster Recovery document, available on
Powerlink, for more information on the usage and limitations of
this feature.
WAN deduplication
A consistency group policy has been added that enables users
using Gen4 RPAs to eliminate the transfer of repetitive data to a
remote site, saving bandwidth.
Call home events
A proactive online service capability has been built into RPAs to
enable RPAs to continuously monitor their own health and the
health of the RecoverPoint system. If a serious problem arises, the
call home event mechanism automatically opens a service request
with EMC Customer Service, enabling them to proactively
engage the relevant EMC personnel, start working with the
relevant customer parties, or use a configured ESRS gateway, to
resolve the issue, as soon as possible.
25
Event filtering
The event filtering mechanism enables creation of profiles for
filtering system events for inclusion in notifications. A single
event filter can be used with email, SNMP, and syslog
notifications.
Storage awareness
The new storage awareness mechanism enables RecoverPoint to
detect and handle high loads on storage. RecoverPoint does so by
stopping the sending of reads and writes whenever a storage
device becomes unresponsive, and then, gradually increasing the
I/O rate until the required I/O rate is achieved again. Storage
awareness is enabled by default and should not be disabled
unless specifically asked to do so by EMC Customer Service.
I/O throttling
The new I/O throttling mechanism enables users to limit the
storage read-rate during initialization, allowing the production
storage to handle the I/O rate. When enabled, the read-rate of all
RPAs in your RecoverPoint cluster is limited to 200 (low) / 50
(high) MBps, per storage array. I/O throttling is disabled by
default and can be enabled using the config_io_throttling
RecoverPoint CLI command.
Enhanced within-site communication
To further improve high-availability of RecoverPoint, within-site
communication between RPAs is also done over the local Fibre
Channel connection, in addition to the existing LAN and WAN
connections.
Ability to configure RPA Ethernet auto-negotiation
The Ethernet speed (in Mb/s) of an RPAs WAN and LAN
interface can be modified to ensure that the management traffic
does not exceed a certain transmission rate.
For more information, refer to the Installation Manager chapter
of the EMC RecoverPoint Deployment Manager 1.0 Product Guide.
Bandwidth limitation warning
A warning has been added to the RecoverPoint system to inform
users of the implications when groups running on the same RPA
are configured with and without bandwidth limitations.
RPA clock sync errors
Two new errors have been added to the RecoverPoint system in
order to inform users when an RPAs clock is out of sync (and
back in sync) with the local clock or the NTP server (if an NTP
server has been defined by the user).
Enhanced support for VMware
From SSI 5.0(4j), SANTap splitter correctly rejects VMware
VAAI SCSI commands. This is also true for SSI 4.2(3k) and
later in the 4.2 series.
Brocade splitter now correctly rejects VMware VAAI SCSI
commands.
Cisco enhancements
Stale ITL handling
Stale ITLs are created when the connection to a LUN is lost.
RecoverPoint now automatically ends the session as soon as
the connection to a LUN is lost, allowing the SANTap services
to remove the stale ITL. There might be some performance
improvement in removing stale ITLs.
Time stamps in SANTap exceptions log
Logs from SANTap switch will now include a timestamp, to
allow easier correlation with other RPA system logs.
Disabling and enabling Brocade bindings
This feature is intended for use only by EMC customer service for
troubleshooting. RecoverPoint now allows you to disable and
enable Brocade bindings, rather than adding and removing
bindings. The corresponding commands do the same thing,
except that disable_brocade_bindings retains the information
about the binding pairs in the settings and in the GUI. This allows
you to use enable_brocade_bindings without having to
remember each pair of initiator and storage WWNs. In addition,
the zoning database aliases are displayed next to the binding,
allowing you to manage bindings by host and storage name
rather than by WWN. This feature is disabled for safe bindings.
Support for RecoverPoint/Cluster Enabler 4.1
Support for IBM AIX 6.1 host-based splitting
27
Support for RecoverPoint Adapter for VMware vCenter SRM
releases 1.0 SP3 and 1.0 SP2 P1
For more information, refer to the EMC RecoverPoint Adapter for
VMware vCenter Site Recovery Manager Release Notes.
New CLI commands
Table 27 on page 27 presents new CLI commands in this release.
Modified CLI commands
Table 28 on page 28 presents CLI commands that have been
modified in this release.
Changes to RecoverPoint Management Application GUI
Table 29 on page 29 presents changes that have been made to the
RecoverPoint GUI in this release.
Fixed problems
Table 27 New CLI commands in RecoverPoint 3.4
New CLI Command Feature
create_event_filter Event filtering
edit_event_filter Event filtering
get_event_filter_settings Event filtering
remove_event_filter Event filtering
add_email_users Event filtering
get_email_users_settings Event filtering
remove_email_users Event filtering
config_splitter_policy Configures the policy for the specified splitter at the
specified site.
disable_brocade_bindings Disables Brocade bindings while retaining the binding
information.
enable_brocade_bindings Enables Brocade bindings that were disabled.
get_ssh_keys VNX support
get_call_home_events Call home events
Table 28 Modified CLI commands in RecoverPoint 3.4
Modified CLI Command Feature CLI Modification
create_alert_rule Event filtering Command removed.
config_snmp_traps Event filtering Changed command name to config_snmp. Removed
trap_level parameter, added event_filters parameter.
get_snmp_settings Event filtering In output, removed Trap level field, added Event filters field.
config_syslogs Event filtering In output, removed Trap level field, added Event filters field.
get_syslog_settings Event filtering In output, removed Level field, added Event filters field.
disable_alerts Event filtering Changed command name to disable_email.
enable_alerts Event filtering Changed command name to enable_email.
test_alerts Event filtering Changed command name to test_email.
get_logs Event filtering Changed command name to get_events_log. Added
excluded_events parameter.
get_alert_settings Event filtering Command removed.
get_splitter_settings RecoverPoint/SE converter
wizards
Added Auto-register RPAs initiators field to display class of
splitter settings output.
get_system_settings RecoverPoint/SE converter
wizards
Added During RPSE Conversion option to the Maintenace
Status optional field.
start_upgrade RecoverPoint/SE converter
wizards
Added rpse_conversion to the mode parameter.
remove_ssh_key VNX support Added ability to run non-interactively.
add_ssh_key VNX support Added ability to run non-interactively.
set_policy Deduplication Changed values of compression parameter from none / 1 -
10, to none, low, medium and high.
Added deduplication parameter, with values of yes / no.
config_io_throttling Auto-throttling Changed max_rate parameter name to throttling.
Changed values of throttling parameter from integer /
unlimited to none / low / high.
Added storage_aware parameter, with values of yes / no.
29
Table 29 Changes to the Management Application in RecoverPoint 3.4
Element/Process Description Location
Event filtering Reorganized the System Settings menu to contain the
Events Filter option, which opens the Events Filters
window (for creating, editing, and removing event filters).
When the Events Filter option is expanded, it provides
access to the Emails, SNMP, and Syslog options.
Select System Settings > Event Filters
from the System menu.
Event filtering Added the excluded events to the parameters for the Log
Filter command.
With the events log displayed, click the
Log Filter button to adjust the
parameters for filtering the events to be
displayed in the events log.
Event filtering Changed Log button (in top right corner of Component
Pane) to Event Properties; it now opens the Event
Properties (rather than the Details) dialog box.
Open the events log, and highlight an
event in the log; then click the Event
Properties button.
Enable/Disable Brocade
bindings button
Allows user to disable and enable Brocade bindings without
loosing the binding information.
Attached volumes area of the Brocade
splitter dialog box
Compression section The Compression section has been renamed to
Bandwidth Reduction.
Group Policy tab
Compression level
setting
The Compression level setting has been renamed to
Compression.
Group Policy tab > Bandwidth
Reduction tab
Compression values The values of the Compression setting have been
changed from none / 1 - 10, to none, low, medium and high.
Group Policy tab > Bandwidth
Reduction tab > Compression setting
Compression
(Bandwidth
Reduction) section
Added Deduplication setting, with values of yes / no. Group Policy tab > Bandwidth
Reduction tab
Call Home Events Tab
in System Settings
dialog box
Added a Call Home Events Tab to the System Settings
dialog box.
Main menu > System > System
Settings > Call Home Events
Navigation tree of
System > System
Settings dialog boxes
Removed the Settings from all names of items in the
Navigation tree of the System > System Settings dialog
boxes. For example, Account Settings is now named
Account.
System > System Settings
Fixed problems
Fixed problems
Table 30 on page 30 lists the problems fixed in RecoverPoint
3.4 SP1 P1.
Table 31 on page 31 lists the problems fixed in RecoverPoint 3.4 SP1.
Table 32 on page 35 lists the problems fixed in RecoverPoint 3.4 P1.
Table 33 on page 39 lists the problems fixed in RecoverPoint 3.4.
Problems fixed in
3.4 SP1 P1
This sections presents the problems fixed in RecoverPoint 3.4 SP1 P1.
Table 30 Problems fixed in 3.4 SP1 P1 (Sheet 1 of 2)
Topic Summary
Array splitter
specific
[26282] 3.4 SP1 and later
Using a Symmetrix splitter, when attaching a volume that was in write
disable, replication will not start.
Workaround: Change the device mode to write enable.
Array splitter
specific
Using a Symmetrix splitter, a consistency group will be unable to replicate
and devices may remain read-only in the following scenario:
1. Device belongs to cluster A.
2. Try to attach the device to cluster B.
3. The attach fails due to device belonging to another cluster.
4. User tries to detach but splitter doesnt complete detach.
5. User detaches from cluster A.
6. User re-attaches device, but device is already marked as belonging to
another cluster. Splitter cant change this resulting consistency group
failure.
Workaround: Reformat repository volume.
Array splitter
specific
Before adding a Symmetrix splitter to your environment, certain
operations must be performed on all RPAs. Contact EMC Customer
Service for assistance.
After performing the operations, the following limitation applies:
the splitter is not supported in a CLR configuration where one copy is in
replicating synchronously and one copy is replicating asynchronously.
31
Fixed problems
Problems fixed in
3.4 SP1
This section presents the problems fixed in RecoverPoint 3.4 SP1.
Array splitter
specific
Using a Symmetrix splitter, in various scenarios involving failure of control
commands from splitter to array, fully functional devices whose relevant
consistency group is replicating will show various error messages.
Workaround: None, however, you can ignore the error messages.
System [26279] When running the detect_bottlenecks CLI command, or viewing
the consolidated statistics output, RPO statistics are missing from the
output. Workaround: Contact EMC Customer Service.
Table 30 Problems fixed in 3.4 SP1 P1 (Sheet 2 of 2)
Topic Summary
Table 31 Problems fixed in 3.4 SP1 (Sheet 1 of 5)
Topic Summary
Host OS
specific
[24481] Attempting to install an AIX host-based splitter on a mounted file
system will not succeed, as indicated by SAN diagnostic errors received
during installation. The AIX host might not boot or the KDriver will not load
on next reboot. Note: KDriver logs can be mounted on another file system.
Host OS
specific
[23576] When using a host-based splitter (KDriver) in a Windows
environment, and there are no LUNs attached to the splitter, if you
configure the consistency group to boot from SAN (shadow host) and then
remove the configuration, the splitter will not start.
Workaround 1: Install new version of KDriver.
Workaround 2: Remove the registry key manually with regedit (very risky).
Installation [25171] In the Installation Manager (boxmgmt), if an RPA has fake
(spoofed) WWNs and you want to restore the default (original) WWNs, you
cannot restore them by leaving the WWN fields blank or empty.
Workaround: Retype the original WWNs to restore them on the RPA.
Intelligent
switch
specific
[26036] In a Brocade splitter environment, any scenario involving change
the target RPA for replication (flipover) will cause an inconsistency.
Workaround: Perform a volume sweep.
Intelligent
switch
specific
[25844] In a Brocade splitter environment, the splitter may become
unresponsive and replication may stop when there are aborted slow path
commands (such as storage or RPA not responding). High number of ITLs
increases probability of leaks. The issue is exposed faster when AVT
support is on, as parallel SAN discovery (introduced in 3.4) increases the
rate of slow path commands sent to the splitter.
Fixed problems
Intelligent
switch
specific
[24308] When using a SANTap splitter, large scale configuration changes
(for example, enabling a large number of consistency groups at one time)
may cause a temporary pause of replication and the splitter may become
unresponsive (uncontrollable) for several minutes.
Workaround: Split big configuration changes into several small
configuration changes (for example, enabling a small number of
consistency groups at a time).
Intelligent
switch
specific
[24206] In a Brocade splitter environment, when you try to add a large
number of bindings at the same time, the bindings are not added. The
splitter process freezes and eventually crashes.
Workaround: Add the bindings in small groups and not all together.
Intelligent
switch
specific
[24149] In a Brocade splitter environment, any scenario leading to a
prolonged volume flush operation (such as continued errors from either
target or RPA) may cause the splitter to become temporarily unresponsive.
Intelligent
switch
specific
[24146] In a Brocade splitter environment, attaching a volume in an
environment with a large total volume size to protect may cause temporary
loss of paths going through the splitter and cause the splitter to be
temporarily unresponsive. Workaround: Contact EMC Customer Service.
Intelligent
switch
specific
[24111] Using a SANTap splitter, if attaching volumes to the splitter results
in over 2048 ITLs in the splitter (ITLs associated with the new volumes
together with existing ITLs), some consistency groups may stop replicating
and go into Regulated state.
Workaround: Detach the newly added volumes from the splitter to return
to normal replication of existing consistency groups.
System [25808] When you attempt to pause on an image, image access will take
longer time than that experienced in RecoverPoint 3.3.x versions. The issue
may be more severe on consistency groups with large journal volumes.
System [25799] In the RecoverPoint GUI, if you try to add a filter for a specific LUN
using the vCenter filter dialog box, you will get an internal error message.
Workaround: Filter the entire ESX or VM that contains the LUN.
System [25740] In the RecoverPoint GUI, if you change the value in the Search
Base Distinguished Name field in the LDAP Configuration dialog box, the
change is not saved by the system. As a result, LDAP connectivity will fail.
Workaround: In addition to changing the Search Base Distinguished
Name field value, change another field value and then save the changes.
All changes will then be saved.
System [25622] If a consistency group has more than 1600 replication sets, RPAs
may enter reboot regulation.
Workaround: Split the consistency group into smaller consistency groups.
Topic Summary
33
Fixed problems
System [25527] In the RecoverPoint GUI, if you select a point-in-time image and do
not specify a time deviation, you will fail to find the image. This is because
the system interprets the deviation value of 0 to mean only the exact
image can be found.
Workaround: Specify a deviation value instead of leaving it as 0.
System [25401] When attaching volume to a splitter during writes, over-complete
writes may occur. An event about over-complete writes will occur.
Workaround: Stop writes before attaching volume to splitter.
System [25378] In the RecoverPoint GUI, if you configure automatic snapshot
consolidation with the value of indefinitely in any time interval (daily, weekly,
or monthly), the consolidation policy change will fail with the message
Snapshot consolidation policy times should be increasing.
Workaround: Configure the automatic snapshot consolidation using the
RecoverPoint CLI.
System [25168] In the RecoverPoint GUI, if the time on the RPA was changed
(moved backwards), it is possible that when you try to enable image access
on a snapshot created after the time on the RPA was changed, you will
access a different snapshot instead (a snapshot with a similar time stamp).
Workaround: Use the RecoverPoint CLI to access the correct snapshot.
System [24977] If a user-initiated integrity check occurs during host I/Os to a
non-distributed group, it might cause an initialization for all groups handled
by the RPA the issue occurs on, including groups handled by its peer and
replicating to this RPA. This initialization is for the I/Os written in the prior 20
minutes.
System [24900] When you try to access another image (GUI or CLI) while system is
in image access mode, the consistency group copy will remain on the same
image and will not move to the requested snapshot. That is, while the GUI
reports the old image as the image in access, the system does not change
the snapshot in access.
Workaround: Disable image access and only then access the new image.
System [24678] If the process that runs site control crashes, or the RPA that runs
site control reboots, all CRR consistency groups will perform a short
initialization.
System [24516] In the Getting Started Wizard of the RecoverPoint GUI, changes
that you make to account settings in the Account screen (such as Software
Serial ID) will not get updated in the system settings.
Workaround: After completing the Getting Started Wizard, change the
account settings in the Account tab of the System Settings dialog box or in
the RecoverPoint CLI.
Topic Summary
Fixed problems
System [24646] When an event regarding a volume occurs, the name of the volume
in the event may be displayed incorrectly in the GUI (name may be empty
or display the old consistency group/copy name).
System [24643] Running the RecoverPoint CLI command test_snmp will cause the
CLI to stop working. Workaround: Contact EMC Customer Service.
System [24642] When using the RecoverPoint Installation Manager (boxmgmt) to
run the internal commands ping, ping6, or telnet for a domain name,
the ping and ping6 commands will fail with an unknown host message,
while the telnet command will fail with a temporary failure in name
resolution message.
Workaround: To check for IP connectivity, enter a literal IP address instead
of the domain name. To check if DNS resolution is working correctly, run the
ssh internal command.
System [24440] In the Management Application GUI, if you remove and add the
same volume in the Volumes Configuration dialog, an error message will
appear, even though you didn't actually change the volumes configuration.
Workaround: Ignore the error message.
System [24392] If you try to collect system information (logs) from splitters from an
RPA that is not RPA1 or RPA2, the collection will fail with the message,
Internal error: Failed to retrieve splitter details from server.
Workaround: Collect splitter logs from RPA1 or RPA2.
System [24337] In a RecoverPoint/SE environment, when trying to add a volume in
the Volumes Configuration dialog, the Select Volume dialog view will be
empty. Workaround: Use the Add/Edit Journal Volumes Wizard for
handling journal volumes and the New Replication Set Wizard for creating
replication sets.
System [24136] Attaching new volumes to splitters (when creating a new group,
replication set, or manually attaching a volume to a splitter) fails and the
error message Error: Maximum number of LUNs exceeded is issued.
Happens if user excessively removes consistency groups or replication sets
from the system without first detaching volumes from splitters.
Workaround: Format the repository volume at both sites.
System [23171] When you try to collect logs and some of the logs are too large in
size for the requested time interval, these logs will not be collected. This will
be indicated at the end of the log collection process with an error message
from one or more of the RPAs saying that the size of the logs is too large to
be collected. Workaround: Collect logs for a shorter time interval (several
hours). If this does not help, contact EMC Customer Service.
Topic Summary
35
Fixed problems
Problems fixed in
3.4 P1
This section presents the problems fixed in RecoverPoint 3.4 P1.
System [22823] Replicating locally, when an RPA has a number of consistency
groups getting writes and one group not getting writes, snapshots on the
non-stressed group will not so long as the other groups are still stressed.
This will result in not seeing snapshots (images) of the non-stressed group
in the RecoverPoint UI.
Workaround 1: Move the consistency group without writes to another RPA.
Workaround 2: Stop writes/make writes with a lower rate on the stressed
consistency groups.
System [21969] Using the RecoverPoint CLI in expert mode, running the
add_volume command when it contains invalid parameter values will cause
invalid devices to appear in system. Workaround: Ensure you enter valid
parameter values when running the command in expert mode.
System [20220] If you perform a minor upgrade (e.g. from 3.2 SP1 to 3.2 SP2 P2),
create an event that did not exist in the earlier release, then downgrade to
the earlier release, the event log displayed in the RecoverPoint GUI
Component Pane will be corrupted.
Workaround 1: Unless the event is an RPA event, format the repository
volume at both sites.
Workaround 2: Create many events that will override the problematic
event.
Topic Summary
Table 32 Problems fixed in 3.4 P1 (Sheet 1 of 4)
Topic Summary
Array specific [25623] In an environment with VNX/CLARiiON arrays, a LUN may
incorrectly appear in the UI with the name of another LUN. This will only
happen when the same LUN appears with different LUN numbers to
different ports of the same RPA (for example, if a LUN belongs to two
storage groups, each masked to different ports of the same RPA).
Workaround: Contact EMC Customer Service.
Host OS
specific
[25560] 3.3 SP2 P1 and later
Installation of a KDriver fails on Solaris 9.
Fixed problems
Intelligent
switch
specific
[24713] If you attempt to upgrade a Brocade splitter environment that has
added safe bindings which have not been approved, then the upgrade will
fail with error Failed to verify that groups are suspended.
Workaround 1: Before performing the upgrade, ensure that all safe
bindings are approved in the Brocade splitter environment.
Workaround 2: Contact EMC Customer Service.
System [25270] When failing over a large consistency group, the replication
process may crash in a loop and all the consistency groups will need to be
initialized. The probability of the problem occurring increases when using
distributed consistency groups.
Workaround: If the loop of crashes occurs, then disable and enable the
consistency group. If every initialization is a full sweep, then change the
preferred RPA of the group back and forth.
System [25002] Selecting a time zone region from the list of available time zones
regions in boxmgmt (all of the same time zone) results in another region
chosen. While the wrong time zone region (name) is displayed in the
configuration screen/message/log, the time is set correctly.
System [24945] When using consistency groups larger than 2 TB, long
initializations (such as full sweeps) can cause inconsistencies between the
replica copy and the production copy.
Workaround 1: Disable then enable the consistency group to start a new
full sweep.
Workaround 2: Split the consistency group to be less than 2 TB and use a
group set instead.
System [24926] When replicating a CRR or CLR configuration and using the
enable deduplication feature, repeated initializations may occur, possibly
leading to reboot regulation.
System [24883] When using a Symmetrix array running Enginuity code 5671 and
later, RecoverPoint may miscalculate the array serial number. As a result,
Replication Manager will not be able to use RecoverPoint to replicate LUNs
on this array. A Replication Manager error will appear with the message
Production device X is not configured in any RecoverPoint consistency
group.
System [24832] When initialization occurs of a consistency group using thin LUNs
and a CLARiiON splitter, this may lead to inconsistent data between the
production and replica copies. The probability of this problem occurring
increases when the thin LUNs are large (hundreds of TB).
Workaround 1: Work with thick LUNs.
Workaround 2: Contact EMC Customer Service to disable the support of
fast initialization in RecoverPoint.
Topic Summary
37
Fixed problems
System [24774] If a user is logged into Unisphere and changes the RecoverPoint
security level to high, then the user won't be able to perform any actions on
the RPA (such as create a new consistency group). This problem occurs
because there is no way to unlock the user that is used to log in to the RPA
from Unisphere.
Workaround: Connect to RPA using SSH as security-admin user and
return the security level to low.
System [24762] Trying to start the RecoverPoint Management Application using
https://<ip> will not succeed. Java console will show the following error
com.sun.deploy.net.FailedDownloadException: Unable to load resource:
https://<ip>/https/webstart.jnlp.
System [24730] In the RecoverPoint GUI, for a consistency group in a CDP
configuration, when you select the Measure lag when writes reach the
target RPA checkbox in the Advanced Policy settings, the value is not
updated in the policy (that is, the value does not represent the actual
settings value). Also, changing the checkbox value will cause all other CDP
consistency group policies to display the same checkbox value (although
their settings remain the same). Furthermore, if you change the Policy
settings of one of these modified CDP consistency groups, then the
Measure lag value will be applied as well, which in turn can negatively
affect performance.
Workaround 1: Before changing any policy setting on a CDP consistency
group, first check that the Measure lag checkbox value of is correct (that
is, what you set).
Workaround 2: To ensure you are definitely changing the Measure lag
value on a CDP consistency group, select and clear the checkbox first.
System [24715] During an upgrade, if you open the RecoverPoint GUI of an RPA
that has already been upgraded, and other RPAs in the cluster have not yet
been upgraded, the GUI will not show statistics for the consistency groups
that are running on RPAs that have not yet been upgraded.
Topic Summary
Fixed problems
System [24706] When working, mostly on the site control RPA and (mostly) using
RPA platforms earlier than Gen4, and when the management process
needs to send emails during high memory consumption, this may result in
one or more of the following process failures, leading to the RPA going
down:
management process (resulting in GUI freezing for a short time)
replication or control process (resulting in short initializations on the
consistency groups that run on the site control RPA, or even on all the
consistency groups)
To reduce the likelihood of this problem, consider the following actions:
change the email preferences so that less emails will be sent, upgrade to
Gen4 RPAs, consult EMC Customer Service on reducing the management
process memory consumption.
System [23802] Periodic email alerts may be sent to the postmaster (administrator
of a mail server) whenever Cron runs a script on the RPA that causes
something to be printed to the standard error. These emails contains the
subject Cron. These emails are not logged in the collected log files.
Topic Summary
39
Fixed problems
Problems fixed in
3.4
This section presents the problems fixed in RecoverPoint 3.4.
Note: Problems listed here were still known problems as of 3.3 SP1.
Table 33 Problems fixed in 3.4 (Sheet 1 of 10)
Topic Summary
Array specific [21572] If a CLARiiON array has the characters -- in its name, a
RecoverPoint error message will appear and you will not be able to collect
splitter logs.
Workaround 1: Rename the CLARiiON array.
Array splitter
specific
[24083] When using a CLARiiON splitter with FLARE R29 and later and a
consistency group with thin LUNs, initializations may continually restart.
The probability of this problem occurring increases with the number of thin
LUNs, their size, and the uptime of the RPAs.
Array splitter
specific
[23338] Using a CLARiiON splitter and a distributed consistency group,
when there are I/O reads in virtual access mode, I/Os abort the host
(deadlock in replication) and timeout messages will appear.
Workaround: Use logged access mode for distributed consistency groups
with CLARiiON splitters.
Array splitter
specific
[23114] When using a multi-cluster CLARiiON splitter and the splitter is
shared by four RPA clusters, when you create a new replication set and
attach it to the splitter, the system will not let you attach the volumes, as
indicated with the message, Error: Exceeded maximum number of RPA
clusters to which splitter may be attached.
Array splitter
specific
[22086] When using a CLARiiON splitter, virtual with roll mode, and writes
with high parallelism or hot spots, the splitter may cause application I/O
errors or cause the RPA to log out.
Workaround: Use physical access mode or don't write until roll is
complete.
Array splitter
specific
[20815] When secure files are empty, core files may be created in the
control directory when the system is verifying CLARiiON credentials (which
is normally done once per day). Secure files can be empty after running
load_settings,. In most cases, this behavior is accompanied by generation
of event 4139. Workaround: Insert CLARiiON credentials.
Host OS
specific
[22750] When using a KDriver in a Windows environment with boot from
SAN technology and attaching a volume (add replication set/enable
consistency group), replication does not start and KDriver may crash.
Fixed problems
Host OS
specific
[22143] In a Windows environment using KVSS, the kvss.log file keeps
getting larger and continues to consume disk space.
Workaround: Manually delete the kvss.log file if it gets too big.
Installation [17918] After an RPA reboots, there is a short time interval when the SSH
connection is open, but not all necessary RPA processes are up. A user
(boxmgmt) will not be able to connect to the RPA via SSH if attempted
during this time interval.
Workaround: If unable to connect, wait 30 seconds and try again.
Intelligent
switch
specific
[24430. 22945] Replication inconsistencies may occur in environments with:
SANTap splitters
Symmetrix storage
Host connected to Symmetrix FA ports without V-bit set
Consistency group that contains LUNs with IDs higher than 255 (LUN
IDs as seen by the hosts, not the RPAs)
If all of the ITLs (paths) for a LUN are over LUN ID of 255, the following
message will appear in the GUI, WARNING: Copy contains volumes that
are not seen by any SANTap splitter: [RSet details here]. If part of the ITLs
are with LUN number that is 255 or lower, then no warning will appear, but
replication inconsistencies may happen.
Workaround: Move all replicated LUNs to LUN IDs of less than 256.
Intelligent
switch
specific
[24122] A replication volume may seem to be consistent for 24 hours after
an upgrade, when in fact the replication volume will be inconsistent and
may cause a full sweep. The problem will occur in the following scenario:
- System is running release 3.2.SP2 or earlier
- A SANTap splitter environment
- The storage configuration is changed without disabling a consistency
group
- A non-disruptive upgrade is performed to release 3.2.SP3 or later
Workaround: Immediately after the upgrade, run the RecoverPoint CLI
command refresh_santap_view. RecoverPoint will identify the storage
configuration change and do a full sweep (if necessary).
Intelligent
switch
specific
[24007] When using a SANTap splitter and SSI 4.2(3i)/(3j)/(3k), there is a
memory leak in the SANTap process that will cause the splitter to become
unresponsive (unknown) and the intelligent fabric module to reload. This
will result in momentary path failures in hosts. Under some circumstances,
this may require volume synchronization.
Topic Summary
41
Fixed problems
Intelligent
switch
specific
[23045] Using a Brocade or SANTap splitter, when different hosts use
reservations and rapidly access the same LUNs in image access mode,
RecoverPoint takes an excessively long time to manage RecoverPoint and
host-to-storage paths. As a result, host-to-storage operations may time out,
enabling image access mode may fail in RecoverPoint, and consistency
groups may enter a regulated state. The problem has been observed with
ESX clusters, but may also occur with any active-active cluster.
While fixes made in RecoverPoint 3.1 SP1 P1 significantly reduce the
probability of this problem from occurring, the problem may still occur in
very large scale environments.
Intelligent
switch
specific
[22622] When using a SANTap splitter, RPAs may be unable to access a
volume if the limit on AVT initiators has been reached by WWNs of other
RPAs. This problem may occur when physical paths are unavailable and
requires use of AVT paths (e.g. reading from a reserved volume).
Workaround: Change zoning with AVTs so that only one WWN per RPA
port is zoned with each AVT.
Intelligent
switch
specific
[22508] Using a SANTap splitter, adding a volume when switch is in an
error state may cause an operation to be terminated midway. When the
operation is automatically retried by RecoverPoint, it may cause the RPA
control process to crash.
Intelligent
switch
specific
[22022] Using a SANTap splitter, if logged access is used on an RPA, there
may be I/O errors in logged access, the splitter state may change to
unstable, and the consistency groups may enter regulation.
The probability this problem will occur is greater when:
the queue depth of the writes is high (high-parallelism).
other consistency groups are in transfer and using the same RPA.
Workaround: To lower the probability of this problem, use a different RPA
for the logged access or lower the queue depth of the host.
Intelligent
switch
specific
[21945] When using a Brocade splitter and attempting to add Brocade
bindings, the operation may fail.
Workaround: Retry the operation. If it fails, try to add one binding at a time.
If the problem persists, contact EMC Customer Service.
Intelligent
switch
specific
[21417] When using a Brocade or SANTap splitter with reservation support
and a CLARiiON array, registration of host initiator with Compaq TRU64
initiator type results in display of San Diagnostics error requesting
CLARiiON-Open type. However, since Compaq TRU64 is a valid initiator
type, this error can be ignored.
Topic Summary
Fixed problems
Intelligent
switch
specific
[18802] Using Brocade and McData switches, a change in the Brocade
splitter configuration (such as consistency group enable/disable) may
cause the relevant hosts to lose paths to the storage.
Workaround: Reboot the relevant hosts.
System [24987] In large scale environments (such as one with numerous
consistency groups or volumes), short initializations may occur to some of
the consistency groups. The RecoverPoint GUI may disconnect and event
3035 (An internal process restarted, starting control process) may also
appear.
System [24553] The RPAs Tab of the Component Pane incorrectly shows
Connectivity is OK (green checkmark) for an RPA even when the FC
connectivity is down (as correctly shown with a red x in the RPA
Properties dialog of the RPA).
Workaround: Open the RPA Properties dialog of the RPA to see if the FC
Connectivity status is OK or not.
System [24307] In the RecoverPoint GUI, commands related to the vCenter
Servers are grayed out in the vCenter Servers view in the Navigation
Pane.
Workaround: Perform the commands from vCenter Servers view using the
buttons in the Component Pane.
System [24302] When enabling image access in a boot from SAN configuration, a
loop of assertions in replication will cause reboot regulation.
System [24249] When using a distributed consistency group and in virtual with roll
mode, when the roll completes replication, the replication process may fail,
cause an inconsistency, or both.
Workaround: Don't use virtual with roll mode for distributed consistency
groups.
System [24231] When using a distributed consistency group and in virtual with roll
mode, when the roll completes replication, the replication process may fail,
cause an inconsistency, or both.
Workaround: Don't use virtual with roll mode for distributed consistency
groups.
System [24040] When using a SANTap, Brocade, or KDriver splitter and using
virtual access with role mode, the remote copy hosts may experience SCSI
errors and lose access to the volumes. If a copy enters regulation state, it
will stop replicating.
Workaround: Do not use virtual access with roll mode; continue using
logged access or virtual access mode instead.
Topic Summary
43
Fixed problems
System [23932] When transfer of a consistency group is started, there is a low
probability that it may enter high-load state and the RPA replication process
may fail in the following scenario:
scaled environment
RPA is stressed
there are writes to some of the consistency groups on the RPA
there are no writes to the consistency group being transferred
System [23926] Although an RPA is configured to synchronize its time with an NTP
server, the RPA clock remains non-synchronized and this might affect the
timestamps of logs, snapshots, and other RecoverPoint components that
are time-dependent. Any place where timestamps are used (logs, journal
snapshots, and so on) can be affected.
System [23504] If an Admin or SE user performs the balance_load CLI command
when using distributed consistency groups, the system will provide an
incorrect or invalid load balance scheme suggestion (either the suggested
value is incorrect or the suggested RPAs [both in primary and secondary]
won't even exist in the cluster). If the wrong suggested load balance
scheme is applied, the load won't be properly balanced across all RPAs.
System [23443] Attempting to change a certificate by manually entering the
certificate and a private key does not work (error message Internal error).
Even when trying to import the certificate by FTP, the action will not
succeed (a failure will be seen in the security tests the user performs).
System [23374] Moving multiple consistency groups in and out of image access
mode concurrently results in replication crash and RPA reboots. RPAs may
enter reboot regulation and drop from the RPA cluster, thereby disrupting all
replication. This issue only results when consistency groups in image
access mode are receiving incoming writes to the replica/DR image or
physical volume.
Workaround: All writes to the presented volume should be quiesced
before moving any other consistency group to image access mode in order
to avoid an occurrence of this issue.
Topic Summary
Fixed problems
System [23284] When installing or upgrading to RecoverPoint 3.3, 3.3 SP1, or 3.3
SP1 P1, the transfer protocol is automatically set to FTPS. In environments
that block transfer of data over FTPS, the EMC System Reports database
does not receive reports and alerts from the customer.
Workaround 1: In the Management Application GUI, set the System
Reports transfer method to SMTP, as described in the EMC RecoverPoint
Administrators Guide.
Workaround 2: Unblock the transfer of data over FTPS by ensuring that
ports 989 and 990 are open, and then running a signed script, which is
available from EMC Customer Service.
System [23230] When a consistency group is configured for synchronous
replication or dynamic sync mode, and is defined with a WAN compression
level that is not None, replication may crash due to lack of memory, causing
a short initialization for groups that are running on the specific RPA.
Workaround: Change the WAN compression level for the relevant
consistency group to None.
System [23215] In some cases, you will be unable to select a repository volume
when its LUN ID number is greater than 255.
Workaround: Change the LUN ID number of the chosen repository volume
to be lower than or equal to 255.
System [23175] When the memory limit of the installation server is exceeded, you
will not be able to access the Installation Manager (boxmgmt) or perform a
boxmgmt command. You may see a message such as Cannot connect to
server or Out of memory.
System [23096] In a RecoverPoint/SE environment, clearing the CLARiiON splitter
credentials will cause the control process to crash and the site control to
change. Workaround: Do not clear the CLARiiON splitter credentials.
System [22814] Using a distributed consistency group, when the group is closed
and then re-opened its state may be aggregated wrongly and cause
replication assertion.The groups running on the RPA which had its
replication process restarted will perform a short initialization.
System [22780] After an RPA reboots, the time may drift (go back) on the RPA.
When this happens, the RPA may enter reboot regulation because of a
wrong calculation of previous reboots.
Topic Summary
45
Fixed problems
System [22774] If the production volume has a very long delta marking stream
(probably due a lot of time without transfer) and then you remove a
replication volume, this may trigger a full sweep and journal loss on the
consistency group.
Workaround: If group transfer was paused for a long time, do not remove
the replication volume. Remove the replication volume only after the
consistency group is in transfer and completed initialization.
System [22771] When using a distributed consistency group, if one of the group
copies is stuck, replication of the group is terminated. In a SANTap
environment, this may also cause a full sweep.
Workaround: To prevent the full sweep in a SANTap environment, do NOT
use the following configuration for distributed consistency groups:
1. The primary RPA is RPA1, and RPA2 is one of the secondary RPAs.
2. The primary RPA is not RPA1, and RPA1 is one of the secondary RPAs.
System [22701] When using distributed consistency groups and replication is
terminated during non-consistent init (one-phase distribution) mode, one or
more distributed consistency group copies may become stuck in
Recovering state and stop replicating.
Workaround: One at a time, reboot the target side RPAs that handle all
copies for this distributed consistency group. When the RPA that handled
the stale copy comes up, the status of the distributed consistency group
should change from Recovering to Initializing.
System [22581] Replication operation may be disrupted in environments with:
intelligent fabric splitter
host that performs reservation
distributed consistency group
storage that doesnt support penetration (this requirement is not
necessary in 3.3)
On environments with SANTap splitters, initialization may take too much
time. On environments with Brocade splitters, initialization fails (periodically
starts, progresses, pauses, and restarts). If the host sends reservation after
the initialization ends (during regular replication or target-side processing),
disruptions to replication operation may be experienced, which may cause
events in the GUI.
Workaround 1: Upgrade to a version with a fix.
Workaround 2: Convert the problematic distributed consistency group into
a non-distributed (regular) consistency group.
Workaround 3: If running RecoverPoint version 3.3 and the storage array
supports reservation penetrations, upgrade to RecoverPoint 3.3.SP1 or
later.
Topic Summary
Fixed problems
System [22523] If a user modifies a splitter configuration (such as attaching
volumes or changing credentials) at the same time the system is passing
site control to another RPA, the RPA may reboot.
System [22484] An event (4305) stating that the target storage is too slow to handle
the distribution process may appear when there is actually no problem. The
event has a higher probability of appearing when there are no writes. Also,
the event won't appear in the GUI when it should appear, or as an
exception when running detect_bottlenecks CLI command.
Workaround: You can ignore the event if it appears.
System [22443] In the following scenario:
Using one of the following splitters: CLARiiON, host-based (KDriver), or
Brocade
Environment has both Gen1 RPAs and Gen3/Gen4 RPAs
An RPA warning will appear in the format WARNING: Different number of
paths to RPAs: 4 paths to RPA<x>; 2 paths to RPA<y>. Verify that zoning is
configured so that number of paths to each RPA is the same.
Workaround 1: If using a version earlier than 3.3 SP2, ignore warning if all
RPAs with 4 paths are Gen3/Gen4 and all RPAs with 2 paths are Gen1.
Workaround 2: If using version 3.3 SP2 and later, contact EMC Customer
Service.
System [22270] When attempting to collect logs (system information), if the
computer's clock is not set correctly and you select the default time interval,
the system will get a wrong start and end time. In this case, the log
collection may fail or data will be collected, but from the wrong time interval.
Workaround: Set the clock according to the real time.
System [22155] This issue occurs in high load, large scale, and slow target storage
environments. Deadlocks occur due to the pause of transfer (close pipe),
when a few deadlocks occur at the same time, replication process
mishandles them and freezes. Control process then restarts the replication
process. Since consistency groups move to other RPAs because they
cannot work on this RPA, it may lead to close pipe on the next RPA, which
may lead to the same issue on multiple RPAs.
Workaround: Pause transfer for all consistency groups on the RPA, wait a
few minutes to let the system stabilize, and resume transfer.
System [22150] In the RecoverPoint GUI, when the journal incoming rate is very
small (no writes for a long time), the Predicted Protection Window will
become very large, and the system will nullify it to zero.
Workaround: Ignore the events predicting the protection window, or
disable/remove the consistency group if there are continuous no writes to it.
Topic Summary
47
Fixed problems
System [22076] Adding replication volumes during initialization of a distributed
consistency group causes replication process to crash.
Workaround: None, however system will automatically recover.
System [21995] When running the balance_load CLI command, in some cases the
report headline will state Action may be necessary when in fact the
environment is not stable and the headline should state Action is
necessary. The rest of the report data is correct.
Workaround: When the report headline states Action may be necessary,
refer to the rest of the report data and apply the load balancing
recommendation.
System [21947] If an RPA sees a splitter and the site control is unable to
communicate with it for four minutes, the site control declares the splitter as
uncontrollable, the splitter state in the GUI and CLI becomes unknown, and
transfer is paused to ensure data integrity between the replica and
production. In the four minutes that it takes to declare the splitter
uncontrollable, RecoverPoint cannot detect whether or not any writes have
passed through the splitter, and the users data integrity may be
compromised.
Workaround: None, however four root cause events were added to the
system to advise users on the appropriate course of action, and the
expected system behavior, in such scenarios.
System [21881] In a scaled environment, loading a CLI script that has many
add_volume CLI commands might cause the CLI to crash.
System [21759] When using the RecoverPoint Installation Manager (boxmgmt) to
install an environment, the time zone can be selected from a display name
instead of the actual timezone ID, which might cause problems with daylight
saving in zones of the same region.
System [21520] The replication process may crash in large-scale environments
when there is a heavy write load from multiple consistency groups that run
on the same RPA.
System [21354] Even though no RecoverPoint or RecoverPoint/SE license is
installed, a system limitation message will be displayed in the GUI and CLI
saying Days until license expires.
Workaround: Ignore the limitation and install a license.
System [21163] If the WAN and LAN are on the same network, the site
management (floating) IP may stop responding.
Workaround: Remove the WAN gateway, then reboot all of the RPAs.
Topic Summary
Fixed problems
System [21132] If the journal volume gets corrupted, there is a probability that the
corruption will not be caught and replication will crash. Since the system
cannot recover until all RPAs are in reboot regulation mode, eventually the
RPA cluster will crash.
Workaround: Disable and enable the consistency group with the corrupt
journal. This will cause a full sweep and journal loss, as expected.
System [20083] In the RecoverPoint GUI, if the Collect System Information Wizard
is running and then an RPA is rebooted, the wizard will stay open
indefinitely.
Workaround: Click 'Cancel', close the wizard, and restart info collection.
System [20080] From Installation Manager (boxmgmt), you cannot set the
temporary IP when the IP type is IPv6.
Workaround: None, but setting temporary IP is optional.
System [17912, 23666] In CLARiiON splitter environments, when replication sets
are created from volumes that were recently added to storage, the new
volumes may not automatically be attached to splitters. Because the
system scans the LUNs at each site once every 30 minutes, the list of
available volumes might contain volumes that have not been automatically
attached to existing splitters, even though the corresponding LUNs were
defined and are displayed in the Navisphere GUI. In RecoverPoint/SE, this
problem is more stark, since users can manually attach volumes to splitters
only using the RecoverPoint CLI.
Workaround: Wait 30 minutes before adding newly defined LUNs to a
replication set.
System [15911] If you enter fake RPA WWNs, then you want to restore the default
WWNs, you cannot restore them by leaving the WWN fields blank or empty.
Workaround: Retype the default WWNs to restore them.
System [15026] In a remote replication environment, when site control moves from
one RPA to another, all consistency groups will perform a short
initialization. This state will be displayed in the Transfer field of the
Consistency Group Status tab in the GUI.
Topic Summary
49
Environment and system requirements
Environment and system requirements
Generally, all RecoverPoint hardware and software components are
installed by EMC Customer Service personnel. Specific requirements
by both EMC and the customer are expected to be addressed before
the equipment is shipped to the customer site.
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 (ES).
Powerlink 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 Powerlink:
1. Go to Powerlink.
2. Enter the following text in the Search box and click Search:
EMC software release end of service life
3. Find the EMC Software Release and End of Service Life
Notifications document in the results.
4. 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 releases 3.4 and later have the following limitations:
When using distributed consistency groups in iSCSI
environments, there can be a maximum of two RPAs per RPA
cluster, unless Fibre Channel switches are used.
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, appliance,
management, and WAN 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 the mixing of splitters within the same
RPA cluster at the same site, subject to the following limitations:
Mixing of Cisco SANTap and Brocade SAS fabric-based
splitters within the same RPA cluster at the same site is not
supported.
Each volume can be attached to only one splitter type.
All volumes that belong to a given consistency group of a
given copy must be attached to the same type of splitter. For
example, for volumes of the same consistency group on the
same copy, you cannot attach some volumes to a host-based
splitter and others to a SANTap splitter.
Note: VNX splitters and CLARiiON splitters are considered the same
type of splitter.
51
Note: There are no limitations regarding the mixing of splitters across
separate RPA clusters or sites. For instance, CRR replication can take
place between a site that uses Cisco SANTap splitters and a site that uses
Brocade SAS splitters.
RecoverPoint supports thin provisioning on all EMC arrays and
on Hitachi arrays only.
Multipath AVT 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 site may not be able to communicate with RPAs on
another site if there is a network address translation (NAT)
firewall between the sites.
The RecoverPoint Management Application GUI 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 is supported for CRR configurations only.
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.
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 1024
snapshots (images) are presented.
VMware ESX replication capabilities and limitations are specified
in EMC RecoverPoint Replicating VMware Technical Notes.
When using Symmetrix splitters:
The splitter can be shared by up to six RPA clusters.
On every site that uses the splitter, the site control RPAs (RPA
1 and RPA 2) must be Gen4 RPA hardware platforms.
Symmetrix array and Symmetrix splitter limitations are
specified in the EMC RecoverPoint Deploying with Symmetrix
Arrays and Splitter Technical Notes.
Virtual access is not supported by hosts running Linux OS.
When using VNX/CLARiiON splitters:
A pair of splitters (running on the same array) can be shared
by up to four RPA clusters.
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.
When RPAs are connected directly to Fibre Channel ports on
VNX/CLARiiON arrays in order to support iSCSI customer
hosts:
In order for the RPAs to connect to all of the Fibre Channel
ports on the array, MirrorView must not be installed on the
array.
Synchronous replication is not supported.
RecoverPoint will fail zero-fill ioctl (punch) commands, and
therefore should not be used with applications that support
these commands.
Efficient initialization of thin LUNs is achieved only when
both VNX/CLARiiON SPs are functioning normally, and
running a FLARE 29 or later bundle.
When upgrading from RecoverPoint 3.1 and later to 3.4 and
later, CLARiiON splitter credentials are not saved by
RecoverPoint, causing connectivity loss between the
RecoverPoint system and the splitters. The credentials must be
reentered to reestablish connectivity.
53
When multiple RPA clusters share a VNX/CLARiiON splitter
pair (CX3 models running R26 or later, CX4 models running
R29 or later, and VNX models running R31 and later), and are
running on the same array, each RPA cluster must have a
unique name.
Use of the Fake Sizing feature (available in RecoverPoint 3.3
SP1 and later) requires installation of FLARE R30 or later.
Unisphere only supports RecoverPoint/SE environments
using VNX/CLARiiON splitters. It does not support
RecoverPoint/SE environments using host-based splitters
(KDrivers). If you are using KDrivers, you must close
Unisphere, remove the KDrivers from the RecoverPoint/SE
environment, and reopen Unisphere to see the
RecoverPoint/SE interface.
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.
RecoverPoint intelligent fabrics support environments with
switches from a single vendor. ISL-ing of intelligent fabrics into
environments with switches from multiple vendors is not
supported, unless specifically approved by EMC prior to
purchase.
All Recoverpoint with Brocade FAP configurations that have
McData/Connectrix M-series switches within the configuration
require specific EMC approval/RPQ prior to purchase and
implementation.
RecoverPoint does not support frame redirect mode in a fabric
that contains Brocade Silkworm 3xxx switches, even if no relevant
host or target is connected to those switches.
AIX-based hosts, whether splitting is host-based or fabric-based,
are supported only when the FC SCSI I/O Controller Protocol
Device (fc_err_recov) is set to fast_fail (rather than delayed_fail).
AIX-based hosts, running SDD multipath drivers, with IBM
Shark storage, are certified for 16-bit LUNs (but not for 32-bit
LUNs), unless specifically approved by EMC prior to purchase.
In a Windows environment, following first-time initialization,
access to an image (including virtual access) is not enabled until
distribution of the initialization image has been completed.
DMP multipath drivers are supported only on active-active
storage devices.
Note: VNX/CLARiiON storage devices, which are active-passive,
support Veritas DMP only when using the VNX/CLARiiON splitter.
It is recommended to run only a single consistency group in
virtual image access mode using the same RPA.
Replication of dynamic disks in a Windows environment without
Veritas Volume Manager is not supported.
When running the Management Application GUI on a
Solaris/SPARC machine, the animated representation of data
flow in the Component pane is not displayed.
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.
The WAN deduplication feature is only supported when using
Gen4 RPA hardware platforms throughout the environment.
For Symmetrix
Enginuity versions earlier than Release Level

5772, or VNX/CLARiiON storage that is not using PowerPath,
AIX KDrivers are supported only if AIX is configured not to use
reservations.
However, AIX KDrivers are supported when running
applications that use SCSI-3 reservations, such as AIX VCS with
VVM and I/O fencing enabled.
55
Table 34 on page 55 summarizes RecoverPoint support for AIX
KDrivers when using reservation protocols other than SCSI-3.
When working in a SANTap environment, the maximum queue
depth for Emulex and QLogic HBAs should be set to 250 per HBA
port.
Microsoft VSS limitations (not specific to RecoverPoint) when
replicating a Microsoft VSS image:
When attempting to access a VSS 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.
There is a known issue in Symantec when attempting to use
VSS snapshots for Veritas Volume Manager (VxVM) based
volumes.
For VNX/CLARiiON arrays, each storage group can support a
maximum of 255 volumes. RecoverPoint can support more than
255 volumes per VNX/CLARiiON array by using multiple
WWNs and registering the RPA initiators to more than one
storage group.
The Predicted Protection window feature is not supported when
the current protection window is less than 24 hours.
Table 34 Support for AIX KDrivers not using SCSI-3
With PowerPath Without PowerPath
Standalone
host
Host in
cluster
Standalone
host
Host in
cluster
VNX/CLARiiON Supported Supported Without
reservations
Not supported
Symmetrix
5772 or later
Supported Supported Supported Supported
Symmetrix
5771 or earlier
Without
reservations
Not supported Without
reservations
Not supported
Known problems Table 35 on page 56 lists the known problems found in RecoverPoint
and RecoverPoint/SE 3.4 and later.
Table 36 on page 59 lists the known problems found in RecoverPoint
and RecoverPoint/SE 3.4 and earlier.
Where a problem is only relevant to a specific RecoverPoint release, it
is noted in the problem summary.
Table 35 Known problems found in RecoverPoint and RecoverPoint/SE 3.4 and
later (Sheet 1 of 3)
Topic Summary
Array splitter
specific
Initializations in synchronous replication mode may be slower.
Workaround While the consistency group is initializing, change the group
from synchronous replication mode to asynchronous replication mode.
When initialization completes, change the group back to synchronous
replication mode.
Array splitter
specific
Using a Symmetrix splitter, when creation of an Open Replicator
RecoverPoint session fails, RecoverPoint may pause data replication in
order to maintain data integrity.Workaround: Contact EMC Customer
Service.
Array splitter
specific
Using a Symmetrix splitter, if RecoverPoint fails to terminate an Open
Replicator RecoverPoint session, the splitter will not be able to replicate the
volume and the session state will move to verify_in_progress and from
there to failed. As a result, the consistency group will become paused on
error and replication will stop.Workaround: Contact EMC Customer
Service.
Array splitter
specific
Using a Symmetrix splitter, sometimes the splitter will only identify that the
Open Replicator RecoverPoint session moved to failed state after 10
minutes. As such, RecoverPoint may generate bookmarks which are not
valid. If a user will check consistency after a disaster, a 10 minute interval is
required before creating the bookmark. Workaround: In case of I/O errors,
wait 10 minutes for the next bookmark to be consistent.
57
Array splitter
specific
Using a Symmetrix splitter, transfer will be stuck in error and a generic
warning about Symmetrix error will appear when some replication-related
disaster (such as replication process crash in synchronous replication)
happens during failover.
Workaround: Disable/enable consistency group, or detach/attach relevant
volumes from relevant splitter, or remove relevant Open Replicator
RecoverPoint sessions from Symmetrix.
Array splitter
specific
When using Symmetrix splitters, the Description displayed in the System
Monitoring section of the Component Pane in the RecoverPoint GUI is
incorrectly labeled number of host-based splitters.
Array splitter
specific
Using a Symmetrix splitter, if RecoverPoint fails to terminate an Open
Replicator RecoverPoint session, the splitter will not be able to replicate the
volume. As a result, the consistency group will become paused on error
and replication will stop.
Array splitter
specific
Using a Symmetrix splitter, if the RecoverPoint system suffers a
communication problem (such as RPA reboot or splitter crash) while the
splitter is acting on the VMAXe array, the Symmetrix device may stay
locked. In such an event, RecoverPoint will be unable to perform actions on
the device and as a result the consistency group will become paused on
error and replication will stop.
Array splitter
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.
Intelligent
switch
specific
[24216] When using a SANTap splitter and SSI versions 4.1.x, 4.2.x, or
5.0.4i, a high-load may occur in environments containing multiple back-end
VSANs. This may result in consistency groups becoming regulated,
performance degradation, and requirement of volume synchronization.
Workaround: Work with a single back-end VSAN.
Topic Summary
System [26138] When you attempt to pause on an image, image access will take
longer time than that experienced in RecoverPoint 3.3.x versions. The issue
may be more severe on consistency groups with large journal volumes. The
image that the system will eventually pause on may be slightly later than
the one you requested.
Workaround: Best practice when attempting to pause on the latest image
is to first create a bookmark (give it a name) and then pause on it.
System [26184] When you execute the kutils SQLSnap command for SQL server
instance (clustered or stand-alone), the RecoverPoint snapshot will not be
created. Workaround: Contact EMC Customer Service.
System [26112] In the RecoverPoint GUI, you will not be able to remove an event
filter from the SNMP or Syslog pages under the System Settings menu.
Workaround: Remove the event filter using the RecoverPoint CLI.
System [26043] When you disable image access when the system is enabling
logged image access, the GUI display will change from enabling logged
access to enabling virtual access until image access will be completely
disabled by the system (state will be changed to No access).
System [25785] In the RecoverPoint GUI, whenever an event is created regarding a
group link, the copies' names in the links details may be displayed in
reverse order. Workaround: Use the RecoverPoint CLI to see the correct
order of copies' names (by getting the event from the CLI).
System [24125] In the Management Application GUI, after you remove a volume
from a copy in the Volumes Configuration dialog, the volume will appear
twice in the Select Volume dialog of the New Copy Wizard.
Workaround: Ignore the duplicate volume.
Topic Summary
59
earlier (Sheet 1 of 14)
Topic Summary
Array splitter
specific
[20608] When using a CLARiiON splitter or multi-cluster splitter, if you do
not separate the RPA cluster into different storage groups, or if you add the
same LUN to more than one storage group, you will be able to configure the
LUN as a journal volume in more than one RPA cluster. This configuration
may lead to journal corruption and/or restart and regulation of the
replication process.
Workaround: Reconfigure the storage groups correctly.
Array splitter
specific
[15405] Working with CLARiiON Splitter and domino configuration, a host
application performs I/O to RP protected LUNs and the Active CLARiiON
SP reboots. After the Active CLARiiON SP restarts, the host application
may experience I/O errors.
Array splitter
specific and
intelligent
switch
specific
[14876] In the following scenario:
VMware ESX Server environment
Non-host-based splitter (SANTap, Brocade, or CLARiiON)
RecoverPoint cluster failure on the production site
If VMware VMotion or start up of a VMware Virtual Machine (VM) is
attempted, they will stop responding and eventually fail.
Workaround: Note that the following workaround may increase the
possibility of a full sweep in environments with RecoverPoint releases
earlier than 3.0 SP1: Reduce the delay-expiry timeout to a small value,
such as 5 seconds.
Host OS
specific
[21792] Replication of EFI-labeled LUNs will not succeed and applications
might go down under the following conditions:
Using KDrivers on Solaris hosts
All LUNs above 1 TB in Solaris version prior to Sol 10, release 09/10
All LUNs above 2TB in newer Solaris versions
Any smaller LUN labeled specifically with EFI
Workaround: Change the labeling system of the LUNs from EFI to VTOC.
Restrictions:
Prior to Sol 10, release 09/10, LUN size must be smaller than 1 TB.
For newer Solaris versions, LUN size must be smaller than 2 TB.
Note: Changing the label will destroy the current data on the disk.
Host OS
specific
[16261] After installing a KDriver on a Windows 2008 host, a script that
references entries in Device Manager may not execute properly (even if
previously the same script ran without error on a Windows 2003 host).
Workaround: Ensure that the script ignores any device with the suffix
KASHYA.
Host OS
specific
[13282] When using Windows hosts, GPT-partitioned disks, and volumes
on one side that are a different size from the corresponding volumes on the
other side, RecoverPoint may be unable to access the replica image in
virtual access mode.
Workaround: Use same-sized volumes on the two sides.
Host OS
specific
[12408] In a Sun Cluster environment, if the node holding the quorum loses
all network interfaces, the other node panics, and reboots in a degraded
mode, such that the KDriver fails to come up at that node. RecoverPoint
may take up to seven minutes to declare the KDriver dead, during which
time transfer is paused by system. Once the splitter is declared dead,
transfer resumes.
Host OS
specific
[11327] RecoverPoint VSS utilities (KVSS) may not work properly on
servers running Windows Server 2003. The potential problems are avoided
by ensuring that Microsoft hotfixes 898790 and 913648 are installed.
Host OS
specific
[10787, 20012, 23260, 25994] For a consistency group running AIX hosts,
an error on that group's active RPA or its RPA fiber may cause one or both
of the following:
full-sweep resynchronization.
temporary database freeze.
Host OS
specific
[9865] When a Solaris-based or AIX-based host boots with a single path to
the RPA, a single path warning is displayed. Upon subsequent connection
of a second path, the system may fail to clear the warning for up to 15
minutes, during which time you should ignore the warning.
Host OS
specific
[9658] A host running Solaris 10 and using Subsystem Device Driver (SDD)
may be unable to communicate with the RPA after an RPA reboot. To
restore the connection, run a manual device rescan (cfgadm).
Host OS
specific
[9226] A Blue screen (Windows stop error) on a cluster server in an
MSCluster configuration running Windows 2003 can occur when
RecoverPoint reservation-awareness support is disabled for the
consistency group that contains the volumes attached to the MSCluster.
The other cluster server will not be able to bring the relevant replicated
volumes online, which it is supposed to do automatically.
Workaround:
1. In the RecoverPoint Management Application main menu, select the
group that contains the volumes attached to the MSCluster, select
Group Properties, click the General tab, and activate the Reservation
support checkbox (prevents the problem from recurring).
2. From the RecoverPoint Installation Manager, select Setup > Advanced
Options > Clear reservations.
3. Reboot the cluster server displaying the blue screen.
Topic Summary
61
Host OS
specific
[7267] If the startup type for the KDriver service on a Windows-based host
is not set to automatic (Control Panel > Administrative Tools >
Services), a replicated drive (or drives) may not be available following
reboot of the host machine (even though they may reappear after a
rescan). The KDriver initially fails I/O to the drive; however, after reaching a
timeout, it permits I/O to the drive, without splitting. To correct this situation,
you must first ensure that the service startup is set to automatic. In
addition, if there have been unsplit writes to the drive, you must initiate a
full-sweep resynchronization by, for example, using the set_markers
command.
Host OS
specific
[6675] RecoverPoint does not support USCSI in a Windows environment.
Running a USCSI command on a Windows-based host (i.e., on which a
KDriver has been installed) may result in the host writing data to storage
without also splitting it to the RPA. As a result, a full-sweep
resynchronization will be performed by the system.
Host OS
specific
[6386] Splitters installed on a Solaris host can be successfully attached
only to replication volumes that have slice 2 (i.e., a backup slice that
contains the entire disk).
Workaround: Use the Solaris format command to manually add slice 2.
Host OS
specific
[6284] For Solaris machines on which VxVM is installed but not running,
there is no automatic path selection when attaching the host to a volume.
Workaround: select the path manually.
Host OS
specific
[4647] On a VMware ESX server with multipathing, when resuming normal
operations after a path failure, the RPAs will experience a delay of
approximately 15 seconds until recognizing the paths that are now
available.
Host OS
specific
[3699] On Solaris hosts, a KDriver failure during host reboot will cause all
volumes accessible to that host to become writable. This is incorrect
behavior for volumes attached to a consistency group for which the
writes_no_marking parameter (for example, Allow application to run
when RecoverPoint cannot mark data) is not set.
Host OS
specific
[3085] On Itanium 64-bit Windows hosts, the KDriver Add/Remove icon in
Add/Remove Programs does not appear.
Host OS
specific
[2609] On Solaris hosts, disks cannot be labeled while attached to a host.
In order to modify a disk label, the consistency group containing this disk
must first be disabled and the disk must be detached from the host using
the RecoverPoint management. After labeling the disk, it can be
re-attached to the group, and the group can be re-enabled.
Topic Summary
Installation [12557] Installation may fail with various errors when trying to install as
domain administrator on a Windows Server 2008 with x64, x86, or IA-64
architecture. Workaround: Install as local administrator.
Installation [9641] In the Installation Manager, under Diagnostics > IP diagnostics >
Test throughput, the WAN interface option sometimes fails to return all
of the needed information. As an alternative means to obtain the missing
information, use the System connectivity test under Diagnostics > IP
diagnostics > System connectivity.
Installation [8483] If the events log displays the message Got a message sent by
myself, a configuration error has occurred in which two RPAs have been
installed at the same site, in conflict with the specified layout.
Installation [6153] For hosts running AIX, when working with a single switch in an
RDAC multipathing environment, each HBA and DS4000 controller
combination must be in a separate SAN zone.
Installation [4785] Exit an Installation Manager wizard with Ctrl-C. Upon re-entering the
wizard, it opens in the same context from which you previously exited using
Ctrl-C.
Installation [4440] Modifying the time zone in the RecoverPoint system requires
formatting the repository volume.
Installation [3907] The RPA is up log event includes a list of the reasons for the
reboot. After a reinstallation of the RecoverPoint system, the event still lists
reboot reasons that are from prior to the reinstallation.
Intelligent
switch
specific
[25834] When using a SANTap or Brocade splitter, if the intelligent switch is
down, RecoverPoint may not recognize this fact and as a result transfer will
be closed (transfer is Paused by system or Error, splitter is marked as
uncontrollable).
Workaround: Detach all volumes from splitter. After disaster is over, attach
the volumes as clean in smaller chunks, not all at once.
Intelligent
switch
specific
[25805] When using a SANTap splitter, attaching many volumes as clean at
once may cause volume sweeps in a scaled environment (many ITLs).
Workaround: Attach the volumes as clean in smaller chunks, not all at
once.
Intelligent
switch
specific
[23497] Using a SANTap splitter, when you save settings and then load
settings the SANTap credentials password is lost. Then, when attempting to
collect logs (system information), the log collection will fail due to an
authentication error. Workaround: Reenter the SANTap login credentials
(switch password) even though you see the *****.
Topic Summary
63
Intelligent
switch
specific
[21942] When configuring more than 2030 CDP replication sets with two or
more Brocade or SANTap splitters, the control process crashes.
Intelligent
switch
specific
[21150] When upgrading a Brocade splitter environment to 3.2 or later, the
system will fail to apply the settings because of a binding configuration
issue at one of the sites (some initiators were bound on both splitters).
Since the RecoverPoint system goes into maintenance mode, you cannot
apply settings or change them.
Intelligent
switch
specific
[17989] When using Cisco SANTap intelligent module, System Monitoring
incorrectly shows that the number of host ITLs has exceeded the system
limit, although the RPA and SANTap splitter are replicating normally. The
Cisco switch sometimes incorrectly reports the number of host ITLs
consumed.
Workaround: If correct number of host ITLs must be determined, the
module running the SANTap services should be reloaded.
Note: Reloading the module is a major operation that is generally not
recommended.
Intelligent
switch
specific
[17977] System Monitoring incorrectly shows that ITLs per DPP and/or
ITLs per module have exceeded the system limit, although the RPA and
SANTap splitter are replicating normally. The Cisco switch sometimes
incorrectly reports the number of ITLs consumed.
Workaround: If correct number of ITLs must be determined, the module
running the SANTap services should be reloaded.
Note: Reloading the module is a major operation that is generally not
recommended.
Intelligent
switch
specific
[17854] When using Cisco SANTap intelligent module and SSI 4.1(3i) and
earlier, running switch CLI command show isapi tech support santap file
<filename> fails to redirect file to a log.
Workaround 1: When using SSI 4.1(3i), run switch CLI command clear
tech-support-lock and then run command show isapi tech support
santap file <filename>.
Workaround 2: When using SSI 4.1(3i), run switch CLI commands: show
isapi tech-support, show santap tech-support, and show debug
santap event-history. Running these three commands will dump the
output to the screen.
Topic Summary
Intelligent
switch
specific
[16081] Using a Brocade splitter in frame redirect mode, when trying to add
a new switch to an existing fabric that works with No Access default zone
setting, a zone conflict occurs, even if the cfgclear command was used to
clear all zone settings on the new switch.
Workaround:
Perform these operations on the switch to be added to an existing fabric:
1. Use cfgclear command to delete the defined database.
2. If there is effective configuration, use cfgdisable command to disable the
configuration and use cfgsave command to save the cleared database.
If there is no effective configuration, use cfgsave command.
3. Set defzone --allaccess and use cfgsave command.
4. Connect the new switch to the existing fabric.
5. Set defzone --noaccess and use cfgsave command. This step is only
needed if the existing fabric does not already have no access
configured.
Intelligent
switch
specific
[13289] This problem may occur only when working with an intelligent
Connectrix AP-7600B switch or PB-48K-AP4-18 blade, in frame redirect
mode, with hosts running AIX, HP-UX, or other FCID-aware OS. Upon
binding a host initiator to a storage target, including (unbinding and) binding
that is part of a major upgrade procedure, the host loses access to the
protected storage port. Workaround: Rescan the SAN. If the host still does
not regain access to the storage, reboot the host.
Intelligent
switch
specific
[12315] In a SANTap environment, rebooting the passive controller on a
CLARiiON array may cause host I/Os to timeout, delaying host I/O flow
significantly and possibly causing application downtime.
Workaround 1: If SP reboot is planned, schedule it to a time when the host
is not performing I/Os.
Workaround 2: Disable write cache on the CLARiiON array.
Topic Summary
65
Intelligent
switch
specific
[12186] With a Solaris 10 host, running Emulex HBA and Leadville drivers,
and working in frame redirect mode with a Connectrix AP-7600B or
PB-48K-AP3-18 -- after binding the host initiators, the host loses all
connectivity with the target storage port to which it was bound. (If the host
has multipath connectivity to the storage, and only one path was bound, the
other path will still be able to access the target storage.)
Workaround:
1. On the switch to which the host is connected, run: portdisable <port id>
The port id variable is the physical switch port to which the relevant host
HBA port is connected. This shuts down the switch port. The host HBA port
loses connectivity to all storage, not just to the port to which it was bound.
2. On the switch to which the host is connected, run: portenable <port id>
This restarts the switch port, after which connectivity to the target storage
port is restored.
Intelligent
switch
specific
[9514] In SANTap-based environments, some warnings regarding
component status that are displayed in the System Status pane of the
Management Console may not be echoed in the Components Information
pane for that component, for example, in the Volumes or Splitters tab.
Intelligent
switch
specific
[8098] In a SANTap environment, if for any reason the state of a
VMware-replicated volume becomes no access (for example, the
target-side log is full, a related storage disaster has occurred), the VMware
application may not correctly identify failed I/Os. As a result, unless a
timeout is enforced at the application level, the application may hang while
waiting for the I/O results.
Intelligent
switch
specific
[6195] If an RPA simultaneously loses connection to the splitter and storage
most likely in a single-switch configuration a full-sweep
resynchronization may subsequently be required.
System [26050] When using distributed consistency groups, if you change the
group size while the group is performing other actions (which take time, for
example, due to deadlocks in replication or writing to repository) and
replication that runs 1-3 distributed consistency group copies is stopped,
the distributed consistency group will stop working, not marking or
replicating.
Workaround: Stop the replication processes that run other distributed
consistency group copies.
Topic Summary
System [26030] In the System Monitoring section of the Component Pane in the
RecoverPoint GUI, the image access limitations displayed for distributed
consistency groups are incorrect - they show one quarter of the amount of
journal space used for image access (instead of the whole amount, which
is usually 20% of the journal size).
Workaround: To calculate the correct limitation for any distributed
consistency group, multiply the value by four.
System [25853] Sometimes, when replication is stuck, the system may not be able
to recover. In the RecoverPoint GUI, the transfer will be N/A for
consistency groups that run on the RPA with the stuck replication process.
Workaround: Reboot the RPA with the stuck replication process.
System [25237] In the RecoverPoint GUI, when synchronously replicating
consistency groups, if you change the primary RPA of the groups, the
outgoing data line in the Statistics Tab of the Component Page may appear
larger than the incoming data line.
Workaround: Ignore the outgoing data graph if it is not identical to the
incoming data graph for synchronous groups.
System [25007] 3.3 SP1 and later
In the RecoverPoint GUI, despite the fact that the measure lag when writes
reach the target RPA (opposed to journal) checkbox appears in the
Consistency Group Advanced Policy Settings when a CDP consistency
group (or CLR local link) is in asynchronous mode, enabling this setting will
not change the group's policy. That is, if you exit the Advanced Policy
section and return to it, you will see the checkbox is cleared.
System [24281] When using Brocade switches on two sites, and there is a long
distance between them, high-loads and performance degradation of I/Os
between the sites may occur.
Workaround: Use the following Brocade command to set the switch ports
to Long Distance:
portcfglongdistance <port_no> LS 1 100
LS Indicates Long distance Static
System [23847] 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.
System [23813] 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 connection 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.
Topic Summary
67
System [23771] RecoverPoint email alerts that are sent to a user and contain more
than one event will only indicate the first event, rather than indicating that
there is more than one event (Supplementary event summary).
System [23679] In the Management Application GUI, there is no option to attach
as clean a volume when using the Replication Set Wizard. Workaround:
Use the Volumes Configuration dialog box to attach a volume as clean.
System [22856] This problem may occur when performing one of the following
operations:
Installing a new RecoverPoint or RecoverPoint/SE environment
Adding a new RPA to an existing environment
Replacing an older RPA with a new RPA in an existing environment
And using Gen4 RPAs which were manufactured after Q2-2010 that have
QLE2564 4-port 8Gb HBAs with serial numbers with the format
XFDXXXXXXXXXX.
When RecoverPoint is installed it uses the WWNs assigned by QLogic in
the HBA flash to determine the RPA WWNs. The WWNs that were
assigned by QLogic to these HBA ports are consecutive. This convention
breaks the logic in the RecoverPoint code and causes a collision between
node-WWNs and port-WWNs of different ports on the same RPA. The
consequences of this collision depends on the Fiber Channel switch that
the RPA is connected to. Possible problems include switch reboot, switch
unresponsiveness to RPA requests (which may result in empty SAN view
for the RPA), and more. This problem may also lead to downtime at the
production site.
Workaround 1: Modify (spoof) RPA WWNs using the RPA Installation
Manager (boxmgmt). From the Main menu, select Setup > Modify
settings > Site details > WWN node/port pair addresses.
System [22621, 24584] An RPA or RecoverPoint splitter that was downgraded may
go into a loop of assertions that will cause reboot in the following scenario:
Before downgrade, all RPA code and splitters are 3.4 and later releases
The environment has Brocade, VNX/CLARiiON, or KDriver splitters
You then downgrade either the RPA code or a splitter to an earlier major
RecoverPoint release (such as 3.3.x or 3.2.x)
Workaround 1: To prevent the problem, before downgrading the splitter,
remove it from the system.
Workaround 2: If you downgraded the splitter without removing it first,
reboot all the RPAs, one by one, on the sites that use the splitter.
Workaround 3: If you downgraded the RPA code, reboot the splitter after
the downgrade.
Topic Summary
System [21705] When replicating synchronously, there may be I/O delays every
once in a while (1 in a 1000 I/Os), which cause delays in synchronous
replication. However, by staying under the recommended throughput
(according to customer latency), the problem will not occur.
Workaround: Use distributed consistency groups.
System [21610] Running the Microsoft Cluster Diagnostics and Verification
(ClusDiag.exe) tool on Windows 2008 system running RecoverPoint and
Microsoft Cluster Server (MSCS) triggers a full sweep.
Workaround: When running the Cluster Diagnostics and Verification tool
on a volume that belongs to an enabled consistency group, do not run any
of the Storage tests available on the Testing Options window.
System [21001] When a splitter is disconnected from the RPA cluster, the
bookmarks created on the replica copy might be inconsistent with the
production at that time.
System [20881] In a scaled environment, if the remote journal volume is not fast
enough to handle 128 consistency groups on one RPA, and the groups are
flipped over to one RPA, some groups may become stuck in ready state for
a long time. If this time exceeds 20 minutes, the replication process will
restart. The problem is more likely to occur on Gen3 RPAs.
Workaround 1: Upgrade to a Gen4 RPA and increase journal speed when
working with a lot of groups.
Workaround 2: If user cannot increase journal performance, there is a
tweak that can be performed. For details, contact EMC Customer Service.
System [20762] Attempting to configure the MTU value of an RPA in an
environment with IPv6 addresses will cause the RPA to enter reboot
regulation.
System [20714] When an initialization process occurs (for example, after high load
or any consistency group switches over), all the snapshots in the journal
may disappear. This may happen when using very small journals (5 GB).
Workaround: Use journals that are at least 10 GB in size.
System [17271] When attempting to collect logs from CLARiiON arrays on sites
using IPv6 protocol, the splitter log files will not download.
Workaround: In the Navisphere GUI, right-click an SP and select File
Transfer Manager and manually collect the splitter logs.
System [16824] When site 1 and site 2 RPAs are both on the same subnet (for
instance, when using a VPN), and IPv6 addresses are being used, one
RPA cluster will fail. Workaround: Do not put site 1 and site 2 on the same
subnet when using IPv6 addresses.
Topic Summary
69
System [16015] In the New Replication Set Wizard of the Management
Application GUI, you cannot edit a replication set. Workaround: Use the
Volumes Configuration dialog to edit a replication set.
System [14681] When Snapshot Consolidation is enabled:
The Predicted Protection Window information is unavailable.
The Current Protection Window Status may be incorrect.
System [14647] If an SQL server on the remote cluster is configured to have a
dependency between the cluster initialization and database initialization,
running kutils.exe sqlRestore command will generate a false error
message, even though the restore succeeds.
Workaround: User should configure the remote SQL server to not have a
dependency between the cluster and the database.
System [13502] 3.0 SP1 and later
When you attempt to run a stand-alone kutils command, and vcredist.exe is
not installed, kutils will not start, and an error message will be displayed. To
correct the problem, download vcredist.exe from Microsoft, and install.
System [12337] The RecoverPoint Management Application, when running on a
Solaris/SPARC machine, does not operate properly using the default
Solaris/SPARC toolkits. To eliminate this problem, run the following
commands before opening the Management Application:
setenv AWT_TOOLKIT XToolkit #selects the XToolkit
export AWT_TOOLKIT=XToolkit
System [12252] Virtual with roll mode is not supported when enabling image
access for hosts running Solaris or AIX using Veritas Cluster Server in a
SANTap environment.
System [12201] When a volume name is changed in a storage array, the new name
is not automatically updated in the RecoverPoint Management Application
GUI. Workaround:
1. Remove the volume from the RecoverPoint configuration.
2. Change the volume name in the storage array.
3. Rescan all volumes in RecoverPoint.
4. Add the volume to the RecoverPoint configuration.
Topic Summary
System [10941] In the following scenario:
Clustered environment
Image access enabled, in virtual access mode
RPAs lose connection with replication volumes
Upon restoring the connection, a partition table modified message is
erroneously displayed on the Management Console.
Also, in this situation, the system may, without instruction from the user,
disable access to the remote image (that is, resume distribution). If so,
and you want to continue working in virtual access with the enabled image,
take the resource offline, re-enable image access (in virtual access mode),
and remount the resource.
System [10220] In the event that target-side log usage reaches (or approaches)
100%, it is no longer possible to add volumes that can be used to provide
uninterrupted use of the target-side log, except through the following
procedure:
1. Close running applications.
2. Unmount file systems.
3. Disable access to image.
4. Add journal volumes.
5. Wait for completion of initialization.
6. Re-enable access to the image.
7. Mount file systems and start applications.
System [10200] The system may not always immediately detect a disconnection of
the Management Console and attempt to reestablish the connection. To
correct this problem, close the Management Console manually, and then
reopen it.
System [9772] When an application that uses SCSI reservations (such as Microsoft
Cluster) is brought up on a Windows-based host at the source site (or at
the target site, if a failover has occurred since the application was last in
operation), there may be a delay (~1 min) in RPA ability to access volumes
that are reserved by that host. During the delay:
Transfer is paused, if either the host is at remote side or transfer is
initializing.
An error is displayed and events are issued to the events log.
The user should not take any corrective action. The system will restart
transfer when the RPA regains access to the volumes.
Topic Summary
71
System [9765] If the RPA that is running site management crashes, and shortly
thereafter you run detect_bottlenecks or export_statistics through one
of the other RPAs, you may receive an erroneous error message. The
problem should disappear if you wait a few minutes, and then rerun the
command.
System [9684] When a CLI command (in interactive mode) prompts the user for a
password, Ctrl-C cannot be used to abort the command. To abort the
command, press Enter (up to three times) until the CLI command line
prompt reappears.
System [8593] If you are unable to successfully open the Management Console,
you should use the system behavior and messages to guide your attempt
to identify and correct the problem, as follows:
If a new, empty login box appears, try logging in as a different user (with
security permissions). If successful, change the password for the initial
user.
If you receive an error message that instructs you to check RPA and
network settings, check the network settings (for example, that the
proper ports are open at the firewall). If necessary, correct.
For any other error message, proceed as follows:
1. Try to log in as user boxmgmt. If successful, use the Run SAN
diagnostics option (Installation Manager) to check the status of the
repository volume connection. If necessary, connect the repository
volume.
2. If SAN diagnostics do not indicate any problem with the repository
volume connection, or if you are unable to log in as user boxmgmt, use
the Collect system info option (Installation Manager), send the collected
information to technical support, and reboot the RPA.
System [7163] If the number of splitters added over the lifetime of the system
exceeds 450 (regardless of the number removed), the RPA cluster may
become unstable. Workaround: reapply the settings on all RPAs.
System [7044] If the system issues a target-side log is full event, application writes
are expected to fail, although it may take a few minutes before the system
actually enforces this. No action is necessary; however, if no further host
access to the target-side image is required, you should disable image
access.
System [6912] Target-side host reboot may cause transfer to pause briefly.
System [6656] When an RPA is working with an initiator port on a QLogic switch,
and IOGuard is enabled, the RPA does not see the splitter on the name
server, and therefore misreports the state of the host. Workaround:
Disable the IOGuard parameter when working with a QLogic switch.
Topic Summary
System [6533] With regard to SCSI LUN numbering, RecoverPoint supports
replication of LUNs in the Mode 0 (0255) and Mode 1 (016384) LUN
number range; however, numbers greater than 4096 are masked into the
04096 range.
System [6447] If a splitter is removed from system settings, but the KDriver is not
uninstalled and continues to run on its host machine, phantom events for
that splitter may subsequently continue to appear in the log.
System [5938] In some cases, in the event of an RPA reboot, the system may fail to
update the reason for the reboot (i.e., and continues to display the reason
for the previous reboot).
System [5922] Following an RPA reboot, splitters that are not visible in the SAN
environment in steady state may erroneously appear to be down.
System [5182] When booting a host during a repository volume failure or an RPA
cluster failure, the file system may fail to mount.
Workaround: mount the file system manually.
System [5032] If an RPA fails to detect its internal disk, boot fails.
System [4721] There cannot be more than one RPA cluster in the same zone. This
limitation can be manually overridden by technical support if required.
System [4524] When disconnecting all network connections from an RPA, event
4003 (Group Capabilities Changed) incorrectly indicates that the repository
volume is unknown.
System [3639] In the RecoverPoint Management Application, it is possible to select
a non-Windows host as a boot-from-SAN shadow host, even though
RecoverPoint supports replication boot volumes only for Windows hosts.
System [3496] In case of an RPA failure, the RecoverPoint system will indicate that
the WAN connection to this appliance is down.
Topic Summary
73
Technical notes
Technical notes
This section contains important information for the current release.
Upgrading to
RecoverPoint
3.4 SP1 P1
To resolve the issues listed in Fixed problems on page 30, you must
upgrade to RecoverPoint 3.4 SP1 P1.
It is recommended to upgrade all relevant splitting technologies
(KDriver, VNX/CLARiiON, SANTap, and Brocade) only after all
RPAs have been upgraded to the latest 3.4 release.
Updates from release 3.1 and later are non-disruptive when using the
Deployment Manager; no full sweep occurs and no journal data is
lost. Updates from releases earlier than 3.1 are disruptive and require
updating to the latest 3.3 release before upgrading to the latest 3.4
release.
Instructions for upgrading the RPAs are presented in the Upgrade
RPA Software chapter of the EMC RecoverPoint Deployment Manager
1.0 Product Guide.
Licensed features When performing a major upgrade to RecoverPoint 3.4 and later, it is
recommended to obtain a new license key (for no extra cost) from
EMC for the RecoverPoint 3.4 release. Until a new license is set in the
RecoverPoint environment, licensed features will remain disabled.
Licensed features in RecoverPoint 3.4 and later: None.
Documentation
The following documents are available to support the current release
of RecoverPoint. All are located in the documentation library on:
http://Powerlink.EMC.com
EMC RecoverPoint Deployment Manager 1.0 Product Guide
EMC RecoverPoint Deployment Manager 1.0 Release Notes
EMC RecoverPoint Administrators Guide
EMC RecoverPoint CLI Reference Guide
EMC RecoverPoint Security Configuration Guide
EMC RecoverPoint Deploying with Symmetrix Arrays and Splitter
Technical Notes
Software media, organization, and files
EMC RecoverPoint Deploying with VNX/CLARiiON Arrays and
Splitter Technical Notes
EMC RecoverPoint Deploying RecoverPoint with SANTap and
SAN-OS Technical Notes
EMC RecoverPoint Deploying RecoverPoint with SANTap and NX-OS
Technical Notes
EMC RecoverPoint Deploying with the Brocade Splitter Technical
Notes
EMC RecoverPoint Replicating VMware Technical Notes
EMC RecoverPoint Zoning and LUN Masking Technical Notes
EMC RecoverPoint Adapter for VMware vCenter Site Recovery
Manager Release Notes
EMC RecoverPoint/Cluster Enabler Product Guide
EMC RecoverPoint/Cluster Enabler Release Notes
Software media, organization, and files
RecoverPoint software is downloaded and installed by EMC
personnel, and is not customer-accessible.
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 the RecoverPoint system for the first time,
or for upgrading to a RecoverPoint 3.4 release from earlier
RecoverPoint releases, are presented in the EMC RecoverPoint
Deployment Manager 1.0 Product 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.
75
Installation
To use RecoverPoint release 3.4 and later with the VNX/CLARiiON
splitter, the following must be installed:
RecoverPoint splitter enabler
VNX OE/CLARiiON FLARE bundle
RecoverPoint splitter driver
When installing or upgrading RecoverPoint, it is recommended to
install or update both the OE/FLARE bundle and RecoverPoint
splitter driver to the latest versions.
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 EMC Symmetrix VMAXe array supports a RecoverPoint
array-based splitter when using RecoverPoint 3.4 SP1 and later. This
splitter is commonly referred to as the Symmetrix splitter. 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
SANTap switches
RecoverPoint can be deployed with SANTap and Connectrix B-Series
switches.
NX-OS When installing or upgrading RecoverPoint, it is recommended to
install or update both the SSI and the NX-OS to the latest versions.
Special instructions for deploying the RecoverPoint system with a
SANTap-based intelligent switch and an NX-OS, and other relevant
information, are presented in the EMC RecoverPoint Deploying
RecoverPoint with SANTap and NX-OS Technical Notes.
SAN-OS When installing or upgrading RecoverPoint, it is recommended to
install or update both the SSI and the SAN-OS to the latest versions.
SANTap-based intelligent switch and a SAN-OS, and other relevant
information, are presented in the EMC RecoverPoint Deploying
RecoverPoint with SANTap and SAN-OS Technical Notes.
Troubleshooting and getting help
Deploying
RecoverPoint with
Connectrix B-Series
switches
RecoverPoint is compatible with the Connectrix AP-7600B and
PB-48K-AP4-18, running the versions of the SAS and FOS specified
for each release. The PB-48K-AP4-18 blade should be installed in
either a ED-DCX-B or ED-48000B.
When installing or upgrading RecoverPoint, it is recommended to
install or update both the SAS and the FOS to the latest versions. For a
complete list of Connectrix B-Series switches compatibilities with
RecoverPoint, refer to the ESM.
SAS-based intelligent switch, and other relevant information, are
presented in the EMC RecoverPoint Deploying with the Brocade Splitter
Technical Notes.
Where to get help EMC support, product, and licensing information can be obtained as
follows.
Product information For documentation and release notes, or for
information about EMC products, licensing, and service, go to the
Powerlink

website (registration required) at:
http://Powerlink.EMC.com
Technical support For technical support, go to EMC Customer
Service on Powerlink. To open a service request through Powerlink,
you must have a valid support agreement. Please contact your EMC
sales representative for details about obtaining a valid support
agreement or to answer any questions about your account.
Your comments Please include the title, part number, and revision of the document.
If you have issues, comments, or questions about specific information
or procedures, include the relevant page numbers and any other
information that will help us locate the information you are
addressing.
SSG_Documentation@EMC.com
77
Copyright 2011 EMC Corporation. All rights reserved.
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.
For the most up-to-date listing of EMC product names, see EMC Corporation Trademarks on EMC.com. All
other trademarks used herein are the property of their respective owners.

rp3 4 Release Notes 300-012-258 A05

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

rp3 4 Release Notes 300-012-258 A05

Загружено:

Авторское право:

Доступные форматы

1

unified storage environments.

Enginuity versions earlier than Release Level

Вам также может понравиться