{"id":46341,"date":"2020-10-13T09:00:07","date_gmt":"2020-10-13T07:00:07","guid":{"rendered":"https:\/\/nolabnoparty.com\/?p=46341"},"modified":"2021-01-24T16:57:13","modified_gmt":"2021-01-24T15:57:13","slug":"recoverpoint-for-vms-upgrade-to-v5-3-with-html-plugin","status":"publish","type":"post","link":"https:\/\/nolabnoparty.com\/en\/recoverpoint-for-vms-upgrade-to-v5-3-with-html-plugin\/","title":{"rendered":"RecoverPoint for VMs: upgrade to v5.3 with HTML plugin"},"content":{"rendered":"

\"recoverpoint-5-3-upgrade-with-html-plugin-support-01\"<\/p>\n

After a long wait, Dell released the new RecoverPoint<\/a> 5.3 providing the HTML plugin<\/strong> and the support for VMware vSphere 7.0<\/a>.<\/p>\n

To take benefit of the new HTML plugin<\/strong>, the target vSphere version must be 6.7 U1 or above<\/strong>. For lower versions, the flex plugin<\/strong> remains the administrative console in vCenter instead.<\/p>\n

 <\/p>\n

Upgrade the vRPA cluster<\/h2>\n

The upgrade procedure requires a specific order of the RecoverPoint components to process to avoid service disruption.\u00a0If you have at least two vRPAs per vRPA cluster<\/strong>, the upgrade is not disruptive for replication jobs and can be easily completed. Check out this guide<\/a>\u00a0to upgrade the vRPA cluster.<\/p>\n

Both source <\/strong>and DR vRPA clusters<\/strong> must be upgraded to take benefit of new features<\/a>. Download from Dell website the lastest version of RecoverPoint for VM<\/a>.<\/p>\n

 <\/p>\n

Source and DR vRPA clusters<\/h4>\n

The source vRPA cluster upgraded to version 5.3.<\/p>\n

\"\"<\/p>\n

Also the DR vRPA cluster has been upgraded to version 5.3.<\/p>\n

\"\"<\/p>\n

 <\/p>\n

Upgrade Splitters and JAMs automatically<\/h2>\n

Since the procedure to upgrade splitters and JAMs for the entire ESX cluster requires to put the host in maintenance mode<\/strong>, you must have at least two hosts ESXi<\/strong> to maintain uninterrupted replication.<\/p>\n

Before proceding make sure the DRS feature is enabled and set as Automatic<\/strong> in the vSphere cluster.<\/p>\n

SSH one vRPA<\/strong> in the cluster and enter the admin credentials to login. In the Main Menu<\/strong> options, access the Setup<\/strong> section by typing 2<\/strong>. Press\u00a0Enter<\/strong>.<\/p>\n

\"\"<\/p>\n

Select Advanced options<\/strong> option. Type 8<\/strong> then press Enter<\/strong>.<\/p>\n

\"\"<\/p>\n

Select Splitter actions<\/strong> option. Type 12<\/strong> then press Enter<\/strong>.<\/p>\n

\"\"<\/p>\n

Select Upgrade Splitter<\/strong> option. Type 1<\/strong> then press Enter<\/strong>.<\/p>\n

\"\"<\/p>\n

Enter the required parameters:<\/p>\n

    \n
  • vCenter Server IP addres<\/li>\n
  • TCP port number<\/li>\n
  • Username<\/li>\n
  • Password<\/li>\n<\/ul>\n

    Type y<\/strong> then Enter<\/strong> to retrieve the certificate.<\/p>\n

    \"\"<\/p>\n

    Type y<\/strong> to approve the certificate. Specify the ESX cluster to upgrade<\/strong> (1 in the example).<\/p>\n

    \"\"<\/p>\n

    Type y<\/strong> to begin the upgrade process. Each ESXi host enters in Maintenance Mode and splitter and JAM VIBs are upgraded<\/strong> accordingly.<\/p>\n

    \"\"<\/p>\n

    VMs are moved out<\/strong> from the processed ESXi host.<\/p>\n

    \"\"<\/p>\n

    The host is then placed in Maintenance Mode<\/strong>.<\/p>\n

    \"\"<\/p>\n

    When the upgrade process has been completed, type q<\/strong> to quit.<\/p>\n

    \"\"<\/p>\n

    Splitters and JAMs are now upgraded to version 5.3.<\/p>\n

     <\/p>\n

    Manually upgrade a single ESXi host<\/h2>\n

    If your vRPA cluster contains only one vRPA, you need to perform a manually upgrade procedure. In this scenario you must pause all replications<\/strong> before starting the upgrade and power off running VMs.<\/p>\n

    Put the host to upgrade in Maintenance Mode and access the host console via SSH<\/strong>.<\/p>\n

    \"\"<\/p>\n

    Check the installed version<\/strong> with the following commands:<\/p>\n

    # esxcli software vib list | grep rp<\/span>
    \n# esxcli software vib list | grep emc<\/span><\/p>\n

    \"\"<\/p>\n

     <\/p>\n

    Upgrade the splitter<\/h4>\n

    Using a tool like WinSCP, copy the kdriver_RPESX-00.rel5.3_m.448.vib<\/em> file to the ESXi host to upgrade.<\/p>\n

    Remove the old version of the splitter and install the new one with the following commands:<\/p>\n

    # esxcli software vib remove -n RP-Splitter<\/span>
    \n# esxcli software vib install -v \/tmp\/kdriver_RPESX-00.rel5.3_m.448.vib --no-sig-check<\/span><\/p>\n

    \"\"<\/p>\n

     <\/p>\n

    Upgrade JAMs<\/h4>\n

    Copy the EMC_bootbank_emcjiraf_5300.m.448-1OEM.600.1.17.3657938.vib<\/em> file to the host then remove the old version and install the new one. You may need to reboot the host<\/strong> if you can't remove the old JAMs.<\/p>\n

    # esxcli software vib remove -n emcjiraf<\/span>
    \n# esxcli software vib install -v \/tmp\/EMC_bootbank_emcjiraf_5300.m.448-1OEM.600.1.17.3657938.vib --no-sig-check<\/span><\/p>\n

    \"\"<\/p>\n

     <\/p>\n

    Upgrade the flex plugin<\/h2>\n

    If the installed vSphere version is below 6.7 U1<\/strong>, the flex plugin is the only option you have to manage RecoverPoint from the vCenter.<\/p>\n

    In vSphere Client, access the dashboard from Menu > RecoverPoint for VM<\/strong>. Click Help<\/strong> and select Upgrade RecoverPoint for VM<\/strong>.<\/p>\n

    \"\"<\/p>\n

    Select 5.3.0.0<\/strong> as version to upgrade to.<\/p>\n

    \"\"<\/p>\n

    Click OK<\/strong>.<\/p>\n

    \"\"<\/p>\n

    Logout<\/strong> and login again to enable in vCenter the new version 5.3 of the flex plugin.<\/p>\n

    \"\"<\/p>\n

    Checking the RecoverPoint for VMs cluster management, the plugin has been upgraded successfully.<\/p>\n

    \"\"<\/p>\n

     <\/p>\n

    Install the HTML appliance<\/h2>\n

    To enable the HTML plugin in vCenter, you need to install the new appliance that manage this service.<\/p>\n

    Run the Deploy OVF template<\/strong> wizard from vSphere Client. Click Browse<\/strong> and select the .OVA file to use and click Next<\/strong>.<\/p>\n

    \"\"<\/p>\n

    Specify the Virtual machine name<\/strong> and a location then click Next<\/strong>.<\/p>\n

    \"\"<\/p>\n

    Select the compute resource to run the appliance and click Next<\/strong>.<\/p>\n

    \"\"<\/p>\n

    Click Next<\/strong>.<\/p>\n

    \"\"<\/p>\n

    Select the datastore to use and click Next<\/strong>.<\/p>\n

    \"\"<\/p>\n

    Specify the correct Destination Network<\/strong> (it should be the VMs traffic network) and click Next<\/strong>.<\/p>\n

    \"\"<\/p>\n

    Enter the network parameters and click Next<\/strong>.<\/p>\n

    \"\"<\/p>\n

    Click Finish<\/strong> to proceed with the installation.<\/p>\n

    \"\"<\/p>\n

    When the installation has been completed, right click the appliance and select Power > Power On<\/strong>.<\/p>\n

    \"\"<\/p>\n

     <\/p>\n

    Configure the HTML plugin<\/h2>\n

    Access the RecoverPoint for VMs cluster management and click on the Configure plugin server<\/strong>\u00a0link.<\/p>\n

    \"\"<\/p>\n

    Enter the IP<\/strong> address for the plugin server and click Validate certificate<\/strong>.<\/p>\n

    \"\"<\/p>\n

    Click Confirm<\/strong> to approve the certificate.<\/p>\n

    \"\"<\/p>\n

    The certificate has been approved. Click Configure<\/strong>.<\/p>\n

    \"\"<\/p>\n

    After few seconds the plugin configuration completes. Click Finish<\/strong>.<\/p>\n

    \"\"<\/p>\n

    The Plugin Server<\/strong> has been configured in the vRPA cluster.<\/p>\n

    \"\"<\/p>\n

    To enable the new plugin it is recommended to Logout<\/strong> from the HTML vSphere Client, and then to log in again.<\/p>\n

    \"\"<\/p>\n

    When you login again, refresh the browser to activate the plugin.<\/p>\n

    \"\"<\/p>\n

    From the HTML vSphere Client, navigate Menu > RecoverPoint for VMs<\/strong>\u00a0to access the the HTML ReoverPoint area.<\/p>\n

    \"\"<\/p>\n

    The HTML RecoverPoint plugin.<\/p>\n

    \"\"<\/p>\n

    vRPAs clusters are discovered by the plugin server and registered to the vCenter Server. As a result, the plugin server knows how to direct API calls<\/strong> to the correct vRPA cluster.<\/p>\n

    \"signature\"<\/p>\n","protected":false},"excerpt":{"rendered":"

    After a long wait, Dell released the new RecoverPoint 5.3 providing the HTML plugin and the support for VMware vSphere 7.0. To take benefit of the new HTML plugin, the target vSphere version must be 6.7 U1 or above. For lower versions, the flex plugin remains the administrative console in vCenter instead.<\/p>\n","protected":false},"author":3,"featured_media":46342,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"rop_custom_images_group":[],"rop_custom_messages_group":[],"rop_publish_now":"initial","rop_publish_now_accounts":{"linkedin_93tdZWzMZc_93tdZWzMZc":"","facebook_2879994398731222_17841400390232720":"","twitter_113568041_113568041":"","mastodon_115463926174894442_115463926174894442":""},"rop_publish_now_history":[],"rop_publish_now_status":"pending","footnotes":""},"categories":[2138,2139],"tags":[2257,703,2114],"class_list":["post-46341","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-backup-en","category-recoverpoint-en","tag-html","tag-plugin-en","tag-recoverpoint","has_thumb"],"_links":{"self":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/posts\/46341","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/comments?post=46341"}],"version-history":[{"count":0,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/posts\/46341\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/media\/46342"}],"wp:attachment":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/media?parent=46341"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/categories?post=46341"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/tags?post=46341"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}