Managing vCenter Server database space requirements
search cancel

Managing vCenter Server database space requirements


Article ID: 338818


Updated On:


VMware vCenter Server


By default, vCenter Server does not apply a retention policy on the data stored in the vCenter Server database and retains all the database table information with the exception of performance data. By design, performance data is retained for one year. The database always keeps growing to eventually consume all the available disk capacity and preventing the database server and vCenter Server from functioning properly.

The lack of control might result in customers databases growing to the point where it might impact the functionality.


VMware vCenter Server 6.0.x
VMware vCenter Server 5.5.x


Determining what is growing in the vCenter Server database

The vCenter Server database is a complex database and there are several areas that can cause problems. Out of the many tables in vCenter Server, there are very few which accumulate data during regular operation. These tables do accumulate data during regular operation:
vpx_sample_time1 to vpx_sample_time4
These tables store the reference time frames for the performance data in the vpx_hist_stat tables.
vpx_event and vpx_event_arg
These tables store the event information from the Tasks and Events tab in vCenter Server.
These tables store the task information from the Tasks and Events tab in vCenter Server.
This small subset of the tables in vCenter Server accounts for the majority of cases that are showing substantial growth in the database. For more information, see Determining where growth is occurring in the VMware vCenter Server database (1028356).

Configuring Database Settings

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. For more information, see the Configure Database Settings in the vSphere Web Client section in the VMware vSphere 5.5 vCenter Server and Host Management guide.

Truncating performance data


Manual Options

Administrators can also manually resolve this issue by using one of these methods:
  1. Backup the vCenter Server database first. For details on backup, see the knowledge base articles listed below:

VMware Knowledge Base Articles:

Other references:

  1. Purge the vCenter Server database manually. See Selective deletion of tasks, events, and historical performance data in vSphere 5.x and 6.x (2110031)

You can also use these options to manage the vCenter Server database space requirements:

See Also:

Monitor vCenter Server Appliance database disk usage (2058187)

Reducing the size of the vCenter Server database when the rollup scripts take a long time to run (1007453)

Note: If any other table is showing growth, file a support request with VMware Technical Support and note this KB Article ID in the problem description. For more information, see How to File a Support Request.

Note: The preceding links in this article were correct as of September 16, 2014. If you find the links are broken, please provide feedback and a VMware employee will update the link.

Additional Information

For translated versions of this article, see:

Details about this error is mentioned in the Resolved Issues under Upgrade and Install section of vCenter Server 5.5 Update 2 Release Notes.