Support for Backup Exec System Recovery

[jmosquera]

Hi, anyone has tried to import Backup Exec System Recovery images to an ESX 3.0?. It seems that VMware Converter doesn't recognize this format of files; when I try a conversion, it gives me a "Source format was not understood" error

[Jasemccarty]

Have you also tried the VMware Importer?

[shaneyoder]

I also tried VMware Converter 3.0 GA with a BE System Recovery 6.5 image and recieved the same error. I will test Importer to see if it gives teh same results.

[admin]

I think there is some confusion here...Converter supports Symantec Livestate System Recovery images, not Backup Exec System Recovery.

[shaneyoder]

Here's the FAQ:

What 3rd party images are supported with VMware Converter?

A: VMware Converter can currently import system images (Windows operating system only) from Symantec Backup Exec System Recovery (formerly LiveState Recovery)[/b] and Norton Ghost versions 9 and higher. It can also import Microsoft Virtual PC 7 and Virtual Server formats.

It's the same product, just a newer version and renamed. So, apparently it is supposed to work with BE System Recovery.

[admin]

A related thread...

http://www.vmware.com/community/message.jspa?messageID=483945

[shaneyoder]

So, it looks like it should be working. Has anyone got it to work yet?

[stevea85]

Hi. I am using VMWare Converter 3 and trying to import an sv2i file which was created with Backup Exec System Recovery Server 6.5.0.14095 but I too am getting an error "Source format was not understood". I was under the impression that this should work!

[Jasemccarty]

I'd be curious to see the .sv2i for the Backup Exec System Recovery file.

I'm wondering if it is having a problem with parsing it correctly.

[asatoran]

I don't think the image format changed going from LiveState to Backup Exec System Recovery. I am able to use the older versions of LiveState v2i Browser to restore individual files from images made with the newer BESR.

[shaneyoder]

Previously, I always selected images on a network share. I saw a few other posts that referenced timeout issues and such.

I tried copying my images local to the machine Converter is installed on, and it works just fine now. It is the same image, just local instead of on a network share. Interesting!

[jmosquera]

So, the problem is the parser file?. I had problems with this parser file; when I had move the parser and images files to a different location (to a network shared, for instance), backup exec wasn't able to find the right path to the image files

[Namlak]

I've got one machine out of four that works perfectly - network or local drive (even USB drive).

The failing machines are running XP SP2, 2003 x64 Enterprise, and Vista.

The machine that works every time is XP SP2. Nothing special with the POSSIBLE exception that I used it way back when while evaluating Livestate. But I'm not sure about that. But there is a \*possibility* that some Livestate system componets are still lurking.

[Namlak]

OK add to the list of machines that give the "format not understood" error:

The \*exact* same machine that made the Livestate files and has Livestate currently installed (under Win 2k3 SP2) and another XP SP2 box.

So for whatever reason, I have one XP machine that imports these files just fine and all the others have failed.

This is a fine introduction to evaluating this product.....[u][i][b]VMware, are you reading this???[/b][/i][/u]

[mleune]

VMWare converter 3 should be aligned with Backup Exec System Recovery 6.5 AND 7.0 (which is almost released to manufacturer). Unfortunately I cannot get answers on when Converter will adapt Symantec Backup Exec system Recovery version 7.

I would like VMWare to comment on this.

Thank you.

[neilltyler]

I'm getting the same message with a 2003 Domain Controller. Has anyone gotten this to work with 2003 server?

[Francois Fontaine]

Ok guys, I got you answer;

You only have to upgrade you "Backup Exec system Recovery Server" to build 6.52.17171 (the latest). After that, recreate an image with your new build, and it will then convert in the VMware converter. Did it yesterday night, and the conversion whent 100%.

[mattlewis]

i was getting the error using BESR 7.0. i upgraded my converter from 3.0.0 to 3.0.2 and the problem was solved.