We have just released RP4VMs 5.2 Patch 2, here’s what’s new, if you want to have a full overview of the previous 5.2 initial release, you can read about it here https://volumes.blog/2018/07/11/recoverpoint-for-virtual-machines-rp4vms-5-2-is-here-heres-whats-new/
During installation, the user is required to replace the default admin user password with a new unique password. This password serves also as the password for the root user across all vRPAs in the system.
In new installs, the predefined admin user has all permissions. All other predefined users have been eliminated.
ln RecoverPoint for VMS 18.104.22.168, to further enhance security, the run internal command option in the boxmgmt CLI menu is removed.
For upgraded systems, the role of the admin user is extended to include all permissions. Upgrade has no impact on other users.
Root access is disabled by default for local, as well as remote, access. Access can be enabled by admin user (or subsequently disabled) from the Boxmgmt CLI.
In new installations of RecoverPoint for VMs 22.214.171.124, and later, there is no predefined boxmgmt user. Use the admin user to launch the Boxmgmt CLI.
RecoverPoint for VMs 126.96.36.199 includes a new predefined role, ‘sysmgmt’. A user defined with this role logs in directly to the Sysmgmt CLI, and has the same permissions as the admin user, with the exception of the Web Download and SE permissions.
Support for VMware vSphere 6.7
RecoverPoint for VMs 188.8.131.52 introduces support for VMware vSphere 6.7. (including vSphere 6.7 U1)
When protecting VMs or adding a copy, ESX hosts of the production and copy VMs are now automatically registered in RecoverPoint for VMs.
Up to 15 shared datastores for journals are now automatically registered in RecoverPoint for VMs.
When using vCenter linked mode, it is no longer necessary to register all of the linked vCenter Servers, and only the vCenter Server(s) managing the protected VMs, copy
VMs and vRPAs must be registered with RecoverPoint for VMs.
Production Journal Reduction
The default production journal size has been changed to 3GB.
Auto VMkernel port creation
The user can now configure the VMKernel ports from the RecoverPoint for VMs plugin UI, and they will be automatically created for all the ESXi hosts in the ESXi cluster.
In addition to VM-based licensing, the RecoverPoint for VMs licensing model now includes socket-based licensing. With socket-based licensing, the number of licenses is determined by the number of physical CPU sockets in the ESXi servers that host the production VMs. When users add socket-based and VM-based licenses to the same system, the VM-based license capacity automatically converts to socket-based licenses at a ratio of 15 VMs per socket.
Both VM and socket-based licenses may now be installed as subscriptions. A subscription license has a start and end date. Subscription and permanent licenses may co-exist in the same system.
Refer to the RecoverPoint for Virtual Machines Administrator’s Guide for more details.
Journal Access Module (JAM)
For fresh installs of RecoverPoint for VMs 5.2, JAM provides enhanced vSAN support, and improved scale and reliability for access to journal and repository volumes. It is installed automatically on ESXi clusters that run vRPAs.
One splitter communication mode
Starting from this release, only IP communication between the splitter and vRPAs will be supported. iSCSI communication between the splitter and vRPAs is no longer supported. While this simplifies network configuration and new installations, there are special instructions that must be followed when upgrading to version 5.2. For these instructions, see the Install and upgrade section in these release notes.
The default I/O throttling setting varies according to the RecoverPoint for VMs product release. RecoverPoint for VMs 5.2 Release Notes
RecoverPoint for VMs release
Default I/O throttling setting
184.108.40.206 and earlier
220.127.116.11 and later
For more details on this change, see RP-8875 in Known issues in RecoverPoint for VMs on page 7 and the RecoverPoint for VMs Installation and Deployment Guide.
You can download the 5.2 P2 installation by clicking the screenshot below