Community Pick: Many members of our community have endorsed this article.
Editor's Choice: This article has been selected by our editors as an exceptional contribution.

HOW TO: Improve the transfer rate of a Physical to Virtual (P2V), Virtual to Virtual Conversion (V2V) using VMware vCenter Converter Standalone 5.0

Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)VMware and Virtualization Consultant
CERTIFIED EXPERT
EE Fellow, MVE, Expert of the Year 2021,2017-11, Scribe 2016-2012, Author of the Year 2018-6,2013-2012 VMware vExpert Pro, vExpert 2022-2011
Published:
Updated:
VMware vCenter Converter Standalone 5.0 is a FREE tool available from VMware upon registration, the purpose of this software tool is to easily convert physical or virtual computers, images of computers to VMware virtual machines. Server and Workstation operating systems are supported in the conversion.

Download VMware vCenter Converter Standalone 5.0 here
VMware vCenter Converter Standalone 5.0 Documentation
VMware vCenter Converter Standalone 5.0 User Guide

In September 2011, VMware released version 5.0 of VMware vCenter Converter Standalone 5.0, with many new features including partition alignment important for aligning partitions correctly on storage array networks (SAN).

BUT, we've noticed that completing conversions using VMware vCenter Converter Standalone 5.0 compared to using VMware vCenter Converter Standalone 4.3, were taking much longer, and the transfer rate of a conversion had become degraded when using version 5.0.

The following modification will improve the transfer rate when using VMware vCenter Converter Standalone 5.0, to similar transfer rates obtained when using VMware vCenter Converter Standalone 4.3 to perform conversions.

It would appear that VMware uses a proprietary VMware protocol called NFC, to image to destination, also by encrypting (SSL) the data payload transfers in version 5.0, this additional overhead causes transfer performance degradation. The result of which is a longer than expected conversion time, when compared to version 4.3.

Turning OFF SSL Encryption in VMware vCenter Converter Standalone 5.0 can improve transfer rates.

To turn OFF SSL Encryption in VMware vCenter Converter Standalone 5.0, please follow the following steps:-

1. Find and Edit converter-worker.xml

This file is location in the following locations

Windows Vista, Windows 7, Windows 2008
%ALLUSERSPROFILE%\VMware\VMware vCenter Converter Standalone

Windows XP, Windows 2003, Windows 2000
%ALLUSERSPROFILE%\Application Data\VMware\VMware vCenter Converter Standalone

2. Change the SSL Key <useSsl> true </useSsl> to false



You may find it easier to alter/edit the file using Microsoft XML Notepad 2007 to edit the XML file. But Notepad or Wordpad can edit the file, just ensure, you make a copy of the original file for backup before making any alterations. Using XMP Notepad 2007, you do not have to scroll the contents of the file, and the <useSsl> section is quicker to find and edit, but whatever tool you find most comfortable to use to edit the file, is okay.
Change the following XML entry from

<useSsl> true </useSsl>

to

<useSsl> false </useSsl>

Save the XML file.

Edit converter-worker.xml using XML Notepad - value - true
Edit converter-worker.xml using XML Notepad - value - false

3. Restart Service

For changes to take effect - Restart "VMware vCenter Converter Standalone Worker" service.

4. Results


We have seen performance increases from at least 2x to 6x. So if you want to half the conversion time at least, then alter the encryption setting. If appropriate for your environment.

In the following example, a Windows 2003 Server was converted from Virtual Machine to Virtual Machine (V2V) using VMware vCenter Converter Standalone 5.0 installed on the server to be converted. In the first conversion (TaskId10) the SSL Key was left as the default TRUE, and encryption was used. In the second conversion (TaskId11), the SSL Key was set to false.

As can be seen from the following screenshots Average Transfer rate has increased from 2 MB/s to 6 MB/s and the conversion time has reduced from 1hr 38mins to 33mins.
.

 A performance increase of 60%! just by chaning a value from true to false.

Conversion with default XML value set to True
Conversion with default XML value set to false
Thank you for reading my article, please leave valuable feedback.
51
59,643 Views
Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)VMware and Virtualization Consultant
CERTIFIED EXPERT
EE Fellow, MVE, Expert of the Year 2021,2017-11, Scribe 2016-2012, Author of the Year 2018-6,2013-2012 VMware vExpert Pro, vExpert 2022-2011

Comments (36)

CERTIFIED EXPERT
Fellow
Expert of the Year 2021

Author

Commented:
@Mathiau - Correct!

Article was published 3 years ago!

Commented:
Wow ya, seems a few have kept it going..lol
CERTIFIED EXPERT
Fellow
Expert of the Year 2021

Author

Commented:
@Mathiau - The problem is the "cut and paste" and Google Monkeys, and have no idea, this has changed, three years later, because they have no experience, other than Google!

So 10 out of 10.....Mathiau for at least knowing what we call in the trade a "golden nugget!"

Thanks

Andy
Pete LongSolutions Architect
CERTIFIED EXPERT
Distinguished Expert 2020

Commented:
Andrew,

Witten in 2013, and helped me out today! I was running Converter 6.2, on an old Windows Server 2003 server (don't ask)
I can confirm that the XML was set to 'true' , I also upped concurrent tasks to maximum and concurrent tasks to maximum.
Conversion went from 12 Days 11 hours at 135Kbps (seriously)
to
3 hours at 35Mbps

Nice one ThanQ
CERTIFIED EXPERT
Fellow
Expert of the Year 2021

Author

Commented:
Thanks Pete, sometimes legacy articles and historic articles help....!!!!!

View More

Have a question about something in this article? You can receive help directly from the article author. Sign up for a free trial to get started.