Using ghost32.exe I was ale to convert the .gho file to a vmdk. After the conversion the file was only 119MB. I know it should be at least 40GB because are 18 2 G Ghost spanned image files. I have ghost deployed laptops with the gho file. and it is 40GB
The documentation states that converter supports Norton Ghost directly. yet, via the GUI, it doesn't allow you to select the more common .gho file that it would create. Some versions can create the .sv2i or .sv2 file which is also used in other Symantec backup software.
gho to vmdk converter 18
I can confirm Ulli. I have always "ghosted" to a fresh VM using the ancient mod-boot floppy. Then I use converter to do the rest. Incidentally, in VC 2.5 with the converter plug-in, it is just a right-click action. I have never seen it able to directly convert a .gho file.
Yeah, Over the weekend I had a chance to look at Ghost 12 on a friends computer. There is a separate section dedicated to restoring backups. one of the restore types says to go to sv2i format. Output a Windows XP home backup to that format, and converter accepted it.
4/06/20091:07:00 PMWould be blocked by Access Protection rule (rule is currently not enforced) %machine%\%user%C:\Program Files\Symantec\Ghost\ghost32.exeE:\GHOST\IMAGE\image.vmdkVirtual Machine Protection:Prevent modification of VMWare virtual machine filesAction blocked : Create
I stumbled into the converter, that evidently downloaded with WMWare Workstation 8. However, I get an error "The source parameters are invalid" when I try to convert the backup. I've pasted the log below. It seems to me that "2012-01-05T09:40:02.282-05:00 [06880 error 'Default'] SourceSelectPluginModel::BuildFilter 3rd party type livestateBackup not found" is my problem. How do I fix this or whatever else is wrong and how do i fix that?
Could you try to convert the file from GHO to a VMDK? In that case, you could create a new virtual machine and during creation say that the file for the disk already exists and point to that converted vmdk.
Using the standalone converter, I get the aforementioned error "The source parameters are invalid" when I try to convert the backup. I still think this is the best avenue to use. So I'm really interested in how to get around this error. I don't know if the "2012-01-05T09:40:02.282-05:00 [06880 error 'Default'] SourceSelectPluginModel::BuildFilter 3rd party type livestateBackup not found" is germane.
I tried to use the standalone converter for this, but I don't see an option for building a vm from a boot disk. It only has options for a running machine, some vmware things, or a backup image. Is it possible to create a vm from an old boot disk that's not the current host boot disk?
BTW, for VMware programmer employees, it would be nice if the converter could wrap up what continuum says and do it as one of the converter options in one of those first drop down (combo) boxes. Continuum's advice makes perfect sense, but is not at all obvious if you don't already know all the nooks and crannys of vmware. I would think that the case of pulling the boot disk away from a dead motherboard would be a common occurrence. And the whole reason I keep doing this is that it takes so horribly long to reinstall years of software utilities, as I do being a consultant and hardware/software developer. It would take weeks. Note also that, finally, since I believe workstation 6.5++ may really be able to handle multiple monitors, I may next bite the bullet and run ALL my stuff in vms, with only a bare bones host. This way, when the host dies 5 or 10 years from now, I'm not in another pickle. I think I hit this pickle every 3 to 5 years, overlapping with multiple platforms for different development uses, over the past 30+ years. ((EDIT: but workstation doesn't perfectly emulate all the hardware stuff, so sometimes I can't use a vm for some kind of usb-connected in-circuit emulators))
Thank you so much for your detailed instructions. I was not able to use the .gho methods to get W2K to virtualize, but your steps worked out perfectly! I will inform that version 4.3 of the VMWare converter does not work with W2K for some reason.I had to download 4.01 and it all worked out.Thanks for your detailed explanations, saved my life.
I am trying to convert a W2K system to a VM.Do you install the VMware Standalone Converter on the W2K system? or on another system, say a WinXP or Win7 system?From the steps above, I am gathering that the VMware converter should be installed on the system where you want the VM to be created...Extract the sysprep tools on the W2K system...Next, apply the update rollup for W2K SP4 on the W2K system...Then, run the Converter on the WinXP/Win7 system, deploy the agent to the W2K systemthen using Converter connect from the WinXP/Win7 system to the agent running on the W2K system and convert to a VM image file to be created on the WinXP/Win7 system.Just trying to clarify the steps in the procedure and where you install, run the tools.t.fahey
Anonymous,You install the converter either on the vCenter server (4.x) or on a desktop machine (XP/Win7), then deploy the sysprep tools on the same machine where vCenter Converter is installed, not on the machine you want to convert.Also, you need the older version of the standalone converter to make sure it supports Win2k.
HelloI would like some extra info please:1. Should I run sysprep on my W2K server before copying the sysprep files to the converter machine ?I downloaded and copy the sysprep for W2k (from MS), but vmware converter still request them in the programdata folder.2. I am using esx5 on my host server. the converter I found there does not take in charge W2K. I had to download version 4.0.1 of converter and run it from another pc. Can I send the data directly from converter 4 to esx5 infrastructure ?thanks for your helpHdo
hdo,1) You should place the sysprep files on the program data on the machine that has the converter installed on it, not on the Windows 2000 machine.2) Converter v4 will be able to communicate with vSphere 5 hosts, but the VM hardware will be the older version.After you finish the conversion, do not power on the VM. Right click it in vCenter and upgrade the VM hardware, then you can power it on & install the latest VMware tools.
Hello Daryl,I apologize for the late reply. According to this link -os.html , Windows 2000 is still supported on vSphere 5, but the converter won't support it, so make sure you grab the right version of the converter.To be honest, if this is a critical system yet fragile, then I suggest you power it off & clone the disks using any cloning tool.I personally would load Linux from a live CD like Knoppix, then use the 'dd' command to clone the disk to another disk or to an image file.This way, if the converter breaks the machine, you can at least restore the OS & data to the original state.Good luck!
Anonymous,That most likely means Windows filesystem quiesce service failed to snapshot the filesystem.You have two options: Use the old VMware cold clone CD (requires booting from the CD -- downtime) or use a cloning tool that the new converter can convert from it to a vmware virtual machine.
My Conversion was with a system that had four data disks. It worked out for me to use Windows' Backup to store the data and then just convert C:. After the conversion completed I added the other drives and did a restore from the backup. As these were DB disks, it was important to turn off & disable the DB engines before the backup, and then to restore before enabling the backup. I used Windows update to Roll up the patches, and that worked fine for me. The only other glitch (which you pointed to) was that the VMware converter started the conversion before the source was backup from the reboot. Making sure the source was backup (with the VMware agent running) and just selecting the C: drive) reduced the conversion to about 15 minutes for a 10 GB C: drive. The restore from the .bkf for the D:, E:, & F: disks looks to be about 2 hours for about 225 GB. I was looking at converting to either VMware or Hyper-V depending on which was the path of least resistance. Your instructions were so well written that they gave me confidence to go ahead and try it. Vere UN-Traumatic experience. Thank you!
Sameer,Things have gotten easier now. After you convert the physical box into a VM, you can mount the .vmdk file in a Windows machine and browse its files. So you can insert your file in there.Check this link: 4 Ways to Mount a VMDK Image File in Windows
DataNumen Exchange Recovery is the best OST to PST converter and OST recovery tool in the world. It can convert the orphaned or corrupt Outlook OST files to PST files for easy access.
Now you can open the converted PST file with Microsoft Outlook and see the converted objects. Please note our OST to PST converter software will try to put the converted objects in their original folders. However, for the lost & found objects, they will be recovered and put in special folders like Recovered_Group1, Recovered_Group2, etc.
MS Outlook cannot open or import OST files directly. To access the mailbox data inside an offline OST file, you need to use our OST to PST converter to perform the conversion of OST files to PST files, and then open or import the PST files in Outlook.
Currently, our OST converter tool supports all Windows OS versions, including Windows 95/98/ME/NT/2000/XP/Vista/7/8/8.1/10 and Windows Server 2003/2008/2012/2016/2019. And it supports both 32bit and 64bit systems. 2ff7e9595c
Comments