Enhanced vMotion Compatibility: When not to engage? Never.

We’ve all been there.  We setup that cluster and the question of EVC comes up.  I say always enable EVC if you are deploying either from an internal or customer perspective in the Managed Hosting space.

So Take a first example.  You are.

1. A MSP (or any other type of orgainization using VMware 5.0 and higher)

2. Deploying a new cluster of freshly purchased hardware.  Lets just say its 20 hosts.

3. Intended use is for customer deployment that may or may not need to grow in the future.

I say you always set EVC to the highest chipset level possible for the new hardware.  That way if the customer does decide to expand:

a.  they can add to their cluster when expansion comes to roost

b.  When the time for expansion comes they can decide at that time whether to go with a new cluster on the faster hardware or add to the existing.

Obviously, if you don’t then they are forced to start a new cluster.  This may or may not align with the customers needs, but its important to retain the flexibility to meet the customers needs, so I say EVC at the highest possible level.

I also say the same remains true even if you are not an MSP or an MSP deploying a cluster internally.  Yes, you will lose the chipset features of the newer servers, but at least you have the choice at a point in the future to decide to make that sacrifice or not.

If you feel differently, I’d love to learn why EVC should never be used.  Let me know your thoughts and comments.


Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s