Unable to reconfigure the recovered virtual machine

Products

• VMware Live Recovery

Issue/Introduction

This resource provides a guide to identify symptoms and align them with solutions to resolve the failure of recovering a virtual machine via vSphere Replication

Symptoms:

• When you try to recover a VM, whose virtual machine configuration (VMX) file contains ethernet key entries that start with both lower and upper case, the recovery fails with the following error: 

2021-12-15 16:18:07.799 ERROR hms.recovery [hms-incoming-eventhandler-thread-3384] (..hms.recovery.RecoverJob) [operationID=########-####-####-####-########f9a2-HMS-16284] | Failed to reconfigure recovered VM: java.lang.NullPointerException
java.lang.NullPointerException: null

 

• VMX file for the recovered VM would have ethernet entries similar to below with both upper and lower cases:

ethernet1.addressType = "vpx"
ethernet1.generatedAddress = "##:##:##:##:##:e8"
ethernet1.pciSlotNumber = "256"
ethernet1.present = "TRUE"
ethernet1.shares = "normal"
ethernet1.uptCompatibility = "TRUE"
ethernet1.virtualDev = "vmxnet3"
Ethernet1.opaqueNetwork.id = "########-####-####-####-########4130"
Ethernet1.opaqueNetwork.type = "nsx.LogicalSwitch"
Ethernet1.externalId = "########-####-####-####-########96f4:4001" 

 

• HBR logs will have duplicate entries for the same ethernet card as below:

2022-05-21T21:26:39.042Z verbose hbrsrv[01085] [Originator@6876 sub=Image opID=########-####-####-####-########93d6-HMS-5216:hs-88d0:hs-c694] Flush: Adding key 'Ethernet0.startConnected' for vmx file 'hbrcfg.GID-########-####-####-####-########0ac0.415683.vmx.10898'.
2022-05-21T21:26:39.042Z verbose hbrsrv[01085] [Originator@6876 sub=Image opID=########-####-####-####-########93d6-HMS-5216:hs-88d0:hs-c694] Flush: Adding key 'ethernet0.startConnected' for vmx file 'hbrcfg.GID-########-####-####-####-########0ac0.415683.vmx.10898'

Environment

VMware Site Recovery Manager 8.x

Cause

HBR does not support same ethernet card with upper and lower case entries in the VMX file

Resolution

This issue is resolved in vSphere Replication 8.5.0.4.

Workaround:

There is no workaround for this issue. We recommend upgrading to vSphere Replication 8.5.0.4.

Additional Information

Please refer the release notes of 8.5.0.4:

https://docs.vmware.com/en/vSphere-Replication/8.5/rn/vsphere-replication-8504-release-notes.html#2975587

Impact/Risks:

The issue effects vSphere Replication 8.5.x