Virtualising a DB server

Soldato
Joined
5 Jul 2003
Posts
16,206
Location
Atlanta, USA
Hi all,
Has anyone got any tips for virtualising a database server.
Im planning on doing a P2V conversion of our dangerously slow physical Db server onto a much faster virtual host.

Any tips beyond disk IOPs that i should be aware of?

Thanks in advance all. :)
 
Hi,

Done this with a few old 2003 DB servers. Depending on whether your going to do an online or offline migration i'd suggest stopping the SQL service so no new data is written during the migration.
I'll probably do it offline over a weekend. :)


If possible do not P2V it. Create a new DB server and migrate the DB onto it.
Why?

Without looking at trending information its hard to tell. Why is it slow. Because it is being hammered or the hardware is old?
Old hardware, almost no resources free, too expensive to upgrade the hardware, etc;
 
P2V should always be used as a last resort,
Its not really all that feasible to move DB's off a server and create a new one.
Having to redo all the permissions, repoint database locations in apps, etc; is both a massive ball ache and in some scenarios, not even possible. :(

Right, so basically, as long as i stop the relevant services, everything should be hunky dory! :)
 
For the love of god don't get rid of the old box. Not at least until it is fully tested and has been in production for a while. I have a bit better insight than most on how P2V's actually work, I used to be an engineer for Platespin. We had major issues with Microsoft, specifically with AD, different variations of HAL's, etc. In any case try the P2V, if it works, great. But ensure you do full testing afterwards and you keep the box on standby just in case. A lot of my techie calls where from clients where we would P2V DC's, DB servers etc and issues became apartment a long time after it had actually happened.

Anyway good luck mate, hopefully it will be smooth sailing!
Always do, i always make sure i have a 'back out option' where i can. :)

Jobs a good'en then! Will give this a go in the coming weeks. :)

Thanks for the input everyone.:)
 
As an update:
Job done! :)

Went suprisingly smoothly.
3 hours to do the entire thing, and works sweet as a nut thus far!:eek::D

Can start monitoring performance come Monday afternoon when all the DB's get hammered, see what's limiting it if anything.

Thanks for the input everyone. :)
 
Glad it went OK!
Suprised me how well it went.
Couldnt be bothered waiting a few days for it to do almost a tera's worth of drives, so i gave it a go with resizing down to what it should be instead, went really quick, end of day one of DB usage, not a single issue.:cool:
 
Last edited:
Back
Top Bottom