HDM Reset

CAUTION: Use this functionality with caution, as this can lead to HDM configuration data loss. This should only be used when the system has entered an unrecoverable state.

HDM Reset is used to recover from situations when HDM enters into an unrecoverable state. It removes all cloud and on-premises component states, and is equivalent to a factory reset. HDM Reset is usually followed by re-deployment of HDM.

What HDM Reset Won’t Do

HDM reset is not about removing all states. It only removes the states that are required to bring the system back to a point where HDM can be reinstalled.

  1. It will not remove storage policies.
  2. The VAIO component will not be removed from EXSi.
  3. It will not uninstall or unregister the vCenter plug-in.

When to Perform HDM Reset

The few cases where HDM Reset may be required are:

  • Multiple HDM components are simultaneously failing. HDM tries to recover from multiple component failures. However, this will likely require an HDM reset.
  • Prolonged WAN outages. HDM can handle transient network failures, but long outages (greater than 5 minutes) may render it incapable of recovering.
  • Component recovery failure for an extended period of time. HDM will attempt to recover the failed components a few times. But if the failure condition does not disappear, the component recovery may continue to fail indefinitely. This may be the case if the Control Panel in the HDM appliance shows the components in the degraded state for more than 15 minutes.
  • Reset Required message received. If HDM logs the following message in the on-premises vCenter: “Fatal Unrecoverable failure detected in HDM component: <component_name> Please reset the HDM system and retry migration operations for the VMs in <vm_name> and <pool_name> resource pools”

HDM Reset Steps

Pre-requisites

  1. HDM appliance must be powered on.

Steps

Note : Ignore step 5 and 6 in case of Ultra Lite deployment.

  1. To access the HDM dashboard, select HDM from Shortcuts or from the Menu in the on-premises vCenter.
  2. Select the Administration tab, then HDM Health and HDM Reset (Figure 43). If the HDM Reset button is not enabled, then reboot the HDM appliance and try again.
  3. Select the HDM RESET button to trigger the reset.
  4. You can view the task in the on-premises vCenter (Figure 44).
  5. SPBM should be removed or VMs with SPBM should be powered off.
  6. Restart the praapa IOFilter service from all ESXis under on-premise cluster.
  7. Restart the HDM appliance from vCenter and wait for the restart to complete.

Figure 43: vCenter HDM Reset Tab

alt_text

Figure 44: Reset Task in the On-Premises vCenter

alt_text

  1. On restart, you should see that the earlier queued task for HDM reset in vCenter can now proceed.
  2. Once the reset is complete, the vCenter task is updated (figure 45).

Figure 45: Updated Task in On-Premises vCenter

alt_text

  1. The VMs will be migrated back and will remain in ‘_HDM_MIGRATEPOOL’.
  2. Be sure to monitor the state of the HDM components in the Control Panel of the HDM appliance to ensure that the on-premises load balancer, database, HA manager, and PrimaryIO manager are running. This will indicate the successful completion of the HDM reset.

VM Recovery Following HDM Reset

To recover VMs following an HDM reset, the following steps should be performed:

  1. Power on the VM and verify the sanity of the data
  2. If the power-on and data sanity checks pass:
    1. Delete the HDM migrate time snapshot
    2. Move the VM to its pre-migration resource pool
  3. If the power-on or the data sanity fail:
    1. Restore the data from the migrate time snapshot
    2. Delete the HDM migrate time snapshot
    3. Move the VM to its pre-migration resource pool
    4. Power on the VM

Redeployment Following an HDM Reset

As mentioned in earlier sections, a typical HDM deployment consists of the following steps:

  1. Deploy the HDM appliance
  2. Register the HDM plug-in
  3. Deploy HDM on-premises
  4. Deploy HDM in the cloud

HDM reset would undo the steps 3 and 4, above, so these have to be executed again:

  1. Deploy HDM on-premises
  2. Deploy HDM on the cloud