Troubleshooting › Backup and Recovery Operations › Virtual Machines Do Not Start After Recover VM Operations Complete

Virtual Machines Do Not Start After Recover VM Operations Complete

Valid on Windows platforms.

Symptom

Virtual machines may not start properly after Recover VM operations complete. In addition, you may encounter the Stop Error screen (blue screen) when you try to start the virtual machine. The problem occurs only when you back up virtual machines that reside on ESX Server version 4.0 (and older versions) using VCB and a previous release of the agent, and recover the virtual machines to alternative servers running ESX Server version 4.1 (and later versions) using VDDK.

Solution

This behavior occurs because the agent cannot define the SCSI controller type from data that was backed up using VCB from a previous release of the agent. The solution to this problem is to change the SCSI controller type manually after the recovery operation completes, and then restart the virtual machine.

To change the SCSI controller type, do the following:

1. Open the VMware vSphere Client and select the virtual machine that you recovered.
2. Right-click the virtual machine and click Edit Settings on the pop-up menu.

   The Virtual Machine Properties dialog opens.

3. Do one of the following:
   • When the source virtual machine is available in the ESX Server system, verify that the SCSI controller type that was used for the backup is same as the SCSI Controller Type that appears on the Virtual Machine properties for the recovered virtual machine. If the SCSI Controller Type is the same, no changes are required.
   • When the source virtual machine is not available in the ESX Server system, for any reason, change the SCSI Controller Type from LSI Logic Parallel to LSI Logic SAS.

     You can now restart the recovered virtual machine successfully.