OS did not boot in the allotted time
This error occurs when the VM being Power On by the SureBackup job fails to become stable within the "Maximum allowed boot time" specified in the Application Group settings or the Linked Jobs section.
The SureBackup job determines stabilization using different Stabilization Algorithms. These algorithms are hypervisors specific: VMware Stabilization Algorithm / Hyper-V Stabilization Algorithm. The most commonly used one, "Stabilization by IP," watches the VM as it is Powered On and waits to see if an IP address is reported by the integration services running within the Guest OS (VMware Tools or Hyper-V Integration Services). If an IP fails to be reported to the hypervisor before the "Maximum Allowed Boot Time," the error "OS did not boot in the allotted time" occurs.
If this is the first time SureBackup is being configured, keep in mind that the default Maximum Allowed Boot Time values may require adjustment to find the right value for each VM in each environment. One suggested method to determine the appropriate Maximum Allowed Boot Time, is to set the value to large number, then run the SureBackup job. If it completes without failures, review how long it took for the SureBackup job to report that stability had been achieved. Using that value, add 5 or so minutes, and set that as the new Maximum Allowed Boot Time.
A simple solution to resolve "OS did not boot in the allotted time" is to increase the Maximum Allowed Boot Time to a very high value. This will likely make the error stop occurring, as it will give the VM as much time as it needs to reach a stable state. However, it will mask any subtle on-boot issues that may be occurring or occur in the future. The Maximum Allowed Boot Time serves two purposes, it controls how long SureBackup will wait for the VM to stabilize, and it can help to alert the backup admin of potential on-boot issues that may be affecting the original VM that was backed up.
The best course of action is to adjust the Maximum Allowed Boot Time to a sufficient value for the VMs being tested to boot consistently. The default Maximum Allowed Boot Time values are viable for most environments but may require some adjustment to find the correct value for each VM in each environment.
This advice applies to both Windows and Linux VMs
To troubleshoot the "OS did not boot in the allotted time" error, start the SureBackup job (or Retest the individual VM) and observe the VM being tested. There are two key things to keep an eye on:
Issues Observed and Recommendations
In rare cases, during the boot of the VM being tested by SureBackup, the VMware Tools Service may fail to start.
To check if this has occurred, do the following:
One of the most common reasons a Linux VM fails "Stabilization by IP" is that it fails to acquire an IP because the MAC address that VMware randomly assigns does not match the MAC address the NIC is hardcoded to expect. To resolve this, either (a) update the configuration within the original VM to prevent it during future restores and SureBackup jobs or (b) assign a static MAC to the vNIC.
VMware KB2002767: Networking does not work in a cloned Linux virtual machine
VMware KB219: Setting a static MAC address for a virtual NIC
This form is only for KB Feedback/Suggestions, if you need help with the software open a support case