P2V migration times and recommendations

[rafaelmartin]

Hi List,

We need to virtualize aprox. 400 physical servers in VMWare VI3 and blades.

To design the master project and estimate dates, we take the example in vmware web page:

I think the time to design/create deliverables in the project is fine, but I need to optimize the time in migration phase, in other words, how to make the migrations in smaller possible time.

For example, in my labs I used HP VMMP to perform migrations tests, and the used time for one server was 100 min aprox (Win 2003, partition C: only, 10GB data, HD 36Gb - RAID1, gigabit network) ; this includes copy time, drivers install, reboots, basic opreations like ping, DNS, etc.

Assuming these features, I calculate a ratio of 2 or 3 servers per day for migrations.

I really would appreciate the experience and comments you have in projects like this, specially REAL TIME TAKED in customer migrations, recommendations, best practices, problems found in field, precautions and evertything you think could be important to mention.

Thanks!

Rafael

[esiebert7625]

Which product do you plan on using for your P2V's?

With Converter I've done about 50 conversions. The amount of time Converter takes can vary based on a few factors. Converter uses two different clone methods based on if you are re-sizing the source computers disks or not. With block-by-block cloning (no resize) the copy times are fairly consistent because it is copying at the disk block level. I saw an average of about 10-12GB per hour on 100Mbps, with gigabit you should be able to get about 20-30GB an hour. You would expect gigabit to be 10 times faster but it seems like the clone process does not take full advantage of all the bandwidth available. With file-by-file cloning (resize disks) the speed can vary widely based on the total number of files to be copied and their sizes. Lots of small files takes alot longer then copying a lesser amount of larger files.

Check out the below links for more information on Converter...

Best Practices - http://vmware-land.com/Converter.html

Converter tutorial - http://www.petri.co.il/virtual_convert_physical_machines_to_virtual_machines_with_vmware_converter.h...

Introducing the Next Generation of P2V: Vmware Converter 3.0 - http://download3.vmware.com/vmworld/2006/tac9453.pdf

Converter FAQ - http://www.vmware.com/products/converter/faqs.html

Converter 3.0.1 Manual - http://www.vmware.com/pdf/VMware_Converter_manual301.pdf

Converter 3.0.1 Release Notes - http://www.vmware.com/support/converter/doc/releasenotes_conv301.html

Converter Data Sheet - http://www.vmware.com/pdf/converter_datasheet.pdf

What machines should not be converted - http://www.vmware.com/community/thread.jspa?threadID=73357

Fyi…if you find this post helpful, please award points using the Helpful/Correct buttons.

-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-=-

Thanks, Eric

Visit my website: http://vmware-land.com

-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-=-

[rafaelmartin]

I am evaluating to use HP VMMP (Server Migration Pack) and/or VMConverter.

The hardware for the new VI3 infraestructure is based in HP c-Class blades, and I have some experience in VMMP Products.

Another question.

What do you think about hot clonning?,

I have an HP recommendation that this only be used for testing purposes or for non-critical and relatively static servers.

Regards,

[esiebert7625]

I have not been impressed with the HP migration products.

Hot cloning works pretty well but should only be used for certain types of servers. Transaction sensitive servers like SQL/Oracle/Exchange should definitely be cold-cloned. I hot-cloned about 75% of my servers, it works great for servers that have mainly static content like web servers.

P2V Product Comparison - http://www.vmug.nl/downloads/PQR-Virtualization_Migration_Solutions%20Feature%20Matrix.pdf

Converter snapshot during hot migration - http://www.vmware.com/community/thread.jspa?threadID=87540&messageID=660907

http://www.vmware.com/community/thread.jspa?messageID=722132&#722132

http://www.vmware.com/community/thread.jspa?messageID=739252&#739252

[Ken_Cline]

I'm going to disagree (sort of) with Eric on the hot cloning thing...I don't ever like to use it for PRODUCTION boxes. Unless you're very careful and turn off any application-related services, you have the POTENTIAL to have your "clone" and your source not being identical.

That being said - I love hot migrations for capturing a copy of a production server for use in a dev/test environment!

[esiebert7625]

Yeah I might agree with that, the last post I made had a link to Pangchen talking about the hot clone snapshot process. If you can cold-clone it is always preferrable over hot-cloning. Out of dozens of hot clones I only had an issue with one of them which had corrupted and missing files.

[rafaelmartin]

Thanks Ken, Eric!

Rafael

[esiebert7625]

No problem, don't forget to award points for helpful answers using the Helpful/Correct buttons....thanks

[jjohnston1127]

I've only had problems hot-cloning a domain controller. The only reason we did that is because it was the business' critical server that ran everything - file shares, domain, etc. Poor design, but its what they had available. Sometime during the process the netlogon share and the file replication service got hosed and screwed it up.

Granted, a DC is the only "live" server I've tried migrating. Most servers are just file servers, web servers, utility servers, etc.

VMWare Converter is probably the only thing I'd ever use unless for some reason it wouldn't read the disks.

[esiebert7625]

Yeah DC's are usually a big no-no when it comes to converting. It's just as easy to build a new DC as a VM and dcpromo it.