Professional Documents
Culture Documents
Deployment Manager Release Notes - 300-010-477 - 13
Deployment Manager Release Notes - 300-010-477 - 13
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:
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.
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).
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.
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.
RecoverPoint/SE Installer ✓ ✓2 ✓ ✓ ✓
RecoverPoint Installer3 ✓ ✓4 ✓ ✓ ✓
Connect Cluster ✓ ✓
RPA Replacement ✓ ✓ ✓ ✓ ✓
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.
Note: This section is for informational purposes only. You should use only the latest
available release of RecoverPoint Deployment Manager.
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.
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.
Fixed problems are sorted alphabetically by product feature and by issue number within
each product feature.
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.
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.
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.
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.
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.
Known problems
Table 8 on page 11 lists the known problems in RecoverPoint Deployment Manager.
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).
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.
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.
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.
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.
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.
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.
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)
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:
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.
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.
Refer to the relevant EMC RecoverPoint Release Notes for information on the licensed
features for the release.
Product information
For documentation, release notes, software updates, or information about EMC products,
go to EMC Online Support at:
https://support.emc.com
Technical support
Go to EMC Online Support and click Service Center. You will see several options for
contacting EMC Technical Support. Note that to open a service request, you must have a
valid support agreement. Contact your EMC sales representative for details about
obtaining a valid support agreement or with questions about your account.
Copyright © 2010 - 2015 EMC Corporation. All rights reserved. Published in the USA.
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).