Server sluggish after vCenter upgrade to 4.0

I nopticed the server got really sluggish after the vCenter upgrade from 2.5 to 4.0 32-bit.  I also upgraded VIC and Update Manager to 4.0
Looks like the sqlsvr and tomcat6 processes occupy almost all the RAM.  Leaving only 50MB out of 4GB.

Reboot helps but then those processes slowly grow and server gets sluggish again.

Please advice
LVL 17
Tiras25Asked:
Who is Participating?
 
Tiras25Connect With a Mentor Author Commented:
I thin I found the problem.  The vcdb SQL 2005 database grew to 20GB.  I am working on shrinking it back to 20 days history now.  I will report back once completed.

Thank you.
0
 
FerrostiCommented:
In case your SQL servers database is located in a VM file system you will have a massive bottleneck there which will consume lots of CPU cycles as well as RAM. Could this be the case? If VMWare did bad on the VM disk abstraction layer this would be something to have a look at.
0
 
Tiras25Author Commented:
Got it.  Looks like I will have to open a case with VMWare.
0
The 14th Annual Expert Award Winners

The results are in! Meet the top members of our 2017 Expert Awards. Congratulations to all who qualified!

 
Luciano PatrãoICT Senior Infraestructure  Engineer  Commented:
Hi

vCenter consumes some CPU with the tomcat's. Some times is 2% to 10%, but sometimes is about 80% to 100%. It depends what vCenter is doing, or if there is any 3tr party software connected to the vCenter(like backups, or other management tool) and this will consume some of the CPU trough tomcat's.

Also the SQL will take some of the CPU, but not as the tomcat's.

Take a look at this articles:

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1022137

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1022101

Jail
0
 
Tiras25Author Commented:
Looks like the sqlsrv.exe process increases drastically as I look at it.  
The thing is it didn't happen before the upgrade.  I also upgraded the dev enviroment from 3.5 to 4 and didn't see that issue.
0
 
Paul SolovyovskySenior IT AdvisorCommented:
Try this:

Install a fresh vCenter on a VM or a different physical system or re-install from scratch.  If you don't have custom alert notification this shuoldn't take too long.  I have seen strage things when the database says that it's upgraded but after installing a new install with a new database the issues go away.  You should also run the scripts to enable additional alerts in 4.0 if you haven't done so already.
0
All Courses

From novice to tech pro — start learning today.