RELEASE NOTES. Release Notes P/N REV 02. EMC RecoverPoint. Release 4.0. June 28, 2013

Transcription

1 RELEASE NOTES EMC RecoverPoint Release 4.0 Release Notes P/N REV 02 June 28, 2013 These release notes contain information about release 4.0 and service pack and patch releases of the EMC RecoverPoint product family. Topics included in this document are: Revision history... 2 Product description... 2 New features and changes Fixed problems Environment and system requirements Known problems and limitations Technical notes Documentation Software media, organization, and files Installation Troubleshooting and getting help... 27

2 Revision history Revision history The following table presents the revision history of this document: Table 1 Revision history Revision Date Description 02 June 28, 2013 Release of P1, see New features and changes for release 4.0 P1 on page May 13, 2013 Release of RecoverPoint 4.0, see New features and changes for release 4.0 on page 10. Product description The EMC RecoverPoint product family provides a comprehensive data protection solution for enterprise and commercial customers, providing integrated continuous data protection and continuous remote replication to recover applications to any point in time. RecoverPoint systems enable reliable replication locally with one RPA cluster, and over any distance to up to four remote RPA clusters. RecoverPoint systems support replication of data that applications are writing to SAN-attached storage using existing Fibre Channel (FC) and iscsi infrastructure to integrate seamlessly with existing host applications and data storage subsystems. For remote replication, the systems use existing connections to send the replicated data over FC and WAN, and uses FC and IP infrastructure to replicate data asynchronously or synchronously. The systems provide failover of operations to another cluster in the event of a disaster at the production cluster. The RecoverPoint family consists of three licensing offerings: RecoverPoint/CL for EMC and non-emc storage platforms. RecoverPoint/EX for EMC storage platforms (Block), licensed by storage array. RecoverPoint/SE for VNX series, CLARiiON CX3 and CX4 series, and Celerra unified storage environments. Note: Throughout this document, in the context of comparing RecoverPoint and RecoverPoint/SE, the term RecoverPoint is synonymous with RecoverPoint/CL and RecoverPoint/EX, unless otherwise noted. Note: An EMC Support Matrix (ESM) on E-Lab Navigator serves the RecoverPoint product family. After logging in, select the PDFs and Guides tab and look for RecoverPoint in the Information Management Software section. 2 EMC RecoverPoint 4.0 Release Notes

3 Product description Notes on performance Table 2 on page 3 identifies the build and size of the RecoverPoint ISO image associated with the 4.0 release. The build also appears in the Unisphere for RecoverPoint login screen, in response to the get_versions CLI command, and in the Installation Manager (boxmgmt) header. Table 2 RecoverPoint release, build, and ISO image size Additional performance information will be provided in the RecoverPoint 4.0 Performance Guide, to be available shortly after product release. Table 3 on page 3 and Table 4 on page 3 present general throughput and IOPS values for Gen4/Gen5 RPAs and for virtual RPAs (vrpas). You can use these values to develop general sizing requirements for your RecoverPoint system. Note, however, that the following limitations apply: Release Build ISO image size 4.0.P1 4.0.P1_f GB _f GB Values in tables are for non-distributed consistency groups. Throughput rates were measured using a write size of 64 KB. The values include writes only. Note: Reads do not impact performance. These values are independent of: Link type (WAN-IP, FC) Replication mode (async, sync) Table 3 Average sustained throughput and IOPS per RPA Throughput (MB/s) IOPS (per splitter type) RPA 120 VNX/CLARiiON Symmetrix VPLEX Notes: 1. Throughput and IOPS increase linearly with the number of RPAs, provided that the splitter supports the increased levels of performance. 2. For async replication of distributed consistency groups, RecoverPoint 4.0 supports throughput of up to 400 MB/s, depending on storage array configuration. Table 4 Average sustained throughput and IOPS per vrpa vrpa Profile Throughput (MB/s) IOPS 8 CPU 8 GB RAM CPU 4 GB RAM CPU 4 GB RAM Note: Each vrpa CPU operates at speed of 2.13 GHz EMC RecoverPoint 4.0 Release Notes 3

4 Product description For additional information on RecoverPoint 4.0 scale and performance, contact your EMC sales representative. Configuration limits In addition to being supported on 64-bit RPA hardware platforms, RecoverPoint/SE is now supported on virtual RPA platforms. For deployment, best practices, and limitations, refer to the EMC RecoverPoint vrpa Technical Notes. RPA clusters consisting of physical RPAs require either a dual fabric or a direct attach network topology. Table 5 on page 4 lists the 4.0 releases supported across RPA hardware types. EMC will continue to support existing configurations of RPA hardware platforms running earlier versions of RecoverPoint. Table 5 RecoverPoint releases support across RPA hardware types RPA hardware 4.0 and later Intel R1000 (Gen5) Supported 1 Dell PowerEdge R610 (Gen4) Supported 1 Dell PowerEdge 1950 phase 3 (Gen3) or Dell PowerEdge 2950 phase 3 Dell PowerEdge 1950 phase 2 (Gen1) or Dell PowerEdge 2950 phase 2 Legacy hardware (such as the IBM xseries 336) Not supported Not supported Not supported 1. When using a mix of RPA hardware types (Gen5 and Gen4), it is highly recommended to configure the latest types as RPA 1 and RPA 2 (cluster control RPAs) to improve system function and performance. Break fix/support EMC will handle break/fix activity for Gen4 and Gen5 RPA hardware platforms purchased through Direct Express and Channel Express. SAN support Table 6 on page 4 lists Fibre Channel support across RPA hardware types. When using virtual RPAs, iscsi is supported in 1 Gb/s and 10 Gb/s network infrastructure. Table 6 Fibre Channel support across RPA hardware types RPA hardware 1 Gb/s 1 2 Gb/s 4 Gb/s 8 Gb/s Gen4 Not supported Supported Supported Supported Gen5 Not supported Supported Supported Supported 1. No support for basic connectivity of Gen4 or Gen5 in 1 Gb/s SAN. 4 EMC RecoverPoint 4.0 Release Notes

5 Product description General The tables in this section present the general configuration limits and scalability limits for the RecoverPoint system. Unless otherwise stated, RecoverPoint refers to all three family products (RecoverPoint/CL, RecoverPoint/EX, and RecoverPoint/SE). Table 7 on page 5 lists the general configuration limits for 4.0 and later releases. Table 7 General configuration limits (page 1 of 4) Parameter Supported operating systems Supported storage arrays Supported splitter types Maximum capacity Maximum number of arrays Maximum number of RPA clusters in a system Unisphere integration Journal compression Maximum number of open RecoverPoint CLI connections per RPA cluster Maximum number of open RecoverPoint CLI connections being set up concurrently Maximum number of concurrent RecoverPoint GUI sessions per RPA cluster RecoverPoint 4.0 and later RecoverPoint/CL: Heterogeneous RecoverPoint/EX: Heterogeneous RecoverPoint/SE: Windows Server 2000/2003/2008/2012 and heterogeneous with VNX/CLARiiON splitter Refer to the EMC Support Matrix for details. RecoverPoint/CL: Heterogeneous (EMC and non-emc) RecoverPoint/EX: EMC (block) RecoverPoint/SE: VNX series, CLARiiON CX3 and CX4 series, and Celerra unified Refer to the EMC Support Matrix for details. RecoverPoint/CL: Symmetrix, VPLEX, and VNX/CLARiiON RecoverPoint/EX: Symmetrix, VPLEX, and VNX/CLARiiON RecoverPoint/SE: VNX/CLARiiON RecoverPoint/CL: Per license (maximum 2 PB) RecoverPoint/EX: Per license (maximum 2 PB) RecoverPoint/SE: 2 PB RecoverPoint/CL: Unlimited RecoverPoint/EX: Unlimited RecoverPoint/SE: One per RPA cluster RecoverPoint/CL: 5 RecoverPoint/EX: 5 RecoverPoint/SE: 2 RecoverPoint/CL: Not supported RecoverPoint/EX: Not supported RecoverPoint/SE: Supported RecoverPoint/CL: Supported RecoverPoint/EX: Supported RecoverPoint/SE: Not supported EMC RecoverPoint 4.0 Release Notes 5

6 Product description Table 7 General configuration limits (page 2 of 4) Parameter Minimum Adobe Flash Player for RecoverPoint GUI Minimum supported web browser for RecoverPoint GUI Minimum supported screen (display) resolution for RecoverPoint GUI RecoverPoint 4.0 and later 10.2 Internet Explorer 7.0 Mozilla Firefox 3.0 Google Chrome 2.0 Safari for Mac x768 Number of RPAs in a cluster 2-8 Maximum number of SAN entities (WWNs) seen by an RPA Maximum number of paths per RPA 1 Recommended minimum repository volume size Minimum journal size Maximum journal size per consistency group Maximum number of distributed consistency groups Maximum number of journal volumes per consistency group copy RPA MTU packet size Maximum size of replicated LUNs In virtual access, maximum offset of image in journal In virtual access, maximum writes per RPA Maximum number of consistency groups in system Maximum number of copies per consistency group Maximum number of local copies per consistency group K 2.86 GB 10 GB (non-distributed consistency group) 40 GB (distributed consistency group) 10 TB ,000-9,000 bytes for IPv4 1,280-9,000 bytes for IPv6 32 TB 1.2 TB 40 GB 128 (not recommended to configure more than 64 per RPA) 2 5 (includes production copy) 2 (includes production copy) 6 EMC RecoverPoint 4.0 Release Notes

7 Product description Table 7 General configuration limits (page 3 of 4) Parameter Maximum number of consistency group remote copies per RPA cluster Maximum number of consistency groups in group set Maximum number of non-production copies in cluster Maximum number of replicated production volumes in system Maximum number of replication sets per consistency group Maximum number of replication volumes per system Maximum number of exposed LUNs per ESX servers Maximum number of ESX servers in discovery per RPA cluster Total number of LUNs that are visible to ESX servers per RPA cluster Total number of VMs that are visible to ESX servers per RPA cluster Maximum number of vcenter servers in discovery per RPA cluster Minimum bandwidth for replication Asynchronous replication over FC distance limit Asynchronous replication over IP latency limit Synchronous replication over FC distance limit Synchronous replication over FC latency limit Synchronous replication over IP latency limit RecoverPoint 4.0 and later continuous local replication or continuous remote replication continuous local and remote replication (when using physical RPAs) 2048 (when using virtual RPAs) Mb/s Per topology as supported by elab 200 ms (round trip time) 200 km (full round trip) 4 ms (round trip time) 10 ms (round trip time) EMC RecoverPoint 4.0 Release Notes 7

8 Product description Table 7 General configuration limits (page 4 of 4) Parameter Maximum number of synchronous replication links per consistency group Stretch cluster distance limit (on the stretch side) RecoverPoint 4.0 and later 1 local (FC) 1 remote (FC or IP) 30 km Maximum WAN packet loss 1% 4 1. Where path is a LUN WWN seen by an RPA port. The same LUN WWN seen from different RPA ports is counted multiple times. 2. A single RPA cannot be configured to have more than 64 consistency groups. However, in the event of RPA failure, groups on one RPA will move to other RPAs in the cluster. In such a case, an RPA can temporarily hold up to 128 groups, and the data of all the groups will continue to be transferred between clusters. This state is temporary, however, as an RPA with more than 64 groups may run into high loads, and you may not be able to meet your group policies. 3. More groups can be supported. Consult EMC Customer Support for setting a minimal interval for bookmarking. 4. RecoverPoint performance and ability to meet replication policies cannot be guaranteed if WAN packet loss exceeds this limit. Scalability The scalability limits when deploying RecoverPoint with the currently available splitter types are as follows: VNX/CLARiiON scalability Table 8 on page 8 lists the VNX/CLARiiON scalability limits: Table 8 VNX/CLARiiON scalability limits Parameter Maximum number of attached LUNs per splitter Maximum number of RPA clusters connected to splitter Limit 2K when using VNX OE for Block or earlier 8K when using VNX OE for Block later than when using VNX OE for Block or earlier 6 when using VNX OE for Block later than Maximum number of splitters per RPA cluster One splitter serves both storage processors of a VNX/CLARiiON array. 8 EMC RecoverPoint 4.0 Release Notes

9 Product description Symmetrix scalability Table 9 on page 9 lists the Symmetrix scalability limits: Table 9 Symmetrix scalability limits Parameter Maximum number of attached LUNs per splitter Limit in VMAX 10K 2, 20K, 40K arrays Maximum number of RPA clusters connected to splitter 6 Maximum number of splitters per RPA cluster 4 1. In a continuous remote replication configuration. 2. When using RecoverPoint 4.0 and EMC Enginuity release 5876 or later for Symmetrix VMAX 10K. (When not using both of these products, 2048 LUNs are supported.) VPLEX scalability Table 10 on page 9 lists the VPLEX scalability limits. Table 10 VPLEX scalability limits Parameter Limit Maximum number of attached LUNs per splitter 2K when using GeoSynchrony 5.1 8K when using GeoSynchrony 5.2 Maximum number of RPA clusters connected to splitter 4 when using GeoSynchrony when using GeoSynchrony 5.2 Maximum number of splitters per RPA cluster 10 Splitter support for different size volumes 1 No, when using GeoSynchrony 5.1 Yes, when using GeoSynchrony 5.2 Maximum number of directors for VPLEX Local 8 Maximum number of directors for VPLEX Metro Whether or not the VPLEX splitter supports fake size, that is, if a replica volume attached to the VPLEX splitter must be the exact same size as the production volume or not. Splitter interoperability RecoverPoint/CL and RecoverPoint/EX support the mixing of VNX/CLARiiON, Symmetrix, and VPLEX splitters between different RPA clusters and within the same RPA cluster, as shown in Table 11 on page 9. Table 11 Splitter interoperability between RPA clusters and within RPA clusters Splitter type 1, 2,3 VNX/CLARiiON Symmetrix VPLEX VNX/ CLARiiON Supported Supported Supported Symmetrix Supported Supported Supported VPLEX Supported Supported Supported 1. Each volume can be attached to only one splitter type. 2. A consistency group copy can span both Symmetrix and VNX/CLARiiON splitters, but not VPLEX splitters. 3. A volume can only be included in one consistency group across all RPA clusters in the case of multi-cluster (sharable) splitters. EMC RecoverPoint 4.0 Release Notes 9

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

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

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

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

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

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

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

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

18 Fixed problems Issue number Product feature Problem summary Table 13 Problems fixed in RecoverPoint 4.0 (page 4 of 4) System In an environment with at least 3 RPAs with a distributed consistency group with at least 3 preferred RPAs, in case of within-site FC connectivity problems between two RPAs, replication will not start. Workaround 1: Fix the connectivity problem. Workaround 2: Define different preferred RPAs System In a scaled environment, where SAN Discovery might take some time, if volumes were not exposed to an RPA and then many new volumes were exposed to an RPA just prior to installation, installation will be blocked and user will see error SanView is empty. Note: In a VPLEX environment, the maximum number of volumes for VPLEX deployment per VPLEX cluster is 5K. Workaround 1: Wait until SAN Discovery finishes, then perform installation. Workaround 2: Avoid exposing many new volumes to RecoverPoint prior to installation , System In an environment where replica storage is a bottleneck and there is low journal size, a high write rate may lead to a journal loss in replica and full sweep afterwards. The probability of this problem occurring increases when there are sync and async links in the same direction. Workaround: Use a larger journal, or restrict journal lag by some value System If a Fibre Channel disaster occurs when a distributed consistency group is replicating synchronously, transfer will go down (display N/A ) for a number of minutes. Afterwards, the RPA will automatically recover and an initialization will occur System Initialization restarts, high latency for user I/Os, and possibly aborted I/Os may occur in the following scenario: Initialization in synchronous replication mode Measure lag when writes reach the target RPA setting (in Consistency Group Advanced Policy of the RecoverPoint GUI) or measure_lag_to_box parameter (in the set_policy CLI command) equals No relatively high write rate on the production copy Specifically, near the end of the initialization, host I/Os will not be acknowledged for a considerable period of time, which may cause the host to abort an I/O. The abort will cause the system to stop responding to writes for several seconds, after which an initialization will start again. It is possible that this behavior will reoccur. Workaround: Set the Measure lag when writes reach the target RPA setting or the measure_lag_to_box parameter to equal Yes. 18 EMC RecoverPoint 4.0 Release Notes

19 Environment and system requirements Environment and system requirements Generally, RecoverPoint hardware and software components are installed by EMC personnel. Specific requirements by both EMC and the customer are expected to be addressed before the equipment is shipped to the customer site. However, as mentioned in RecoverPoint/SE is now customer upgradable on page 11, customers can now access RecoverPoint software and perform their own upgrades. End of service dates and extended support EMC has a standard software support duration policy which specifies that a major version will reach End of Service Life (EOSL) a minimum of 36 months following the General Availability (GA). EOSL may be followed by an Extended Support period during which customers may elect to pay an additional fee to extend their support coverage rather than migrate to a current software version. Once a software product reaches EOSL, EMC Technical Support is no longer available under base support/maintenance agreements. Customers interested in uninterrupted support must upgrade to a current release or contract for Extended Support. EMC Online Support site contains a list of documents that provide end-of-service and extended support information for EMC software and hardware products. To access these documents on EMC Online Support: Go to EMC Online Support, at Go to Support by Product pages and search for RecoverPoint CL. In the product page, scroll down the left and click Release and End of Life Dates. Find the EMC Software Release and End of Service Life Notifications document in the results. Open it and search for your product and version. This document provides EOSL dates for EMC software products. Note: This policy is in effect for select releases and will be phased in as new versions are made available. In cases where a software release is not eligible for Extended Support, the previous policy, which specifies product support and maintenance under Continuous Coverage Product Maintenance (CCPM), terms still apply. EMC RecoverPoint 4.0 Release Notes 19

20 Known problems and limitations Known problems and limitations This section lists the limitations and known problems in the current RecoverPoint release. Note: All information regarding interoperability limitations is available on E-Lab Navigator. Limitations RecoverPoint 4.0 and later releases have the following limitations: To remove an RPA cluster, the Installation Manager (boxmgmt) must be used. Gen5 (Intel) RPAs support BMC and RMM4. Gen4 RPAs support Dell idrac, OMSA, and the Dell MIB. When setting a consistency group as distributed, the capacity of the group's copy journals should not be less than the minimum journal size required for distributed groups. Adding journal volumes for such groups necessitates a disabling and re-enabling of the consistency group, which causes a full sweep. There is a small improvement in performance when a distributed group is run on three RPAs. A steep improvement in performance is experienced when the group is run on four RPAs. All IP addresses in the RecoverPoint system (that is, RPA, Management (LAN), and WAN/Private IP addresses) must be unique within the RecoverPoint system, even if they are not on the same subnet and there is no routing between them. RecoverPoint supports thin provisioning only on all EMC arrays and on Hitachi arrays. AVT failover mode is not supported on all storage arrays. The RecoverPoint multi-wwn (virtual ports) feature requires that the fabric switch supports arbitrated loop capability. RecoverPoint is supported in environments that utilize VLAN tagging (802.1q). RPAs do not tag the traffic that they send. RecoverPoint is not supported in environments that utilize IP L2 prioritization (802.1p). RecoverPoint is not supported in environments that utilize Differentiated Services Code Point (DSCP) Quality of Service (QoS). RPAs on one cluster may not be able to communicate with RPAs on another cluster if there is a network address translation (NAT) firewall between the clusters. Unisphere for RecoverPoint may not be able to communicate with RPAs if there is a network address translation (NAT) firewall between the machine that runs the GUI and the RPAs. RecoverPoint/CE and later supports replication for continuous remote replication consistency groups and continuous local and remote consistency groups. For the latter groups, however, failover is supported only to a remote copy, and failback will always be to the original production copy. 20 EMC RecoverPoint 4.0 Release Notes

21 Known problems and limitations In a RecoverPoint environment with Windows Server 2003 Enterprise running Exchange 2007 Cluster Continuous Replication with Majority Node Set Quorum, RecoverPoint VSS utilities (KVSS) will fail to install due to a known MSDTC limitation in a non-shared Quorum configuration (MNS). Note: This limitation is resolved in Windows Server 2008 and later releases. The number of snapshots that can be taken is unlimited. However, when selecting an image from the list in the Enable Image Access dialog box (RecoverPoint GUI), a limit of 1013 snapshots (images) are presented. VMware ESX replication capabilities and limitations are specified in EMC RecoverPoint Replicating VMware Technical Notes. When using VNX/CLARiiON splitters: In certain configurations, consistency groups cannot include Solaris-based hosts replicating data on heterogeneous arrays. Refer to the ESM for supported configurations. Note: Consistency groups can include Solaris-based hosts replicating data on heterogeneous arrays when the Solaris-based hosts use VxVM. RecoverPoint replication and MirrorView replication cannot concurrently operate on the same volume. If MirrorView is installed on a VNX/CLARiiON array, RecoverPoint cannot utilize the ports reserved by MirrorView. MirrorView must be disabled before the RecoverPoint splitter driver can be enabled. When multiple RPA clusters share a VNX/CLARiiON splitter pair (CX3 models running FLARE or later, CX4 models running FLARE or later, and VNX OE for Block models running and later), and are running on the same array, each RPA cluster must have a unique name. RecoverPoint volumes repository, journal, and replication should not be configured on CLARiiON CX4 disk drives with FLARE 29 or later installed that have spin-down capability. Normally, RecoverPoint will prevent volumes protected by RecoverPoint from spinning down; however, if a volume does spin down, an error will be raised until the volume spins up again. It is recommended to run only a single consistency group in virtual image access mode using the same RPA. RecoverPoint does not currently support WAN accelerators, unless the device is ally supported in the EMC Support Matrix with RecoverPoint. EMC is aware of configurations in which performance is degraded when using WAN accelerators in conjunction with RecoverPoint, such as when enabling compression on both RecoverPoint and the WAN accelerator. When replicating a Microsoft VSS image, attempting to access an image on the target-side image when there is an MSCS cluster at the target side, and the replication volumes are resources in the target cluster, the replicated disk on the target side will not be visible to the MSCS cluster. EMC RecoverPoint 4.0 Release Notes 21

22 Known problems and limitations For VNX/CLARiiON arrays, each storage group can support a maximum number of volumes, based on the storage system and the storage operating environment. RecoverPoint can replicate more volumes per VNX/CLARiiON array by using virtual WWNs. The Predicted Protection window feature is not supported when the current protection window is less than 24 hours. The CLI script converter (the convert_script CLI command) does not support the conversion of measure_lag_to_box parameter from 3.4 or earlier scripts. When loading the converted CLI script into the new environment, each consistency group will be created with value of Yes for all group links, unrelated to the value of this parameter in the old environment. Known Problems Issue Number Product Feature Problem Summary Table 14 on page 22 lists the known problems found in RecoverPoint 4.0 and later. Table 15 on page 23 lists the known problems found earlier than RecoverPoint 4.0. Where a problem is only relevant to a RecoverPoint release, it is noted in the problem summary. Table 14 Known problems found in RecoverPoint 4.0 and later Array splitter Array splitter If you try to reinstall a RecoverPoint/SE environment from scratch (including formatting the repository volume) without running the clear_settings CLI command beforehand, a generic warning will appear stating that devices are attached to another cluster, and replication won't start. Workaround: Contact EMC Customer Support for a procedure to resolve the issue. When a user adds volumes to the same copy of the same consistency group, but from different clusters, and the volumes are added simultaneously or when the WAN is disconnected, the number of volumes can exceed the maximum number supported by the splitter. Control attempts to add the volumes to the splitter until the consistency group is regulated. Workaraound: Detach volumes from the splitter until the number is within the maximum allowed System In a high throughput environment, ally with large journal lag, replication may stop on all consistency groups running on the RPA System When cluster control comes up, the settings may not yet be loaded when usersystem tries to useing them, causing control process to crash and restart System No warning is issued when configuring RPAs that do not exist in all the copy sitesclusters. As a result, another RPA, not the preferred RPA, will be used for replication of the group copy. Workaround: Before configuring the RPAs, verify that the designated RPAs are responding from all copy sitesclusters. After configuring the RPAs, review RPA settings, verifying all RPAs are accounted, with no missing copy sitesclusters VMware VMware ESX Virtual Machine does not shut down when shutting down the RecoverPoint Appliance (RPA) using the boxmgmt CLI command. Workaround: Shut down VMware ESX Virtual Machine and RecoverPoint Appliance manually vrpa In a vrpa environment, when the iscsi IPs of all RPAs are changed at the same time, an unexplained reboot may occur. Workaround 1: Detach all RPAs before changing their iscsi IPs. Workaround 2: Change the IPs of each RPA one at a time. For example, verify that RPA 1 is exposed to the repository before changing the IP of RPA EMC RecoverPoint 4.0 Release Notes