vSphere4 and VMware Converter

We're about to convert a critical SQL server and 2 Exchanger servers to run on vSPhere4 and have a few questions

To convert we're going to run a cold-clone but it doesn't appear to have the option to set Thin Provisioning.  Do we need to convert the server first and then move to another datastore and choose Thin Provisoining for the migration.  Or is there another way?

Secondly, after conversion do people bother with removing the redundant hidden NICs.  I'd have thought it's no biggie as it would have to be a very deliberate\daft act to re-enable?

And finally, after previous conversions weve found we sometimes need to remove the new VM from the domain and readd.  We dont really want to have to do this with our critical server, particularly Exchange.  Are we doing something wrong?


kswan_expertAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Paul SolovyovskySenior IT AdvisorCommented:
We're about to convert a critical SQL server and 2 Exchanger servers to run on vSPhere4 and have a few questions

To convert we're going to run a cold-clone but it doesn't appear to have the option to set Thin Provisioning.  Do we need to convert the server first and then move to another datastore and choose Thin Provisoining for the migration.  Or is there another way?

--You don't need to do a cold-clone, I would shutdown the SQL Services.  The only way to make it thin is to choose the option "copy all disks and maintain layout" otherwise you'll have to go with a flat volume structure.  This can always be changed using sMotion I believe by copying to a different store and choosing thin.

As part of the conversion you can choose to shutdown the old server and bring down the VM.

Secondly, after conversion do people bother with removing the redundant hidden NICs.  I'd have thought it's no biggie as it would have to be a very deliberate\daft act to re-enable?

--As part of good practice remove any hardware that's not used, nics, serial, parellel ports, etc..

And finally, after previous conversions weve found we sometimes need to remove the new VM from the domain and readd.  We dont really want to have to do this with our critical server, particularly Exchange.  Are we doing something wrong?

--normally not needed but I would also remind you to remove and hardware specific apps, such as HP Insight Agents, and Dell OpenManage software, these take a good chunck of resources.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
VMware

From novice to tech pro — start learning today.