SRG RecoverPoint Upgrades and Maintenance
SRG RecoverPoint Upgrades and Maintenance
Copyright © 2017 Dell Inc. or its subsidiaries. All Rights Reserved. Dell, EMC, and other trademarks
are trademarks of Dell Inc. or its subsidiaries. Other trademarks may be the property of their
respective owners. Published in the USA.
THE INFORMATION IN THIS PUBLICATION IS PROVIDED “AS IS.” DELL EMC 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 DELL EMC software described in this publication requires an applicable software license. The
trademarks, logos, and service marks (collectively "Trademarks") appearing in this publication are the property of DELL EMC
Corporation and other parties. Nothing contained in this publication should be construed as granting any license or right to use any
Trademark without the prior written permission of the party that owns the Trademark.
AccessAnywhere Access Logix, AdvantEdge, AlphaStor, AppSync ApplicationXtender, ArchiveXtender, Atmos, Authentica,
Authentic Problems, Automated Resource Manager, AutoStart, AutoSwap, AVALONidm, Avamar, Aveksa, Bus-Tech, Captiva,
Catalog Solution, C-Clip, Celerra, Celerra Replicator, Centera, CenterStage, CentraStar, EMC CertTracker. CIO Connect,
ClaimPack, ClaimsEditor, Claralert ,CLARiiON, ClientPak, CloudArray, Codebook Correlation Technology, Common Information
Model, Compuset, Compute Anywhere, Configuration Intelligence, Configuresoft, Connectrix, Constellation Computing, CoprHD,
EMC ControlCenter, CopyCross, CopyPoint, CX, DataBridge , Data Protection Suite. Data Protection Advisor, DBClassify, DD
Boost, Dantz, DatabaseXtender, Data Domain, Direct Matrix Architecture, DiskXtender, DiskXtender 2000, DLS ECO, Document
Sciences, Documentum, DR Anywhere, DSSD, ECS, elnput, E-Lab, Elastic Cloud Storage, EmailXaminer, EmailXtender , EMC
Centera, EMC ControlCenter, EMC LifeLine, EMCTV, Enginuity, EPFM. eRoom, Event Explorer, FAST, FarPoint, FirstPass,
FLARE, FormWare, Geosynchrony, Global File Virtualization, Graphic Visualization, Greenplum, HighRoad, HomeBase, Illuminator
, InfoArchive, InfoMover, Infoscape, Infra, InputAccel, InputAccel Express, Invista, Ionix, Isilon, ISIS,Kazeon, EMC LifeLine,
Mainframe Appliance for Storage, Mainframe Data Library, Max Retriever, MCx, MediaStor , Metro, MetroPoint, MirrorView, Mozy,
Multi-Band Deduplication,Navisphere, Netstorage, NetWitness, NetWorker, EMC OnCourse, OnRack, OpenScale, Petrocloud,
PixTools, Powerlink, PowerPath, PowerSnap, ProSphere, ProtectEverywhere, ProtectPoint, EMC Proven, EMC Proven
Professional, QuickScan, RAPIDPath, EMC RecoverPoint, Rainfinity, RepliCare, RepliStor, ResourcePak, Retrospect, RSA, the
RSA logo, SafeLine, SAN Advisor, SAN Copy, SAN Manager, ScaleIO Smarts, Silver Trail, EMC Snap, SnapImage, SnapSure,
SnapView, SourceOne, SRDF, EMC Storage Administrator, StorageScope, SupportMate, SymmAPI, SymmEnabler, Symmetrix,
Symmetrix DMX, Symmetrix VMAX, TimeFinder, TwinStrata, UltraFlex, UltraPoint, UltraScale, Unisphere, Universal Data
Consistency, Vblock, VCE. Velocity, Viewlets, ViPR, Virtual Matrix, Virtual Matrix Architecture, Virtual Provisioning, Virtualize
Everything, Compromise Nothing, Virtuent, VMAX, VMAXe, VNX, VNXe, Voyence, VPLEX, VSAM-Assist, VSAM I/O PLUS, VSET,
VSPEX, Watch4net, WebXtender, xPression, xPresso, Xtrem, XtremCache, XtremSF, XtremSW, XtremIO, YottaYotta, Zero-
Friction Enterprise Storage.
Revision Date: 14/02/2017
Revision Number: MR-7WN-NSRPUM.3.0
Upgrades from RecoverPoint 3.5 and later are performed using RecoverPoint Deployment Manager and
are non-disruptive to the environment; they do not cause application or replication downtime, nor journal
loss. Dell EMC RecoverPoint Deployment Manager is a package of wizards that help you perform a
number of important RecoverPoint operations from a single management point.
• Best practice is to upgrade splitters to the same RecoverPoint release as the software.
• Completing the upgrade procedure may take several hours, depending on the ISO file version, network
speed, and size of environment being upgraded.
• The Upgrade Cluster Wizard supports auto-recovery. If a step fails, run the wizard again. It continues
from the failed step.
NOTE: RecoverPoint upgrade includes hardware upgrade and software upgrade, with different procedures
for each.
• Select the desired operation from the list of operations available, for example here we are selecting
Upgrade operation.
• RecoverPoint for VNX is an exception for the CCA process, and you will receive a reminder when you
are trying to generate an upgrade procedure through SolVe Desktop.
This procedure document will be saved in the MS Word format in the specified location and will guide you
through the entire upgrade process.
Information about the RecoverPoint Change Control Process can be obtained from either of these two
sources:
http://10.241.171.170/RecoverPoint/Change_Control/RecoverPoint_Change_Control_Process
https://servicepartners.emc.com/restricted/frame.asp
A list of Mandatory Dell EMC Knowledgebase articles will be provided with your approved RecoverPoint
Change Control. It is very important that you review and understand each article before proceeding.
In Unisphere, select Admin > System Analysis Tools > Collect System Information. Select the desired
collection period. Only three days of information can be collected at one time.
RPA Clusters specifies the RPA clusters from which to collect system information. If none of the check-
boxes are selected, system information is collected only from the RPA cluster from which the collection
process is triggered. This setting is only relevant when Include Information from RPA Clusters check-
box is selected. This option enables the collection of system information from RPA clusters.
Include Core Files selects whether or not to include core files in the output. Core files may be large.
Therefore, including these files in the collection process may substantially increase collection time. Output
can be sent to the RPA or an external FTP server.
• The first path provides options for installation, upgrade, and other operations for RecoverPoint 5.0
releases. End users who would like to install the latest RecoverPoint 5.0 release on a new hardware
appliance or virtual RecoverPoint Appliance (vRPA) should use this option.
• Users who would like to upgrade to the latest RecoverPoint 5.0 version from version 4.0,4.1, or 4.4
should choose the second option.
• Users who would like to upgrade to the latest RecoverPoint 5.0 version from version 3.5 or earlier
should choose the third option. This option will launch the version of Deployment Manager that
supports 3.5.
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 Upgrade wizard applies the upgrade to all
RPAs. Once the upgrade is complete, you can continue using the Unisphere for RecoverPoint GUI.
While the upgrade procedure does not upgrade RecoverPoint splitters (VNX, VMAX, and VPLEX), a
RecoverPoint 4.1 environment can support both v4.1 and v3.5 splitters. Dell EMC advises you to upgrade
splitters to the same RecoverPoint release to gain the latest splitter functionalities and features.
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 the point where a step failed.
The Deployment Manager application stores logs in specified locations. These are useful if for any reason,
an upgrade fails to complete.
Prepare for Upgrade logs are named and found in: <unzip_location>/logs/ndu_prepare.log
Previously run wizard logs (Prepare and Apply [or Resume]) are found in:<unzip_location>/oldlogs/*.log
Although non-disruptive to normal operations, it is important to take into consideration that the upgrade
procedure may take a number of hours to complete, depending on the ISO file distribution, network speed,
and size of the environment being upgraded.
To use the Upgrade Cluster Wizard, on the login screen, select Other operations (EMC personnel) and
enter your RecoverPoint login credentials. The default CLI username and password is admin and admin.
On the Deployment Manager wizard selection screen, select option Upgrade Cluster.
If you do not have Internet connectivity, or do not have EMC Online Support credentials, select the ‘Use
an offline Upgrade Change Management XML file’ check-box and load the XML file into the wizard from a
local folder (where you have saved the file).
To obtain the XML file, you must open an Upgrade Service Request with Customer Support. In the
request, ask for the latest Upgrade Change Management XML file for the RecoverPoint Deployment
Manager, and indicate the intended date of the upgrade. The file will be provided within one (1) business
day as an email attachment, so ensure a valid email address is provided. Once provided, the file must be
used within 30 days of delivery.
If you choose Download from FTP server, enter the FTP credentials of an FTP server where the
RecoverPoint ISO file is located to download it to the RPAs. Enable FTP credentials including FTP server
IP address, port number, FTP username and password, File location, and File name. The file name must
be the same file name as the ISO file that was downloaded from support.emc.com.
The system verifies the ISO file and its distribution to all RPAs and confirms that this was successful or
that errors were detected. When all status indications appear normal (green check mark), click Next.
Once errors and warnings are resolved, click Refresh to rerun the system diagnostics.
A configuration file is required to apply the upgrade. If the upgrade is to be applied at a later date,
Deployment Manager will need this file to be able to apply the upgrade.
The system you are upgrading may have modifications. If this is the case, these may need to be applied to
the system before you can actually apply the upgrade.
Specify a path and file name to save a system modifications file. By default, the file name is
ndu_mod.properties.
• If Deployment Manager does not indicate that modifications are found, a message appears stating that
no file was created and saved. You can continue and apply the upgrade.
• If modifications are found, they are saved to a file. You must submit the file to Dell EMC Customer
Support and wait for a response before applying the upgrade.
You must submit this file in an Upgrade Service Request to Customer Support for analysis. In the request,
indicate that the attached file needs to be reviewed for a pending upgrade, and indicate the intended date
of the upgrade. Allow at least 5 business days for a response from Customer Support before performing
the Apply Upgrade configuration step of the wizard. This time allows Customer Support to research the
contents, and respond to you. After analysis, the response will be in the form of the file being returned to
you.
If you select the ‘Apply upgrade now’ check-box and click Next, the system takes you to ‘Apply upgrade
configuration’. If you leave the ‘Apply upgrade now’ check-box cleared and click Finish, the Upgrade
RPAs Wizard closes. A typical reason not to proceed with the upgrade is to allow time for full ISO
download onto the RPAs. Depending on bandwidth, the download could take a significant amount of time.
It may be best to prepare for the upgrade and allow time for the download prior to the scheduled time for
the actual upgrade procedure. When the scheduled time arrives, you can get back to this point and use
the configuration file to pick up where the system left off.
Enter the path to the configuration file, saved during the Prepare phase of the upgrade. This file must be
available, or the prepare will need to be run again.
If a system modifications file was provided to you by Customer Support, you must import it now. Enter the
path and file name of the file. 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. Click Next to proceed.
It is strongly recommended to resolve these warnings and errors 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.
If no warnings or errors are found, ‘Environment diagnostics completed successfully’ will be displayed.
The next step is to verify the login credentials are correct for storage connectivity. If the connectivity
results contain any warnings, it is recommended to fix them before going to the next step.
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.
During this step the system goes into maintenance mode. While in this mode, the RecoverPoint GUI
becomes read-only; the GUI can only be used to monitor the system and modifications cannot be made.
Once the upgrade is complete, RecoverPoint exits maintenance mode and automatically performs SAN
Diagnostics.
After performing a major upgrade, the previous license will automatically be converted to the new license
format. However, the new license is temporary and only valid for 90 days from the date of upgrade. After
that, you must install one or more permanent license files to replicate with RecoverPoint. Refer to the
EMC RecoverPoint Administrator's Guide for detailed instructions on upgrading your license. Refer to the
EMC RecoverPoint Release Notes for information on the licensed features for the release. After upgrading
the RecoverPoint system, you must fill out the RecoverPoint Post-Deployment Form and send it to the
EMC Install Base (IB) group to register your RecoverPoint system.
After an upgrade of the RecoverPoint Cluster software, the write splitter versions for the new
RecoverPoint versions should be verified for compatibility. The RecoverPoint support matrix posted in
eLab is an easy-to-use tool (https://elabnavigator.emc.com/eln/search?RecoverPoint) for checking the
correct versions of RecoverPoint along with the versions of write splitter code. The table displays an
example covering the VNX, VMAX and VPLEX splitters.
Remember that RecoverPoint 4.0 and above only supports array-based splitters. SAN- and host-based
splitters are no longer functional with RecoverPoint 4.0. Array-based splitters with older code will function
but will need to be updated as soon as possible.
To upgrade a 4.4 cluster, use the Deployment Manager, this time following the RecoverPoint 4.0 or later
releases branch. This will lead you into selecting the Upgrade Cluster Wizard.
Any site that has connectivity to support.emc.com, and where the user has the credentials, will be given a
download directly to each RPA in the cluster.
If this is not possible, an ISO image can be provided locally via DVD or USB. This must be provided for
each RPA. Also, an FTP server can be used.
• First, ensure that you have a secure shell (SSH) client, such as PuTTY, on your Laptop.
• The RecoverPoint version (release number) and code level of the existing cluster need to be verified.
These can be verified by using CLI or using the RecoverPoint Management Application GUI:
‒ Using CLI
o Login as admin
o Run the get_version command to view the running RecoverPoint version
‒ Using the Unisphere for RecoverPoint
o Login as admin
o Select Help > About Unisphere for RecoverPoint
Once the version of the running RecoverPoint cluster is known, it can be determined if the replacement
RPA needs to be upgraded prior to installation.
• Always use the latest version of Deployment Manager for performing any upgrade or maintenance task.
Go to support.emc.com website and download the latest version if you do not have the latest version.
• Use SolVe Desktop (RecoverPoint Procedure Generator) to generate the procedure for physical RPA
replacement.
• To obtain an image of the RecoverPoint software, go to the support.emc.com website. Find and
download the RecoverPoint ISO image that corresponds to your release number and code level. Verify the
checksum against the md5sum listed in Dell EMC support.
If you have all these conditions met, you are ready to proceed with removing the failed RPA.
Alternatively, you can use the CLI to check the status of the RecoverPoint cluster. Log in as the admin
user and run the get_system_status command.
• The new RPA has a RecoverPoint software ISO image that is the same release as that running on the
other RPAs in the cluster
Using the Installation Manager (boxmgmt) menu, download the correct ISO file using FTP. After
downloading, place the downloaded ISO image on a service laptop. Then, configure an FTP server for the
service laptop. Next, connect to the new RPA with an SSH client and login with the boxmgmt account.
Answer ‘no’ to any wizards that may start after login.
From the main menu, select Installation>Upgrade>Download ISO. Enter the FTP information and the
path to the ISO image. The box will load the image, apply the image, and reboot. When the RPA
completes the reboot, it will have the correct version installed. An important point to remember is that if a
temporary IP address was configured prior to the reboot, it will be lost and have to be set again.
Proceed to the next slide to explore the second option, i.e. using Dell EMC Online Support website.
The appliance boots from the DVD drive and installs the software. This can be observed from a monitor
connected to the RPA, but it is not required to do so. After approximately 10 minutes, the drive opens and
the RPA reboots. Connect to the RPA with the boxmgmt account and verify the version is correct. Connect
via the WAN default address of 10.77.77.77, or use a KVM. At this point, a temporary IP address matching
the address of the failed RPA can be configured.
The RecoverPoint RPA Replacement Wizard is a graphical user interface (GUI) that helps you replace an
existing RPA in an RPA cluster with a new RPA without any application or replication downtime. Once the
wizard is completed, you will be able to continue using the RecoverPoint Management Application GUI
and CLI.
Throughout the RPA Replacement Wizard, you must enter a number of settings into the system. To
improve system performance, it is recommended to enter values in all fields. Whenever you click Next to
continue, the system will automatically save configuration settings in the configuration file. The system
does not allow you to navigate forward if you have not completed any step, as it is mandatory to go
through all the steps.
When using the Deployment Manager RPA Replacement Wizard, it is important to know the cluster
management IP address for the cluster that contains the failed RPA.
If you choose this option, the system creates a new RPA replacement configuration file. The configuration
settings of the existing RPAs are added to the configuration file. The system uses these settings to
complete the RPA replacement. It is important to provide a valid file name and directory location. By
default, the file name and directory location is:
Edit the field to change the information, or click Browse to select a different location to save the file, as
well as rename it.
If you choose this option, the system loads the settings from a previously saved RPA replacement
configuration file. The system allows you to complete the RPA replacement using this file.
Once the wizard is open and you click Next to continue, the system automatically saves the configuration
settings in the configuration file that you created.
Enter the cluster management address of the cluster with the failed RPA. If continuing from a saved
configuration file, an IP address will automatically be entered.
Enter a RecoverPoint username and password. For username boxmgmt, the default password is
boxmgmt.
Enter a RecoverPoint username and password. For username admin, the default password is admin.
At this point, it might be easier to power off the RPA that has failed. This will make identification of the
RPA for the Deployment Manager wizard easier.
Select the check-box at the bottom of the screen if the RPA to be replaced has been physically removed
from the system and the new RPA is racked, connected, up, and has the relevant ISO image applied to it.
It is very important to select this check-box if the new RPA is in place. If the check-box is not selected, and
the new RPA is powered on and has the IP address of the failed RPA, the procedure will power off the
new RPA. The best practice at this point is to replace the RPA and select the check-box.
Notice, the last step is to verify the RPA is powered off. This is why you did not swap the RPA with the
new one at this point.
Once the cluster has successfully prepared the RPA for replacement, click Next to continue.
1. Record the orientation of the network and Fibre Channel (FC) cables of the RPA being replaced, then
disconnect the cables from the RPA.
2. Disconnect the power cables from the RPA being replaced and remove it from the rack.
3. Place the new RPA in the rack, connect the network, FC, and power cables, and power on the RPA.
4. Verify that the RecoverPoint release on the new RPA corresponds to the release running on the other
RPAs in the cluster.
5. Log in to the new RPA as user boxmgmt, enter the temporary IP address, subnet mask, and gateway of
the replaced RPA, then log out.
6. Verify that the new RPA is the same type (physical or virtual) as the other RPAs in the cluster.
If any of the conditions are not fulfilled, it is recommended to close the wizard, fulfill the conditions, and
then run the wizard again.
Select the ‘I have fulfilled the conditions for replacing the RPA’ check-box, and click Next to continue.
The first one would be to use the spoofing of the WWNs to make them the same as the RPA that is
being replaced. This of course is quicker, and will make sure that the new RPA sees the same storage as
the failed RPA.
The other would be to use the new WWNs of the RPA and re-zone and re-mask to connect the RPA to
storage. The wizard will display all existing WWNs and the new ones.
The information summary presented in the table can be exported for further use by clicking the Export to
CSV file button.
The system presents the results for: Severity, RPA, Message ID, Category, and Description. The system
confirms that all components are OK and that no errors exist. If errors are detected, you can click the error
to display details and instructions on how to correct the problem.
To proceed to the next step in the wizard, you must resolve all errors. Once all the errors are resolved,
click Refresh to re-run the SAN diagnostics process.
It is highly recommended to resolve all SAN discovery warnings, even though the system allows you to
ignore them and continue the installation.
As recommended, and by default, all the system modifications will be selected to run on the new RPA.
However, you can select which ones to apply to the new RPA, and clear the ones you do not want to
apply.
• Power Supply
• I/O Module
• DIMMs
• Fan
• Chassis
To replace any Gen6 Field Replaceable Units (FRUs), SolVe Desktop can be used to generate the
procedure as shown in this screenshot.
A double disk drive failure in a RecoverPoint Appliance Gen6 is not a FRU. Dell EMC customer service
needs to follow a different procedure to resolve a double disk drive failure.
Use the error messages and log files to identify the faulty power supply and its respective RPA. The faulty
PSU should show an amber light.
Specifically, this power supply error could have been caused by unsecured power cables that fell out. So
in the details of this alert message, you are asked to check the electrical power to both power supplies of a
particular RPA. If the amber LED of the power supply is still glowing, contact Dell EMC and order the
replacement part.
There are two slots for I/O modules in the RecoverPoint Appliance Gen6 - slot 0 and slot 1. The I/O
modules are only cold-swappable, this means the RPA needs to be powered off. Always follow the proper
power off procedure.
When the FC I/O module in a RecoverPoint Appliance Gen6 is replaced, there is no need for rezoning.
The WWNs are derived from the seed programmed into the chassis. The seed varies per RPA.
The DIMM location and slot numbering can be seen on the fan connector cover once you have opened the
chassis.
Once the modules are received, the impacted RPA is powered off. The system service LED (amber) will
be on indicating the physical RPA. Next, both power cords need to be removed from the unit to completely
power it off.
Remove the Fan Connector Cover for easier access and replace all four (4) DIMM modules.
The location of each fan unit is shown on the Fan Connector Cover. This cover can be seen after you
have removed the chassis cover.
After the RPA is opened, remove the Fan Connector Cover for access to the six fan units and perform
replacement according to the latest service instructions.
The faulted RPA is powered off and replacement should always be performed according to the latest
service instructions.
The replacement chassis does not include I/O modules nor is the RecoverPoint OS installed.
Follow these steps in the service procedure to replace a chassis. These steps might take 2 to 3 hours from
the moment you receive the chassis FRU to having the RPA working in the RP cluster.
The main steps to prepare the new chassis for the hardware swap are to configure the BIOS setup and to
configure the resume of the new chassis.
Next, the RecoverPoint OS is installed using a bootable USB device. Finally, configurations and
validations of the new chassis are necessary, before the RPA can be used to rejoin the RPA cluster using
the RPA Replacement Wizard in the Deployment Manager utility.
Next, move the I/O modules to the new chassis and place them in the same slots they originated from on
the defective chassis.
If the faulted RPA only has the 16 Gb Fibre Channel I/O module, make sure that the replacement chassis
has a filler in the second slot.
When connected, use Putty with a serial connection option and a 115200 baud rate. Power up the new
chassis, and use the <F2> or <DEL> key when the message to enter the BIOS setup appears.
The BIOS entries of the USB Mass Storage Drive and the Launch VGA OpROM need to be set to
Enabled. Verify the settings, or make necessary changes and select Save on Exit.
During bootup, the POST alphabet listing will appear. Break into the alphabet by pressing <CTRL>+<C>
(Control-C) keys and wait until the alphabet listing stops. Enter the password as it is given to you in the
procedure.
When the Diagnostic Menu appears, enter the option 35 – Resume PROM Sub-Menu and press the
Enter key. From here, you can select to set the resume and edit the settings for the XP chassis.
The utility Rufus 2.8 or higher needs to be used to create a bootable USB thumb drive on your laptop with
the RecoverPoint ISO installation file.
When successfully created, plug the USB drive into the USB port of the replacement chassis. The BIOS
needs to be entered again during the boot. The boot order is overridden for the next boot. For this, you
select the USB device that you plugged into the chassis.
Once you press the Enter key, the system boots off the USB device and installs the RPA OS. This
installation also installs any available updates to the BIOS, POST, and firmware automatically.
The installation takes about 10 – 15 minutes. When finished, you should see the RPA login prompt.
First, the BIOS password is set, and then the temporary management IP address is configured when
prompted after logging into the RPA as user boxmgmt.
The next steps can use the temporary IP address in a Putty SSH session. After the RPA login, as user
boxmgmt, select in the Main menu Setup and then Advanced Options.
Scripts provided in the procedure can be copied and pasted into the option Run script. The first script
validates the RPA Gen6 installation, the second script enables web access for the BMC port.
Finally, the BMC support is configured. The BMC access can be configured for the WAN, LAN, or for the
dedicated BMC port. This is done with the information from the customer according to their security needs.
In the Storage configuration screen, select the option Spoof the HBA WWNs of the RPA being
replaced, so that no rezoning is necessary.
If the RPA is successfully replaced, the RP system will automatically redistribute the consistency groups
that were running on the replaced RPA to the new RPA. Refer to the RecoverPoint Installation and
Deployment Guide for additional details for replacing an RPA.
Launch the SolVe Desktop from your local machine and select RecoverPoint from the product list.
The procedure document will be saved in the MS Word format in the specified location.
As of release 3.5, RecoverPoint Deployment Manager has a Modification Wizard to help you non-
disruptively modify the settings of a system of up to two clusters (3.5.x) or an individual cluster (4.0 or
later) from a single management point. The procedure is done without replication downtime, without
requiring a full sweep, and without journal loss.
Starting in RecoverPoint 4.0, cluster modification is performed on one cluster at a time. To perform cluster
modification on another cluster, you must log into that cluster using another instance of the Cluster
Modification Wizard. The steps of the Cluster Modification Wizard are covered in detail in the following
slides.
• The computer that the wizard is run from must be able to communicate with all RPA management
(LAN) networks on both sites.
• Ensure that ports 21, 22, 8081, and 8082 (all TCP) are open on the computer to enable communication
with 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 running
Deployment Manager from. It is highly recommended to have the latest Java 6 update installed.
Select the ‘I have fulfilled the conditions for modifying the system settings‘ checkbox, and click Next to
continue.
Enter a cluster management or an RPA IP address. If continuing from a saved configuration file, an IP
address will automatically be entered.
Enter a RecoverPoint username and password. For username boxmgmt, the default password is
boxmgmt.
Enter a RecoverPoint admin username and password. For username admin, the default password is
admin.
The system creates a new cluster modification configuration file. The configuration settings of the existing
RPAs are added to the configuration file. The system uses these settings to complete the cluster
modification. Provide a valid file name and directory location. By default, the file name and directory
location is C:\Documents and Settings\<username>\RecoverPoint\MOD_config.properties.
The system loads the settings from a previously saved cluster modification configuration file. The system
allows you to complete the cluster modification using this file.
Once the wizard is open and you click Next, the system will automatically save the configuration settings
in the configuration file you create.
The current RPA cluster iSCSI settings are displayed here. Modify the values you want to change.
The current cluster iSCSI IP configurations and RPA iSCSI IP settings are displayed here. Modify the
values you want to change.
The current storage CHAP and iSCSI IP configurations are displayed here. Modify the values you want to
change.
• When upgrading a RecoverPoint system to a different code level (If the system was previously
connected, it will automatically register the changes with Dell EMC)
There are three ways to register RecoverPoint: online, through email, or by phone.
Please be aware that some activities must be completed before registering RecoverPoint:
• The RecoverPoint registration process will fail if you do not first configure your SMTP.
• To send system reports and alerts, a permanent RecoverPoint license must exist in the system; system
reports and alerts will not work with a temporary license.
• Before making changes to System Reports and Alerts and configuring SMTP, please make sure:
o To transfer system reports and alerts using SMTP or ESRS, ensure that port 25 is open and
available for SMTP traffic.
o To transfer system reports and alerts using FTPS, ensure that ports 990 and 989 are open and
available for FTPS traffic.
1. Choose either the Getting Started Wizard or the Admin Tab in Unisphere for RecoverPoint
The first step to register RecoverPoint is to select a method for registration. If it is your first time launching
Unisphere for RP then use the Getting Started Wizard > Register RecoverPoint to make configuration
changes, or select Admin > Register RecoverPoint to register and display the RecoverPoint Post-
Deployment Form.
1. Ensure that the Enable System Reports and Alerts checkbox is selected, and the radio button is set to
System reports and system alerts.
• The Enable New Release Notification check-box is selected by default.
• To transfer system notifications through RecoverPoint’s built-in FTPS server: in the Transfer
Method section, select the FTPS radio button.
• To transfer system notifications through an ESRS gateway:
a) In the Transfer Method section, select the ESRS radio button.
b) In the ESRS gateway IP address field, specify the IP address of your ESRS gateway in
IPv4 format.
• To transfer system notifications through an SMTP server:
a) In the Transfer Method section, ensure the SMTP radio button is selected.
b) In the SMTP server address field, specify the IP address or DNS name of your
dedicated SMTP server, in IPv4 or IPv6 format.
c) In the Sender email field, specify the email address from which the system notifications
will be sent.
In the Update Post-Deployment Form Details dialog box, you will now need to:
1. Select the relevant RPA cluster from the RPA Cluster drop-down
2. Update the form according to the instructions in the table shown on the left side of this slide
3. Click Apply to save each change to the form, without closing the dialog box
If the customer does not have SyR connectivity, and you cannot therefore configure system reports and
alerts, you can skip the remaining steps in this procedure, go to Export the post-deployment form to a CSV
file, and Register RecoverPoint by email or phone.
You can save your RecoverPoint registration information or Register RecoverPoint by email or phone by
exporting the RecoverPoint post-deployment form and all of its contents as a comma-delimited file (*.csv)
that can be opened in MS Excel or any other reader of CSV files. The Activity Date field in the exported
CSV file contains the date and time that the file was exported.
The Procedure for exporting the Post-Deployment Form to a CSV file is:
2. Click the Export button at the top right corner of the screen
1. Access https://support.emc.com
• For Dell EMC customers and partners: Email the post-deployment form to the Install Base group at
[email protected].