RecoverPoint - Change RPA Installation Parameters-5.3 SP3
RecoverPoint - Change RPA Installation Parameters-5.3 SP3
RecoverPoint - Change RPA Installation Parameters-5.3 SP3
Topic
Change RPA Installation Parameters
Selections
Select RecoverPoint Release: 5.3 SP3
REPORT PROBLEMS
If you find any errors in this procedure or have comments regarding this application, send email to
SolVeFeedback@dell.com
Copyright © 2022 Dell Inc. or its subsidiaries. All Rights Reserved. Dell Technologies, Dell, EMC, Dell
EMC and other trademarks are trademarks of Dell Inc. or its subsidiaries. Other trademarks may be
trademarks of their respective owners.
The information in this publication is provided “as is.” Dell Inc. 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 software described in this publication requires an applicable
software license.
This document may contain certain words that are not consistent with Dell's current language guidelines.
Dell plans to update the document over subsequent future releases to revise these words accordingly.
This document may contain language from third party content that is not under Dell's control and is not
consistent with Dell's current guidelines for Dell's own content. When such third party content is updated
by the relevant third parties, this document will be revised accordingly.
Page 1 of 55
Contents
Preliminary Activity Tasks .......................................................................................................3
Read, understand, and perform these tasks.................................................................................................3
Change the RPA communication security level ..........................................................................................25
Modify the network topology .......................................................................................................................25
Installing the splitter with Boxmgmt CLI ......................................................................................................25
Install the splitter with the RecoverPoint for VMs VIB installer ...................................................................25
Install JAM ..................................................................................................................................................26
Add vRPAs to a vRPA cluster.....................................................................................................................28
Remove a vRPA from a vRPA cluster ........................................................................................................28
Replace a vRPA..........................................................................................................................................28
Change default passwords .........................................................................................................................29
Collect logs .................................................................................................................................................30
7 ............................................................................................................................................31
Deploying RecoverPoint for VMs in a VxRail™ environment .....................................................................32
Downloading from the VxRail Marketplace............................................................................................32
Preparing the network for VxRail ...........................................................................................................32
Create vRPAs for VxRail .......................................................................................................................33
Create and configure VMkernel ports for VxRail ...................................................................................33
Create a vRPA cluster for VxRail...........................................................................................................33
Adding VxRail appliances or nodes .......................................................................................................34
8 ............................................................................................................................................35
Troubleshooting vRPAs ..............................................................................................................................35
● vRPA is down .....................................................................................................................................35
vRPA is detached from the vRPA cluster ..............................................................................................36
vRPA cannot detect storage or splitter ..................................................................................................36
Page 2 of 55
Preliminary Activity Tasks
This section may contain tasks that you must complete before performing this procedure.
Table 1 List of cautions, warnings, notes, and/or KB solutions related to this activity
2. This is a link to the top trending service topics. These topics may or not be related to this activity.
This is merely a proactive attempt to make you aware of any KB articles that may be associated with
this product.
Note: There may not be any top trending service topics for this product at any given time.
Page 3 of 55
RecoverPoint for Virtual Machines 5.3.3
Installation and Deployment Guide
Page 4 of 55
Introduction to RecoverPoint for VMs
RecoverPoint for VMs is a virtualized solution that provides data replication, protection, and recovery
within the VMware vSphere environment.
Definition of key terms and a system diagram help you to understand the
system operation. Topics:
• RecoverPoint for VMs system
Page 5 of 55
Introduction to RecoverPoint for VMs
Page 6 of 55
Introduction to RecoverPoint for VMs
2
Preparing to install RecoverPoint for VMs
Guidelines help you choose the number of vRPAs and vRPA clusters, vRPA performance profile, and
network adapter topology.
Preparing the VMware network and determining storage capacity sets the stage for a
successful installation. Topics:
• RecoverPoint for VMs networking example
• Planning your system
• Preparing the VMware environment
• Understanding the installation flow
Page 7 of 55
Figure 2. Networking example
Page 8 of 55
For a comprehensive and up-to-date list of system limitations, see the RecoverPoint for Virtual Machines
Release Notes.
Allocating IP addresses
Knowing how many IP addresses you need for the RecoverPoint for VMs system helps you to allocate
the IP addresses before the installation is scheduled.
The RecoverPoint for VMs system requires these IP addresses:
● Cluster management IP address for each vRPA cluster
● An IP address for each vRPA network adapter (see Choosing a network adapter topology) ● An IP
address for each VMkernel port
● An IP address for each plugin server
● An IP address for the NTP server (recommended)
● An IP address for the primary and secondary DNS servers (optional)
To allocate the necessary IP addresses for the RecoverPoint for VMs system, consult with the network
administrator.
Document these addresses in an installation data form or spreadsheet before you begin the installation.
Page 9 of 55
The actual number of vRPAs that you need for each vRPA cluster depends on the capabilities of your
storage, network, ESXi hosts, and the scale and performance requirements of your system.
For specific details and examples, refer to the RecoverPoint for Virtual Machines Scale and Performance
Guide.
NOTE: By default, all RAM is reserved and vCPU reservation is set to 3400MHz.
If required, you can add memory and CPU resources after initial OVA deployment. For each vRPA,
power off the vRPA, select Edit Settings for the vRPA VM, and add the needed resources.
For details and examples, refer to the RecoverPoint for Virtual Machines Scale and Performance Guide.
I/O throttling
I/O throttling is used to slow down storage reads that are part of any initialization process including the
initial full synchronization (full-sweep).
Page 10 of 55
I/O throttling mitigates the negative impact of initialization on production performance. As a result,
however, the initialization process may take longer than expected.
I/O throttling is initially enabled at 400 MBps.
You can use the config_io_throttling Sysmgmt CLI command to set the I/O throttling setting.
For more information on I/O throttling, see the RecoverPoint for Virtual Machines Scale and Performance
Guide and the RecoverPoint for Virtual Machines CLI Reference Guide.
NOTE: IPv6 is supported on vRPA LAN and WAN interfaces, but not on vRPA Data interfaces.
This selection is made when you run the Install a vRPA cluster wizard in the RecoverPoint for VMs
Deployer.
For high-availability deployments in which clients have redundant physical switches, route each data card
to a different virtual switch with a separate network adapter.
Page 11 of 55
For each network adapter, you have the option to assign a dynamic or static IP address.
When using Dynamic Host Configuration Protocol (DHCP):
● Separating WAN and LAN interfaces on different network adapters is supported only when using static
IP addresses for the LAN interface
● Redundant, highly available DHCP servers in the network ensure that when a vRPA restarts, it
acquires an IP address
Steps
● Ensure that you open port 443 between the vCenter Server and the vRPAs in both directions, and port
7225 in the vCenter Server-to-vRPAs direction only.
● Ensure that ESXi clusters can communicate with their vRPA targets. Configure the ESXi firewall
profile to allow communication through the network.
● See the RecoverPoint for Virtual Machines Security Configuration Guide for more information.
Page 12 of 55
● Ensure that port 443 is open for bi-directional communication between the plugin server and the
vCenter Server. ● Ensure you open port 9443 for plugin server-to-vRPA communication.
See the RecoverPoint for Virtual Machines Security Configuration Guide for more information.
NOTE: Each ESXi host should have its own dedicated datastore for the scratch directory.
For more details and examples, refer to the RecoverPoint for Virtual Machines Scale and Performance
Guide.
For additional guidelines and sizing tools, contact Customer Support.
Page 13 of 55
Figure 3. Stages of the installation flow
Install vRPA clusters Install vRPA clusters RecoverPoint for VMs Deployer
Configure plugin server Configure the plugin server RecoverPoint for VMs Deployer
Connect vRPA clusters Connect vRPA clusters RecoverPoint for VMs Deployer
Use the RecoverPoint for VMs plugin for the vSphere Client (HTML5) or the vSphere Web Client (Flex) to
make final preparations for protecting VMs, including registering and licensing the system, and creating
any required VMkernel ports (Completing installation of the RecoverPoint for VMs system).
3
Installing the RecoverPoint for VMs system
Installing the RecoverPoint for VMs system involves deploying the vRPAs, installing the vRPA
clusters, and connecting the vRPA clusters together. In the RecoverPoint for VMs plugin for
vSphere Client (HTML), it also involves installing and configuring a plugin server.
Topics:
• Download the installation package
• Deploy vRPAs
• Deploy the plugin server
Page 14 of 55
• Install vRPA clusters
• Configure the plugin server
• Connect vRPA clusters
• Completing installation of the RecoverPoint for VMs system
Steps
1. Browse to https://www.dell.com/support.
2. Perform a search in the Type a Product Name text box for RecoverPoint for Virtual
Verifying signatures
Use the relevant procedure to verify a signature that is attached to an OVA or ISO file that you
downloaded from the RecoverPoint for VMs downloads page.
Page 15 of 55
1. To import the Public Key, run:
bash-4.4# gpg --import pubkey.gpg
GPG acknowledges successful import of the Public Key.
2. To verify the signature, run:
bash-4.4# gpg --verify rp.iso.sig rp.iso
GPG confirms that the signature is good.
Deploy vRPAs
Deploy a standard OVA to create vRPAs for RecoverPoint for VMs.
Prerequisites
Ensure that you have completed:
● Preparations for installation.
● Installation data form or spreadsheet to facilitate entering requested information (recommended). See
Installation data forms.
Steps
1. In the vSphere Client (HTML5) or Web Client (Flex), right-click an ESX cluster, and select Deploy OVF
Template....
2. In the Select an OVF template screen, either enter a URL from which to download the OVF package
from the Internet, or choose a location from which to access the file locally.
3. In the Select name and folder screen, type a name for this vRPA and select a folder or data center.
If you type the name of an existing vRPA, you are not permitted to continue.
4. In the Select resource screen, specify the vRPA OVF package location.
5. In the Review details screen, review the general properties of the OVF template. To accept, click Next.
6. In the Accept License Agreements screen, if you accept the terms of the End-User License
Agreement, click Accept and Next.
7. In the Select configuration screen, select the desired vRPA performance profile.
8. If prompted to select a resource, in the Select a resource screen, select a cluster, host, or resource
pool.
9. In the Select storage screen, select a disk format, storage policy, and high-performance datastore
(best practice) to host the vRPA virtual machine files.
All ESXi hosts in the cluster where the vRPAs reside must share the datastore where the
repository VMDK resides. Do not deploy the vRPA on a local datastore.
10. In the Setup networks screen, select a destination network for the RecoverPoint Management
Network, and select an IP protocol.
11. In the Customize template screen, type these vRPA LAN settings: IP address, subnet mask, and
gateway.
Follow instructions on the screen for using DHCP or static IP addresses depending on the network
adapter topology.
12. The Ready to Complete screen summarizes all the selections. Select Power on after deployment. To
create the vRPA, click Finish.
The Deploying vRPA screen appears, showing the progress.
13. Power on the vRPA VM.
14. To create additional vRPAs, repeat this procedure.
Page 16 of 55
Results
When a vRPA is created, the vRPA Summary tab shows the vRPA package contents as specified. The
selected IP policy is implemented automatically when the vRPA is powered on.
Next steps
To enable redundancy in case an ESXi host or datastore fails, ensure that vRPAs do not share the same
ESXi host or datastore.
When you finish creating vRPAs:
● If you are running vSphere 6.7 Update 1, or later, continue to "Deploy the plugin server".
● Otherwise, continue to "Install vRPA clusters".
Prerequisites
Ensure that you:
● Have completed preparations for installation.
●Are running vSphere 6.7 Update 1 or later.
NOTE: In systems running vSphere versions earlier than 6.7 U1, you can use the plugin server
to leverage use of the REAPER API (even though it does not support use of the RecoverPoint
for VMs plugin for the vSphere Client).
Steps
1. Navigate to vCenter.
You are prompted to launch VSPHERE CLIENT (HTML5) or VSPHERE WEB CLIENT (FLEX)
2. Click VSPHERE CLIENT (HTML5) to launch the HTML5-based vSphere client.
3. In the vSphere Client, right-click the ESX cluster and select Deploy OVF Template. The Deploy OVF
Template screen opens.
4. In the Select an OVF template screen, select an OVF template for the RecoverPoint for VMs vSphere
plugin server from a remote URL or local file system.
5. In the Select a name and folder screen, specify a unique name for the plugin server, and select the
location of the virtual machine on which you want to deploy your plugin server.
6. In the Select a compute resource screen, select the destination compute resource for this operation.
7. In the Review details screen, review the general properties of the OVF template. To accept, click Next.
8. In the Select storage screen, select the storage for the configuration and disk files including the virtual
disk format and VM storage policy.
9. In the Select networks screen, select a destination network for each source network.
10. In the Customize template screen, customize the deployment properties of this software solution. a.
Select the time zone.
b. The network management default is DHCP. If you are managing your network using static IP
configuration, values for the gateway, netmask, and IP address are mandatory. Values for DNS
and and FQDN are optional, but entering a DNS address is recommended.
11. In the Ready to complete screen, review the details of the deployment and, when satisfied, click
FINISH to create the plugin server.
To track that the plugin server creation is successful, check for an OVF deployment in the Recent
Tasks window of the vSphere Client.
Page 17 of 55
12. Power on the plugin server VM.
Next steps
After installing a vRPA cluster, you should configure this plugin server with the vCenter on which the
vRPA cluster resides.
To create a plugin server for another vCenter, either at this site or a different site, repeat this procedure.
Prerequisites
● If you have changed the default plugin server certificate and have not yet configured the plugin server,
perform Changing the plugin server certificate .
● If you have changed the default plugin server certificate and have already configured the plugin
server, perform Changing a registered plugin server certificate .
● Get the Installation data forms that you created when planning the system ready so that when you are
prompted to type data, you can consult them.
Steps
1. In a web browser, type https://<LAN-ip-address> where <LAN-ip-address> is the LAN IP
address of vRPA 1 or vRPA 2 in the cluster you are installing. In the home page, click RecoverPoint
for VMs Deployer.
If you are using DHCP, obtain the LAN IP address from the vSphere Client or vSphere Web Client by
selecting the vRPA and clicking the Summary tab.
2. If prompted, type the login credentials for the admin user, and click Sign in. The RecoverPoint for VMs
Deployer home page appears.
3. Select the Install a vRPA cluster wizard.
4. On the Version Requirements page, the version requirements file is automatically downloaded and
validated to ensure that the system meets the requirements. If you have a .json configuration file
that you want to import, click the Settings icon and then click Import.
If version requirements verification is successful, click Next to continue. If issues are found, analyze
and fix blocking issues before continuing.
If the version requirements file fails to download, you are prompted to select one of these options:
● Retry downloading the up-to-date requirements from Dell Online Support ● Provide version
requirements file manually ● Do not check version requirements
NOTE: To obtain the version requirements file for offline installation, browse to
https://rplicense.emc.com/download.
This page provides an option to download or email the a-cca.xml file. If this option is not
available, open a Service Request with Customer Support Services (severity level 3). In the
request, ask for the latest version requirements file for the RecoverPoint for VMs Deployer. The
file is provided within one (1) business day and must be used within 30 days.
5. On the Installation Prerequisites page, type the requested information for the vCenter on which the
current vRPA is running, and then click Connect.
Page 18 of 55
If the SSL Certificate window appears, verify the vCenter's SSL certificate and click Confirm.
6. Review the Pre-installation Validation Results area. If validation errors are listed, fix them before
proceeding.
If an error can be automatically fixed, the Fix button appears in the Auto-Fix column.
7. On the Environment Settings page, define the required settings.
● Type a name for the vRPA cluster.
● To align with security best practices, replace the default admin user password with a new unique
password.
NOTE: The admin user (with the administrator role) is authorized with all access permissions
for managing your RecoverPoint for VMs system. Use the same admin password for all vRPA
clusters in a system, and all vRPA clusters under the same vCenter Server. The password for
the admin user serves also as the password for the root user across all vRPAs in the system.
●Type IP addresses for DNS and NTP servers.
8. On the vRPA Settings page:
a. Select the vRPAs for the vRPA cluster and click the Apply Selection button.
b. Select a repository volume from the list. All ESXi hosts in the cluster where the vRPAs reside must
share this volume.
9. On the Network Settings page, provide the requested settings for the vRPA cluster and its vRPAs.
● In the Network Adapters Configuration area, keep the default setting or click Edit to choose a
different network adapter topology.
● In the Network Mapping area, for each network adapter, select a value and whether to use DHCP.
Type a Cluster Management IP address.
● In the vRPA Settings area, type the requested IP addresses. If the network configuration requires
gateways to communicate with remote vRPA clusters, click Add to insert each gateway. For each
gateway that you add at the current cluster, add a gateway at the remote cluster.
● In the Advanced Settings area, change the MTU values only if required. MTU values must be
consistent across the communication interface from source to target. See KB article 484259 for
more information.
10. Click Install to initiate completion of the vRPA cluster installation.
You can follow progress of the installation on the Deployment progress page.
During successful installation:
● The Flex-based RecoverPoint for VMs vSphere plugin is installed automatically. Installation of the
plugin usually occurs immediately, but it might take some time for the vCenter to identify the plugin.
If you experience issues with the RecoverPoint for VMs plugin, log out and log in again to the
vSphere Web Client as described in "Troubleshooting the RecoverPoint for VMs plugin".
● The HTML5-based RecoverPoint for VMs vSphere plugin is installed after the plugin server is
deployed and configured (see Configure the plugin server).
● Splitters and Journal Access Modules (JAMs) are pushed to all ESXi hosts in the ESXi cluster
where the vRPAs are installed.
If installation fails:
● To identify the cause of failure, review the displayed error messages.
● To return to the step in the wizard where you can fix the problem, click Back. Fix the problem and
retry the installation.
● Alternatively, you can retry the operation that failed by clicking Retry the operation.
● If installation continues to fail, contact Customer Support.
Results
If you are running vCenter 6.7 U1, or later, and this is the first vRPA cluster installed on the vCenter, click
Proceed to configure plugin server now to configure your RecoverPoint for VMs plugin server for this
vCenter. If you don't configure the plugin server now, you can configure it later using the Configure plugin
server option in the RecoverPoint for VMs Deployer home screen.
Page 19 of 55
To enable multi-site replication, create additional vRPA clusters by repeating this procedure for each site.
To export a configuration file of the vRPA cluster settings, click the Settings icon (upper right), and then
click Export. This file provides a record of the vRPA cluster configuration for the major version you have
installed. You use it to restore the vRPA cluster settings after an installation failure (requiring the
installation to be repeated).
When all vRPA clusters are created, continue to "Connect the vRPA clusters".
Prerequisites
● Ensure that the admin user credentials are the same for all vRPA clusters on the vCenter that you are
registering to the plugin server.
● If you want to use a certificate that has been altered, for example, one that has been signed by your
organization's internal certificate authority, see "Changing the plugin server certificate" in the
RecoverPoint for VMs Administrator's Guide.
Steps
1. To start configuration of the RecoverPoint for VMs plugin server:
a. Select Configure plugin server on the Deployer home page.
b. Alternatively, immediately after successfully installing a vRPA cluster, click Proceed to Configure
plugin server.
2. Enter the IP address for the plugin server.
Results
● The plugin server installs the HTML-based RecoverPoint for VMs plugin on the vCenter Server.
Installation of the plugin usually occurs immediately, but it might take some time for the vCenter
Server to identify the plugin. It is recommended to log out from the vSphere Client, and then to log in
again. To access the plugin, navigate to RecoverPoint for VMs in the vSphere Client menu.
● The plugin server discovers and registers all vRPA clusters that are hosted by the vCenter Server and
have the same admin user password, including vRPA clusters that may be added later. As a result,
the plugin server knows how to direct API calls to the correct vRPA cluster.
Page 20 of 55
To enable replication between any two vRPA clusters, use the Connect vRPA clusters wizard to establish
a connection between them.
Prerequisites
● Do not exceed the maximum number of five vRPA clusters per system.
● (Recommended) Create Installation data forms.
● Ensure the remote vRPA cluster is not:
0 in maintenance mode.
○ an existing, configured vRPA cluster.
○ previously connected to a vRPA cluster.
● Ensure the remote vRPA cluster does not:
0 have protected VMs, consistency groups, or group sets.
○ have user or journal volumes.
○ have a license other than a vCenter license.
● If required, add a gateway for communication between vRPA clusters; add a gateway at each vRPA
cluster before connecting the vRPA clusters.
● If you have changed the default plugin server certificate and have not yet configured the plugin server,
perform Changing the plugin server certificate .
● If you have changed the default plugin server certificate and have already configured the plugin
server, perform Changing a registered plugin server certificate .
NOTE: A remote vRPA cluster that meets these requirements is called a "clean" cluster.
Steps
1. In a web browser, type https://<cluster_management-ip-address> for the vRPA cluster that
you want to connect.
2. In the RecoverPoint for VMs Deployer home page of the current cluster, select the Connect vRPA
clusters wizard.
3. On the Environment Settings page, type the requested information for the remote cluster. It is
important to enter the WAN IP of one of the remote vRPAs.
4. In the Current Cluster Settings area, review the list of gateways that are configured for this vRPA
cluster. If required, add one or more gateways on the current vRPA cluster. Remember that for each
additional gateway at the current cluster, you must add a gateway at the remote cluster.
5. On the Add Cluster Progress page, the remote cluster is connected to your RecoverPoint for VMs
system, and IP communication is enabled between the remote cluster and the current cluster.
NOTE: This does not enable communication between the remote cluster and any other
clusters in your system. To enable communication between the remote cluster and
additional clusters, follow the procedure in Enable communication between vRPA clusters.
Page 21 of 55
Completing installation of the RecoverPoint for VMs
system
Installation is almost complete. Once you register and license your system, and create any VMkernel
ports that are needed, you will be able to begin protecting VMs.
Protect VMs
The RecoverPoint for VMs system is ready for operation. Use the RecoverPoint for VMs plugin (HTML5-
based or Flex-based) to begin protecting VMs. See the RecoverPoint for Virtual Machines
Administrator''s Guide for instructions on protecting VMs and monitoring the system.
4
Maintaining RecoverPoint for VMs
Maintaining the RecoverPoint for VMs system involves tasks such as collecting logs, modifying vRPA
cluster network settings and topology, and adding, removing, or replacing vRPAs.
The topics in this chapter provide procedures for system
maintenance. Topics:
• Register ESX clusters
• Add ESXi host to a cluster
• Configure VMkernel ports
• Enable communication between vRPA clusters
• Modify vRPA cluster network settings
Page 22 of 55
• Change the RPA communication security level
• Modify the network topology
• Installing the splitter with Boxmgmt CLI
• Install the splitter with the RecoverPoint for VMs VIB installer
• Install JAM
• Add vRPAs to a vRPA cluster
• Remove a vRPA from a vRPA cluster
• Replace a vRPA
• Change default passwords
• Collect logs
Steps
1. Access the vSphere Client or Web Client.
In the vSphere Client, click System > ESX Clusters.
In the vSphere Web Client, click RecoverPoint for VMs Management > Administration > vRPA
Clusters, and select the ESXi Clusters tab.
2. Select the ESX cluster to be registered, and click Add. Verify that the connectivity status is OK. If there
are connectivity issues with the cluster, click Troubleshoot.
Prerequisites
An ESXi must be registered (see Register ESX clusters) before you can configure VMkernel adapters on
it.
Steps
1. For each ESXi host, click Manage > Networking > VMkernel adapters.
2. Add the VMkernel adapters.
● Assign IP addresses that are on a routable subnet or on the same subnet as the vRPA data
interfaces.
Page 23 of 55
It is recommended also that the VMkernel and vRPA data ports be on the same L2 network.
● For a standard vSwitch, create a VMkernel port with the network label: RP-VM-Kernel-
Port-Group ● For a distributed vSwitch:
○ Create a VMkernel port on the relevant port group.
○ On the Ports tab of the Distributed Ports Group page, label each VMkernel port that is to be used
for splitter-tovRPA communication as RP-VM-Kernel-Port-Key.
The vRPA data IP addresses are assigned when deploying the vRPA cluster.
Steps
1. Use an SSH client to connect as admin user to a cluster management vRPA of one of the pair of
vRPA clusters between which you want to enable communication.
2. From the Boxmgmt CLI Main Menu, select Cluster operations > Configure connection types to other
clusters in the system > Configure cluster connection types.
3. Select the vRPA cluster with which you want to enable communication.
Results
Bi-directional IP communication is enabled between the designated pair of vRPA clusters.
Repeat this procedure for each pair of vRPA clusters for which you want to enable communication.
Prerequisites
To modify the network adapter topology, refer to Modify the network topology.
Steps
1. In a web browser, type https://<cluster_management-ip-address> for the vRPA cluster that
you want to modify.
2. In the home page, click RecoverPoint for VMs Deployer.
3. If prompted, type the login credentials for the admin user and click Sign in.
4. Under More actions, select Modify vRPA cluster network.
5. Make the desired changes to the Environment Settings page. If you have a .json configuration file
that you want to import, hover over the Settings icon and click Import.
6. Make the desired modifications changes to the Network Settings page.
Some settings cannot be modified.
Page 24 of 55
7. To apply the changes, click Modify. To export a configuration file of the vRPA cluster settings, click the
Settings icon (upper right), and then click Export. This file provides a record of the vRPA cluster
configuration.
Steps
1. Pause transfer between the production and copies of the consistency groups for the vRPA cluster that
you are modifying.
2. From the vSphere Client or Web Client, add the vNIC on all vRPA VMs. Ensure that the type is
VMXNET3.
3. Use an SSH client to log in to the vRPA as the admin user.
a. Detach the vRPA from the vRPA cluster. From the Main menu, select Cluster operations > Detach
RPA from cluster.
b. From the Main menu, select Setup > Modify settings > Enter cluster details > Network Interface
and IPs Configuration.
c. Select the network topology that you want to use.
d. Attach the vRPA back to the cluster. From the Main menu, select Cluster operations > Attach RPA
to cluster.
4. Repeat step 3 for each vRPA in the vRPA cluster.
5. Start transfer between the production and copies of the consistency groups for the modified vRPA
cluster.
Steps
1. Use an SSH client to connect as admin user to a cluster management vRPA.
2. From the boxmgmt Main Menu, select Setup > Advanced options > Splitter actions > Upgrade Splitter.
3. Provide the vCenter Server credentials.
4. Let the system provide the vCenter certificate automatically and, if it's correct, approve the certificate.
5. Select one or more of the ESXi cluster(s) in this vCenter on which you want to deploy the splitters.
Install the splitter with the RecoverPoint for VMs VIB installer
During system installation, the RecoverPoint for VMs splitter VIB is installed on ESXi hosts automatically.
Use this procedure if you need to install the splitter VIB manually.
Prerequisites
Note the Secure boot considerations.
Page 25 of 55
About this task
Steps
1. To copy the splitter VIB, use an SSH client with secure copy protocol:
scp <vib name> <username>@<ESXi host IP>:/scratch
For example, run:
scp EMC_bootbank_RP-Splitter_RPESX-00.5.3.2.0.0.m.222.000.vib
root@10.10.10.10:/scratch
2. To install the splitter VIB in the ESXi host console:
● In RecoverPoint for VMs version 5.3 SP2 and later, run the command:
esxcli software vib install -v /<vib_full_path>
● In RecoverPoint for VMs versions prior to 5.3 SP2, run the command:
esxcli software vib install -v /<vib_full_path> --no-sig-check
Results
The RecoverPoint for VMs splitter name is displayed at the top of the list.
Next steps
Repeat this procedure for every ESX on which you want to install the RecoverPoint for VMs splitter VIB.
Install JAM
During new installations of RecoverPoint for VMs (but not upgrades), the RecoverPoint for VMs Journal
Access Module (JAM) VIB is installed automatically on all ESXi hosts that belong to ESXi clusters on
which vRPAs are running. Use this procedure if you need to install the JAM VIB manually.
Prerequisites
Note the Secure boot considerations.
Page 26 of 55
About this task
In RecoverPoint for VMs versions prior to 5.3 SP2, there is only one JAM VIB. In RecoverPoint for VMs
5.3 SP2 and later versions, there is one JAM VIB for ESXi version 6.x hosts and another for ESXi version
7.x hosts.
Steps
1. To copy the JAM VIB, use an SSH client with secure copy protocol:
scp <vib name> <username>@<ESXi host IP>:/scratch
For example:
● On ESXi 6.x hosts, run:
scp EMC_bootbank_emcjiraf_5320.m.186-1OEM.650.1.17.4598673.vib
root@10.10.10.10:/ scratch
● In RecoverPoint for VMs versions prior to 5.3 SP2, run the command:
esxcli software vib install -v /<vib_full_path> --no-sig-check
Results
The RecoverPoint for VMs JAM installation name is displayed at the top of the list.
Next steps
Repeat this procedure for every ESX on which you want to install the RecoverPoint for VMs JAM VIB(s).
Page 27 of 55
Add vRPAs to a vRPA cluster
Use this procedure to add a vRPA to an existing vRPA cluster. A vRPA cluster can have up to 8 vRPAs,
and all vRPAs in a cluster must run the same RecoverPoint for VMs version.
Prerequisites
If you are not using the default vRPA web server certificate, ensure that your certificate is the same one
used for all vRPAs in the vRPA cluster.
Steps
1. In a web browser, type https://<cluster_management-ip-address> for the vRPA cluster to
which you want to add vRPAs.
2. In the home page, click RecoverPoint for VMs Deployer.
3. If prompted, type the login credentials for the admin user and click Sign in.
4. Under More actions, click Add vRPAs to vRPA cluster.
5. In the Add Prerequisites step, acknowledge that you have met the listed conditions by selecting the
checkbox.
6. In the Add vRPAs step, select one or more VMs/vRPAs to add to the cluster.
● New vRPAs must have the same RecoverPoint software ISO image as the existing vRPAs in the
cluster. ● A cluster can have a maximum of 8 vRPAs.
7. In the vRPA Cluster Settings and vRPA Settings sections, type required information for the vRPAs you
are adding.
8. In the Add vRPAs Progress step, on reaching 100%, click Finish to return to the Home Page. If adding
a vRPA fails:
● To identify the cause of failure, review the displayed error messages.
● To return to the step in the wizard where you can fix the problem, click Back. Fix the problem, and
then retry the installation wizard from that point.
● Alternatively, you can retry the operation that failed by clicking Retry the operation.
● If adding a vRPA continues to fail, contact Customer Support.
Steps
1. In a web browser, type https://<cluster_management-ip-address> for the vRPA cluster from
which you want to remove a vRPA.
2. In the home page, click RecoverPoint for VMs Deployer.
3. If prompted, enter the login credentials for the admin user and click Sign in.
4. Under More actions, click Remove vRPA from vRPA cluster.
● The highest numbered vRPA (the last one added) will be removed.
● The consistency groups of the removed vRPA will be non-disruptively moved to a different vRPA.
● The preferred vRPA setting for those consistency groups will be automatically updated.
Replace a vRPA
Use this procedure and wizard to replace a vRPA with a different vRPA.
Page 28 of 55
Prerequisites
This wizard does not support replacing a vRPA within a vRPA cluster that has only one vRPA. If you
must replace a vRPA in a single-vRPA cluster, contact Customer Support.
Steps
1. In a web browser, type https://<cluster_management-ip-address> for the vRPA cluster in
which you want to replace a vRPA.
2. In the home page, click RecoverPoint for VMs Deployer.
3. If prompted, type the login credentials for the admin user and click Sign in.
4. Under More actions, click Replace vRPA.
5. In the Prerequisites step, acknowledge that you have met the listed conditions by selecting the
checkbox.
6. In the Replace vRPA step, select the vRPA that you want to replace.
7. Select the vRPA you want to add as a replacement.
8. In the Replacement Progress step, on reaching 100% click Finish to return to the home page.
If replacing a vRPA fails:
● To identify the cause of failure, review the displayed error messages.
● To return to the step in the wizard where you can fix the problem, click Back. Fix the problem, and
then retry the installation wizard from that point.
● Alternatively, you can retry the operation that failed by clicking Retry the operation.
● If replacing a vRPA continues to fail, contact Customer Support.
Steps
1. Create an SSH connection to the vRPA management IP address, using your RecoverPoint for Virtual
Machines admin username and password to log into the Boxmgmt CLI. Then select System
management CLI to open the Sysmgmt CLI.
Alternatively, if you have created a user with the sysmgmt role, use that user to log in directly to the
Sysmgmt CLI.
2. In the Sysmgmt CLI, run the set_password command to change the password for the current user,
or run the set_user command to change the password of another user, provided that your user/role
includes the security permission.
Page 29 of 55
NOTE: Keep passwords in a place where they are secure and available to you.
Collect logs
During deployment, collecting logs for the current vRPA cluster and its vRPAs provides information that
may be helpful in troubleshooting the installation.
Steps
1. In a web browser, type https://<LAN-ip-address> where <LAN-ip-address> is the vRPA cluster
management IP address. In the vRPA cluster home page, click RecoverPoint for VMs Deployer.
2. If prompted, type the login credentials for the admin user and click Sign in.
3. Display the log collection settings in the RecoverPoint for VMs Deployer home page.
● In RecoverPoint for VMs 5.3 SP2 and later versions, in the upper-right corner, click Collect Logs.
● In RecoverPoint for VMs versions prior to 5.3 SP2, at the upper right of the home page, click the
Settings icon, and then click Collect Logs.
4. In the Collect Cluster Logs dialog box:
Page 30 of 55
Results
Depending on the size of the environment, log collection may take several minutes to complete. When
the collection process is complete, a success message is displayed with the location (i.e. vRPA cluster)
containing the logs.
Next steps
1. In the success message, click the name of a vRPA cluster to open a browser window to the location of
the collected logs.
2. If prompted to, log into the vRPA cluster with your admin user credentials.
3. Click a vRPA log name to download the vRPA log.
The name of each vRPA log has a *.tar extension and it includes the
<clustername><vrpaname> and <vrpaip> for easy identification. The log collection date is
displayed under Last Modified.
Page 31 of 55
Deploying RecoverPoint for VMs in a VxRail™ environment
Follow specific guidelines when deploying RecoverPoint for VMs in a VxRail environment.
Steps
● Use the default configuration of two network adapters (WAN + LAN on one adapter and data on the
other) unless required to use a different network adapter topology. For this configuration, define two
port groups: RP_WAN+LAN and RP_DATA. ● If using a single network adapter, define one port
group: RP_ALL.
● If using four network adapters, define four port groups: RP_WAN, RP_LAN, RP_DATA1, RP_DATA2.
Page 32 of 55
Create vRPAs for VxRail
Use the OVA file and guidelines in this procedure to create vRPAs for VxRail environments.
Steps
1. In the Select storage screen, in the VM Storage Policy drop down, select VxRail-Virtual-SAN-
Datastore. The compatible VSAN datastore will be selected.
2. Deploy two vRPAs and configure VM-Host affinity rules to avoid running both vRPAs on the same
ESXi node (recommended).
Steps
1. Create one or two VMkernel ports on each ESXi node by selecting an existing distributed vSwitch
“VMware HCIA Distributed
Switch.”
A single VMkernel port is required when using the default of two network adapters (WAN + LAN on
one network adapter and data on the other network adapter). This configuration is standard. Two
VMkernel ports are required when you are using two network adapters for data.
2. To select one network adapter (uplink) as active, override the NIC teaming policy. The other network
adapter should be marked as unused.
When using a single VMKernel port, assign uplink1 to the port.
When using two VMkernel ports:
● Assign uplink1 to one VMkernel port and uplink2 to the second VMkernel port.
● For uplink2, use traffic shaping to limit bandwidth to no more than 1Gb/s (if NIOC is enabled with
the default VxRail setting, traffic shaping is optional):
a. Locate the port group, right-click it, and select Edit Settings.
b. In the Edit Settings window, change traffic shaping for the port group:
Traffic shaping Field Value
Page 33 of 55
About this task
When creating a vRPA cluster:
Steps
1. In the Environment Settings step, select the vSAN datastore from the table of available datastores.
2. In the Network Settings step of the wizard, specify the vRPA data network addresses (and not the
VMkernel port IP addresses that were created earlier).
Steps
1. Verify that the nodes are added into the same vSAN cluster and under the same vCenter.
2. Configure each ESXi node with the required data network adapters for enabling splitter-to-vRPA
communication.
3. If you created a new ESXi cluster, register it within the vRPA cluster.
This action installs the RecoverPoint for VMs splitters on the new ESXi nodes.
4. Adjust VM-host affinity rules for the vRPAs to ensure that they are running on separate ESXi servers.
Page 34 of 55
Installing in VxRail environments
Troubleshooting vRPAs
This section describes how to troubleshoot these vRPA conditions:
● vRPA is down
● vRPA is detached from cluster
Steps
1. Check the RecoverPoint for VMs dashboard for Error events indicating that the vRPA is not online.
2. Log in to a surviving vRPA and type the RecoverPoint admin username and password to log in to the
Boxmgmt CLI. Then select System management CLI to open the Sysmgmt CLI. Alternatively, if you
have created a user with the sysmgmt role, use that user to log in directly to the Sysmgmt CLI. To
check the cluster status, use the get_system_status Sysmgmt CLI command. Choose to retrieve
the status of all categories.
3. Confirm that the failed vRPA cannot be reached.
4. Check any conflicts in the vRPA resource reservation that might have led to the vRPA being powered
off. Resolve any issues before proceeding.
5. In the vSphere Web Client, right-click the vRPA that is down and select All vCenter Actions > Power >
Power On.
6. To ensure that the vRPA was powered on successfully, monitor the vRPA console in the vSphere
Web Client.
7. To investigate the root cause of the vRPA failure, collect logs.
Page 35 of 55
vRPA is detached from the vRPA cluster
If the vRPA is detached from the vRPA cluster, check for vRPA errors and cluster status.
Steps
1. Check the RecoverPoint for VMs dashboard for Error events indicating that the vRPA cannot access
storage or communicate with the splitters.
2. Create an SSH connection to a surviving vRPA, using your RecoverPoint for Virtual Machines admin
username and password to log into the Boxmgmt CLI. Then select System management CLI to open
the Sysmgmt CLI. Alternatively, if you have created a user with the sysmgmt role (RecoverPoint for
Virtual Machines 5.2.0.2 or later), use that user to log in directly to the Sysmgmt CLI. Use the
get_system_status Sysmgmt CLI command to check the cluster status. Choose to retrieve the
status of all categories.
3. Confirm that the detached vRPA cannot be reached from the surviving vRPA.
4. Log in to the Boxmgmt CLI of the detached vRPA using admin username and password, and select
Cluster operations > Attach RPA to Cluster. To ensure that the vRPA was powered on successfully,
monitor the vRPA console in the vSphere Web Client.
5. To investigate the root cause of the vRPA detachment from the cluster, collect logs.
6. If you are using a licensed version of RecoverPoint for VMs, contact Customer Support.
Steps
1. Ensure the vRPA is online.
2. Ensure the vRPA is attached to the cluster.
3. Verify that the splitters are running:
a. Login to ESXi hosts.
b. Run: ps |grep kdriver
c. Ensure that splitter processes are running.
4. To investigate the root cause of why the vRPA went down, collect logs.
5. If you are using a licensed version of RecoverPoint for VMs, contact Customer Support.
Troubleshooting splitters
The section describes how to troubleshoot the splitter when it is not visible or is in error state.
Steps
1. If possible, vMotion any protected VMs from ESXi hosts with splitters in error state continue or resume
replication.
2. Ensure that the splitter processes are running on the host you are troubleshooting:
a. Login to the ESXi host and use the following command: ps |grep kdriver
Page 36 of 55
b. If processes are not running, place the ESXi node in maintenance mode and restart.
3. To investigate the root cause of the splitter failure, collect logs.
4. If you are using a licensed version of RecoverPoint for VMs, contact Customer Support.
Steps
1. Log out of vSphere Web client and log back in. Check if the RecoverPoint for VMs plug-in is listed
under Inventories.
2. If the RecoverPoint for VMs plug-in is not listed, close all active vSphere Web client user sessions.
Then check if the RecoverPoint for VMs plug-in is listed under Inventories.
3. If the RecoverPoint for VMs plug-in is still not listed, restart the vCenter Web Client service.
4. If the plug-in is still not visible in the vSphere Web Client, validate the vCenter Credentials
configuration. You may need to reconfigure vCenter credentials. Consult Customer Support if
protected VMs exist.
5. If the plug-in is still not visible in the vSphere Web Client, collect logs to investigate the root cause of
why the plug-in is not visible.
Steps
1. Log out of the vSphere Web Client and log back in.
2. Refresh the vSphere Web Client.
3. Log out all users from the vSphere Web Client.
4. Restart the vSphere Web Client.
5. Log in to the Managed Object Browser at https://<vSphere Web Client>/mob. Ensure the
vCenter credentials are configured correctly.
Access to the Managed Object Browser is disabled by default in vSphere 6.0 and later. For
instructions on how to enable access, refer to VMware KB2108405.
6. Restart vRPA1.
7. Restart vRPA2.
8. To investigate the root cause of the vRPA failure, collect logs.
9. If you are using a licensed version of RecoverPoint for VMs, contact Customer Support.
Page 37 of 55
About this task
Use this procedure, for instance, if you want to use a certificate that has been signed by your
organization's internal certificate authority.
Steps
1. Connect to the plugin server with root permissions.
2. Create a backup of the existing certificate and key files:
/etc/nginx/ssl/rpcenter.cert
/etc/nginx/ssl/rpcenter.key
3. Disable the firewall on the plugin server.
Run the command /sbin/SuSEfirewall2 off
4. Upload the new certificate and key files to /etc/nginx/ssl.
5. Rename the new certificate file to rpcenter.cert and the new key file to rpcenter.key.
6. Reboot the plugin server VM.
7. In the RecoverPoint for VMs Deployer, click Configure plugin server home screen.
Enter the plugin server IP address in IPv4 format, confirm the new certificate, and click
Configure.
For more information, see the "Configure the plugin server" in the RecoverPoint for VMs Installation
and Deployment Guide.
Results
RecoverPoint for VMs is configured to use the new plugin server certificate.
N
e
x
t
st
e
p
s
N
O
T
E
:
Check that the certificate is the same across all vRPAs of the same cluster before adding the vRPA to
the cluster.
Log into vSphere Client from the relevant vCenter Server and check that the RecoverPoint for VMs
HTML5 plugin is displayed.
Page 38 of 55
Changing a registered plugin server certificate
Use this procedure to change the plugin server certificate after the plugin server has already been
configured using Deployment Manager.
Steps
1. Connect to the plugin server with root permissions.
2. Create a backup of the existing certificate and key files:
/etc/nginx/ssl/rpcenter.cert
/etc/nginx/ssl/rpcenter.key
3. Disable the firewall on the plugin server.
Run the command /sbin/SuSEfirewall2 off
4. Upload the new certificate and key files to /etc/nginx/ssl.
5. Rename the new certificate file to rpcenter.cert and the new key file to rpcenter.key.
6. Power off the plugin server VM.
7. Unregister the RecoverPoint for VMs HTML5 plugin from the relevant vCenter Server.
See "Unregistering the plugin from the Managed Object Browser" in the RecoverPoint for VMs
Installation and Deployment Guide.
8. Power on the plugin server VM.
9. Navigate to https://RPCIP/ui.
10. Click Authorize and enter the vCenter Server Credentials.
11. Navigate to DELETE /vcs/{vc-id} near the bottom of the Swagger page.
12. Select Try it Out, enter the vCenter Server serial number, and select Execute.
A 204 response is returned.
13. In the RecoverPoint for VMs Deployer, click Configure plugin server home screen.
Enter the plugin server IP address in IPv4 format, confirm the new certificate, and click
Configure.
For more information, see the "Configure the plugin server" in the RecoverPoint for VMs Installation
and Deployment Guide.
Results
RecoverPoint for VMs is configured to use the new plugin server certificate.
N
e
x
t
s
t
e
p
s
Page 39 of 55
N
O
T
E
:
Ensure the certificate is the same across all vRPAs of the same cluster before adding the vRPA to the
cluster.
Log into vSphere Client from the relevant vCenter Server and check that the RecoverPoint for VMs
HTML5 plugin is displayed.
Page 40 of 55
2. If the consistency group is still in Error state, try the following:
a. Check if the image access buffer is full. If so, disable image access.
b. Resolve any WAN issues.
c. Check if the consistency group is in a permanent high-load state.
3. To investigate why the consistency group is in error state, collect logs.
4. If you are using a licensed version of RecoverPoint for VMs, contact Customer Support.
A
RecoverPoint for VMs installation form
The installation form is a data sheet or spreadsheet that lists the site-specific values that you require to
successfully complete the installation.
To streamline the installation tasks, create the RecoverPoint for VMs installation form during the planning
phase.
Topics:
• Installation data forms
Page 41 of 55
Installation data forms
The best practice for successful installations is to collect and document required data before the
installation.
The forms that are provided in this section are examples of the types of information you should collect
before installation. You can create a planning spreadsheet that matches specific requirements (number
of vRPA clusters, network topology, and so forth).
You are directed to type the data from these forms (or similar data sheet) during the installation process.
Cluster/site name
Time zone
Local domain
Primary DNS
server (optional)
Secondary DNS
server (optional)
Primary NTP
server
(recommended)
Secondary
NTP server
(recommended)
Cluster
management IP
Management
default gateway
IP
Management
subnet mask IP
WAN default
gateway
WAN subnet
mask
SMTP (optional)
vCenter IP
vCenter
credentials
RecoverPoint for VMs installation form
Page 42 of 55
Table 2. Example: vRPA cluster/site form (continued)
vRPA cluster vRPA cluster 1 vRPA cluster 2 vRPA cluster 3 vRPA cluster 4 vRPA cluster 5
vCenter
credentials
Plugin server (per
vCenter Server)
VMkernel IP pool
ESXi 1
_Data1 IP
_Data2 IP
_Management IP
ESXi 2
_Data1 IP
_Data2 IP
_Management IP
WAN IP
vRPA_1
Data1 IP
Data2 IP
LAN IP
WAN IP
vRPA_2
Data1 IP
Data2 IP
LAN IP
vRPA_3 WAN IP
Data1 IP
Page 43 of 55
Data2 IP
LAN IP
WAN IP
vRPA_4
Data1 IP
Data2 IP
LAN IP
WAN IP
vRPA_5
Data1 IP
Data2 IP
LAN IP
vRPA_6 WAN IP
Data1 IP
LAN IP
WAN IP
vRPA_7
Data1 IP
Data2 IP
LAN IP
WAN IP
vRPA_8
Data1 IP
Data2 IP
Page 44 of 55
vCenter <name> <name> <name> <name> <name>
Server <ip_address> <ip_address> <ip_address> <ip_address> <ip_address>
B
Support procedures for uninstalling vRPA
clusters
When the automated uninstaller tool is unavailable, you can manually uninstall a vRPA cluster by using
support procedures to guide you.
The topics in this Appendix provide procedures for use in manually uninstalling a vRPA cluster.
Topics:
Page 45 of 55
• Uninstalling a single vRPA cluster from a vCenter manually
• Uninstalling all vRPA clusters from a vCenter manually
• Unprotect VMs
• Remove ESX clusters from vRPA clusters
• Remove a vRPA from a vRPA cluster
• Detaching vRPAs
• Powering off vRPAs
• Deleting the repository folder
• Verifying that the configuration parameters are empty
• Removing custom tokens from the Managed Object Browser
• Unregistering the plugin from the Managed Object Browser
• Removing unused directories
• Uninstall the RecoverPoint for VMs splitters
• Uninstall JAM
Prerequisites
Obtain the internal cluster name of the vRPA you are uninstalling by connecting to the vRPA Boxmgmt
CLI as the admin user, and selecting Main Menu > Setup > View Settings.
Steps
1. If the vRPA cluster is active:
a. Unprotect the virtual machines. For more information, see Unprotect VMs.
b. Remove all ESX clusters from the vRPA cluster. For more information, see Remove ESX clusters
from vRPA clusters. Repeat this step for all ESX clusters in the vRPA cluster.
2. If you are removing just one vRPA cluster from a system with at least two clusters, perform the
following procedure: Uninstall a vRPA cluster.
If the procedure Uninstall a vRPA cluster was successful, skip to step 6. If the procedure Uninstall a
vRPA cluster failed, continue with the next step.
3. Detach the vRPAs from the cluster. For more information, see Detaching vRPAs.
4. Power off the vRPAs. For more information, see Powering off vRPAs.
5. Remove the custom tokens that correspond to the RecoverPoint for VMs cluster ID. For more
information, see Removing custom tokens from the Managed Object Browser.
6. Delete from all datastores the repository folder of the cluster you are uninstalling. For more
information, see Deleting the repository folder.
7. Verify that the configuration parameters are empty. For more information, see Verifying that the
configuration parameters are empty.
Page 46 of 55
NOTE: Perform this step only if you encountered problems when unprotecting the VMs.
Performing this step requires downtime of the production VM.
8. Ensure that the vRPA virtual machines are powered off, and delete them.
9. If the ESX cluster you are removing is not registered to any other vRPA cluster, you can uninstall the
RecoverPoint for VMs splitter on that ESXi host. For more information, see Uninstall the RecoverPoint
for VMs splitters.
Prerequisites
Obtain the internal cluster name of the vRPA you are uninstalling by connecting to the vRPA Boxmgmt
CLI as the admin user, and selecting Main Menu > Setup > View Settings.
Steps
1. If the vRPA cluster is active:
a. Unprotect the virtual machines. For more information, see Unprotect VMs.
b. Remove all ESX clusters from the vRPA clusters. For more information, see Remove ESX clusters
from vRPA clusters. Repeat this step for all ESX clusters in all vRPA clusters.
2. If you are removing just one vRPA cluster from a system with at least two clusters, perform the
following procedure: Uninstall a vRPA cluster.
If the procedure Uninstall a vRPA cluster was successful, skip to step 6. If the procedure Uninstall a
vRPA cluster failed, continue with the next step.
3. Detach the vRPAs from the cluster. For more information, see Detaching vRPAs.
4. Power off the vRPAs. For more information, see Powering off vRPAs.
5. Remove the custom tokens that correspond to the RecoverPoint for VMs Internal cluster name. For
more information, see Removing custom tokens from the Managed Object Browser.
6. Delete from all datastores the repository folders of all clusters. For more information, see Deleting the
repository folder.
7. Verify that the configuration parameters are empty. For more information, see Verifying that the
configuration parameters are empty.
NOTE: Perform this step only if you encountered problems when unprotecting the VMs.
Performing this step requires downtime of the production VM.
8. Ensure that the vRPA virtual machines are powered off, and delete them.
9. Unregister the plug-in from the Managed Object Browser. For more information, see Unregistering the
plugin from the Managed Object Browser.
10. Uninstall the RecoverPoint for VMs splitter. For more information, see Uninstall the RecoverPoint for
VMs splitters.
11. Unregister the RecoverPoint extension from the Managed Object Browser. For more information, see
Unregistering the plugin from the Managed Object Browser.
12. Remove the RecoverPoint datastore element. Delete the RecoverPoint.flp file located in the
RecoverPoint folder.
Page 47 of 55
Unprotect VMs
To stop replication for a vRPA, unprotect the associated VM.
Steps
1. In the vSphere Web Client home page, click the RecoverPoint for VMs Management icon > Protection
tab. Click Virtual Machines.
Alternatively, in the vSphere Client home page, open the RecoverPoint for VMs menu, and click
Protection > Protected VMs.
2. Select the VM you wish to stop replicating. Click the Unprotect icon. Repeat for each protected VM.
Steps
1. Access the RecoverPoint for VMs plugin in your vSphere client.
● In the RecoverPoint for VMs HTML5 plugin:
a. Select System > ESX Clusters.
b. If you are replicating remotely, select the vRPA Cluster from which you want to unregister the
ESX cluster.
● In the RecoverPoint for VMs FLEX plugin:
a. Select Administration > vRPA Clusters, and select the ESXi Clusters tab.
b. Select the relevant vRPA cluster.
2. Click the Delete icon next to each ESX cluster to unregister that ESX cluster from the specified vRPA
cluster.
Results
The ESX cluster is unregistered from the specified vRPA cluster.
Steps
1. In a web browser, type https://<cluster_management-ip-address> for the vRPA cluster from
which you want to remove a vRPA.
2. In the home page, click RecoverPoint for VMs Deployer.
3. If prompted, enter the login credentials for the admin user and click Sign in.
4. Under More actions, click Remove vRPA from vRPA cluster.
● The highest numbered vRPA (the last one added) will be removed.
● The consistency groups of the removed vRPA will be non-disruptively moved to a different vRPA.
● The preferred vRPA setting for those consistency groups will be automatically updated.
Page 48 of 55
Detaching vRPAs
Steps
1. Use an SSH client to connect to a vRPA and enter login credentials for the admin user.
2. From the Main Menu, select Cluster Operations > Detach from Cluster. Replication is paused.
3. Repeat this procedure on all vRPAs in all vRPA clusters in the system.
Steps
1. At the vSphere Web Client, in Inventory, select Hosts and Clusters. Select a VM that was protected by
RecoverPoint for VMs. Power off the VM. Right-click and select Edit Settings...
2. In the Edit Settings dialog box, select the VM Options tab. Expand the Advanced column. In the
Configuration Parameters row, click Edit Configuration... to edit the advanced configuration
parameters.
3. In the Configuration Parameters window, ensure that all configuration parameters with "RecoverPoint"
or "esx_splitter" in the name have empty values.
The following parameters must not exist or have empty values:
● RecoverPoint RPA number
● RecoverPoint CGUID
● RecoverPoint Cluster ID
● esx_splitter.globalOptions
● esx_splitter.scsi0:1.options
Page 49 of 55
Removing custom tokens from the Managed Object
Browser
About this task
The custom tokens that correspond to the RecoverPoint for VMs cluster ID need to be removed from the
cluster(s) being reinstalled for all previously used vCenters.
NOTE: Access to the Managed Object Browser is disabled by default in vSphere 6.0. For
instructions on how to enable access, refer to VMware KB2108405.
Steps
1. In a web browser, enter the fully-qualified domain name (or IP address) of the vCenter Server system:
https://<hostname.yourcompany.com>/mob/?moid=CustomFieldsManager
2. Log in using your vCenter login credentials.
3. In the Methods table, select RemoveCustomFieldDef.
A new browser window opens with the void RemoveCustomFieldDef command displayed.
4. In the Parameters table, enter the value of a custom field listed in the Properties table that
corresponds to the Internal cluster name, RecoverPoint_TOKEN, for example,
config.RecoverPoint_TOKEN;3070371118132351610.
5. Click Invoke Method.
6. If you are reinstalling several clusters, repeat steps 3 through 5 for each custom field listed in the
Properties table that corresponds to the Internal cluster names.
Steps
1. In a web browser, enter the fully-qualified domain name (or IP address) of the ESXi or vCenter Server
system:
https://<hostname.yourcompany.com>/mob/?moid=ExtensionManager
2. Log in using your vCenter login credentials.
3. In the Methods table, select UnregisterExtension.
A new browser window opens with void UnregisterExtension command displayed.
4. In the Parameters table, enter com.dell.recoverpoint.vc.h5plugin (HTML5 value), or
com.emc.recoverpoint.vwc (FLEX value), and click Invoke Method.
Page 50 of 55
Removing unused directories
From the vCenter, remove RecoverPoint for VMs Flex plugin directories that are no longer being used.
Steps
1. Connect to the vCenter server (using a local network mapping or Remote Desktop Connection).
Delete the following folder:
● vCenter 6.5/6.7 and Windows vCenter:
C:\ProgramData\VMware\vCenterServer\cfg\vsphere-
client\vcpackages\vsphere-client-serenity\com.emc.recoverpoint.vwc-
<version>
● vCenter 6.5/6.7 and vCSA: /etc/vmware/vsphere-client/vc-packages/vsphere-
client-serenity/ com.emc.recoverpoint.vwc-<version>
2. Restart the vSphere Web Client. For instructions, refer to VMware KB1003895 (Windows), VMware
KB2109887 (Linux vCenter 6.x), or VMware KB2147152 (Linux - vCenter 6.5).
Steps
1. Use ESXCLI to obtain a list of all installed vSphere Installation Bundles (VIBs):
esxcli software vib list
2. Ensure that a bundle named RP-Splitter is installed.
3. On the ESXi host, enter maintenance mode:
esxcli system maintenanceMode set -e=true
NOTE: For VSAN environments, this command requires an additional switch (refer to the
vSphere documentation for the vSphere version that you are using).
Uninstall JAM
Use this procedure to uninstall the JAM VIB from an ESXi host.
Steps
1. On the ESXi host, vMotion all VMs to another ESXi host.
2. At the ESXCLI, enter maintenance mode. From the ESXi host console, use SSH to run the command:
esxcli system maintenanceMode set -e=true
Page 51 of 55
NOTE: For VSAN environments, this command requires an additional switch. Refer to the
vSphere documentation for the vSphere version that you are using.
C
vSphere upgrades
You may be required to upgrade a vCenter or an ESXi host that is used in the RecoverPoint for VMs
system.
Information about these tasks helps you to successfully perform these
upgrades. Topics:
• Upgrading vCenter
• Upgrading an ESXi host
Upgrading vCenter
About this task
The vCenter upgrade is transparent to RecoverPoint for VMs provided that the upgrade process does not
cause a change in the vCenter UUID.
Use this procedure when you need to upgrade the vCenter within a RecoverPoint for VMs system.
During the upgrade:
● vRPA clusters cannot be managed from this vCenter. Ensure you have access to other vCenters.
● Data replication and recovery point objective (RPO) might be affected.
● vCenters in Enhanced Linked Mode might be impacted (one vCenter at a time).
●RecoverPoint for VMs plug-in should remain intact.
CAUTION: To avoid changing the vCenter UUID during the upgrade process, ensure that you select
the Use existing inventory option.
Steps
1. If you are upgrading to vCenter 6.5, follow the Best practices for upgrading to vCenter Server 6.5.
2. If you are upgrading to vCenter 6.7, follow the Best practices for upgrading to vCenter Server 6.7.
When upgrading to vCenter Server 6.7 U1, or later (from vCenter Server earlier than 6.7 U1), Deploy
the plugin server and Configure the plugin server for each vCenter.
Results
Page 52 of 55
The vCenter Server is upgraded to the specified version.
Next steps
If RecoverPoint for VMs is in an error state after you upgrade the vCenter, check if the vCenter UUID has
changed. If it has, contact Customer Support.
Prerequisites
Before upgrading to ESXi 7.0U2 or later, ensure your vRPA clusters and splitter and JAM VIBs are all
running RP4VMs 5.3 SP2 or later versions.
vSphere upgrades
Steps
1. At the ESXCLI, enter maintenance mode. From the ESXi host console, use SSH to run the following
command:
esxcli system maintenanceMode set -e=true
NOTE: For VSAN environments, this command requires an additional switch (refer to the
vSphere documentation for the vSphere version that you are using).
If you are upgrading from an ESX version prior to 7.0, remove the VM Storage Policy of any vRPA
VM, if it resides on the ESX host, by completing the following steps before putting ESX into
maintenance mode: a.Select the vRPA VM in vSphere, and click Edit > VM Storage Policies.
b. Write down and save the names of the VM Storage Policies applied to each VMDK. Some VMDKs
will have a RecoverPoint_JCD policy and some will have a Datastore Default policy.
c. Set all VM Storage Policies to Datastore Default.
After the upgrade of the ESX host completes, change the storage policy of the vRPA VM back to its
original configuration.
2. (Optional) If DRS is in automatic mode, vMotion is carried out automatically. If not, you must manually
use vMotion to move all VMs to a different ESXi host in the ESX cluster.
3. If you are upgrading from an ESX version prior to 7.0, Uninstall the RecoverPoint for VMs splitters and
Uninstall JAM.
Page 53 of 55
4. Follow the VMware instructions for ESXi upgrade.
Upgrading https://docs.vmware.com/en/VMware-vSphere/6.7/vsphere-esxi-67-upgrade-guide.pdf
to 6.7
Upgrading https://kb.vmware.com/s/article/78205
to 7.0
5. Exit maintenance mode. From the ESXi host console, use SSH to run the following command:
esxcli system maintenanceMode set -e=false
The ESXi is updated with a new splitter and JAM VIBs.
6. (Optional) If DRS is not in automatic mode, use vMotion to manually move VMs to the upgraded ESXi
host.
Results
The ESXi is upgraded.
Next steps
1. Repeat this procedure on every ESXi that has secure boot disabled and belongs to an ESX cluster
hosting vRPAs.
2. Enable secure boot on every ESXi host in every ESX cluster hosting vRPAs.
vSphere upgrades
D
Installing on Nutanix
There are no special instructions for installing RecoverPoint for VMs on Nutanix.
Topics:
• Installing RecoverPoint for VMs on Nutanix
Page 54 of 55
Prerequisites
RecoverPoint for VMs is supported by Nutanix AOS 4.7.5 or 5.0.2, or later. If necessary, upgrade your
Nutanix installation to one of those versions.
NOTE: You do not need to modify the Nutanix settings when installing RecoverPoint for VMs.
Installing on Nutanix
Page 55 of 55