How do I convert an existing backup to a VM image on a different machine?
Updated: 21 May 2010 | 8 comments
I have a machine that is acting up that has good backup images that crashed when I tried to convert one of the backups to a VM image. I tried to use another machine to convert the backup to a VM image but I could not get it to work. First I copied the backup the the backup directory of the other machine, but it did not see it. Then I browsed for the backup image from the other machine but I just get an error message when I try to convert. Is there any way to do this when the source machine is no longer working? If not that seems like a big problem as you would have to know ahead of time that your machine is going to fail and create the VM image then (so you could host the machine virtually while you fixed the problem).
Comments
When you attempted to browse by file name for the *.V2i image locally copied to the system to which will be performing the conversion (e.g. What you would do when the source machine of the recovery point images is down) what was the error message you said you received?
I've had the same problem. I made an image with BESR 8. I tried to convert it to a virtual machine using VMWare converter and it says that the image is either corrupt or invalid. Then I tried to use the BESR interface to convert it and it locks my whole computer up. I have to hard power it off to recover. I used live update to get all the patches. Was this feature ever tested? I think I'm going to go back to using version 7 until more bugs have been fixed.
I have the same problem, I start the conversion process and the client get frezze and after turn off I look in the event log but I didnt found some reason of the fail.
VMware Virtual Machine Importer has encountered an internal error: A V2I library function call failed: Error ED800001: D:\Backup\CLK_C_Drive001.v2i is corrupt, because its size is not a valid image size.
Guys,
You are trying to do what is not possible.You must point VmWare converter at the sv2i index file, NOT the actual v2i files. Renaming those will not work either.
Selecting the sv2i will open the actual images.
Thanks
Is this solved?
Does booting a pre-made guest OS having a blank HD with the *.iso of the SRD and mapping to the share where the image getting these errors when converted and restoring like a physical machine using the restore Anyware option work for people on this thread?
Would you like to reply?
Login or Register to post your comment.