Welcome to Dell Technologies RecoverPoint for Virtual Machines 5.3
"How-to" series
Prerequisites for a successful RecoverPoint for Virtual Machines upgrade.
Reference Dell Knowledge Article # 19482
This video was created to
Perform a successful upgrade of RP4VM
Successful upgrade of RP4VM will prevent a series of unwanted conditions
like DRU (Data replication unavailable)
delay on NDU (non-disruptive upgrade) completion
or more serious issues as necessity to re-install the whole environment
This video presents the following
Conditions to be met before performing an upgrade.
Principal known issues that can be encountered during an upgrade
and workaround to prevent it.
Correct sequence of steps to be performed during the upgrade.
When to do this
Before performing the RP4VM upgrade
always refer to this KB to perform all necessary pre-check
and preemptive workaround for known issues.
Before you begin
Have virtual center administrator credentials
Have vRPA admin/root credentials
Have ESXi root credentials
Have HTTPS ssh connectivity to the vRPA
Have HTTPS connectivity to vCenter
Have SSH connectivity to the ESXi in the cluster which is hosting the vRPAs.
Pre-check and preemptive workarounds.
Demonstration
Verify vCenter and ESXi versions.
Log in to vCenter with administrator credentials.
Ensure vCenter version is 6.5 or later, or 6.7 U1.
Click on the question mark on the top right corner
and select About VMware vSphere.
Confirm the vSphere client version later than 6.5 or 6.7 U1.
Ensure ESXi are at minimum version of 6.5.
Select Host and Clusters from vSphere left panel.
Then select the cluster with the ESXi host you need to check.
From each host, select Summary and review their Hypervisor version.
Demonstration
Ensure that the security level of the RecoverPoint cluster
is set to “Not authenticated nor encrypted” or “Authenticated and encrypted”.
Log in as admin on RPA CLI.
Select option [2] Setup.
Then option [8] Advanced options.
[2] Security options.
[6] Change appliance communication security level.
If the default level is not "Authenticated and encrypted”
or “Not Authenticated and encrypted”
proceed changing it to one of those two levels
and repeat for all other clusters connected.
Demonstration
Ensure that Site Control RPA is RPA 1
If you are upgrading to version 5.3.1 or later
this preemptive workaround can be skipped.
Log in as admin on RPA 1 CLI.
Select option [3] Diagnostics.
Then option [1] IP diagnostics.
And option [2] view IP details.
Confirm if the interface ETH column 1 is assigned to RPA 1 or not.
If not, reboot RPA 2 to have the site control moved to RPA 1.
Demonstration
Verify the presence of an old data structure present
in replicated Virtual Machine.
If you are upgrading to version 5.3.1 or later
this preemptive workaround can be skipped.
Log in as admin on RPA CLI.
Select option [2] Setup.
Then select option [8] Advanced options, and option [4] Run script.
Copy and paste the assigned script from KB180298.
Confirm with Enter, and add your name when requested.
If the script outputs any VM names
unprotect the VMs and re-protect them.
Demonstration
Ensure that RecoverPoint has an updated vCenter certificate.
Log in as admin on RPA CLI.
Select option [6] System management CLI.
Execute the command.
Update vCenter server registration.
And provide all information regarding RPA cluster vCenter address
and credential as requested.
Reference the following for more information.
KB Article # 173920, 182337
173921, 173584
180298 and 180423.
Thank you for watching.