RecoverPoint for VMs: During ESXi upgrades vRPAs cannot vMotion to upgraded ESXi hosts

In some scenarios during ESXi upgrades or during Splitter/Jiraf upgrades on ESXi hosts, the vRPAs cannot be vMotioned between ESXi hosts due to differences in Jiraf IOFilters on the hosts.

How to solve a vRPA cannot vMotion to upgraded ESXi hosts during ESXi upgrades.

The following errors are shown: „The virtual machine is not compatible with the version of the host.” and „The version of the IO filter configured on the VMs disk are not compatible with the one installed on the destination host.”

This may impact automated ESXi upgrade mechanisms, such as VxRail upgrades. This can be caused if the RecoverPoint for VMs Jiraf module has different versions of code.

In some scenarios the storage profile changes between them. vMotion sees a difference and identifies it as a compatibility issue, preventing the use of the profile. While applying the workaround, please make sure „Configure per disk“ is enabled in the „Edit VM storage policies“ window on the upper right.

On the vRPA VMs, right click and navigate to „VM policies“ and select „Edit VM storage policies“. Note down the selected storage policies to change them back later. Change the policies on all disk to „Datastore default“ or „VSAN default“ for VSAN configurations.

Then click Ok. This should allow the vRPA VM to move between ESXi Hosts running different versions of the Jiraf IO filter, vMotion the vRPA and continue upgrades of ESXi or Jiraf codes.

Once the ESXi Clusters have all completed the upgrades, the storage policies can be reset as noted above, back to the same name or hash. If possible, please only use secure boot after running ESXi 7.0.x with RecoverPoint for VMs.

Thank you for watching.