A minor gotcha we ran into with our Virtual Center cluster last week and again possibly today. Virtual Center requires a SQL Server (Microsoft I know) to collect telemetry I think. Not really sure why, but it does. It is not critical to operations of any VM, but you do need it for VMotion, creating new VM’s and other admin work. Well when we built our ESX cluster we put our virtual center DB on the one sql server we had on the LAN in that office that had any amount of stability. Well we were wrong. It turns out that the machine we picked (a dev db) runs out of space because our DBA’s don’t pay attention to their backup schedules. I am making an assumption there but it has happened twice in a week and a half. Well when the server runs out of space, there goes virtual center. Jayson has all the details of the issue, but it boiled down to we couldn’t use our virtual center manager until it was fixed. It is our own fault for putting it on a dev box but it was our only option at the time. We are now just building our own SQL server that the operations group will own and all it will do is the virtual center db.
This ESX roll out is a learning experience, but I still believe that we are far better off with our current infrastructure over past non vmware setup.
Technorati Tags: SQL Server, Virtual Center, virtual infrastructure, VMware ESX Server