Download as pdf or txt
Download as pdf or txt
You are on page 1of 16

RELEASE NOTES

EMC RecoverPoint®
Deployment Manager

Release Notes
P/N 300-010-477
REV 13

February 9, 2015

These release notes contain information about EMC RecoverPoint Deployment Manager.
Users of RecoverPoint Deployment Manager should be familiar with the installation,
upgrade, and deployment of EMC RecoverPoint and RecoverPoint/SE. Topics include:
◆ Revision history ........................................................................................................ 2
◆ Product description................................................................................................... 2
◆ New features and changes ........................................................................................ 3
◆ Fixed problems ......................................................................................................... 7
◆ Environment and system requirements ..................................................................... 9
◆ Known problems and limitations............................................................................. 10
◆ Technical notes ....................................................................................................... 14
◆ Documentation ....................................................................................................... 14
◆ Software media, organization, and files .................................................................. 14
◆ Installation ............................................................................................................. 14
◆ Troubleshooting and getting help............................................................................ 15
Revision history

Revision history
Table 1 on page 2 presents the revision history of this document:

Table 1 Revision history

Revision Date Description

13 February 9, 2015 Added known problems.

12 January 6, 2015 Release of 2.1 SP1.

11 August 27, 2014 Added fixed and known problems.

10 June 24, 2014 Release of 2.1.

09 December 23, 2013 Release of 2.0 SP2 P1

08 August 30, 2013 Release of 2.0 SP1; information added on release


of 2.0.

A07 September 10, 2012 Documentation correction.

A06 May 9, 2012 Release of 1.1.

A05 June 15, 2011 Release of 1.0 SP3.

A04 February 16, 2011 Release of 1.0 SP2.

A03 June 22, 2010 Release of 1.0 SP1.

A02 March 12, 2010 Updated Table 3; added a Limitation and some
Known Problems; updated Technical Notes section
to include release of RecoverPoint 3.3.

A01 January 27, 2010 First release of RecoverPoint Deployment Manager.

Product description
EMC RecoverPoint Deployment Manager (DM) is a standalone software package of GUI
tools that help you install, upgrade, and modify RecoverPoint and RecoverPoint/SE
system.

To perform any of the following operations, use the latest available release of
RecoverPoint Deployment Manager:
◆ Installing RecoverPoint/SE
◆ Installing RecoverPoint
◆ Connecting RPA clusters (from 4.0 or later)
◆ Replacing RPAs in existing RPA clusters
◆ Adding RPAs to existing RPA clusters
◆ Upgrading RPA clusters (from release 3.1 or later)
◆ Converting a RecoverPoint/SE or RecoverPoint system (from 3.4 SP1 or later)
◆ Modifying cluster or system settings (from 3.5 or later)

For details on all of the above operations, refer to the EMC RecoverPoint Installation and
Deployment Guide (formerly titled the EMC RecoverPoint Deployment Manager 1.1
Product Guide).

2 EMC RecoverPoint Deployment Manager Release Notes


New features and changes

As a tool to ease deployment of RecoverPoint, DM has its own release schedule and
compatibility with RecoverPoint releases.

IMPORTANT
For information about specific RecoverPoint releases, refer to the relevant EMC
RecoverPoint Release Notes on the EMC Online Support site (http://support.emc.com).

Table 2 on page 3 identifies the build and size of the file associated with the DM releases.

Table 2 Deployment Manager release, build, and file size

Release Build File size

2.1 SP1 rel4.1.SP1_h.165_DM_2.1.1 67.8 MB

2.1 rel4.1_d.210_DM_2.1 67.7 MB

2.0 SP2 P1 4.0.SP2.P1_m.35 58.9 MB

2.0 SP2 4.0.SP2_m.28 58.9 MB

2.0 SP1 4.0.SP1_k.139 58.9 MB

2.0 4.0_f.226 58.8 MB

1.1 3.5_n.139 25.6 MB

1.0 SP3 3.4.SP1_k.128 24.1 MB

1.0 SP2 3.4_h.102 23.9 MB

1.0 SP1 3.3.SP1_k.63 22.4 MB

1.0 3.3_e.37 22.3 MB

New features and changes


This section describes new features and changes of RecoverPoint Deployment Manager.

Features introduced in DM 2.1 SP1


DM 2.1 SP1 includes the following features and changes:
◆ RPA communication security level screen
The RPA communication security level screen has been added for the RecoverPoint
Installer Wizard and the RecoverPoint/SE Installer Wizard.
◆ ScaleIO registration screens
The Add New RPAs Wizard, RPA Replacement Wizard and the RecoverPoint Installation
Wizard have new screens when using ScaleIO. In the RecoverPoint Installer, a new
repository type screen was added for ScaleIO.
◆ Fixed problems
Table 4 on page 7 lists the problems fixed in this release.

EMC RecoverPoint Deployment Manager Release Notes 3


New features and changes

Features introduced in DM 2.1


DM 2.1 included the following features and changes:

Note: This section is for informational purposes only. You should use only the latest
available release of RecoverPoint Deployment Manager.

◆ In RecoverPoint/SE:
• All arrays for which login credentials are entered into the DM are automatically
registered for RecoverPoint management, and are added to the Registered Storage
table in Unisphere for RecoverPoint (RPA Clusters > Storage).
• The repository volume can be automatically provisioned on a resource pool, if one
is dedicated on storage and mapped to the relevant RPA cluster.
• RAID pools are not automatically provisioned, and must be created on storage by
users if they wish to use automatic journal volume provisioning.
◆ Table 3 on page 4 shows DM 2.1 compatibility with RecoverPoint releases.

Table 3 RecoverPoint DM 2.1 and compatible RecoverPoint (RP) releases

Wizards 4.1 4.0.x1 3.5.x 3.4.x 3.3.x

RecoverPoint/SE Installer ✓ ✓2 ✓ ✓ ✓

RecoverPoint Installer3 ✓ ✓4 ✓ ✓ ✓

Connect Cluster ✓ ✓

RPA Replacement ✓ ✓ ✓ ✓ ✓

Add New RPAs ✓ ✓ ✓ ✓ ✓

Upgrade5 ✓ ✓ ✓ ✓
✓(minor) (minor and (minor and (minor and (minor and
major) major) major) major)

Converter6 ✓
✓ ✓ ✓ (3.4 SP1 and
later)

Modification7 ✓ ✓ ✓
1. As of RecoverPoint release 4.0, all operations (aside from Conversion) are performed per RPA cluster, not per system (up to two RPA
clusters).
2. As of DM 2.0, includes new installations of virtual RPA (vRPA) clusters running RecoverPoint/SE 4.0 and later releases.
3. “RecoverPoint” refers to both RecoverPoint/CL and RecoverPoint/EX offerings.
4. As of DM 2.0 SP1, includes new installations of virtual RPA (vRPA) clusters running RecoverPoint 4.0 and later releases.
5. Upgrade RPAs Wizard for 3.5 and earlier releases; Upgrade Cluster Wizard for 4.0 and later releases.
6. Conversion to a RecoverPoint or RecoverPoint/SE system.
7. System Modification Wizard for 3.5 and earlier releases; Cluster Modification Wizard for 4.0 and later releases.

◆ Fixed problems
Table 5 on page 8 lists the problems fixed in this release.

4 EMC RecoverPoint Deployment Manager Release Notes


New features and changes

Features introduced in DM 2.0 SP2 P1


There are no new features in this release.
◆ Fixed problems
Table 6 on page 8 lists the problems fixed in this release.

Features introduced in DM 2.0 SP2


There are no new features in this release.

Features introduced in DM 2.0 SP1


DM 2.0 SP1 includes the following features and changes:
◆ Install virtual RPA clusters in a RecoverPoint system
Virtual RPA (vRPA) clusters can now be installed using the RecoverPoint Installer. This
enables installation of vRPAs with VNX arrays for RPA clusters with RecoverPoint/CL
and RecoverPoint/EX licenses.
◆ RecoverPoint/SE is now customer installable
Beginning with release 4.0 SP1, RecoverPoint/SE is customer installable. The
RecoverPoint/SE Installation Kit, on EMC Online Support (http://support.emc.com),
contains the latest Deployment Manager software, together with a Quick Start
Installation poster, the RecoverPoint/SE Quick Start Installation Guide, and a link to
tutorial videos.
◆ Installation Change Management procedures for RecoverPoint/SE installations
To ensure your RecoverPoint/SE installation is successful, general and specific
messages related to the installation you are performing are presented to you during
the installation.
◆ Requirement for Java 7 Update 13 or later
To use Deployment Manager 2.0.SP1, you must have a version of Java™ 7 (update 13
or later) installed on the computer running Deployment Manager. It is highly
recommended to have the latest Java 7 update installed.
◆ Fixed problems
Table 7 on page 9 lists the problems fixed in this release.

Features introduced in DM 2.0

Note: This section is for informational purposes only. You should use only the latest
available release of RecoverPoint Deployment Manager.

EMC RecoverPoint Deployment Manager Release Notes 5


New features and changes

DM 2.0 included the following features and changes:


◆ Support for multiple RPA clusters
With the introduction of support for up to five RPA clusters (sites) in a RecoverPoint 4.0
system, the following DM wizards were introduced or modified:
• RecoverPoint/SE Installer Wizard - used to install one RPA cluster.
• RecoverPoint Installer Wizard - used to install one RPA cluster.
• Connect Cluster Wizard - used to connect separately installed RPA clusters.

Note: This was a new wizard introduced at DM 2.0. It must be run to connect multiple
RPA clusters, to create a RecoverPoint system of up to five RPA clusters.

• RPA Addition Wizard - used to add an RPA to one RPA cluster.


• Upgrade Cluster Wizard - used to upgrade one RPA cluster.
• Add New RPAs Wizard - used to add new RPAs to one RPA cluster.
• Cluster Modification Wizard - used to modify settings of one RPA cluster.
◆ Install virtual RPA clusters in a RecoverPoint/SE system
Virtual RPA (vRPA) clusters can now be installed using the RecoverPoint/SE Installer.
This enables installation of vRPAs with VNX arrays for RPA clusters with
RecoverPoint/SE licenses.
◆ RecoverPoint/SE is now customer upgradable
With the release of Deployment Manager 2.0, RecoverPoint/SE 3.5 and later releases
are now customer upgradable. The upgrade process has been greatly simplified and
customers can now perform the RecoverPoint/SE software upgrades on their own
schedule and without the need to schedule and rely on external resources. To perform
the upgrade, you must download the RecoverPoint/SE Upgrade Kit and follow the
instructions in the RecoverPoint/SE Upgrade Guide contained within the kit.
To download the kit from EMC Online Support (http://support.emc.com), click
“Support by Product” and type “RecoverPoint SE” in the “Find a Product” search field.
On the “RecoverPoint SE” page, the kit is located in the “Recommended Resources”
section.
◆ Check for newer Deployment Manager release
Whenever you open the Deployment Manager, you are provided with the option to
check for a newer release of Deployment Manager, and if available, to download it
from EMC Online Support.
◆ Download ISO file from EMC Online Support for installations and upgrades
For upgrades from 3.5.x and later and installs from 4.0.x and later, upon entering valid
EMC Online Support credentials, you can download relevant RecoverPoint ISO files
directly to your local machine, to be used by DM for upgrade and installation.
◆ Upgrade Change Management procedures for RecoverPoint/SE upgrades
To ensure your RecoverPoint/SE upgrade is successful, general and specific messages
related to the upgrade you are performing are presented to you during the upgrade.
◆ Support for RPA clusters running different releases

6 EMC RecoverPoint Deployment Manager Release Notes


Fixed problems

Once all RPA clusters are running at minimum release 4.0, then other clusters in the
system will be able to run later releases (for example, one cluster can run 4.0 and two
clusters can run 4.0 SP1).

Fixed problems
Table 4 on page 7 lists the problems fixed in DM 2.1 SP1.

Table 5 on page 8 lists the problems fixed in DM 2.1.

Table 6 on page 8 lists the problems fixed in DM 2.0 SP2 P1.

Table 7 on page 9 lists the problems fixed in DM 2.0 SP1.

Fixed problems are sorted alphabetically by product feature and by issue number within
each product feature.

Table 4 Problems fixed in DM 2.1 SP1

Issue number Product feature Problem summary

44346 Deployment Manager Deployment Manager 2.1.1 and earlier may fail on a computer running Java version
1.7.0_71 or later and trying to upgrade the ISO.
Workaround: Use Deployment Manager version 2.1.1 or later; or use Java version
1.7.0_67 or older.

40566 RecoverPoint/SE Installer When installing RecoverPoint/SE, and provisioning the repository volume
Wizard automatically, the user may select a resource pool that is too small; that is, less
than 5.72 GB. In this case, the following error is displayed: “Failed to create
repository volume. Internal error. Cannot create a repository volume: An internal
error has occurred. Please contact Customer Support.”
Workaround: Ensure that the resource pools mapped to the RPA cluster have at
least 5.72 GB capacity available.

44223 VNXe When using the VNXe splitter to replicate vRPAs to a VNXe array, the Hardware
Replacement wizard is unable to register the vRPAs as iSCSI hosts on the VNXe
array. The SANView will be empty.
Workaround: Reboot the vRPA. The iSCSI initiators will be registered automatically
on the VNXe.

EMC RecoverPoint Deployment Manager Release Notes 7


Fixed problems

Table 5 Problems fixed in DM 2.1

Issue number Product feature Problem summary

28240 Modification If you change IP settings on an RPA that is installed with RecoverPoint/SE, you may
receive a network error when you run stand-alone SAN diagnostics.
Workaround: For each RPA that encounters errors with SAN diagnostics, for each
HostID=X that is in file "/home/kos/navi/credentials/installation/HostIDs":
- Create backup copies of all files that are being replaced in the subsequent steps.
- Copy "/home/kos/navi/credentials/RPSE/<X>/SecuredCLISecurityFile.xml" into
"/home/kos/navi/credentials/installation/SecuredCLISecurityFile.xml".
- Copy "/home/kos/navi/credentials/RPSE/<X>/SecuredCLIXMLEncrypted.key" into
"/home/kos/navi/credentials/installation/SecuredCLIXMLEncrypted.key".
- In appropriate HostID file, change IP settings to match actual environment storage
IPs.

39118 Upgrade RPAs Wizard When upgrading from 3.5.x to 4.0.x, applying the upgrade may fail (indicating a
connectivity error) on RPAs that are configured with IPv6 addresses.
Workaround 1: For each RPA that fails, detach the RPA from the cluster, modify the
IPs, as needed (including the IPv4 subnet mask, which may be an IPv6 address),
apply the new settings, and re-attach the RPA to the cluster. Then, complete the
upgrade wizard.
Workaround 2: Prior to the upgrade, ensure that all RPAs in the cluster have IPv4
addresses, and record and remove any IPv6 addresses. Following successful
completion of the upgrade, restore the IPv6 addresses and remove the IPv4
addresses.

Table 6 Problems fixed in DM 2.0 SP2 P1

Issue number Product feature Problem summary

37744 RecoverPoint/SE installations When upgrading RecoverPoint/SE from 3.5.* to 4.0.*, and when a failure occurs
and upgrades after one or more RPAs have already been successfully upgraded, it is not possible
to successfully complete the NDU procedure on the remaining RPAs. This is true
even when resuming the upgrade after fixing the cause of the initial failure, in
which case the error message, “Apply Upgrade Failed.
!NDUFLOW.INPUT_NOT_INITIALIZED!” is displayed.
Workaround: Upgrade using Deployment Manager 2.0 SP1.

37609 RecoverPoint/SE installations Installations or upgrades of RecoverPoint/SE 4.0 or later will not succeed if the
and upgrades computer running Deployment Manager 2.0 SP2 does not have Internet
connectivity. When the “Use an offline Upgrade Change Management XML file”
option is selected in the EMC Online Support credentials screen, the following
error message is displayed: “Upgrade Change Management XML file is invalid,
please contact EMC Customer Support.”
Workaround 1: Use Deployment Manager 2.0 SP1.
Workaround 2: Install or upgrade RP/SE only when you have Internet connectivity.

8 EMC RecoverPoint Deployment Manager Release Notes


Environment and system requirements

Table 7 Problems fixed in DM 2.0 SP1

Issue number Product feature Problem summary

34347 RecoverPoint Installer Wizard The Installer wizards allow you to install an RPA cluster even if the RPAs in the
and RecoverPoint/SE Installer cluster are running different releases of RecoverPoint. While the installation will
Wizard complete successfully, the cluster will not be functional.
Workaround 1: Use one of the ISO image update options (EMC Online Support site
or ISO image available locally) to ensure all the RPAs you are installing will run the
same RecoverPoint release.
Workaround 2: Ensure that all RPAs are running the same release of RecoverPoint
before completing the installation.

36080 RecoverPoint/SE installations Installations or upgrades of RecoverPoint/SE 4.0 or later will not succeed if the
and upgrades computer running Deployment Manager does not have Internet connectivity.
Workaround: Install or upgrade RP/SE only when you have Internet connectivity.

35875 Upgrade Cluster Wizard and When performing an upgrade of a RecoverPoint RPA cluster (4.0 and later) or
Upgrade RPAs WIzard system (earlier than 4.0), the upgrade wizard requires you to provide EMC Online
Support site credentials and perform Upgrade Change Management procedures,
even though these procedures are only intended for RecoverPoint/SE upgrades.

35789 Upgrade RPAs Wizard Only relevant when upgrading from release 3.5.x to 4.0.x
Trying to upgrade a one-site system will not succeed, as an RPA will fail to exit
maintenance mode. Workaround: Contact EMC Customer Support.

35990 RPA Replacement Wizard Only relevant to RecoverPoint/SE 4.0.x virtual RPA clusters
When you provide an incorrect RPA or storage CHAP password when replacing a
faulty vRPA that has CHAP credentials configured, the wizard will fail with the error,
“Unable to apply system settings to RPA <RPA number> at cluster <cluster name>.”
Workaround: Run the Cluster Modification Wizard and update the correct CHAP
password.

Environment and system requirements


Deployment Manager has the following environment and system requirements:
◆ A version of Java™ 7 (Update 13 or later) installed on the computer running
Deployment Manager. It is highly recommended to have the latest Java 7 update
installed.
◆ Windows OS: XP, 2003, 2008, 2008 R2, or 7
◆ For installations of RecoverPoint/SE 4.0 and later and RecoverPoint 4.0 SP1 and later,
virtual RPA (vRPA) clusters can be deployed in addition to physical RPA clusters. For
information on vRPA deployment, best practices, and limitations, refer to EMC
RecoverPoint vRPA Technical Notes.
◆ For upgrades from 3.5.x and later and installs from 4.0.x and later, EMC Online
Support credentials are required to benefit from the integration of Deployment
Manager with EMC Online Support. For details, refer to the EMC RecoverPoint
Installation and Deployment Guide.
◆ Under certain circumstances, RecoverPoint/SE upgrades from 3.5.x and later and
RecoverPoint/SE installs from 4.0 SP1 and later may require you to have a
locally-available Upgrade Change Management XML file to complete the upgrade. For
details, refer to the EMC RecoverPoint Installation and Deployment Guide.

EMC RecoverPoint Deployment Manager Release Notes 9


Known problems and limitations

◆ Since the Deployment Manager is a tool to help install new RecoverPoint


configurations and non-disruptively upgrade and modify existing RecoverPoint
configurations, all the relevant requirements for properly functioning RecoverPoint
configurations must be met. These requirements can be found in the EMC
RecoverPoint Release Notes.

Known problems and limitations


This section lists the limitations and known problems in the current RecoverPoint
Deployment Manager release.

Note: All information regarding interoperability limitations is available on E-Lab Navigator.

Limitations
Deployment Manager has the following limitations:
◆ Deployment Manager will not be able to communicate with RPAs if there is a network
address translation (NAT) firewall between the machine that runs the Deployment
Manager and the RPAs.
◆ Configuration files saved with DM versions that are no longer available on EMC Online
Support or Powerlink are not supported for use with the DM version currently
available online. For example, a saved upgrade configuration file created with DM 2.0
should not be applied with DM 2.0 SP1.
◆ The minimum supported screen (display) resolution is 1024x768.
◆ Only one instance of DM can be running at any one time on a work station.

10 EMC RecoverPoint Deployment Manager Release Notes


Known problems and limitations

Known problems
Table 8 on page 11 lists the known problems in RecoverPoint Deployment Manager.

When a problem is only relevant to a specific RecoverPoint release, it is noted as such in


the problem summary.

Table 8 Known problems (page 1 of 3)

Issue number Product feature Problem summary

44223 VNXe When using the VNXe splitter to replicate vRPAs to a VNXe array, the Hardware Replacement
wizard is unable to register the vRPAs as iSCSI hosts on the VNXe array. The SANView will be
empty.
Workaround: Reboot the vRPA. The iSCSI initiators will be registered automatically on the
VNXe.

40864 When attempting to replace a vRPA running RecoverPoint 4.0 or later (in a VNX storage
environment), with a vRPA running the same or later RecoverPoint version, the RPA
Replacement Wizard fails, accompanied by the error, “SAN view is empty. Check zoning and
LUN masking.” At that point, the cluster has one fewer RPA than the other clusters, and will be
more susceptible to full sweeps. This problem is caused by a change in the format of the RPA
IQNs.
Workaround 1: Manually register IQNs on the VNX in the new format, and add them to the
relevant Storage Group; the previous IQNs can be removed.
Workaround 2: Contact
EMC Customer Support to obtain a signed script.

41211 Deployment When using Deployment Manager to configure valid IPv6 gateways with "fe80::" addresses,
Manager configuration fails with the error message: “IP is out of subnet mask range.”
Workaround: Configure the IPv6 gateways using Installation Manager (boxmgmt).

34498 Converter Wizard Only relevant to 4.0-4.0.P1 releases


When trying to convert a RecoverPoint/SE or RecoverPoint system, if there are a different
number of RPAs in the RPA clusters of the system, the wizard will fail.
Workaround: Ensure there are the same number of RPAs in each cluster before running the
wizard.

41110 RecoverPoint RecoverPoint or RecoverPoint/SE installation will fail when attempted after the previous
Installer Wizard installation attempt failed. The error, “Unable to distribute ISO file. RPA already contains
and another ISO file, please contact Customer Support.” will appear in the system information log.
RecoverPoint/SE Workaround: Contact EMC Customer Support.
Installer Wizard

40059 RecoverPoint When you change the default MTU values during RecoverPoint or RecoverPoint/SE
Installer Wizard installation, the values may not be properly configured on the RPA.
and Workaround: Check the MTU values following installation and, if necessary, use Installation
RecoverPoint/SE Manager (boxmgmt) to modify the values.
Installer Wizard

36041 RecoverPoint In the following Installer wizard screens - “Apply iSCSI configuration results”, “Apply
Installer Wizard configuration results”, and “Upgrade and apply configuration results” - if the content of the
and screen exceeds the size of the Deployment Manager window, you will not be able to see the
RecoverPoint/SE results of all the RPAs, as the scrollbar does not appear.
Installer Wizard

41418 RecoverPoint Occasionally, navigation from the “Zoning and LUN masking” step may be blocked,
Installer Wizard accompanied by the error message, “Unhanded exception”.
Workaround: Restart the wizard, using a saved configuration file to avoid re-entry of all the
settings.

EMC RecoverPoint Deployment Manager Release Notes 11


Known problems and limitations

Table 8 Known problems (page 2 of 3)

Issue number Product feature Problem summary

40565 RecoverPoint/SE A maximum of about 18 iSCSI ports can be displayed on the “Storage iSCSI Ports” screen of
Installer Wizard the RecoverPoint/SE Installer wizard. Users who want to configure more ports must tab to
empty rows beyond the visible part of the table, and enter the data without being able to view
what they are entering.

34818 RecoverPoint/SE Only relevant to RecoverPoint/SE 4.0.x virtual RPA clusters


Installer Wizard When using the RecoverPoint/SE Installer Wizard to install a virtual RPA cluster, if you try to
configure the CHAP credentials, you will not be able to select a repository volume and
complete the installation.
Workaround: Create the CHAP credentials on the storage array prior to installing
RecoverPoint/SE. The CHAP user should be of type “Initiator” with initiator name “ANY”.

28566 RecoverPoint/SE Only relevant to RecoverPoint/SE 3.5.x and earlier releases


Installer Wizard Using the RecoverPoint/SE Installer Wizard, if the repository volume is provisioned in an
existing RAID group with some block fragmentation, journal provisioning fails, you are
prompted to contact Customer Support, and installation will fail.
Workaround: Allocate the volume manually.

34481 RPA Replacement Only relevant to RecoverPoint/SE 4.0 release


Wizard When replacing a faulty vRPA, using the RPA Replacement Wizard on a virtual RecoverPoint/SE
cluster, the new vRPA does not accept the new settings. RPA Replacement Wizard does not
support virtual clusters.
Workaround:
Apply the previous RPA’s ISO to the new RPA.
Turn off the faulty RPA.
Set the previous RPA’s IP address to the new RPA.
Run the new RPA.
Use boxmgmt commands “Get remote settings” and “Apply settings”.

29367 System Only relevant to 3.5.x releases


Modification If you rename the site of an environment with a VNX/CLARiiON splitter attached and
Wizard credentials configured, the VNX/CLARiiON credentials will become invalid and the Wizard will
fail to apply system modifications. You will not be able to create new groups, and collecting
logs from VNX/CLARiiON will not work. Workaround: Re-enter VNX/CLARiiON splitter
credentials in RecoverPoint and wait for 10 minutes.

29288 System Relevant to 3.5.x - 4.0.x releases


Modification When using the Wizard to change the WAN protocol from IPv6 to IPv4, and change all WAN
Wizard IPv6 addresses to IPv4 addresses, this may cause a loss of connectivity between RPAs,
leading to the data link to go down and replication to stop (which will also be reflected in the
RecoverPoint GUI). Workaround: Reboot the RPAs, pair by pair (L1/R1, when up, L2/R2, and
so on).

30964 Upgrade RPAs Only relevant to releases 3.4 SP4 - 3.5 SP1 P2
Wizard and During upgrade or installation of a RecoverPoint/SE environment, the system may fail to
RecoverPoint/SE obtain WWNs from the RPAs, leading to the upgrade or installation to fail.
Installer Wizard Workaround: Contact EMC Customer Support for a signed script.

30154 Upgrade RPAs Only relevant when upgrading from a release earlier than 3.5 SP1 to 4.0.x
Wizard Attempting to upgrade a RecoverPoint 3.5.x environment with host-based splitters (KDrivers)
or intelligent fabric-based splitters (Brocade, SANTap) to RecoverPoint 4.0 or later will fail.
Workaround 1: Before starting upgrade, remove all the aforementioned splitter types from the
system.
Workaround 2: After starting upgrade, format the repository volume.

12 EMC RecoverPoint Deployment Manager Release Notes


Known problems and limitations

Table 8 Known problems (page 3 of 3)

Issue number Product feature Problem summary

29698 Upgrade RPAs Only relevant when upgrading from release 3.5.0 to 4.0.x
Wizard When attempting to upgrade an environment with a journal size of less than 10 GB for a
non-distributed consistency group (CG), or less than 40 GB for a distributed CG, the upgrade
will fail.
Workaround 1: Before performing the upgrade, ensure that all array volumes allocated to the
journal for non-distributed CGs are at least 10 GB, and at least 40 GB for all distributed CGs.
Workaround 2: If you are in the middle of performing the upgrade and it has failed, then
reformat the repository volume.

28770 Upgrade RPAs Only relevant when upgrading from a release earlier than 3.5 SP2 to 4.0.x
Wizard If WWN spoofing is done manually on an RPA using “root” user, an upgrade will cause the
storage volumes and LUNs to be inaccessible for that RPA. The spoof information is not
recorded in system settings, resulting in a loss of access to the storage LUNs for the RPA.
Workaround 1: Before the upgrade, perform WNN spoofing using Installation Manager
(boxmgmt) of the RPA.
Workaround 2: After the upgrade, correct the zoning and LUN masking.

27807 Upgrade RPAs Only relevant when upgrading to 3.5.x and earlier releases
Wizard When attempting to apply an upgrade to an environment while an RPA is under heavy load,
the Wizard will fail to perform the upgrade and display the error message, “Failed to get
information from RPA with IP address <IP>”. Workaround: Reduce the load (pause or stop
consistency groups) on the RPA and try again.

27265 Upgrade RPAs If a RecoverPoint setup that was previously installed with one more RPAs using spoofed
Wizard WWNs is reinstalled using the RecoverPoint or RecoverPoint/SE Installer Wizard, then a
subsequent upgrade (using the Upgrade RPAs Wizard) will erase the spoofed WWNs and the
upgrade will fail when the RPA tries to access the repository with the error message “System
unable to configure repository volume. Volume is not visible to RPA.”
Workaround: When the upgrade fails, manually spoof the RPA WWNs using the Installation
Manager (boxmgmt), then click “Retry” to continue the upgrade.

24812 Upgrade RPAs Only relevant when upgrading to 3.4.


Wizard When upgrading an environment that does not have a domain name configured, the apply
upgrade configuration will fail with the error message “Java null pointer exception”.
Workaround: Contact EMC Customer Support.

23682 Upgrade RPAs Only relevant when upgrading to 3.3.SP1 and earlier releases
Wizard When upgrading, once the system goes into upgrade mode, the apply upgrade will fail due to
a system timeout. The following error message appears, “System failed to enter upgrade
mode”. When upgrading to 3.2.x, the upgrade will fail after approximately 5 minutes. When
upgrading to 3.3.x, the upgrade will fail after approximately 10 minutes.
Workaround: Contact EMC Customer Support.

21280 Upgrade RPAs Only relevant when upgrading to 3.2.P1 - 3.3.SP1.P1


Wizard When performing a non-disruptive upgrade, if an RPA that has not yet been upgraded is
removed for maintenance and is not upgraded, the system will start will start crashing after
approximately five minutes. The wizard will stop working and you will be unable to continue.
Workaround: Upgrade the RPA that was removed for maintenance.

21150 Upgrade RPAs Only relevant when upgrading to 3.4.x and earlier releases
Wizard When upgrading a Brocade splitter environment to 3.2 or later, the wizard fails 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. The following message appears in the wizard “Error:
Initiator or Target can only be binded to one Brocade switch”.
Workaround: Contact EMC Customer Support.

EMC RecoverPoint Deployment Manager Release Notes 13


Technical notes

Technical notes
Refer to the relevant RecoverPoint technical notes for information on deploying
RecoverPoint with the following splitter types:
• VNX
• Symmetrix
• VPLEX
• Brocade (earlier than 4.0)
• SANTap (earlier than 4.0)
• VNXe (4.1 and later)
• ScaleIO (4.1 and later)

Documentation
The following documents, available on the EMC Online Support site,
http://support.emc.com, provide additional information about RecoverPoint:
◆ EMC RecoverPoint Installation and Deployment Guide
◆ EMC RecoverPoint Documentation Set (for your RecoverPoint release)

Software media, organization, and files


Generally, RecoverPoint software components, such as Deployment Manager, are
downloaded and installed by EMC personnel. However, as mentioned in
“RecoverPoint/SE is now customer installable” on page 5 and “Install virtual RPA clusters
in a RecoverPoint/SE system” on page 6, RecoverPoint/SE customers can now access
software and perform their own installations and upgrades.

The latest Deployment Manager is available as a zip file that can be downloaded from the
Downloads for RecoverPoint CL section on EMC Online Support:

https://support.emc.com > Support by Product > RecoverPoint CL > Downloads

To launch the Deployment Manager, unzip the folder and open the RecoverPoint_DM.exe
file. The login screen will appear.

Selecting “Other operations (EMC personnel)” requires a username and password and
provides you with access to all of the Deployment Manager wizards, as detailed in
“Product description” on page 2.

Installation
This sections provides an overview of installation and upgrade instructions for
RecoverPoint and RecoverPoint/SE.

14 EMC RecoverPoint Deployment Manager Release Notes


Troubleshooting and getting help

Installing
To install RecoverPoint 3.2 and later, you must use the RecoverPoint Installer Wizard. To
install RecoverPoint/SE 3.2 and later, you must use the RecoverPoint/SE Installer Wizard.

Refer to the EMC RecoverPoint Installation and Deployment Guide for detailed
instructions.

Upgrading
To non-disruptively upgrade RecoverPoint and RecoverPoint/SE 3.1 and later software
releases (the code that runs on the RPAs), also known as performing an NDU, you must
use the Upgrade RPAs Wizard (for releases earlier than 4.0) or the Upgrade Cluster Wizard
(for 4.0 and later releases).

Refer to the EMC RecoverPoint Installation and Deployment Guide for detailed
instructions.

Licensed features
After performing a major upgrade (for example, from 3.2 to 3.3), it is recommended to
obtain a new license key and activation code for the release from EMC (at no extra cost).
Until a new license is set in the RecoverPoint environment, licensed features for the
release will remain disabled.

When upgrading to RecoverPoint 4.1, previous licenses will automatically be converted to


the new license format. However, the new licenses are temporary and valid for 90 days
from the date of upgrade. After that, you must have installed one or more permanent
license files to replicate with RecoverPoint. Instructions for licensing are detailed in the
EMC RecoverPoint 4.1 Administrator’s Guide.

Refer to the relevant EMC RecoverPoint Release Notes for information on the licensed
features for the release.

Troubleshooting and getting help


EMC support, product, and licensing information can be obtained as follows:

Product information
For documentation, release notes, software updates, or information about EMC products,
go to EMC Online Support at:

https://support.emc.com

Technical support
Go to EMC Online Support and click Service Center. You will see several options for
contacting EMC Technical Support. Note that to open a service request, you must have a
valid support agreement. Contact your EMC sales representative for details about
obtaining a valid support agreement or with questions about your account.

EMC RecoverPoint Deployment Manager Release Notes 15


Troubleshooting and getting help

Copyright © 2010 - 2015 EMC Corporation. All rights reserved. Published in the USA.

Published February 9, 2015

EMC believes the information in this publication is accurate as of its publication date. The information is subject to change without
notice.

The information in this publication is provided as is. EMC Corporation makes no representations or warranties of any kind with
respect to the information in this publication, and specifically disclaims implied warranties of merchantability or fitness for a
particular purpose. Use, copying, and distribution of any EMC software described in this publication requires an applicable software
license.

EMC2, EMC, the EMC logo, and EMC RecoverPoint are registered trademarks or trademarks of EMC Corporation in the United States
and other countries. All other trademarks used herein are the property of their respective owners.

For the most up-to-date regulatory document for your product line, go to EMC Online Support (https://support.emc.com).

16 EMC RecoverPoint Deployment Manager Release Notes

You might also like