Acronis BR error 0x0000007B

Source
This article applies to:

• Acronis Backup & Recovery 10 Advanced Server Virtual Edition
• Windows Server 2008 R2 guest OS on ESX(i) 4.1

Symptoms

1. You create a backup of Windows Server 2008 R2 virtual machine running on ESX(i) 4.1 by means of Acronis Backup & Recovery 10 Agent for ESX/ESXi (Virtual Appliance);
2. You recover the created backup to the same or new virtual machine on the same ESX(i) 4.1 Server;
3. The recovered virtual machine fails to boot with blue screen with error code 0x0000007B:

Cause

The issue is caused by file system corruption in the backup file, which is, in turn, caused by inconsistent snapshot created during the backup.
Solution
(!) This has been fixed. The fix is available in the latest build of the product. See Installation of the Latest Update of an Acronis Product.
To resolve this issue without installing the latest build, you will need create a new backup with consistent snapshot, and recover this new backup.
There are two possible ways to create a new backup with the consistent snapshot:

1. Install Acronis Backup & Recovery 10 Agent for Windows inside the virtual machine and back it up by adding the virtual machine to Acronis Backup & Recovery 10 Management Server or by connecting to it from Acronis Backup & Recovery 10 Management Console;
2. You can also uninstall the Volume Shadow Copy Services Support feature of VMware Tools from the virtual machine and recreate its backup.

(!) Use this way only if the backed up VM does not run a database, e.g. Microsoft SQL Server or Microsoft Exchange Server.

Disabling the VSS component of VMware Tools:

Uninstall the Volume Shadow Copy Services Support feature of VMware Tools from the virtual machine:

• Select the virtual machine in question on the ESX server and go to Inventory -> Virtual Machine -> Install/Upgrade VMware Tools:

• This will launch the installation of VMware Tools on the virtual machine:

• Choose Modify:

• Uncheck the Volume Shadow Copy Services Support:

• Complete the modification:

Reboot the virtual machine.