Unable to convert Symantec siterecovery image

[Gonecase]

Hi,

I am trying to convert a Symantec Livestate Recovery image (version 6) using convertor 3.0.3 and it is failing giving me error, unsupported format. The convertor logs have the following error:

Builing partition list: Incorrect volume list - 9 (>4) partition entries in the MBR.

Error while calculating the MBR partition locations

CONVERT_FAIL

Import source not recognized

Cleaning up temp directory C:\WINDOWS\TEMP\vmware-temp\vmware-cgan-37887\temp-wrapper.0 ...

VmiQuerySourceInfoTask::task: Image processing task has failed with MethodFault::Exception: sysimage.fault.IncompatibilityFault VmiQuerySourceInfoTask::task: SetState to error

object explicitly disposed: VmiQuerySourceInfoTask::task VmiQuerySourceInfoTask::task being destroyed

Thanks in Advance

[TomHowarth]

have a read of Eric's notes on VM Converter usage on[VMware-Land|http://vmware-land.com/Converter.html],

Taken directly form site

5. Converter Preparation

• Run on OS greater than or equal to source if source is

• > VM and powered off, or*

• > Symantec Livestate System Image*

Tom Howarth

VMware Communities User Moderator

[Gonecase]

Tom,

I went through the whole document and it is supposed to work, but it is not. What is the meaning of the error message ?

Thanks

[TomHowarth]

From doing a quick search it seem that it could be related to a corupt MBR, have you verified the LiveState image?

Tom Howarth

VMware Communities User Moderator

[Gonecase]

Yes, implemented on a physical system and it works fine !

[continuum]

> Yes, implemented on a physical system and it works fine !

Good - use same procedure to restore into a newly created VM. When done, use Converter to configure the new VM.

___________________________________

description of vmx-parameters:

VMware-liveCD:

[paragsha]

Symantec library lists the volumes and type (primary v/s logical etc.). If the image has more than 4 volumes on a disk and for some reason the Symantec does not give the the correct information regarding extended partitions, we will try and create all of them as primary. A disk cannot have more than 4 primary partitions and hence we complain while creating MBR for them.

Can you attach the .sv2i file (its the configuration file ...usually ~2-5 KB).

Thanks

[Gonecase]

Thanks for the info Pragsha, here is the sv2i file. The server contains one dynamic disk with 6 simple volumes.

[paragsha]

Yes, the .sv2i confirms the problem that I suggested. Since the disk is dynamic, it could have >4 partitions and they don't have to be logical. We are not takig care of this case for backup images, since we don't always have all the information we need about dynamic disks. You have couple of options here:

- Use Symantec software to convert .sv2i/v2i files into VMDK and attach these to a VM. You can then use Converter to do a "reconfigure VM", which will enable the VM to boot

- Edit the .sv2i file so that it has <4 partitions and do the conversion. Obviously the final VM that is created will have the rest of the volumes missing.