In case of Windows machine - you can run synchronization task and schedule incremental synchronization. The only caveat is that you can do this manually through GUI. The other option is to use SDK thus schedule synchronizations programmatically.
HTH
P.S. Client-server and local modes are about which machines you can convert - remote and local one conversions.
I am aware of GUI operations, but that is not an option as it should be automatic. (And I am not keen to make Autoit scripts for this purpose.)
Re the SDK - is there a guide? How to utilize the SDK to acchieve this? Mind I am not a prolific programmer.
Thanks!
JinuV - it is not to be used for DR in the broad sense. I have separate backup solution, however adding another layer is a nice thing.
VMware vCenter Converter Standalone SDK however it's definitely programmer's tool.
Any guide or tutorial how to use it?
Look inside: samples and API index, also the SDK forum.
your best option would be to use a solution like vm create a bare metal back up of the physical server schedule job once a week or what ever and then it can be deployed to ESX as A vm .
but not a good idea why not go fully virtual with the server it self.
and you could have a workflow create in vCO to deploy the VM.
shanec40 - yes, that is the idea. The only trouble is finding reliable tools to do so. With Converter it should work, but there is no command line, only API. Will try to look into it, but I doubt I'll manage it. Did you have something else in mind?
Why not virtual? - Currently no need for that + lacking funds and infrastructure. And I am also reluctant to have another layer in need of management. Having a well backed up physical machine is optimal solution as of now.
What do you mean by Workflow option? I didn't understand fully?
Thanks
Hi,
In my current environment we have boot from SAN configuration and we have entire storage coming from remote SAN (Multipath configured). I have tired VMware vCenter Converter Standalone 6.0 to migrate physical SUSE 11 to Virtual Machine but got error "FAILED: An error occurred during the conversion:'Partition number must be set for the boot volume'" at 97%.
While checking logs we found both the Physical Machine cloned successfully and got error while reconfiguring the destination virtual machine. Further digging into problem we have observed /boot volume is not visible at ‘Source Volume’ TAB in vConverter that means vConverter is not reading /boot volume information from the source Physical Machine. While checking at destination virtual machine we found error at console "Operating System not found".
In VMware vCenter Converter Standalone User's Guide if found "Linux volumes mounted by Device Mapper multipath" is not support for Powered On Machine.
Please help me to understand if vCenter Converter Standalone supports boot from SAN environment?
Your case may be different... I had previously converted some hyper-v servers on a hyper-v host using the standalone converter... in my case I had to uninstall the agent from my host... run the standalone converter (version6) again... it THEN determined oh the that host has no agent let's reinstall it... once it reinstalled it's "own" agent we were good!
Worth a shot if you haven't done it... maybe uninstall the agent on the host machine you're making the call to to convert?
Take a look here: VMware KB: Converting a Linux operating system fails with the error: Unable to create virtual machine
The restrictions on KB still apply for version 6, see: VMware vCenter Converter Standalone Release Notes
Source volumes on top of volume managers other than LVM are not recognized during conversion of powered on Linux machines
Converter Standalone recognizes only managed source volumes that run on the LVM volume manager. Other volume managers, including but not limited to Veritas Volume Manager (VxVM), are not recognized.
Thanks for your valuable response.
I understood from KB multi-path devices and boot from SAN is not supported by vConverter. With current setup i can't use vConverter as solution for P2V.
Do you have any idea on PlateSpin Migrate, Dose PlateSpin Migrte will support the same infrastructure?
Hi guys, it is the second time I post this question culd someone help me??
I have a centOS 6.7 host machine, inside this machine somebody else has installed an HyperV (gen 1) virtual machine. Now I want to make this virtual machine compatibile for the Virtualizer VMware Tools 8389.
Than I have downloaded the VMware vCenter Converter Standalone Client, Now if I click convert machine I can reach this VM by his IP only with the option powered-on machine. Anyway, at the second step the client ask me to chose a WMware Infrastructure server. I don't have a WMware server I just want an image (maybe an .vmx file I don't know..) of the virtual machine converted.
What I have to do?? Can I create a WMware server locally on my machine maybe with WMware Player??
Can someone describe me the step to convert this machine and what I need to do this??
Thank you a lot
Bye
Short answer is - you can't! Read the User's Manual to see how live Linux are converted and why you need a ESX destination.
From the other hand - if your HyperV is first version (i.e. Windows 2008) you can convert the powered off VM to WS format directly.
HTH
There isn't anybody know about this ?
Ok I will read the documentation but please answer this question:
1) I have a HyperV VM on centOS 6.7 physical machine
2) I reach that machine with my conversion tool
3) I select my destination ESXi System as destionation for my clone/conversion
QUESTION:
will the clone/conversion procedure create a new Virtual Machine, or can I select an existing virtual machine on that system? Because of the customer already has a VM inside his EXSi System and don't want to create a new one.
Thanks
Converter always creates new VM, there is no workflow to 'update' an existing VM.
HTH
I need to P2V a Win Server 2003 box. In the newer versions of the vCenter Standalone converter, it appears they've removed support for this OS. They support 2003 R2 but not 2003. It looks like version 5.01 of the Standalone converter supports Win 2003 but I cannot find anywhere to download it. Does anyone know where I can get this?
The Windows XP and Windows 2003 support is stopped because these OSes are discontinued but support is not removed.
Just try the latest Converter 6.0
HTH
We want to p2v with a suse Linux machine.
I start the converter and fill out the credentials, start the process error
the root with poassword is the account I must use,..
Any sugestions are very welcome