Acronis *.tib to *.vhd error

[cscrudder]

I used Acronis True Image Home 2010 to create a backup of a Win 7 (64-bit) *.tib file.

When I try to convert the file using VMware vCenter Converter I receive the error "The Source virtual machine is not recognized".

Is Win 7 / Acronis not supported?

[Mauro Bonder]

check the compatibility.

Source

Destination

Local or remote physical machine running an operating system noted in Supported Guest Operating Systems\ Workstation 6.5.x, Workstation 6.0.x, Workstation 5.x, and Workstation 4.x 1 VMware Fusion 1.x, 2.x vSphere 4.0 ESX Server 3.x ESX Server 3i version 3.5 Installable and ESX Server 3i version 3.5 Embedded ESX Server 2.5.x (if VirtualCenter 2.x manages ESX Server) VMware Server 1.x, 2.x VirtualCenter 2.x Microsoft Virtual PC 2004 (for Windows only), Microsoft Virtual PC 2007 (for windows only) Microsoft Virtual Server 2005, and 2005 R2 VMware Consolidated Backup Acronis True Image Echo 9.1, 9.5, and Acronis True Image 10, 11 (Home product) 1, 2 Symantec Backup Exec System Recovery (formerly LiveState Recovery) 6.5, 7.0, 8.0 and 8.5, LiveState Recovery 3.0 and 6.0 2 Norton Ghost version 10.0, 11.0, 12.0, 13.0, and 14.0 (.sv2i files) 2 Parallels Desktop for Microsoft Windows and Mac OS x 2.5, 3.0, and 4.0 3 StorageCraft ShadowProtect 2.0, 2.5, 3.0, 3.1, and 3.2 2, 4 OVF spec version 0.9 and 1.0 5 Local OVF or OVA file 5 URL to and OVF or OVA file 5

VMware Workstation 6.5.x, 6.0.x, and 5.x 4 VMware Player 1.x, 2.0.x, and 2.5.x VMware Server 1.x and 2.x VMware Fusion 1.x and 2.x ESX Server 3.x and 4.0 ESXi 3.5 and 4.0 Installable and ESXi 3.5 and 4.0 Embedded vCenter Server 2.x and 4.0 OVF and OVA virtual appliances, OVF spec version 1.0 5

¹ Only Workstation 5.5 and 6.x can power on linked imports of .sv2i images. Workstation 6 is required to power on linked clones of Acronis True Image and StorageCraft ShadowProtect images.

² Supported only in Converter Standalone server and agent for Windows.

³ Parallels Virtuozzo Containers are not supported in Converter Standalone.

⁴ For conditions and limitations about importing Backup

Exec System Recovery, ShadowProtect, and Consolidated Backup images,

see chapter 2, "System Requirements," of the VMware vCenter Converter Standalone User's Guide.

⁵ OVF supports import and creation of .vmdk images only.

Windows virtual machines running on Hyper-V Server, Citrix XenServer 4

Enterprise Edition, and Virtual Iron version 4.2 can be imported as

live sources (using local or remote hot cloning) with Converter

Standalone 4.0.1.

Supported Guest Operating Systems

Converter Standalone 4.0.1 supports the following guest operating systems:

• Windows NT SP6 and later

• Windows 2000 SP4

• Windows XP Professional (32 bit and 64 bit)

• Windows Server 2003 (32 bit and 64 bit)

• Windows Vista (32 bit and 64 bit)

• Windows Server 2008 (32 bit and 64 bit)^*

• Red Hat Enterprise Linux 2.1 (32 bit)

• Red Hat Enterprise Linux 3.0 (32 bit and 64 bit)

• Red Hat Enterprise Linux 4.0 (32 bit and 64 bit)

• Red Hat Enterprise Linux 5.0 (32 bit and 64 bit)

• Red Hat Linux Advanced Server 2.1 (32 bit)

• SUSE Linux Enterprise Server 8.0

• SUSE Linux Enterprise Server 9.0 (32 bit and 64 bit)

• SUSE Linux Enterprise Server 10.0 (32 bit and 64 bit)

• Ubuntu 5.x

• Ubuntu 6.x

• Ubuntu 7.x (32 bit and 64 bit)

• Ubuntu 8.x (32 bit and 64 bit)

^* vCenter Converter Standalone 4.0.1 supports only Windows Server 2008 and does not support Windows Server 2008 R2.

**If you found this information useful

, please consider awarding points for "Correct" or "Helpful"**

[cscrudder]

It does list Acronis "True Image 10, 11 (Home product)" but says nothing about True Image 2010

Does this mean that the VMware vCenter Converter is not compatible with the True Image 2010?

[Mauro Bonder]

if not present at lista, he not is supported. But this don´t want say that dont work.

In release notes show: Acronis True Image Echo 9.1, 9.5, and Acronis True Image 10, 11 (Home product) ^{1, 2}

*If you found this information useful, please consider awarding points for "Correct" or "Helpful"*

[asatoran]

For any unsupported image file format, just create a new, blank virtual machine. Then restore your image into the virtual machine, just like you would if it were a physical machine. After restoring, run Converter and choose "Configure machine" instead of convert. This will inject the proper hard drive controller drivers. However, I'm not sure if Win7-64 was supported or reported to work well with VMware Converter.

Otherwise, when doing the inital restore, select whatever "restore anywhere" feature of your imaging program, which usually prompts you for the proper hard drive controller drivers. (The default for a VMware virtual Win7-64 is LSI-SAS SCSI controller.) Depending on your VMware product, one workaround I've used in the past was to make the new virtual machine with IDE hard drives, which Windows has built-in drivers. (Depending on your needs, the lower performance of virtual IDE hard disks may be sufficient for you.)

[cscrudder]

I have spoken with acronis tech support and they gave me insturctions how to convert the *.tib to a *.vhd

http://kb.acronis.com/content/3499

Do note that is blatantly says "(!) You cannot run the converted VHD file as a virtual machine.", but I will cross my fingers for this one. If this fails, I will go with your solution asatoran.

[continuum]

Converter does not know how to patch win7-64.

So you need to do it manually - see my notes on how to do it ...

http://sanbarrow.com/p2v2008r2.html#patching

that applies to win7-64 and 2008 R2




_________________________

VMX-parameters- WS FAQ -[ MOAcd|http://sanbarrow.com/moa241.html] - VMDK-Handbook

You also find me in the support crew of PHD Virtual Backup