Planned Migration of a recovery plan fails with "A general runtime error occurred"

Products

• VMware Live Recovery

Issue/Introduction

Symptoms:

• Planned Migration of a Recovery Plan fails with error:
  "A general runtime error occurred"


• Recovery Plan workflow step 'Change recovery site storage to writable' shows error in Recovery Plan History Report:
  
  
  
  

Validation:

• /var/log/vmware/vmware-dr.log in the Target/Recovery SRM server reports following error:
  
  -->       "</fault>",
-->       "          <Children>",
-->       "            <Step elapsedTime="00:00:00" endTime="2025-02-17T04:59:00Z" objectId="protected-vm-20334681" startTime="2025-02-17T04:59:00Z" status="error">",
-->       "              <Key>RecoveryStepConfigStorageOp.name</Key>",
-->       "              <Name>Configure storage</Name>",
-->       "              <fault>",
-->       "                  <_type>vmodl.RuntimeFault</_type>",
-->       "                  <faultMessage>",
-->       "                      <_length>1</_length>",
-->       "                      <_type>vmodl.LocalizableMessage[]</_type>",
-->       "                      <e id="0">",
-->       "                          <_type>vmodl.LocalizableMessage</_type>",
-->       "                          <arg>",
-->       "                              <_length>3</_length>",
-->       "                              <_type>vmodl.KeyAnyValue[]</_type>",
-->       "                              <e id="0">",
-->       "                                  <_type>vmodl.KeyAnyValue</_type>",
-->       "                                  <key>keyProviderId</key>",
-->       "                                  <value>",
-->       "                                      <_type>string</_type>",
-->       "                                      <_value>TKP01</_value>",
-->       "          </value>",
-->       "        </e>",
-->       "                              <e id="1">",
-->       "                                  <_type>vmodl.KeyAnyValue</_type>",
-->       "                                  <key>host</key>",
-->       "                                  <value>",
-->       "                                      <_type>string</_type>",
-->       "                                      <_value>esx01.xxxxxx.com</_value>",
-->       "          </value>",
-->       "        </e>",
-->       "                              <e id="2">",
-->       "                                  <_type>vmodl.KeyAnyValue</_type>",
-->       "                                  <key>reason</key>",
-->       "                                  <value>",
-->       "                                      <_type>string</_type>",
-->       "                                      <_value>vim.vpxd.encryption.TpmRequired</_value>",
-->       "          </value>",
-->       "        </e>",
-->       "      </arg>",
-->       "                          <key>com.vmware.vim.vpxd.encryption.kmsNotCompatibleWithHost</key>",
-->       "                          <message>Key provider TKP01 is not compatible with the host esx01.xxxxxx.com. Reason: TPM2 device is required.</message>",
-->       "    </e>",
-->       "  </faultMessage>",
-->       "                  <msg>A general runtime error occurred. </msg>",
-->       "</fault>",
  
  

Environment

Site Recovery Manager 8.x

VMware Live Site Recovery 9.x

Cause

Recovery fails as the configuration selected for the Trusted Key Provider and that of ESXi host are not compatible.

Trusted Key Provider is been configured in vCenter with setting of using 'key provider only with TPM protected ESXi hosts' as seen below:



On the other hand, the target ESXi host/s either does not support TPM or its not enabled in BIOS.

Resolution

1. Enable TPM 2.0 in BIOS of the Target site ESXi host servers.

2. If step-1 is not feasible, remove and re-add the Native Key Provider at primary and secondary site such that they have the same Provider IDs but also ensure the option "Use key provider only with TPM protected ESXi hosts" while adding the Native Key Provider is unchecked.

Additional Information

For more details on Configuring Native Key Provider in vCenter, refer Configure a vSphere Native Key Provider