Running Test Recovery fails with Error - "No hosts with hardware version '19' and datastore(s) which are powered on and not in maintenance mode are available."

Products

• VMware Live Recovery

Issue/Introduction

Symptoms:

• Test Recovery plans fails with - "No hosts with hardware version '19' and datastore(s) which are powered on and not in maintenance mode are available."

  
  
  Note: The Advanced Setting parameter for autoResignatureMode is enabled (Status = 1), Path : SRM UI->Summary -> Advanced Parameter -> storage Provider -> autoResignatureMode.

• /opt/vmware/support/logs/srm/vmware-dr.log on SRM at recovered site reports:
  
  

  ####-##-##THH:MM:SS.#### verbose vmware-dr[#######] [SRM@#### sub=DrTask ctxID=######## opID=########-####-####-####-############-getDetailedRecoveryResult] [#####] Task 'dr.recovery.RecoveryHistoryManager.getDetailedRecoveryResult525' completed with result: (dr.recovery.RecoveryHistoryManager.DetailedRecoveryResult) {

  <---------- Truncated output ---------->

-->       "                  <msg>No hosts with hardware version &apos;11&apos; and datastore(s) &apos;&quot;<Datastore-name>&quot;&apos; which are powered on and not in maintenance mode are available.</msg>",
-->       "    </e>",
-->       "  </faults>",
-->       "          <msg>No hosts with hardware version &apos;21&apos; and datastore(s) &apos;&quot;<Datastore-name>&quot;&apos; which are powered on and not in maintenance mode are available. 

Environment

• VMware Live Recovery 9.0.2

• Dell EMC SRDF

• SRA version 10.1.0.0

Cause

The issue originated from the "autoResignatureMode" parameter, which mandates all ESXi hosts to resignature for new VMFS volumes. including those ESXi hosts outside of VMware Live Site Recovery management. Consequently, disrupting existing VM-Host affinity rules.

•  Enabling the storage.autoResignatureMode advanced parameter during a Test Recovery triggers an automatic volume resignaturing process. This process updates the VMFS UUID of the affected datastores. Because VM-Host affinity rules (DRS rules) rely on consistent object identifiers, the change in the volume's signature causes these rules to become invalid or disconnected.

• This impact extends to all ESXi hosts that have visibility into the storage LUNs, including those not managed by the VMware Live Site Recovery (VLSR) recovery plan, leading to log entries indicating affinity rule disruption.

• From the logs /opt/vmware/support/logs/srm/vmware-dr.log, the ESXi host (which is not a member of the active Recovery Plan) reported error regarding VM-Host affinity rules. This occurred because following datastores were resignatured during a Test Recovery operation.

msg = "No hosts with hardware version '19' and datastore(s) '"#########################", "S#########################", "#########################", "#########################", "#########################", "#########################", "#########################",
"#########################", "#########################", "#########################", "#########################", "#########################", "#########################", "#########################", "#########################", "#########################
", "#########################", "#########################", "#########################"' which are powered on and not in maintenance mode are available."
-->          },
-->          (vim.fault.NoCompatibleHost) {
-->             faultCause = (vmodl.MethodFault) null,
-->             faultMessage = <unset>,
-->             host = (vim.HostSystem) [
-->                'vim.HostSystem:########-####-####-####-############:host-11136'
-->             ],
-->             error = (vmodl.MethodFault) [
-->                (vim.fault.VmHostAffinityRuleViolation) {
-->                   faultCause = (vmodl.MethodFault) null,
-->                   faultMessage = <unset>,
-->                   vmName = "##########",
-->                   hostName = "#########.###.####.###"
-->                   msg = "Virtual machine '##########' on host '#########.###.####.###' would violate a virtual machine - host affinity rule."
-->                }
-->             ]
-->             msg = "No host is compatible with the virtual machine."

Resolution

Run below steps:

1. The Advanced Setting parameter "autoResignatureMode" in SRM to be disabled, SRM UI->Summary -> Advanced Parameter -> storage Provider -> autoResignatureMode (Disable =0).
2. The Parameter is recommended to be changed on both the protected and recovery SRM servers to maintain configuration consistency between the two environments.
3. Re-run the Test Recovery Plan.

Additional Information

For reference, Configuring advanced VMware SRM options