VMware Converter standalone OR... I'M CONFUSSED!  Help, please

Hello

I have the vmware converter plugin installed.  What is this for?  I can't find any documentation.  The only documentation I can find is for the stand-alone version.  Work together or what?  Then the documentation still says to install the converter on the source machine and I understand not what converter, they're talking about. I want to do a cold cloning on my SQL servers.  It's the standalone "VMware-converter - 4.0.1 - 161434.exe" and it's the VMware converter ' VMware - Converter.exe "I use the standalone version for a test of my Vista machine as a clone of good hot and has worked.  But I do not understand the cold cloning process.  Can someone point me to the documentation.

My environment is PE2950, ESXi 4.0 embedded, vCenter Server vSphere 4.0.  I am cloning all standard W2K8 servers.  Some SQL, domain controllers and servers of rest files.  A Server Application.

Help!

Thank you

GEOBrasil

GEOBrasil,

I understand the confusion around the different products of converter.  I hope that I can help you better understand which version is right for you.  The reason for the different versions is based on what type of conversion you want to do, which are based on physical operating systems (Source) and your virtual environment (Target) is going to be.

Couple of warning or best practices:

-VMware recommends NO conversion P2V from DC.  It is better to build NEW virtual machines for this.

-Hang your applications (SQL, WEb, etc.) before making a hot-clone (plug-in or standalone Enterprise)

First, for each platform VI3.x, VI4.x there are TWO business (plugin) version and a standalone version (Windows & Linux applications)

-VMware comparison chart gives an overview of the differences (http://www.vmware.com/products/converter/get.html)

Non-exhaustive summary below:

Enterprise Edition:

Pros: vCenter integration and automation, supports

Cons: you have to pay for it (you already have it if not the factor in your assessment.  No 'multi-stage' conversion (i.e. 1 snapshot converter, deltas on a machine running are lost or migrated manually).  No Linux support. Can't stand VI as a platform to target.  Includes the CD "cold-clone".

Stand-alone Edition:

Benefits: support Linux.  Supports the VMware Desktop products (workstation, Fusion, etc.) as target platforms. "Several steps" cloning, intial snapshot conversion as deltas.  Source and target of service and the power of command for Windows.

Cons: Billable per-incident support.  No automation, scheduling.

Cold-conversion

Benefits: no changes can occur on the source server.  preserves the logical partitions.  No service application comes into conflict with the local area.  No installation on the source area

Disadvantages: Requires downtime for the source server.  Requires the driver support for all devices on a physical to be present in BootCD (WinPE) Server

Hope this helps

Tags: VMware

Similar Questions

  • VMware Converter Standalone 5.5 does not display a Drop Down Menu for the Type of Destination

    Hi people,

    I try to use VMware Converter Standalone 5.5 for use with VMware Player and am not able to select the Type of Destination of my choice (I like to choose "VMware workstation" or another VMware virtual machine in the drop-down menu "Select the destination type").  Please see the image below where the combo box is not there at all.  Thanks for your help.  Hai

    converter-issue-image.png

    This isn't a bug, it is a limitation of the converter. It is stated in the documentation. Converter considers that any machine under tension like physics. It cannot convert powered on Linux machines to hosted (i.e. Workstation/Fusion) destinations.

    A solution would be to convert it to ESX and then convert the (from) power off the VM power to the workstation.

    HTH

    Plamen

  • VMware Converter Standalone 5.0 U1 - cannot convert W2k3

    Hello

    I tried convert my physical server Windows 2003 R2 (with Service Pack 2) in VMware (to ESXi host) environment, but 98% is DOWN.

    VMware Converter Standalone version is: 5.0 U1

    The version of VMware ESXi Hypervior is: 5.0 U1.

    VMware Converter Standalone U1 5.0 is installed on this server (that I want to convert).

    I have attached one connects VMware Converter Standalone, a screen displaying the boot.ini file and the error.

    Could someone help me with this problem?

    Greetings,

    Damiano

    Observer the worker saves any error "could not find". I looked through you and found this:

    2012 12-21 T 13: 33:17.620 + 01:00 [02980 error "task-5'"] did not symmpi.sys in \\.\vstor2-mntapi10-shared-EC48ED48000010000000000016000000\WINDOWS\Driver Cache\i386\driver.cab
    2012 12-21 T 13: 33:17.635 + 01:00 [02980 error "task-5'"] could not find symmpi.sys in the specified CAB files
    2012 12-21 T 13: 33:17.635 + 01:00 [02980 error "task-5' '] Reconfiguration failed with: converter.fault.FileNotFound
    2012 12-21 T 13: 33:17.635 + 01:00 [02980 info "task-5' '] restoration of the transaction of reconfiguration...

    Go to System32\Drivers on the source server and determine whether symmpi.sys is in this folder. Otherwise, copy from a known working 2003 VM and copy also in drivers.cab in Windows\Driver Cache\i386\driver.cab

    Run the conversion again and choose the no power over the new VM and not turn off the source, in this way, you can check if the process is running. If so, great! If this isn't the case, observe the worker logs yet, find "could not find" or "reconfiguration failed with" to determine the cause of the failure.

    I have a lot of experience with this exact problem and it is almost always something to do with symmpi.sys

  • VMWare converter standalone fails at 1%.

    Hello

    I have a problem of conversion of some machines on the subnet to another. Since then, I work at the University, here are fairly complex network infrastructure. Whenever I need an open port, I have to record a call and to wait a few days so that it can be resolved.

    I have:

    5.1 ESXi on the subnet has

    PC which is on the subnet and is able to connect to the subnet B via port 80, 445, 9089.

    Some servers that will be migrated at the subnet B.

    Now when I try to set a task with VMware converter standalone installed on PC to clone a physical host (win 2 k 3) on subnet B, I get status failed with the error message: an error occurred during conversion: 'unknown exception '.

    I found on this forum similar problem (P2V conversion fails at 1%, 'an error occurred when converting' unknown exception' ') and double-checked my logs.

    2013-08 - 01 T 11: 11:06.719 + 02:00 [warning 02020 'Default'] [, 0] NfcNewAuthdConnectionEx [NFC ERROR]: unable to connect to peer. Error: Unable to connect to server 1.2.3.4:902 (this is the IP of ESXi server)

    2013-08 - 01 T 11: 11:06.719 + 02:00 [02020 info 'Default'] [, 0] Sysimgbase_DiskLib_OpenWithPassPhrase failed with 'NBD_ERR_NETWORK_CONNECT' (error code: 2338)

    2013-08 - 01 T 11: 11:06.719 + 02:00 [02020 info 'Default'] [, 0] error 2338 opening disk ha-nfcssl: / / [ESXi_storage] servername/servername.vmdk @1.2.3.4:902! 52 14 82 92 62 db ec - a3 c4 4 a 72 fd f1 da b5 ac.

    the problem is unclear to me. Source machine tries to connect directly to ESXi server and storage. But for me to record a call "opening port" for each server that I want to convert is a little awkward to say and I was wondering is - it possible somehow to migration through PC in a subnet that has access to powered on the source machine and the ESXi server. And these machines would not need to directly contact the ESXi Server?

    Thanks for your replies.

    S.

    Hello

    You can convert to the format of the workstation and then convert the resulting ESX VM again. If you have a machine with enough storage in the subnet B, convert, and then physically move the machine or the storage of subnet A and convert again. So, you can bypass the firewall completely.

    HTH

    Plamen

  • VMware Converter Standalone copy is the copy block level and sometimes at the level of files

    Hi team,

    I use VMware converter standalone for P2V and V2V migrations. I noticed that some readers are cloned by the converter by block-level copying and some readers are colned by the file-level copy. Anyone can unmask me why is it so? Block level and file level methodology is decided by the converter on what basis? is the size of the size\sector disc or disc type? Any suggestion will be highly appreciated.

    Thanks in advance

    Kind regards

    Rohit

    Screen enclosed... Post edited by: RohitGoel

    RohitGoel wrote:

    Is there a limit of resizing who decide if vmware converter will use the file level cloning. I have attacehd a screen shot... I'm resizing it had ' (from 50 GB to 80 GB) drive also for traget VM but yet Vmware converter used method block based to clone and 'E' is also a resized to target disk is converted by file based cloning. .. is there something else that decides on the level of the file or block level when it resizes?

    No limit of resizing.

    To resize the D: you extend that will always use at the block level.

    What do you do to E:?  Size reduction?

  • VMWare Converter Standalone 4.1

    Is there a download for Standalone Converter 4.1 VMWare?  Will they have a?

    Thanks in advance.

    AFAIK the vcenter for Converter plugin will die soon - so there must be a new Standalone version soon - (and maybe in a few years we will know

    Check yourself

    VMware vSphere 4.1 is the latest major version of VMware vCenter Converter plugin. VMware will continue to provide technical support for vCenter Converter to the end of its support life cycle. VMware will continue to update and support the product free vCenter Converter Standalone, which allows conversions from sources such as physical machines, machine formats virtual VMware and Microsoft and some third-party disk image formats.

    of http://www.vmware.com/support/vsphere4/doc/vsp_vcc_42_rel_notes.html

    _________________________

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

  • Using vmware converter standalone

    Hola, estoy using vmware converter para comenzar a virtualizar pero Necesito saber como hago UN para the vm no cambie su number, sid, ip, licenses etc.

    Hay siempre esto o Quebec is can sejar tal cual?

    If no converter El cargo in which sysprep can pasar?

    I hope I can help.

    MUCHAS gracias.

    Buenas

    ESO suele pasar con licenses OEM. None are 'legal' porque van en theory sujetas virtualizarlas the red, grafica, memoria y placa base of Mac of the card. As puedes hacer Lo e tratarlas como nuevas, contains the activacion por telefono pero facilities.

    Por cierto, sube al ultimo ServicePack (sp3 of xp, 2 k 3 y xp64 sp2) para descartar antes este tema as tambien dio su guerra por aquel entonces.

    If esta u otra respuesta're util, por favor su marca used notificador.

    Gracias / looks

  • VMware Converter standalone 4.0.1 gets 97% error: impossible to reconfigure the virtual target computer. Linux P2V conversion

    I have 97% then it goes down. I'm conversion server Ubuntu 9.10. I will attach the logs. "GrubInstaller::InstallGrub: /usr/lib/vmware-converter/installGrub.sh failed with return code: 127 and message:

    /VMware - updateGrub.sh: 38: grub: not found

    GRUB runtime error

    Vmware runtime error - updateGrub.sh through chroot into/mnt/p2v-src-root

    22/10/09 discovered Ubuntu 9.10 uses Grub2 is the problem and can it work with Grub2?

    Let me know if you can help.

    OKI I did the P2V and after it failed to 97%,

    I started the virtual machine with the LiveCD mode help, connected root to/dev/sda1, installed grub2 and finally ran "upgrade-from-grub-legacy".

    After the reboot, everything works fine.

    So no need to replace your UUID and all that. That should be enough.

    Thank again for this band of working capital.

    Bragi - of Iceland

  • VMWare Converter Standalone for ESXi 4.0 - thin discs?

    I wonder if there are plans for Converter support the commissioning of thin disks on ESXi 4.0?

    VMotion is not an option for me unfortunately, and am not looking forward to recreate a VM just to get a thin disk...

    In theory, I guess I might be able to create a thin disk and clone one hard drive to another, but it's not something that I've tried before and so I'm not sure of what is involved?

    Someone at - it an entry into that? I'll be workining on ESXi 4.0 installation as soon as I have time (assuming that my whitebox support)...

    Hello.

    Check out http://www.yellow-bricks.com/2009/05/21/vmware-converter-401/ or http://blog.tpv.dk/?p=3

    Good luck!

  • What happened to download VMware Converter Standalone?

    It no longer exists on the site of VMware! Can anyone help? I'm desperate for a copy. I tried older versions too, but there is download link now more. The product has been removed?

    It seems to have made their reappearance on the website now, I was able to download

    Thank you

  • VMware Converter Standalone 4.0.1

    Hola a todos,

    MI problema are el siguiente estoy intentando fisico pasar a Máquina virtual (Vmware ESX 4.0.1) con una Windows 2003 R2 SP1 con SQL 2005 y cuando el 66% leads me da el siguiente error:

    FAILED: A general error occurred: SQL_CANTOPEN:

    Unable to open database file

    He estado buscando information sober este error no nada encuentro.

    Hey David,

    Check the documentation en converter del este enlace:

    http://www.VMware.com/support/converter/doc/releasenotes_conv40.html#introconv

    Problems of sober todo relative information was known. Perhaps encuentres you error.

    Saludos,

    Jose Maria Gonzalez,

    Founder and president of JmGVirtualConsulting.com

    -

  • Convert the physical Linux machine with VMware Converter Standalone 4.0.1 on VMware Workstation

    Hello

    I work in a virtualization project, now I test and I want to test the new version of the converter, because I need to convert some Linux machines and I know that with this version is not difficult.

    I do not have the ready virtual infrastructure so I test on a workstation environment. I would like to know if someone has converted a physical Linux machine to virtual and if the destination has VMware workstation 6.5. I know that this is not supported, but this does not mean that you couldn't do.

    When I have to specify the type of destination, I got the error that you could see on the photo.

    Please let me know if you have tested this before and you know how to solve this problem.

    Thanks in advance!

    See you soon

    Malulas,

    Welcome to the Community Forums.

    To do a physical to virtual conversion, you MUST GO to ESX.  It is a requirement under the guidance of the user manual.

    If the virtual machine was already in ESX, you might be able to export to a workstation image while the ESX VM is powered off.

    Sorry for the bad news.

    Kind regards

    EvilOne

    VMware vExpert 2009

    NOTE: If your question or problem has been resolved, please mark this thread as answered and awarded points accordingly.

  • Unable to get hardware information for the selected with vmware converter 5.5 computer (could not get the ability to \\.\PhysicalDrive0: error opening peripheral drive: 32 an unknown error (0 x 20) (32))

    Hello

    I'm doing a P2V with vmware converter standalone 5.5

    The source is the same machine that hosts the vmware converter 5.5

    The operating system is W2003 which acts as a domain controller

    VMware converter is launched by the administrator account.

    The error that I see on the balls of vmware - converter.worker is:

    2014 02-13 T 17: 36:35.592 + 01:00 [04344 WARNING "Default"] could not get the ability to \\.\PhysicalDrive0: error opening disc device: 32 an unknown error (0 x 20) (32)
    2014 02-13 T 17: 36:35.592 + 01:00 [warning 04344 "Default"] jump drive hard "\\.\PhysicalDrive0."
    2014 02-13 T 17: 36:35.592 + 01:00 [04344 WARNING "Default"] could not get the ability to \\.\PhysicalDrive1: error opening disc device: 32 an unknown error (0 x 20) (32)
    2014 02-13 T 17: 36:35.592 + 01:00 [warning 04344 "Default"] jump drive hard "\\.\PhysicalDrive1."
    2014 02-13 T 17: 36:35.592 + 01:00 [info 04344 "Default"] Found volume with name '\\?\Volume{0395a0a1-8c42-11da-a7d7-806e6f6e6963}\ '.
    2014 02-13 T 17: 36:35.592 + 01:00 [info 04344 "Default"] Found volume with name '\\?\Volume{18297536-8c0b-11da-8528-0014852d7e43}\ '.
    2014 02-13 T 17: 36:35.592 + 01:00 [info 04344 "Default"] Found volume with name '\\?\Volume{caf5e9f8-4e6c-11dd-b440-0014852d7e43}\ '.
    2014 02-13 T 17: 36:35.592 + 01:00 [info 04344 "Default"] Found volume with name '\\?\Volume{2958b89a-b562-11dc-a508-806e6f6e6963}\ '.
    2014 02-13 T 17: 36:35.592 + 01:00 [info 04344 "Default"] Found volume with name '\\?\Volume{0395a09f-8c42-11da-a7d7-806e6f6e6963}\ '.
    2014 02-13 T 17: 36:35.592 + 01:00 [info 04344 "Default"] Found volume with name '\\?\Volume{0395a09e-8c42-11da-a7d7-806e6f6e6963}\ '.
    2014 02-13 T 17: 36:35.592 + 01:00 [04344 WARNING "Default"] could not get the ability to \\.\PhysicalDrive0: error opening disc device: 32 an unknown error (0 x 20) (32)
    2014 02-13 T 17: 36:35.592 + 01:00 [warning 04344 "Default"] jump drive hard "\\.\PhysicalDrive0."
    2014 02-13 T 17: 36:35.592 + 01:00 [04344 WARNING "Default"] could not get the ability to \\.\PhysicalDrive0: error opening disc device: 32 an unknown error (0 x 20) (32)
    2014 02-13 T 17: 36:35.592 + 01:00 [warning 04344 "Default"] jump drive hard "\\.\PhysicalDrive0."
    2014 02-13 T 17: 36:35.592 + 01:00 [04344 WARNING "Default"] could not get the ability to \\.\PhysicalDrive1: error opening disc device: 32 an unknown error (0 x 20) (32)
    2014 02-13 T 17: 36:35.592 + 01:00 [warning 04344 "Default"] jump drive hard "\\.\PhysicalDrive1."
    2014 02-13 T 17: 36:41.155 + 01:00 [warning 04344 'Default'] attention: no attached disks have been detected.
    2014 02-13 T 17: 36:41.155 + 01:00 [04344 error 'Default'] [LiveWindowsComputer] could not find disks connected to the computer.
    2014 02-13 T 17: 36:41.170 + 01:00 [info 04344 "Default"] scheduled timer cancelled, succeeds StopKeepAlive
    2014 02-13 T 17: 36:41.170 + 01:00 [04344 error "Default"] unknown exception when calling VMOMI method queryComputerInfo
    2014 02-13 T 17: 36:50.358 + 01:00 [05648 WARNING "Default"] could not get the ability to \\.\PhysicalDrive0: error opening disc device: 32 an unknown error (0 x 20) (32)
    2014 02-13 T 17: 36:50.358 + 01:00 [05648 WARNING "Default"] Skip hard drive "\\.\PhysicalDrive0".
    2014 02-13 T 17: 36:50.358 + 01:00 [05648 WARNING "Default"] could not get the ability to \\.\PhysicalDrive1: error opening disc device: 32 an unknown error (0 x 20) (32)
    2014 02-13 T 17: 36:50.358 + 01:00 [05648 WARNING "Default"] Skip hard drive "\\.\PhysicalDrive1".
    2014 02-13 T 17: 36:50.389 + 01:00 [info 05648 "Default"] Found volume with name '\\?\Volume{0395a0a1-8c42-11da-a7d7-806e6f6e6963}\ '.
    2014 02-13 T 17: 36:50.389 + 01:00 [info 05648 "Default"] Found volume with name '\\?\Volume{18297536-8c0b-11da-8528-0014852d7e43}\ '.
    2014 02-13 T 17: 36:50.389 + 01:00 [info 05648 "Default"] Found volume with name '\\?\Volume{caf5e9f8-4e6c-11dd-b440-0014852d7e43}\ '.
    2014 02-13 T 17: 36:50.389 + 01:00 [info 05648 "Default"] Found volume with name '\\?\Volume{2958b89a-b562-11dc-a508-806e6f6e6963}\ '.
    2014 02-13 T 17: 36:50.389 + 01:00 [info 05648 "Default"] Found volume with name '\\?\Volume{0395a09f-8c42-11da-a7d7-806e6f6e6963}\ '.
    2014 02-13 T 17: 36:50.389 + 01:00 [info 05648 "Default"] Found volume with name '\\?\Volume{0395a09e-8c42-11da-a7d7-806e6f6e6963}\ '.
    2014 02-13 T 17: 36:50.421 + 01:00 [05648 WARNING "Default"] could not get the ability to \\.\PhysicalDrive0: error opening disc device: 32 an unknown error (0 x 20) (32)
    2014 02-13 T 17: 36:50.421 + 01:00 [05648 WARNING "Default"] Skip hard drive "\\.\PhysicalDrive0".
    2014 02-13 T 17: 36:50.452 + 01:00 [05648 WARNING "Default"] could not get the ability to \\.\PhysicalDrive0: error opening disc device: 32 an unknown error (0 x 20) (32)
    2014 02-13 T 17: 36:50.452 + 01:00 [05648 WARNING "Default"] Skip hard drive "\\.\PhysicalDrive0".
    2014 02-13 T 17: 36:50.499 + 01:00 [05648 WARNING "Default"] could not get the ability to \\.\PhysicalDrive1: error opening disc device: 32 an unknown error (0 x 20) (32)
    2014 02-13 T 17: 36:50.499 + 01:00 [05648 WARNING "Default"] Skip hard drive "\\.\PhysicalDrive1".
    2014 02-13 T 17: 36:56.155 + 01:00 [05648 WARNING 'Default'] attention: no attached disks have been detected.
    2014 02-13 T 17: 36:56.155 + 01:00 [05648 error 'Default'] [LiveWindowsComputer] could not find disks connected to the computer.
    2014 02-13 T 17: 36:56.155 + 01:00 [info 05648 "Default"] scheduled timer cancelled, succeeds StopKeepAlive

    This had already happened with another server (also W2003 DC), but the hardware was completely different; Unfortunately, I wasn't able to solve this year here.

    Any help or advice would be appreciated, thanks in advance

    Thank you for all your help

    I finally found the guilty service.

    It was pcmonitor monitor/remote control software. Once I stopped it is service vmware converter could get the capacity of the physical drives.

    It is rather curious because I made several servers P2V conversions using this software (so far the last one two weeks ago - the difference between that server and this one was that the first was not a domain controller).

    Hopefully this thread will help others in the future.

  • VMWare Converter / ESXi - convert before installing ESXi?

    I need to convert a physical machine into a format that VMWare ESXi will be able to run. The problem is that I have not and can not install VMWare ESXi until this conversion is already done. VMWare converter standalone client customer has two options for the type of destination:

    • Machine virtual VMware Infrastructure (while the right choice, apparently, I can't pick it that I have not yet installed ESXi any where)

    • VMware Workstation or other virtual machines to VMware

    When I choose the second option, I can "Select VMware product", however, ESX/ESXi is not an option. One of these options will convert to a format that ESXi will be able to run once installed without additional conversion?

    I think I should choose VMware Server 1.x as I think it's running version 4, like ESXi hardware.

    The release notes for Converter 4 State that ESXi 3.5 is a goal taken in charge in the future you will be just able to select ESX for the destination and you will be fine.

    In this case, you can select the VMware Workstation or other Machine virtual VMware opton and store than the P2V would be the machine on a Windows share. You can then use again later on, converter to convert the virtual machine in ESX format.

    The user guide for the product says that it is possible and taken care of.

    If you found this helpful, please consider awarding points

  • VMWare Converter - 2gig - not preallocated pieces

    I have a strange problem that I can't find any information on, but I'm betting is a bug. I use 5.0 ESXi and VMWare Converter standalone 5. When converting to a virtual machine (for backup purposes) with a 40 g drive, choose to use the option "not previously affected. The virtual machine is saved and is about 7g. To make it possible to put it on DVD (s), I use the option of breaking into pieces of 2 G, also "not previously affected." However, when you use this option, I get about 20 2 files. Also when you use the option of 2G block, seems always pre assignment even though I specified that it should not. Has anyone experience this problem?

    Welcome to the community,

    What did you choose as a target for the conversion? ESXi does not support fragmented files of 2 GB.

    André

Maybe you are looking for