RecoverPoint SP4 Upgrade

EMC RecoverPoint Procedure Generator
Topic
Upgrade Procedure
Selections
Upgrade Software or Hardware?: Software
Select component to upgrade: RPA and Splitter or RPA only
Select Current Version: 3.3 SP1
Select Version to Upgrade to: 3.4 SP4
Select Replication Configuration: CRR or CLR
Register RecoverPoint with ESRS Gateway?: No
Select Splitter Technology for Site 1: CLARiiON / VNX
Site 1: Select CLARiiON storage-system model?: CX4-120 or CX4-240 or CX4-480
Site 1: What storage-system management software is your storage system running?: Unisphere
-FLARE 30 or later
Site 1: Select the type of install: Install / Update Sofware Enabler
Select Splitter Technology for Site 2: CLARiiON / VNX
Site 2: Select CLARiiON storage-system model?: CX4-120 or CX4-240 or CX4-480
Site 2: What storage-system management software is your storage system running?: Unisphere
-FLARE 30 or later
Site 2: Select the type of install: Install / Update Sofware Enabler
Procedure Generated: 3/29/2013 11:25:22 PM

IMPORTANT: To be sure you have the latest procedure generator application and content, always
choose Yes when asked if you want to update the application or repository.
CHANGE CONTROL
Installation/Upgrade Information:
You must submit a Change Control Request for all installation and upgrade activities.
EMC Personnel:
Refer to http://10.241.171.170/RecoverPoint/Change_Control/ for more details on CCA process. You
need to be on the EMC network.
EMC Partner:
Please fill out the form below and email to recoverpoint_change_control@emc.com for more details about
the CCA process.
RecoverPoint
Change Control Request Form_1_9.docx
EMC CONFIDENTIAL
3.5 SP1
1 of 33

REPORT PROBLEMS
If you find any errors in this procedure or have comments regarding this application, send email to
SolVeFeedback@emc.com
Copyright 2009 2013 EMC Corporation. All rights reserved.

Publication Date: March, 2013
EMC believes the information in this publication is accurate as of its publication date. The information is subject to
change without notice.
THE INFORMATION IN THIS PUBLICATION IS PROVIDED AS IS. EMC CORPORATION MAKES NO
REPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION IN THIS
PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS
FOR A PARTICULAR PURPOSE.
Use, copying, and distribution of any EMC software described in this publication requires an applicable software
license.
For the most up-to-date regulatory document for your product line, go to the Technical Documentation and Advisories
section on EMC Powerlink.
For the most up-to-date listing of EMC trademarks, see the list of EMC Corporation Trademarks on EMC.com.
All other trademarks used herein are the property of their respective owners.
EMC CONFIDENTIAL
3.5 SP1
2 of 33
Contents
RecoverPoint 3.4 SP4 Upgrade........................................................................................... 5
Before you start........................................................................................................................................... 5
Mandatory EMC Knowledgebase Solutions................................................................................................. 5
Upgrading RPA Software to RecoverPoint 3.4 SP4........................................................... 6

Upgrade the RecoverPoint software non-disruptively using Deployment ManagerError: Reference source
not found...................................................................................................................................................... 6
Upgrade matrix to latest RecoverPoint releases............................................................................. 7
PrerequisitesError: Reference source not found............................................................................. 8
Handling system modificationsError: Reference source not found................................................. 9
Verify and disable reservations supportError: Reference source not found.................................. 10
Upgrade procedure............................................................................................................................... 10
Download the Deployment Manager.................................................................................................... 11
Launch Upgrade RPAs Wizard............................................................................................................. 11
1. Prepare for upgradeError: Reference source not found................................................................... 12
2. Login credentials.............................................................................................................................. 13
IP credentials................................................................................................................................ 13
RecoverPoint login credentials..................................................................................................... 13
RecoverPoint CLI credentials....................................................................................................... 13
3. Login credentials summary............................................................................................................... 14
4. ISO file distribution........................................................................................................................... 15
4.1 ISO file informationError: Reference source not found........................................................... 15
4.1.1 FTP credentials summaryError: Reference source not found.............................................. 16
4.2 ISO file distribution summaryError: Reference source not found............................................ 17
5. System diagnostics........................................................................................................................... 18
6. Save system filesError: Reference source not found........................................................................ 19
Save configuration fileError: Reference source not found............................................................. 19
Export modifications (if relevant)................................................................................................... 19
Apply/Resume upgrade configurationError: Reference source not found............................................. 20
RecoverPoint installation credentials............................................................................................ 20
RecoverPoint CLI credentials....................................................................................................... 20
Load saved configuration file........................................................................................................ 20
Import modifications file (if relevant)............................................................................................. 20
Apply upgrade configurationError: Reference source not found........................................................... 21
EMC CONFIDENTIAL
3.5 SP1
3 of 33

Import modifications file (if relevant)............................................................................................. 21
Environment diagnostics...................................................................................................................... 22
Apply/Resume upgrade summary........................................................................................................ 23
Re-enabling reservations support (if relevant).............................................................................. 25
Ensuring upgrade is successful.................................................................................................... 25
Updating license........................................................................................................................... 25
Recovery policy............................................................................................................................ 25
Logs.............................................................................................................................................. 25
Verify and collect system modifications filesError: Reference source not found........................... 26
Removing SCSI-2 reservations supportError: Reference source not found.................................. 28
Site 1 Splitter Upgrade....................................................................................................... 29

RecoverPoint Splitter Requirements..................................................................................................... 29
Mandatory EMC Knowledgebase Solutions......................................................................................... 30
Before you start............................................................................................................................ 30
Installing a software enabler......................................................................................................... 31
Site 2 Splitter Upgrade....................................................................................................... 33
EMC CONFIDENTIAL
3.5 SP1
4 of 33
RecoverPoint 3.4 SP4 Upgrade

Before you start
This procedure should only be used if it was approved for use by the RecoverPoint Change Control
process.
CAUTION: All RecoverPoint upgrade activities require a change control. Please refer to the
RecoverPoint change control process:
http://10.241.171.170/RecoverPoint/Change_Control/RecoverPoint_Change_Control_Process.
Mandatory EMC Knowledgebase Solutions

Note: Review and understand all referenced knowledgebase solutions before proceeding with the
activity.
Table 1
EMC
Knowledgebase
Solution Number
Title
emc197729
RecoverPoint: Images no longer displayed in the image list from journal tab after failing over
preferred RPA
emc217780
RecoverPoint: NDU tool fails during upgrade from Engineering build to RecoverPoint 3.2.
emc217845
RecoverPoint: Non Disruptive Upgrade (NDU) tool fails during upgrade
emc222022
RecoverPoint: NDU tool fails during upgrade to RecoverPoint 3.2 if RPI tool used to install
the original environment
emc220041
RecoverPoint: WAN and LAN on the same subnet will fail when WAN gateway is configured
emc220874
RecoverPoint: NDU tool upgrade to 3.2 fails if LAN and WAN are on the same subnet and
no WAN gateway is configured
emc222065
RecoverPoint : NDU Installation tool fails when connecting to ftp server
emc222066
RecoverPoint : NDU tool fails when non-default admin and/or boxmgmt passwords have
been set for RPA
emc222378
RecoverPoint/Cluster Enabler: RP/CE operations fail following an NDU upgrade
emc224829
RecoverPoint: (SANTap) After an NDU, the splitter status is appearing as unknown at site.
emc227001
RecoverPoint: NDU fails leaving all RPA processes down and GUI and CLI inaccessible
emc238443
Deployment Manager upgrade to 3.3 fails due to Error: Initiator or Target can only be binded
to one Brocade switch
emc239871
RecoverPoint: WAN problems encountered when sites are in the same subnet and the WAN
EMC CONFIDENTIAL
3.5 SP1
5 of 33

gateway is not defined.
emc240960
RecoverPoint: Upgrade function "Download ISO" fails on error "Unable to execute

command. Illegal parameters"
emc242535
RecoverPoint: WAN problems when the sites are in different subnet and the local LAN and
WAN are configured to use the same subnet
emc243009
RecoverPoint: Upgrade from 3.2 to 3.3 with group sets configured will cause Assertion
errors and the upgrade will fail
emc256023
RecoverPoint: Brocade Splitter continuously loses communication with RecoverPoint after

Non-Disruptive Upgrade (NDU) of RecoverPoint 3.2.x to 3.3 SP1.x
emc244711
RecoverPoint: Brocade is no longer qualifying mixed fabric (Brocade and McDATA)

environments for RecoverPoint implementations
emc249286
RecoverPoint: Consistency Groups can go into a Full Sweep upon upgrading or

downgrading FLARE code
emc250167
RecoverPoint: While upgrading RecoverPoint Software the Deployment Manager (DM)

indicates that it can not get the current release from a RecoverPoint Appliance (RPA)
emc268065
RecoverPoint: Intelligent Fabric (Brocade) Splitter: NDU failed while safe bindings in use
emc272499
RecoverPoint: RecoverPoint Management Console / Graphical User Interface (GUI) stops

working after upgrade to RecoverPoint 3.4.x
CAUTION: If Replication Manager is used in the environment, please be aware of compatibility

requirements between different versions of RecoverPoint and Replication Manager. Please
consult the RecoverPoint Support Matrix and Replication Manager Support Matrix for details.
Upgrading RPA Software to RecoverPoint 3.4 SP4

Upgrade the RecoverPoint software non-disruptively using Deployment Manager
Upgrading to the latest RecoverPoint releases requires using the RecoverPoint Deployment Manager,
which contains the Upgrade RPAs Wizard, a Java-based GUI wizard that allows you to perform nondisruptive upgrades of RPA software starting from release 3.1 and later. The Wizard is composed of two
flows Prepare for Upgrade and Apply/Resume Upgrade.
The Prepare for Upgrade wizard guides you through the verification of RecoverPoint credentials and
downloads ISO files to all RPAs in the environment. The Apply/Resume Upgrade wizard applies the
upgrade to all RPAs. Once the upgrade is complete, you can continue using the RecoverPoint
Management Application GUI.
While the upgrade procedure does not upgrade RecoverPoint splitters (KDriver, VNX/CLARiiON,
SANTap, Brocade, Symmetrix, and VPLEX), a RecoverPoint environment can simultaneously support
splitters from two adjacent releases (for example, a 3.5 environment can support both a 3.5 splitter and a
3.4 SP2 splitter). However, EMC advises you to upgrade splitters to the same RecoverPoint release to
gain the latest splitter functionalities and features.
EMC CONFIDENTIAL
3.5 SP1
6 of 33

Upgrade matrix to latest RecoverPoint releases
To
From
Procedure
Disruptive
3.5 and later
1. Deployment Manager upgrade to latest 3.5
No
3.4 and later
No
3.3 and later
No

3.2 SP2 and later
No

3.2 and 3.2 SP1
Latest 3.5 release
No

3.1 and later
No

3.0 and later
1. boxmgmt upgrade to latest 3.1
Yes

3.4 and later
No
3.3 and later
No
3.2 SP2 and later
No

Latest 3.4 release
3.2 and 3.2 SP1
No

3.1 and later
No

3.0 and later
Yes

3.3 and later
EMC CONFIDENTIAL
No
3.5 SP1
7 of 33
Latest 3.3 release
3.2 SP2 and later
No
3.2 and 3.2 SP1
No

3.1 and later
No

3.0 and later
Yes

Latest 3.2 release
3.2 and later
No
3.1 and later
No
3.0 and later
Yes
Prerequisites
Before using the Upgrade RPAs Wizard, ensure the following conditions are met:
The RecoverPoint system is operating without any errors and warnings.
The computer that the Wizard is run from must be able to communicate with the site management IP
and all RPA management (LAN) networks on both sites. Ensure that ports 21, 22, 8081, and 8082 (all
TCP) are open for communication on all RPAs.
Tip: Telnet to these ports on the computer to ensure they are open.
A version of Java 6 (update 13 or higher) must be installed on the computer you are performing the
upgrade from.
RPAs are running RecoverPoint release 3.1 or later.
IMPORTANT: If upgrading to release 3.5 or later, all RPAs must be Gen4 or later. If upgrading to
release 3.4 or later, all RPAs must be Gen3 or later.
You have RecoverPoint login credentials (installation and CLI).
Note: Installation
username
and
CLI username and default password = admin).
default
password
boxmgmt.
If planning to download an ISO file from an FTP server:

You have at least one 3.2 SP2 or later ISO file available on the FTP server.
You have FTP access from all RPAs and you have FTP server credentials.
If planning to download an ISO file from a DVD or USB device:
RPAs that you are upgrading must already be running 3.5 or later.
If upgrading from 3.1 or 3.1 SP1 You have verified and collected system modifications files. For
the procedure, see the "Verify and collect system modifications files" section.
EMC CONFIDENTIAL
3.5 SP1
8 of 33

If upgrading to 3.5 or later You have removed reservations support for consistency groups that
have Reservations Policy=SCSI-2. For the procedure, see the "Removing SCSI-2 reservations
support" section.
If upgrading to a release earlier than 3.5 You have disabled reservations support for consistency
groups that have Reservations Policy=SCSI-2. For the procedure, see the "Verify and disable
reservations support" section.
Handling system modifications

To ensure a properly functioning upgrade of the RecoverPoint system, you must verify if any
modifications (tweak parameters and signed scripts) exist in the system you are upgrading, and if they
need to be applied to the system before you plan to upgrade.
If upgrading from 3.1 or 3.1 SP1, you must check for tweak parameters and signed scripts, as indicated in
the "Verify and collect system modifications files" section.
If upgrading from 3.1 SP2 and later or 3.2 P1 and later, you do not need to check for system
modifications, as the Wizard does this for you automatically.
the "Handling system modifications for upgrades to 3.2 and later" table shows the actions that need to be
taken based on whether system modifications were found or not.
Table 2
Handling system modifications for upgrades to 3.2 and later
Upgrade from
1 - Were tweak
parameters found?
2 - Were signed scripts found?
3.1
No - Apply upgrade.
Yes - Submit tweak
parameters to CS and wait
for response.
Not relevant (Signed scripts

verification is not available in 3.1).
3.1 SP1
No - Check for signed

scripts.
No - Apply upgrade.
Yes - Submit signed scripts to CS
and wait for response.
Yes - Check for signed

scripts.
No - Submit tweak parameters to

CS and wait for response.
Yes - Submit tweak parameters
and signed scripts to CS and wait
for response.
3.1 SP2 and later

3.2 P1 and later
3.3 P2 and later
3.4 and later
3.5 and later
The Wizard automatically checks for tweak parameters and

signed scripts.
If no modification are found - Apply upgrade.
If modifications are found, they are saved to a file - Submit
the file to CS and wait for a response before applying the
upgrade.
When you submit a system modifications file or files (tweak parameters and/or signed scripts) for analysis
to Customer Service, do so in an Upgrade Service Request. In the request, indicate that the attached file
or files need to be reviewed for a pending upgrade, and indicate the intended date of the upgrade.
Recommended severity is no higher than 3.
EMC CONFIDENTIAL
3.5 SP1
9 of 33

IMPORTANT: If modifications are found, they are saved to a file. You must submit this file in an Upgrade
Service Request to Customer Service for analysis, and allow at least 5 business days for a response from
Customer Service before performing the Apply upgrade configuration step of the Wizard. This time frame
is to allow Customer Service to analyze the files, research the contents, and respond to you.
Depending on the response you receive, you will either:
Be provided with a modifications file to insert in the Apply upgrade configuration step of the Wizard.
Be provided with a statement that you can continue the Apply upgrade configuration step of the
Wizard without the need to insert a modifications file.
Verify and disable reservations support

If upgrading to a release earlier than 3.5, the Upgrade RPAs Wizard does not support upgrade of
consistency groups with SCSI-2 reservations policy enabled. You must verify and disable reservations
support before performing the upgrade procedure.
Use the procedure below to verify and disable reservations support for consistency groups that have
Reservations Policy=SCSI-2.
1. [ ] Verify reservations policy of a consistency group:
a. In the Navigation Pane of the RecoverPoint GUI, select and expand a consistency group under
Consistency Groups.
b. Select a copy under the group, click its Policy tab in the Component Pane, and expand the
Advanced section.
If Reservation Policy equals SCSI-2, continue to Step Error: Reference source not found.
If Reservation Policy does not equal SCSI-2, repeat Step Error: Reference source not found for
another copy in the same group.
If you have checked all the copies of the group, and none of the copies have Reservation
Policy=SCSI-2, continue to Step Error: Reference source not found.
2. [ ] Record the name of the consistency group that has at least one SCSI-2-enabled copy, as you will
need this information when enabling reservations support after the upgrade procedure.
3. [ ] Disable reservations support for the consistency group:
a. Select the consistency group which has at least one copy with Reservation Policy=SCSI-2 and
click its Policy tab in the Components Pane.
b. Expand the Advanced section and clear the Reservations Support checkbox.
4. [ ] Repeat this procedure, beginning from Step Error: Reference source not found, for each
consistency group.
IMPORTANT: Once the upgrade is complete, enable reservations support for groups that you
disabled before upgrade.
Upgrade procedure
To perform the upgrade procedure, you must download and launch the Deployment Manager. First
complete Upgrade RPAs Wizard Prepare for Upgrade, then complete Upgrade RPAs Wizard Apply
Upgrade.
EMC CONFIDENTIAL
3.5 SP1
10 of 33

Note: The procedure may take to complete, depending on the FTP server, network speed, and size of
environment being upgraded.
Download the Deployment Manager

To download the Deployment Manager:
1. [ ] From Software Downloads and Licensing section of Powerlink, download the Deployment Manager
zip file.
2. [ ] Copy the file to your computer.
3. [ ] Extract (unzip) the file contents.
Launch Upgrade RPAs Wizard

To launch the Upgrade RPAs Wizard:
1. [ ] Launch the Deployment Manager by opening the RecoverPoint_DM.exe application file.
2. [ ] On the login screen (the "Error: Reference source not found" illustration), select Other operations
(EMC personnel) and enter your RecoverPoint login credentials (CLI).
Note: Default CLI username and password = admin.
IMPORTANT: Selecting Perform RecoverPoint/SE minor upgrade is only intended for
RecoverPoint/SE customers that have received approval to perform such an upgrade. Contact EMC
Customer Service for more information. If you are EMC personnel, it is strongly recommended to upgrade
RecoverPoint/SE using the Other operations (EMC personnel) option.
Figure 1
Deployment Manager login screen
EMC CONFIDENTIAL
3.5 SP1
11 of 33

3. [ ] On the Deployment Manager wizard selection screen, select option Upgrade RPAs Wizards Prepare for Upgrade (the "Error: Reference source not found" illustration).
Note: The Prepare for Upgrade wizard must be run and completed before running the Apply
Upgrade wizard.
Figure 2
Deployment Manager wizard selection screen
IMPORTANT: Ensure you have read and followed the "Prerequisites" section before continuing with
the "1. Prepare for upgrade" section.
1. Prepare for upgrade

Review the conditions for upgrading your environment and verify that you have fulfilled them (the "Error:
Reference source not found" illustration).
Select the I have fulfilled the conditions for upgrading the RPAs checkbox and click Next.
EMC CONFIDENTIAL
3.5 SP1
12 of 33
Figure 3
Prepare for upgrade screen
2. Login credentials
Enter login credentials (the "Error: Reference source not found" illustration):
IP credentials
Enter a site management or an RPA IP address.
RecoverPoint login credentials

Enter RecoverPoint installation username and password.
Note: Installation username and default password = boxmgmt.
RecoverPoint CLI credentials

Enter RecoverPoint CLI username and password.
Only required when upgrading from 3.1.
Note: CLI username and default password = admin.
EMC CONFIDENTIAL
3.5 SP1
13 of 33
Figure 4
Login credentials screen
3. Login credentials summary

Review the statuses of the RPAs in the system (the "Error: Reference source not found" illustration).
The system communicates and validates the statuses of the RPAs and confirms that all components are
OK or that errors are detected.
If errors are detected for an RPA, a comment will appear describing the problem. To proceed to the next
step in the wizard, you must resolve all errors. Once errors are resolved, click Retry to revalidate the
communication statuses.
When all statuses appear OK (green check mark), click Next.
Figure 5
Login credentials summary screen
EMC CONFIDENTIAL
3.5 SP1
14 of 33

4. ISO file distribution
Choose an option on how to distribute ISO files to RPAs.
4.1 ISO file information

There are three options to distribute ISO files to the RPAs (in the "Error: Reference source not found"
illustration, Download from FTP server is selected):
the "Upload from local machine" section
the "Copy from DVD or USB device inserted in the RPAs" section
the "Download from FTP server" section
Note: When upgrading RPAs running releases earlier than 3.5, Download from FTP server is the only
available option for ISO file downloads. When upgrading RPAs running 3.5 or later releases, all three
options are available.
For all options, the ISO file names must be the exact name as they appear on Powerlink, and identical for
all options on both sites (if performing a two-site upgrade). Renaming the files may prevent the upgrade
from working properly.
Upload from local machine

(Only available when upgrading RPAs already running 3.5 or later)
Enter the file name of the ISO file that you located on your local machine (the computer running
Deployment Manager), or click Browse to find the file.
Continue to the "4.2 ISO file distribution summary" section.
Copy from DVD or USB device inserted in the RPAs

(Only available when upgrading RPAs already running 3.5 or later)
Enter the file name of the ISO file that is on the DVD or USB devices.
When using DVD option, a DVD with the ISO file must be loaded in each RPA at the site for the download
to work properly.
When using USB option, a USB with the ISO file must be connected to each RPA at the site for the
download to work properly.
If all of the RPAs being upgraded have DVD/USB devices inserted in them, select the I have a DVD/USB
inserted in all of the RPAs checkbox. This will enable Deployment Manager to automatically download
the ISO files to the RPAs at the site once you click Next.
Continue to the "4.2 ISO file distribution summary" section.
Download from FTP server

Enter FTP credentials of an FTP server where the RecoverPoint 3.2 or later ISO file is located to
download it to the RPAs.
Qualified FTP servers: CuteFTP, Fedora Linux, FileZilla, Gene6, Xlight, Windows FTP Service.
Note: If upgrading a two-site setup, it is recommended to download the ISO file from two local FTP
servers (one FTP server at each site). This operation may significantly reduce the ISO file download time.
Enable FTP credentials (per site, if relevant):
Server IP address.
EMC CONFIDENTIAL
3.5 SP1
15 of 33

Server port number to connect on FTP server (default is 21).
Username.
Password.
Example: /files/folder3
File location (location of ISO file on the FTP server).
Example: rel3.4.SP2_l.48_release_64_emc_md5_e11ce8b9190e8788daeb2e7bfe82b2c6.iso
File name (name of the ISO file on the FTP server).
Once all information has been entered, click Next to begin the download and distribution of the ISO file(s)
to the RPAs.
Continue to the "4.1.1 FTP credentials summary" section.
Figure 6
ISO file information screen
4.1.1 FTP credentials summary

Review the status of the FTP connectivity results (the "Error: Reference source not found" illustration).
Note: This screen only appears if you selected Download from FTP server for one or more sites in the
"4.1 ISO file information" section.
The system communicates and validates the connectivity to the FTP servers and confirms that all
connections are OK or that errors are detected.
If errors are detected for an FTP server, a comment will appear describing the problem. To proceed to the
next step in the wizard, you must resolve all errors. Once errors are resolved, click Retry to revalidate the
communication statuses.
EMC CONFIDENTIAL
3.5 SP1
16 of 33
Figure 7
FTP credentials summary screen
4.2 ISO file distribution summary

Review the status of the ISO file distribution results (in the "Error: Reference source not found" illustration,
Upload from local machine was selected for both sites).
Beside the site name is an indication of the ISO distribution option you selected (local machine,
USB/DVD, or FTP).
If you selected:
Upload from local machine, the file distribution will start automatically. However, once download
begins, you can click Stop to stop the download.
Copy from DVD or USB device inserted in the RPAs
And selected the checkbox, the file distribution will start automatically.
And did not select the checkbox, you must click Start to begin downloading the file.
Download from FTP server, the file distribution will start automatically.
The system verifies the ISO file download and distribution to all RPAs and confirms that they are OK or
that errors are detected.
If errors are detected for an ISO file for a particular RPA, a comment will appear describing the problem.
To proceed to the next step in the wizard, you must resolve all errors. Once errors are resolved, click
Retry to revalidate the communication statuses.
EMC CONFIDENTIAL
3.5 SP1
17 of 33
Figure 8
ISO file distribution summary screen
5. System diagnostics
System diagnostics are performed for the site(s) and the RPAs. By doing so, the system attempts to
validate that the current configuration is appropriate and that RecoverPoint can successfully operate in
the current environment (the "Error: Reference source not found" illustration).
The site system diagnostics will present the following results: Level, Site, and Description.
The RPA system diagnostics will present the following results: Level, RPA, Site, and Description.
The system will confirm that all components are OK and that no errors or warnings exist. If errors are
detected, you must correct them to be able to continue. If warnings are detected, it is recommended to fix
them, if relevant, before you continue, even though the system allows you to ignore them and continue
the upgrade.
Once errors and warnings are resolved, click Refresh to rerun the system diagnostics process.
EMC CONFIDENTIAL
3.5 SP1
18 of 33
Figure 9
System diagnostics screen
6. Save system files

Before applying the upgrade, you must save a configuration file and export a system modifications file to
Customer Service, if relevant (the "Error: Reference source not found" illustration).
Save configuration file

A configuration file is required to apply the upgrade.
Specify a path and file name to save the configuration file.
By default, the file name is ndu_input.properties.
Export modifications (if relevant)

The system you are upgrading may have modifications.
If upgrading from 3.1 or 3.1 SP1, you must follow the procedure in the "Verify and collect system
modifications files" section and not specify a path and file name in the Modifications file field.
If upgrading from 3.1 SP2 and later (including 3.2 P1 and later), you must specify a path and file
name to save the file.
By default, the file name is ndu_mod.properties.
If found, they will be saved to a file. This file must be sent to Customer Service for analysis before
applying the upgrade.
When provided with the option to continue:
If you select the Apply upgrade now checkbox and click Next, the system takes you to the "Apply
upgrade configuration" section.
EMC CONFIDENTIAL
3.5 SP1
19 of 33

If you leave the Apply upgrade now checkbox clear and click Finish, the Upgrade RPAs Wizard will
close.
Figure 10
Save system files screen
Apply/Resume upgrade configuration

If applying or resuming upgrade configuration after launching the Upgrade RPAs Wizard - Apply
Upgrade wizard from the Deployment Manager wizard selection screen, continue here:
Apply/Resume upgrade configuration (the "Error: Reference source not found" illustration).
Enter RecoverPoint login credentials, load configuration file, and import modifications file (if relevant):
RecoverPoint installation credentials

Enter RecoverPoint installation username and password.
Note: Installation username and default password = boxmgmt.
RecoverPoint CLI credentials

Enter RecoverPoint CLI username and password.
Only required when upgrading from 3.1.
Note: CLI username and default password = admin.
Load saved configuration file

This file is required to resume the upgrade.
If you have the file, enter the path and file name you used in the "Save configuration file" section of
the Prepare for Upgrade wizard.
If you do not have the file, you must run the Upgrade RPAs Wizard - Prepare for Upgrade wizard.
Import modifications file (if relevant)

If a modifications file was provided to you by Customer Service, you must import it now. Enter path and
file name of the file.
EMC CONFIDENTIAL
3.5 SP1
20 of 33

If Customer Service instructed you to not import a file, or if no system modifications were found, you can
continue without importing a modifications file by clearing the Modifications file checkbox. Click Yes
when the No system modifications file imported window appears.
To verify if you need to import a modifications file, see the "Verify and collect system modifications files"
section.
IMPORTANT: The system modifications file is important for the upgrade to complete successfully.
Continue only if you are sure that you do not need to import a file.
Figure 11
Apply/Resume upgrade configuration screen
Apply upgrade configuration

If applying an upgrade configuration as a continuation from the "Error: Reference source not found"
section, continue here:
Apply upgrade configuration (the "Error: Reference source not found" illustration).
Import modifications file (if relevant)

If a modifications file was provided to you by Customer Service, you must import it now. Enter path and
file name of the file.
If Customer Service instructed you to not import a file, or if no system modifications were found, you can
continue without importing a modifications file by clearing the Modifications file checkbox. Click Yes
when the No system modifications file imported window appears.
To verify if you need to import a modifications file, see the "Verify and collect system modifications files"
section.
IMPORTANT: The system modifications file is important for the upgrade to complete successfully.
Continue only if you are sure that you do not need to import a file.
EMC CONFIDENTIAL
3.5 SP1
21 of 33
Figure 12
Apply upgrade configuration screen
Environment diagnostics
The results of the environment diagnostics test are displayed on this screen (the "Error: Reference source
not found" illustration). If warnings or errors are found, they will be displayed in the table. If no warnings or
errors are found, Environment diagnostics completed successfully will be displayed.
IMPORTANT: It is strongly recommended to resolve these warnings and error before proceeding.
Failure to do so may lead to disruption in replication or production downtime during a disaster, and other
possible issues during normal operation.
To apply the upgrade, click Next.
EMC CONFIDENTIAL
3.5 SP1
22 of 33
Figure 13
Environment diagnostics screen
Apply/Resume upgrade summary

The system performs pre-apply preparations, applies the upgrade to all RPAs, finishes applying the
upgrade, and verifies that the RecoverPoint setup was upgraded completely (the "Error: Reference
source not found" illustration).
This step may take a number of hours to complete, depending on the size of the environment you are
upgrading (number of RPAs, number of consistency groups, number of volumes, and so on).
During this step the system goes into maintenance mode. While in this mode the RecoverPoint
Management Application GUI becomes read-only. The GUI can only be used to monitor the system and
modifications cannot be made.
Once upgrade is completed, RecoverPoint exits maintenance mode and automatically performs SAN
Diagnostics.
Figure 14
EMC CONFIDENTIAL
3.5 SP1
23 of 33
Figure 15
Apply/Resume upgrade summary screen
Note: If the Wizard is unable to apply the upgrade to an RPA (or pair of RPAs, in the event of a two-site
configuration), a Collect system information dialog box appears (the "Error: Reference source not
found" illustration). In this screen, you should enter FTP server information, to which the system
information (logs) gathered from the RPA (or RPA pair) will automatically be saved.
The system information is saved to a file (or two files for a two-site configuration). The file name will
automatically be appended with the IP address of the RPA (or RPAs) from which the system information
is
collected
(example
filename:).
Important: The file(s) should be submitted to Customer Service, to allow them to analyze the
file(s), research the content, and assist you in successfully completing the upgrade.
To improve Customer Service response time, it is highly recommended to collect and save the
Deployment Manager logs (found in <Deployment Manager unzip location>/logs) to the FTP
server.
EMC CONFIDENTIAL
3.5 SP1
24 of 33
Figure 16
Collect system information screen
Re-enabling reservations support (if relevant)

If upgrade was successful and reservations support for consistency groups was disabled in the "Verify
and disable reservations support" section, go to each of the consistency groups and enable reservations
support by selecting the Reservations Support checkbox in the Advanced section of the Policy tab of
the consistency group.
Ensuring upgrade is successful

To ensure that the upgrade is successful, use the RecoverPoint GUI to verify that all system components
are functioning properly, and consistency groups are running on the same RPAs as before the upgrade:
Ensure check marks appear in the Status columns of all components (such as splitters, RPAs, and
volumes).
In the Status tab of each consistency group, verify that they are running on the same RPAs as before
the upgrade.
Updating license
After performing a major upgrade to RecoverPoint release 3.2 or later, it is recommended to obtain a new
license key (for no extra cost) from EMC for the release. Until a new license is set in the RecoverPoint
environment, licensed features for the release will remain disabled.
Recovery policy
The Upgrade RPAs Wizard supports auto-recovery. Therefore, if a step fails anywhere in the procedure,
running the Wizard again will automatically continue the procedure from where the step failed.
Some failures (such as an RPA that goes down) may require manual intervention (such as starting up an
RPA) before rerunning the Wizard.
Logs
Logs of operations are stored in the following locations:
EMC CONFIDENTIAL
3.5 SP1
25 of 33

Prepare for Upgrade logs are named and found in:
<unzip_location>/logs/ndu_prepare.log
Apply/Resume Upgrade logs are named and found in:
<unzip location>/logs/ndu_apply.log
Previously run wizard logs (Prepare and Apply [or Resume]) are found in:
<unzip location>/oldlogs/*.log
Current account settings (such as licensing information) is saved to a CLI script file before the
upgrade is applied. This file can be used to recreate the system configuration. The file is named and
found in:
<unzip location>/logs/account_settings.cli
Verify and collect system modifications files

As detailed in the "Handling system modifications" section, if upgrading from 3.1 or 3.1 SP1, you must
verify if system modifications - tweak parameters and signed scripts - are applied to the system you plan
to upgrade.
First, you must collect system information logs from RPAs you plan to upgrade. Then, you must check for
tweak parameters and signed scripts. If any modifications are found, you must submit them to Customer
Service for analysis, as indicated above.
Collect system information logs from RPAs

1. [ ] Collect system information logs from RPAs you plan to upgrade:
a. Using SSH, log in to the Installation Manager of one of the RPAs that you plan to upgrade with the
installation username boxmgmt and password (default = boxmgmt).
b. From the Main Menu, select Diagnostics > Collect system information.
c. After the system provides you with the current date and time, enter the start date of today
(MM/DD/YYYY) and the start time of 1 hour earlier than the current time (HH:MM:SS).
d. Press Enter for both the end date and the end time (default is the current date and time).
e. Enter y (yes) to collect system information from the other site.
f. Enter n (no) to send result to FTP server.
g. Enter y (yes) to perform full collection.
h. Select [1] Collect logs from RPAs only.
i. Upon completion, the collected system information is placed in http://[RPA IP address]/info or
https://[RPA IP address]/info.
j. Using HTTP or HTTPS, log in as user webdownload with password webdownload (default).
k. Click and save the tar archive file.
l. Extract the archive file.
Note: The file will be saved as an archive file of your default file archiver, such as WinRAR.
A folder will exist for all RPAs on all sites, in the format:
extracted.<site><RPA_number>.<yyyy.mm.dd>.<hh.mm.ss>
Example: extracted.r1.2010.01.01.03.06.09
EMC CONFIDENTIAL
3.5 SP1
26 of 33

Note: For site, l = local site and r = remote site.
Verify and collect tweak parameters files

1. [ ] Verify and collect tweak parameters files:
a. Open one of the RPA folders (for example, extracted.r1.2010.01.01.03.06.09) and go to files >
home > kos > kbox > src > initialization > tweak_params.
b. Open the file tweak.params.overrides.
The file will contain lines of text.
Any text that appears below the example tweak parameter t_bTestMode indicates a modified
tweak parameter.
Example text indicating one modified tweak parameter (t_logPrintAllSnapshots):
# installation process automatically adds overrides here
# Examples:
#
# OVERRIDE_BASE_t_bTestMode = false
# t_bTestMode = true
#
t_logPrintAllSnapshots = true # Changed by William on Thu May 21 11:02:56 GMT 2010
c. If the file contains modified tweak parameters, save a copy of this file and append the site and
RPA number this file was gathered from to the filename.
Example: tweak.params.overrides.r1
This file must be submitted for analysis in a Customer Service Upgrade Service Request before
upgrading to RecoverPoint 3.2 P1 and later.
Verify and collect signed scripts files

2. [ ] Verify and collect signed scripts files:
IMPORTANT: You
can
skip
this
step
This step must be done if upgrading from 3.1 SP1 only.
if
upgrading
from
3.1.
a. Open one of the RPA folders (for example, extracted.r1.2010.01.01.03.06.09) and go to files >
home > kos.
b. Open the file signed_scripts.log.
The file will contain the line of text:
# installation process automatically adds signed script log here
Any text that appears below this line indicates a signed script.
The example below indicates one signed script (Script: 15467):
# installation process automatically adds signed script log here
*********************************************
Script: 15467
Description: description
Signed by: Keith
Ran by Gil on Sun May 3 12:09:03 2010
EMC CONFIDENTIAL
3.5 SP1
27 of 33

Encoded script:
N2NhMzZkYzBkMjBmYmY1ZGE0OTA2YmIwZjg0NGEzZGMKdW5saW1pdGVkCjAKVGhlIGlkIG9m
IHRo
ZSBzY3JpcHQgaXM6MTU0NjcKZGVzYwpPZGVkCmVjaG8gYmxhYmxhYmxhID4+IC9ob21lL2tv
cy9z
dGFtLnR4dAo=
#
c. If the file contains signed scripts, save a copy of this file and, in front of the txt extension of the
filename, insert the site and RPA number this file was gathered from.
Example: signed_scripts.r1.txt
This file must be submitted for analysis in a Customer Service Upgrade Service Request before
upgrading to RecoverPoint 3.2 and later.
3. [ ] Verify and collect tweak parameters files and Verify and collect signed scripts files for every RPA
folder that exists.
4. [ ] If you identify tweak parameters, signed scripts, or both, follow the instructions in the "Handling
system modifications" section to identify if you need to submit any files to Customer Service for
analysis, and if so, what files you need to submit.
IMPORTANT: If modifications are found, they are saved to a file. You must submit this file in an
Upgrade Service Request to Customer Support for analysis, and allow at least 5 business days for a
response from Customer Service before performing the Apply upgrade configuration step of the
Wizard. This time frame is to allow Customer Service to analyze the files, research the contents, and
respond to you.
Removing SCSI-2 reservations support

If upgrading to RecoverPoint 3.5 or later, the Upgrade RPAs Wizard does not support such an upgrade
when the system contains consistency groups with SCSI-2 reservations policy enabled.
To continue, complete one of these procedures:
When the Host server is running a Windows 2000 or Windows 2003 Cluster:
1. [ ] Upgrade your Host OS into Windows 2008 Cluster.
2. [ ] Verify that your attached SAN Array supports SCSI-3 commands for the replicated LUNs.
3. [ ] Change the consistency group Reservations Policy value from SCSI-2 to Auto.
4. [ ] Restart the upgrade process using RecoverPoint Deployment Manager.
When the Host Server is running Windows 2008:

1. [ ] Verify that your attached SAN Array supports SCSI-3 commands for the replicated LUNs.
2. [ ] Change the consistency group Reservations Policy value from SCSI-2 to Auto.
3. [ ] Restart the upgrade process using RecoverPoint Deployment Manager.
IMPORTANT: Failure to complete the procedure will prevent RecoverPoint Deployment Manager
Upgrade RPA Wizard from upgrading the RPA software code to version 3.5 and later.
EMC CONFIDENTIAL
3.5 SP1
28 of 33

Site 1 Splitter Upgrade
This section describes the splitter upgrade for Site 1.
RecoverPoint Splitter Requirements

The following table identifies CLARiiON FLARE revisions that provide RecoverPoint Splitter support. Any
RecoverPoint (RP) and FLARE combination that is not reflected on the table below is not supported.
Table 3
RecoverPoint Splitter Driver CX4/CX3 Series Support
CX31 Platform
CX42 Platform
V3.5.x
FLARE Release 26 patch .032 (no RP

Splitter Driver needed)
FLARE Release 30 (no RP Splitter Driver needed)
v3.4.x

FLARE Release 30 (no RP Splitter Driver needed)
v3.3.x
FLARE Release 26 patch .029 or .031

+
RP Splitter Driver 03.26.003.6.012
FLARE Release 30, FLARE Release 29 patch .

012, .013, .014 (no RP Splitter Driver needed)
RP Version
v3.2.x
v3.1.x

FLARE Release 29 patch .006

+
RP Splitter Driver 04.29.006.6.003
FLARE Release 26 patch .026, .028,.029

and .031 (no RP Splitter Driver needed)
FLARE Release 29 patch .001, .003, or .006 (no RP

FLARE Release 28 patch .707, .708 or .710 (no RP
1 CX3 series systems:

For RecoverPoint 3.4 & 3.5 support: CX3 storage systems will need to be upgraded to FLARE 3.26.xxx.5.032 or higher.
Note: FLARE 03.26.xxx.5.032 bundle does not support RP v3.4 splitter driver features.
For RecoverPoint 3.3 support: CX3 storage systems running FLARE Release 26 patch .029 and .031 will require the 3.3
RecoverPoint Splitter Driver to be loaded via a non-disruptive upgrade (NDU). CX3 storage systems running FLARE Release
26 patch .032 the RP Splitter driver is not required, it is now included in the FLARE bundle.
For RecoverPoint 3.2 support: CX3 storage systems will need to be upgraded to FLARE 03.26.xxx.5.026 or higher. FLARE
03.26.xxx.5.026, .028, .029, and .031 include an imbedded 3.2 RecoverPoint Splitter Driver, no extra NDU is necessary.
For systems running FLARE 03.26.xxx.5.029 with the 3.3 RecoverPoint Splitter driver already loaded, updating to FLARE
03.26.xxx.5.031 will require the 3.3 driver to be reloaded to the system via NDU. Note that this does not require an upgrade of
RecoverPoint Appliance (RPA) code.
For systems running FLARE 03.26.xxx.5.029 or .031 with the 3.3 RecoverPoint Splitter driver already loaded, updating to
FLARE 03.26.xxx.5.032 does not require the 3.3 driver to be reloaded to the system via NDU. The RP Splitter driver is now
included in the 3.26.xxx.5.032 FLARE bundle. Note that this does not require an upgrade of RecoverPoint Appliance (RPA)
code.
NOTE: The v3.3 RecoverPoint splitter also supports v3.4.x (with the exception of RP 3.4 splitter driver features), v3.2.x and
v3.1.x RecoverPoint Appliance (RPA) code. The v3.2 RecoverPoint splitter also supports v3.1.x RPA code. For reference
only, the previous RecoverPoint splitter support is as follows:
V3.1: FLARE Release 26 patch .020 or .025 + RP Splitter Driver 03.26.003.6.003
V3.1.1: FLARE Release 26 patch .025 + RP Splitter Driver 03.26.003.6.004
V3.2.x: FLARE Release 26 patch .025 + RP Splitter Driver 03.26.003.6.009
2 CX4 series systems:
For RecoverPoint 3.4 and 3.5 support: Option 1 (preferred): CX4 storage systems can be upgraded to FLARE 04.30,
FLARE 04.29.000.5.012, FLARE 04.29.000.5.013, and FLARE 04.29.000.5.014. The FLARE 04.30 version contains an
embedded 3.3.x Splitter Driver for all Flare 30 versions below .522 and contains the 3.4.x Splitter Driver in all Flare 30 versions
EMC CONFIDENTIAL
3.5 SP1
29 of 33

.522 and above. The 04.29 versions include an imbedded 3.3 RecoverPoint Splitter Driver which will not allow functionality
with exclusive 3.4.x features. No extra non-disruptive upgrade (NDU) is necessary. Option 2: CX4 systems can be upgraded to
FLARE 04.29.000.5.006 and the 3.3 RecoverPoint Splitter Driver will need to be loaded via a separate NDU. Note that
systems running FLARE Release 28 will need to upgrade to FLARE 04.29.000.5.006 or higher for RecoverPoint 3.4 support.
Note: These FLARE bundle combinations do not support RP 3.4 splitter driver features.
For RecoverPoint 3.3 support:
Option 1 (preferred): CX4 storage systems can be upgraded to FLARE 30, FLARE 04.29.000.5.012 or FLARE
04.29.000.5.013. This version includes an imbedded 3.3 RecoverPoint Splitter Driver, no extra non-disruptive upgrade (NDU)
is necessary.
Option 2: CX4 systems can be upgraded to FLARE 04.29.000.5.006 and the 3.3 RecoverPoint Splitter Driver will need to be
loaded via a separate NDU. Note that systems running FLARE Release 28 will need to upgrade to FLARE 04.29.000.5.006 or
higher for RecoverPoint 3.3 support.
For RecoverPoint 3.2 support: CX4 storage systems will need to be upgraded to FLARE Release 29 or FLARE
04.28.000.5.707 or 04.28.000.5.708. FLARE 04.29.000.5.001,.003, .006, and 04.28.000.5.707, and 04.28.000.5.708 include
an imbedded 3.2 RecoverPoint Splitter Driver, no extra NDU is necessary.
NOTE: The v3.3 RecoverPoint splitter also supports v3.4.x (with the exception of RP 3.4 splitter driver features), v3.2.x and
v3.1.x RecoverPoint Appliance (RPA) code. The v3.2 RecoverPoint splitter also supports v3.1.x RPA code. For reference
only, the previous RecoverPoint splitter support is as follows:
V3.1: FLARE Release 28 patch .008, .501, .504, or .506 + RP Splitter Driver 04.28.006.6.002
V3.1.1: FLARE Release 28 patch .501, .504, .506, .704, or .706 + RP Splitter Driver 04.28.006.6.003
V3.2.x: FLARE Release 28 patch .704 or .706 + RP Splitter Driver 04.28.006.6.008
Mandatory EMC Knowledgebase Solutions

Note: It is expected that you will review and understand all referenced knowledgebase solutions prior to
proceeding with the activity.
Table 4
EMC Knowledgebase Solution Number
Title
emc222887
RecoverPoint: (CLARiiON splitter) Fibre Channel link between RPA

and splitters or storage volumes (or both) is down
emc242361
RecoverPoint/CLARiiON Splitter: FLARE upgrade to FLARE 29 may

cause a full sweep of all RecoverPoint Consistency Groups"
Before you start

To install a software enabler, you need:
A Windows host or Windows virtual machine that is:
Running a supported operating system version. For supported versions, refer to the EMC Unisphere
Service Manager Release Notes, which is available on the Powerlink website. The EMC Unisphere
Service Manager (USM), replaces the EMC Navisphere Service Taskbar (NST). We recommend
that you install the latest version of the USM.
Connected to the Internet if you need to install the USM and/or download software updates.
Running Java Runtime Environment (JRE). For supported versions, refer to the EMC Unisphere
Service Manager Release Notes.
An account on the Powerlink website:
http://Powerlink.EMC.com.
EMC CONFIDENTIAL
3.5 SP1
30 of 33

Installing a software enabler
Use the Unisphere Service Managers System Software wizards to install software enablers. Unisphere
Server Manager (USM) replaces the Navisphere Service Taskbar (NST). If you are not running the
latest version of USM, we recommend you download and install the latest version.
CAUTION: During the software installation procedure:

- The storage system must not have any faulted or transitioning components.
- You must not power down or reboot the storage system, power down an SP, or remove any
components. Doing so may put the storage system in a state from which it cannot be restarted.
- After the software installation is complete, the storage system reboots automatically. One SP
reboots, and when it has finished, the other SP reboots. This causes any connected servers that
are not configured for high availability to lose access to the storage system until the operation is
completed.
Installing storage-system softwar
To install storage-system software (a new FLARE OE version, software enablers, and/or language packs)
using the USMs System Software wizards, you need to:
Validate the environment of any servers connected to the storage system and install the Unisphere
Service Manager (USM).
Copy any enablers or language packs that you are installing to the software repository.
Run the System Software wizards (the Prepare for Installation wizard and the Install Software
wizard).This section describes how to perform each of these tasks.
Validating server environment and installing USM
You must install USM on a Windows host that is connected to the Internet and on the same LAN as the
management ports on the storage system.
1. [ ]
On the Powerlink website, navigate to the CLARiiON Tools page and select your
CLARiiON system.
Note: To access the CLARiiON Tools page, use the Navigator drop-down menu at the top right of the
Powerlink home page.
2. [ ]
In the navigation pane, click CLARiiON Software Update tools and then CLARiiON
Software Update (Standard).
3. [ ]
On the CLARiiON Software Update (Standard) page:
.a Complete step 1 to determine if you can use the update process.

.b If the storage system has one or more servers connected to its data ports, complete step 2 to
validate the server environment; otherwise, skip this step.
.c Complete step 3 to install the Unisphere Service Manager (USM) on the Windows server or host
from which you will install the storage-system software.
After you accept the USM license agreement, the installation wizard verifies that the server is
running the supported Java Runtime Environment (JRE) version.
EMC CONFIDENTIAL
3.5 SP1
31 of 33

If the server is running an earlier version of the JRE, select Yes when asked if you want to
continue with the installation. The installation wizard prompts you to download and install the
later version of the JRE from the Sun website.
If the server is running a later version of the JRE, the installation wizard asks if you want to
continue with the installation.
.d Select Yes to continue or No to quit the installation.
CAUTION: If you select Yes, the USM may not work properly with a later JRE version. If you
select No, and manually remove the later version of the JRE, other applications that require
this version may not work properly.
Copying enablers and/or Unisphere language packs into the storage-system software repository
Read this section if you have enablers and/or Unisphere language packs to install on the storage system.
1. [ ]
For each enabler that you want to install on the storage system:
.a Locate the enabler CD that shipped in the software or upgrade kit, and insert it into the CD drive
on the Windows server or host from which you will install the software.
Note: This Windows server or host must be on the same network as the storage-system
management ports.
.b Copy the enabler (.ena file) from the CD into the c:\emc\repository\Downloads folder on the
Windows server or host on which you installed USM.
Note: The USM installation process creates a c:\emc\repository\Downloads folder as the default
repository for the CLARiiON Software Assistant to use. If this folder does not exist, create it.
.c Remove the CD from the CD drive.
2. [ ]
For each Unisphere language pack that you want to install, download the language pack
from the Downloads and Licensing section of the Powerlink website into the
c:\emc\repository\Downloads folder.
Running the System Software wizards
1. [ ]
Start the Unisphere Service Manager (USM) by doing either one of the following:
Click the Unisphere Service Manager icon on your desktop, or

Select Start > All Programs or Start > Programs, then select EMC > Unisphere > Unisphere
Service Manager > Unisphere Service Manager
2. [ ]
Log in to your system.
3. [ ]
From the System screen, select Software > System Software > Prepare for
Installation.
4. [ ]
Follow the recommended steps in the Prepare for Installation wizard.
5. [ ]
When the Prepare for Installation wizard is finished, start the Install Software wizard.
6. [ ]
Follow the instructions to install the desired software packages.
EMC CONFIDENTIAL
3.5 SP1
32 of 33

7. [ ]
When the installation is complete, select Notify your service provider with updated
storage system configuration information, and click Finish.
8. [ ]
Close the USM.
After the software installation is complete, the storage system reboots automatically. One SP reboots,
and a short time after the reboot is finished, the other SP reboots. You cannot start Unisphere on the
storage system until the reboot is complete, which could take up to about 45 minutes for each SP.
The reboot is complete when the SP status lights on each SP are on steadily. The SP status lights
are behind the front bezel. Wait until both reboots are complete before continuing.
Verifying the software installation with Unisphere
1. [ ]
Start Unisphere for the storage system by entering the IP address of an SP in the storage
system in a browser window.
2. [ ]
software.
3. [ ]
In the system drop-down list on the menu bar, select the system in which you installed the
In the System > System Information view, select Properties.
4. [ ]
Verify that the list contains an entry for each software package that you installed and that
its status is Active and does not require a commit.
If an entry for a software package, which you installed, requires a commit, select the entry and click
Commit.
Site 2 Splitter Upgrade

This section describes the splitter upgrade for Site 2.
The selected splitter technology for site 1 and site 2 are same. Please refer to site 1 splitter installation.
EMC CONFIDENTIAL
3.5 SP1
33 of 33

RecoverPoint SP4 Upgrade

Uploaded by

Copyright:

Available Formats

RecoverPoint SP4 Upgrade

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

RecoverPoint SP4 Upgrade

Uploaded by

Copyright:

Available Formats

What are the steps to upgrade the RecoverPoint software?

What are the steps to upgrade the RecoverPoint software?

What change control process needs to be followed for the upgrade?

What change control process needs to be followed for the upgrade?

EMC RecoverPoint Procedure Generator

Procedure Generated: 3/29/2013 11:25:22 PM

EMC RecoverPoint Procedure Generator

Copyright 2009 2013 EMC Corporation. All rights reserved.

EMC RecoverPoint Procedure Generator

Upgrading RPA Software to RecoverPoint 3.4 SP4........................................................... 6

EMC RecoverPoint Procedure Generator

Site 1 Splitter Upgrade....................................................................................................... 29

Site 2 Splitter Upgrade....................................................................................................... 33

EMC RecoverPoint Procedure Generator

RecoverPoint 3.4 SP4 Upgrade

Mandatory EMC Knowledgebase Solutions

RecoverPoint: Non Disruptive Upgrade (NDU) tool fails during upgrade

RecoverPoint : NDU Installation tool fails when connecting to ftp server

RecoverPoint/Cluster Enabler: RP/CE operations fail following an NDU upgrade

EMC RecoverPoint Procedure Generator

RecoverPoint: Upgrade function "Download ISO" fails on error "Unable to execute

RecoverPoint: Brocade Splitter continuously loses communication with RecoverPoint after

RecoverPoint: Brocade is no longer qualifying mixed fabric (Brocade and McDATA)

RecoverPoint: Consistency Groups can go into a Full Sweep upon upgrading or

RecoverPoint: While upgrading RecoverPoint Software the Deployment Manager (DM)

RecoverPoint: RecoverPoint Management Console / Graphical User Interface (GUI) stops

CAUTION: If Replication Manager is used in the environment, please be aware of compatibility

Upgrading RPA Software to RecoverPoint 3.4 SP4

EMC RecoverPoint Procedure Generator

3.5 and later

1. Deployment Manager upgrade to latest 3.5

3.4 and later

1. Deployment Manager upgrade to latest 3.5

3.3 and later

1. Deployment Manager upgrade to latest 3.4

2. Deployment Manager upgrade to latest 3.5

1. Deployment Manager upgrade to latest 3.3

2. Deployment Manager upgrade to latest 3.4

1. Deployment Manager upgrade to latest 3.2

2. Deployment Manager upgrade to latest 3.3

1. Deployment Manager upgrade to latest 3.2

2. Deployment Manager upgrade to latest 3.3

1. boxmgmt upgrade to latest 3.1

2. Deployment Manager upgrade to latest 3.2

1. Deployment Manager upgrade to latest 3.4

3.3 and later

1. Deployment Manager upgrade to latest 3.4

3.2 SP2 and later

1. Deployment Manager upgrade to latest 3.3

2. Deployment Manager upgrade to latest 3.4

3.2 and 3.2 SP1

1. Deployment Manager upgrade to latest 3.2

2. Deployment Manager upgrade to latest 3.3

1. Deployment Manager upgrade to latest 3.2

2. Deployment Manager upgrade to latest 3.3

1. boxmgmt upgrade to latest 3.1

2. Deployment Manager upgrade to latest 3.2

1. Deployment Manager upgrade to latest 3.3

EMC RecoverPoint Procedure Generator

Latest 3.3 release