Hello.
3 ESXi Hosts 5.1.0, 1463097 in a cluster.
MS SQL 2008 R2 server (SQL Server 10.50.2500) on a VM MS Windows 2008 R2 Standard server.
Instance name VIM_SQLEXP
DB name: VIM_VCDB.
Recovery model: Simple
DB growth by 1MB unrestricted. Current Database size: 3887MB
Log growth by 10% restricted to 4GB max. Current size after shrink this morning 2MB BUT
Every morning the log file has almost run full but the VMware VirtualCenter Server service is running and I can start the vSphere Client. I know if I don't shrink the log the service will stop later today or tomorrow.
I have studied and followed
Determining where growth is occurring in the VMware vCenter Server database (1028356),
SQL Server Recovery Model Affects Transaction Log Disk Space Requirements (1001046)
Troubleshooting transaction logs on a Microsoft SQL database server (1003980)
but I can't see any table growing that much. I can see that VPX_EVENT grew about 28MB over night but nothing else looks alarming.
Any ideas what it could be?
Best Regards
Peter Rasch Lageri
Denmark
Hello,
some time ago i faced similar situation than you.
I would recommend you to check carefully this, maybe it will be helpful:
Troubleshooting when the vcenter db transaction log becomes full (MS SQL server 2005 express)
Best regards,
Pablo
At that level you have the VC Statistics?
Statistics Level 1 on all.
and while we are at that, Task and Events are retained for 60 days both.
Best Regards
Peter
Ok,
Please, aplly this KB:Purging old data from the database used by VMware vCenter Server 4.x and 5.x (1025914)
Also look at you the following KB
Investigating the health of a vCenter Server database
Creating a Maintenance Plan for SQL Server 2008 R2 for vCenter/UpdateMgr
I have done the first one earlier. The Event Viewer Application log stated that the full log file was the reason that the service stopped.
Management plans are not available in that version of SQL Express.
Best pratices could be interesting but the installation is a rather small one, 3 hosts and 11 VMs.
Best Regards
Peter
Ok, upload the diagnostic logs of VC
Hello,
some time ago i faced similar situation than you.
I would recommend you to check carefully this, maybe it will be helpful:
Troubleshooting when the vcenter db transaction log becomes full (MS SQL server 2005 express)
Best regards,
Pablo
BINGO!
That solved it! Thank you. I had data from january this year which was double the amount expected. Now it's down 60 days as set in the GUI.
GREAT. Standing ovations are in order here.
Absolutely Best Regards
Peter