Read point ten:
You can configure the maximum number of database connections that can occur simultaneously. To limit the growth of the vCenter Server database and save storage space, you can configure the database to discard information about tasks or events periodically.
- In the vSphere Client, navigate to the vCenter Server instance.
- Select the Configure tab.
- Under Settings, select General.
- Click Edit.
- Select Database.
- In Maximum connections, type a number. Increase this number if your vCenter Server system performs many operations frequently and performance is critical. Decrease this number if the database is shared and connections to the database are costly. Do not change this value unless one of these issues pertains to your system.
- To have vCenter Server periodically delete the retained tasks, select the Enabled box next to Task cleanup.
- (Optional) In Task retention (days), type a value in days. Information about tasks that are performed on this vCenter Server system is discarded after the specified number of days.
- To have vCenter Server periodically clean up the retained events, select the Enabled box next to Event cleanup.
- (Optional) In Event retention (days), type a value in days. Information about events for this vCenter Server system is discarded after the specified number of days.
- (Optional) To monitor vCenter Server database consumption and disk partition, open the vCenter Server Appliance Management Interface.
- Click Save.
Optional) In Event retention (days), type a value in days.
Server information is discarded after the specified number of days, so if you reduce the days, the days saved after that date are automatically deleted.
If you decrease the days, the saves beyond that date are automatically canceled.
1 person found this helpful
Just follow KB 1025914 too free up the space for your DB to get vCenter working again. Keep in mind that some additional DB cleanup/merge tasks are needed of you perform a mass delete within a SQL DB.
Normaly my customers sets something between 30-60 days for the retension policy. IIRC VMware sets it to 30 days as default in todays installation. In the early days of Windows vCenter the boxed for limited Task/Events was unchecked.
The Kb actually resolved the issue as the vCenter database sized got decreased immediately after changing the retention period and executing the store procedure for the VCDB. Wondering if there any sql maintenance job that that runs at its schedule time to purge the stale records automatically.