The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides
Purging old data from the database used by VMware vCenter Server 4.x and 5.x (1025914)
- VMware VirtualCenter Server service starts, then fails
- The transaction logs are working correctly
- You observe excessive growth of the
- You see this error message in the Microsoft SQL Event log:
Could not allocate space for object 'dbo.VPX_EVENT'.'VPXI_EVENT_USERNAME' in database 'VCDB' because the 'PRIMARY' filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup.
- Viewing the Disk usage by tables report shows the
VPX_EVENT_ARGtables utilizing the maximum space.
- These troubleshooting steps do not help resolve the issue:
- Purging the old data
- Truncating tables
- Shrinking the logs and database
- Recreating Roll up jobs
To access the Database Retention Policy setting in the vSphere Client, click Administration > vCenter Server Settings > Database Retention Policy.
The scripts attached to this article support purging the performance data from vCenter Server.
Caution: Do not run the scripts attached to this article against a VirtualCenter 2.x database or a vCenter Server 5.1 and 5.5 database.
- For information about purging data in VirtualCenter 2.x, see Purging old data from the database used by VirtualCenter 2.x (1000125).
- For vCenter Server 5.1 and 5.5, see the To truncate all performance data from vCenter Server 5.1 and 5.5 section in Reducing the size of the vCenter Server database when the rollup scripts take a long time to run (1007453).
- SQL Express 2005/2008 (vCenter Server 5.x is bundled with SQL Express 2008) supports a maximum of 5 hosts and 50 virtual machines. If your environment exceeds these thresholds, you must upgrade your database to SQL Standard edition.
Note: This video was originally created for Knowledge Base article Purging old data from the database used by VirtualCenter 2.x (1000125). However, the steps can be used for this article as well.
Caution: The scripts attached to this article are intended for execution by database administrators (DBAs) who are experienced with using database client tools to execute SQL commands. The purpose of the scripts is to delete data. VMware strongly recommends that you stop the VirtualCenter Server service and take a full, reliable backup of your database before attempting this process.
- If you are using SQL 2005 Express, you may need to download and install Microsoft SQL Server Management Studio Express.
- If you are unable to download the scripts attached to this article, please contact VMware Support. For more information, see How to Submit a Support Request.
The database transaction log may fill up during this procedure if sufficient disk space is not available. For SQL Server, if the required disk space cannot be made available, one option is to utilize the "simple" recovery model on the database for the duration of this operation.
Warning: The VirtualCenter Server service must be stopped while the script is running. For more information, see Stopping, starting, or restarting vCenter services (1003895).
- If the database is very large it may take a very long time to run this script. Running the script increments by changing the default cutoff days of 180, which represents 6 months. For example, assuming you have one year of data (365 days) you can increase this to a larger value such as 330 at first, and this will purge only about one month of data. You can then run the script with a cutoff date set to 300 to purge another month of data.
- If the scripts fail to run because of a lack of available database space, you may need to truncate your performance data. If you want to truncate all performance data instead of purging it, see Reducing the size of the vCenter Server database when the rollup scripts take a long time to run (1007453).
- If the database has reached a 4 GB limit in SQL Express, the database is corrupted, or if vCenter Server is unavailable for any reason, purge the
event_argtables either by manually enabling the database retention policy in the database using SQL Studio, or by running the stored procedure to purge the data from these tables.
- The vCenter Server database is usually named
VIM_VCDB, unless it was renamed during initial creation.
- Connect to
Servername\SQL Databaseand log in with the appropriate credentials.
- Click databases to expand and select VIM_VCDB > Tables.
- Right-click the dbo.VPX_PARAMETER table and select Open.
Note: If you are using SQL Server 2008, right-click the dbo.VPX_PARAMETER table and click Edit Top 200 Rows.
- Modify event.maxAge to 30, and modify the event.maxAgeEnabled value to true.
- Modify task.maxAge to 30, and modify the task.maxAgeEnabled value to true.
Note:To improve the time of the data cleanup, run the preceding steps in several intervals. To do this, ensure to keep the default value of event.maxAgeand task.maxAgeand perform step 6 to run the cleanup. Then, reduce the event.maxAgeand task.maxAgevalue by 60 and run the cleanup. Repeat the steps until the value is reached to 30 for the final cleanup process.
- Run the built-in stored procedure:
- Go to VIM_VCDB > Programmability > Stored Procedures.
- Right-click dbo.cleanup_events_tasks_proc and select Execute Stored Procedure.
This purges the data from the
vpx_tasktables based on the date specified for maxAge.
- When this has successfully completed, close SQL Management Studio and start the VMware Virtual Center Server service.
- Using the vSphere Client, log into vCenter Server as an administrator.
- Go to Administration > vCenter Server Settings > Statistics.
- Under Statistics Intervals, ensure the Statistics Level column is set to 1.
- To change the value, select the Interval Duration, click Edit and select Level 1 from the dropdown.
- The execution of
dbo.cleanup_events_tasks_procmay take a long period of time depending on the database size.
- The operation may fail due to the transaction logs being filled up at multiple intervals based on the data to be purged. You must shrink the Transaction logs when required and run
- vCenter Server 5.1 and vCenter Server 5.5, see Reducing the size of the vCenter Server database when the rollup scripts take a long time to run (1007453).
- IBM DB2 databases, see Reorganizing the database. Engage your database administrator to perform any required changes.
- filing a support request with VMware Technical Support, see Filing a Support Request in My VMware (2006985). Note this Knowledge Base article ID (1025914) in the problem description.
Note: When the vCenter Database has been purged, you may notice an improvement in the performance of the vSphere Client connected to the vCenter Server.
For translated versions of this article, see:
- Español: Depurando la base de datos usada por vCenter Server (1034673)
- Português: Como limpar dados antigos do banco de dados usado pelo vCenter Server (2037293)
- 日本語: vCenter Serverで使用しているデータベースから古いデータのパージについて (2014792)
Note: The external links present this article were correct as of May 28, 2014. If you find a link is broken, provide feedback and a VMware employee will update the link.
- Reducing the size of the vCenter Server database when the rollup scripts take a long time to run (1007453)
This Article Replaces
Request a Product Feature
To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.