Below are the steps to change the repair delay time in VMware vSAN (formerly known as Virtual SAN). This is the amount of time vSAN waits after a failure is detected on an ESXi host that is part of vSAN cluster, before repairing a disk component.

This VMware vSAN advanced setting specifies the amount of time vSAN waits before rebuilding a disk object after a host is either in a failed state or in Maintenance Mode. By default, the repair delay value is set to 60 minutes; this means that in the event of a host failure, vSAN waits 60 minutes before rebuilding any disk objects located on that particular host. This is because vSAN is not certain if the failure is transient or permanent.

Note: If a failure in a physical hardware component is detected, such as an Solid State Disk (SSD) or Magnetic Disk (MD), vSAN immediately responds by rebuilding a disk object.

To change the default repair delay time, modify the ESXi advanced option vsan.clomrepairdelay.

Note: The default 60 minutes is designed to cover a multitude of different configurations, setting the above option too aggressively can cause unnecessary resync operations to occur, when changing this advanced option consider these factors:

  • Installation of ESXi updates (if performing updates)
  • ESXi host boot time (Including Power On Self Test)
  • SSD Log recovery for vSAN

Note: Maximum value you can set in minutes for clom repair delay is 4294967295.

Solution:

The option to change the “Clom Repair” value, from vCenter. So if  vCenter is available, we can navigate to Cluster object > Configure > vSAN > Services > Advanced Options:

Change Object Repair Timer Option to the desired value:

Note: You must wait for at least 180 seconds before proceeding with any Maintenance/Disk Group/Disk/reboot related activity after making above changes through UI