printer Print

Customer View

RP4VM: Consistency Groups in Error state when nested ESX hosts are present

Article Number: 540847
Version: 3
Article Type: Break Fix
Last Published: 21 Apr 2020
Summary: Consistency Groups in Error state when nested ESX hosts are present

VCUpdater is failing with Null pointer exception, which is causing all CGs to go into error state.

In connector logs:
2020-01-20 14:13:45,267 [pool-6-thread-1] ( INFO - ESX has null hostKernelModuleSystem: <HOST IP>. Assuming there is no vSCSI splitter...
2020-01-20 14:13:45,278 [pool-6-thread-1] ( WARN - Caught exception when looking for ESX advanced property: no value found for UserVars.RP_SPLITTER_GENERATED_UUID
2020-01-20 14:13:45,286 [pool-6-thread-1] ( ERROR - Exception caught
at ~[vi_connector_commons.jar:?]
at ~[vi_connector_commons.jar:?]
at ~[vi_connector_commons.jar:?]
at ~[vi_connector_commons.jar:?]
at ~[vi_connector_commons.jar:?]
at ~[vi_connector_commons.jar:?]
at ~[vi_connector_commons.jar:?]
at ~[vi_connector_commons.jar:?]

Connection with VC will fail and all CGs will go into error state.
Issue occurs if the customer is using virtual ESX hosts with no kernel modules.
When RP tries to get the ESX host kernel module system, it returns null. VMware then tries to query the module to get the kernel module info on a null value, hence it throws the null pointer exception there.

Remove Nested ESX from the ESX cluster replicated within RP4VM.

Upgrading to version 5.2.x and later will prevent CGs in a mixed environment going into Error.

No fix is available as the problem is caused by an unsupported environment.
Nested ESX hosts are not supported by VMware or RP4VM.

See for more information.

Article Properties
First Published Fri Jan 31 2020
08:53:37 GMT
Primary Product
RecoverPoint for Virtual Machines
RecoverPoint for Virtual Machines 5.1,RecoverPoint for Virtual Machines