Out SQL database for VCenter has filled at one of our clients;
I've gone through and followed VMWare's database cleanup and purge KB's
VMware KB: Purging old data from the database used by VMware vCenter Server 4.x and 5.0.x
The problem I'm running into is that in our Tables there is no vpx_hist_stat1 table; only a view. There are however vpx_hist_stat1_1 through 240 and the same for 2_1, 3_1, 4_1
VMWare's script seems to only work for the vpx_hist_stat1,2,3,4 tables not all these different tables.
I've run the truncation and even shrunk the database size; it's been fully backed up. Purging the old data seems to be the part I can't get complete due to missing tables. Does anyone else have any thoughts? Without our DB under 10gb, the vSphere doesn't see the VM's in vCenter except as orphaned and our Veeam backups fail.
Welcome to the Community,
I'm not sure about the different tables. Anyway, unless already done, you may check which table(s) consume the most space, to see what needs to be cleaned up. Take a look at http://kb.vmware.com/kb/2005333 (Step 5) for an SQL query which shows the current space usage.
André
Hi,
as workaround you can migrate your Express database to FULL SQL 2008 Server see:
VMware KB: Migrating the vCenter Server database from SQL Express to full SQL Server
_________________________________________________________________________________________
If you found this or any other answer helpful, please consider to award points. (use Helpful or Correct buttons)
Regards,
P.
if you are in vcenter, then you should be able to see your own vcenter VM and expand the drive(that is, if your vcenter is a VM)
