Wednesday, April 14, 2010

Better performance on VMWARE converter

At this point you might be realized that one of the activities that take most of the time of a P2V migration is the copy of the data from the physical server to the virtual one.

Well let’s take a look how can we boost your migration.

My advice here just applies to HOT migration, OK ?!?!

So, depending on your choices during the convert wizard you end up with better or poor performance, that’s why your data will be copy or block-level or file-level to.

Block-level is always faster than file-level. And how do you choose one of them ?

Block-level will be used when you maintain or extend the disk on the target.
File-level will be used when you choose a smaller disk on the destination.

Then you asked me, but the feature to reduce the disk size on the destination is something cool to reclaim unused space and save some money with storage.

Yes it is. But depending on your volume size, your P2V cool takes forever to finish and eventually failed.

My advice is to try to use block-level and when the machine is virtualized you can use sVmotion to reduce the disk to thin, saving your storage.

Remember all P2V creates tick disks.
To save storage consumption convert them to thin with sVmotion.

1 comment:

Cinthia Bracco said...

Você está mesmo gostando dessa vida de "blogueiro". Bjo

Post a Comment

Who am I

My photo
I’m an IT specialist with over 15 years of experience, working from IT infrastructure to management products, troubleshooting and project management skills from medium to large environments. Nowadays I'm working for VMware as a Consulting Architect, helping customers to embrace the Cloud Era and make them successfully on their journey. Despite the fact I'm a VMware employee these postings reflect my own opinion and do not represents VMware's position, strategies or opinions.

Most Viewed Posts

Blog Archive