Past two months I’ve received three calls from customers who’s vCenter suddenly stopped working because their SQL database had stopped because the logs had filled up. Turns out few people regularly check the status of their SQL database. VMware has written some very good KB articles on what to do when your SQL DB fills up and stops. So this blog post is only a wake-up call for you to check on your database.
Some good KB articles from VMware on this subject:
- Purging old data from the database used by vCenter Server
- Purging old data from the database used by VirtualCenter 2.x
- Defragmenting VirtualCenter performance data indexes on a Microsoft SQL database
- Investigating the health of a vCenter Server database
- Migrating an existing vCenter Server database to 4.1 using the Data Migration Tool
- Migrating to vCenter Server 5.0 using the Data Migration Tool
- Starting the VMware VirtualCenter Service service fails with the error: Windows could not start the VMware VirtualCenter Server on Local Computer
From Josh Atwell I got this tip: Size Matters, especially when your database is full.