- Run the same process as listed above
This solution is for vCenter Server hosted on a Windows OS. I am just providing the short and sweet version since VMware KB 7960893 provides very detailed information on this process.
- Create new database on new server
- Setup users on new database instance and provide security access with same permissions.
- Shutdown all vcenter services
- Shutdown all vcenter update manager services
- Backup databases
- Restore databases on new database server
- On vcenter server, copy all the scripts for SQL Agent rollup jobs that need to be recreated in new database server instance
- KB 1004382
- Update DSN entries for vcenter server and venter update manager to reflect new database server location.
- Start vCenter services
- Windows 2008 – C:\ProgramData\VMware\VMware VirtualCenter
- Other Windows versions – C:\Documents and Settings\All Users\Application Data\VMware\VMware VirtualCenter\
SSH to appliance.
Stop the service
- /etc/init.d/loginsight stop
Change log insight configuration file to new NFS location
- Vi loginsight-config.xml#
- /etc/init.d/loginsight start
- All and group options for dashboard commands
For the dashboard import, dashboard delete, and dashboard reorder commands, you can use one of the following options instead of specifying a user name:
The --all option applies the command to all user accounts. The --group:<group_names[,] option applies the command to all user accounts that belong to the specified user groups. For example, the command dashboard import group:Administrators,Operators "templates\MyDashboard.bin" imports the dashboard MyDashboard.bin to all user accounts that belong to the Administrators and Operators user groups.
The dashboard import command also has a --set option that enables you to set the dashboard order. For example, the command dashboard import MyUser2 "dashboards/MyDashboard.bin" --set 1 imports the dashboard MyDashboard.bin and makes it the first dashboard in the dashboard list for the user MyUser2.
Location of vCenter Server log files (KB 1021804)
vCenter Server 5.x and earlier versions on Windows XP, 2000, 2003: %ALLUSERSPROFILE%\Application Data\VMware\VMware VirtualCenter\Logs\
vCenter Server 5.x and earlier versions on Windows Vista, 7, 2008: C:\ProgramData\VMware\VMware VirtualCenter\Logs\
vCenter Server Appliance 5.x: /var/log/vmware/vpx/
vCenter Server Appliance 5.x UI: /var/log/vmware/vami
vpxd-profiler.log, profiler.log and scoreboard.log:
cim-diag.log and vws.log:
eam.log: Health reports for the ESX Agent Monitor extension, connectivity logs to vCenter Server.
catalina..log and localhost..log:
Location of vSphere Profile-Driven Storage log files (KB 2056646)
vCenter Server 5.x and earlier versions on Windows XP, 2000, 2003: %ALLUSERSPROFILE%\Application Data\VMware\Infrastructure\Profile-Driven Storage\Logs
vCenter Server 5.x and earlier versions on Windows Vista, 7, 2008: C:\ProgramData\VMware\Infrastructure\Profile-Driven Storage\Logs
vCenter Server 5.x Linux Virtual Appliance: /var/log/vmware/vpx/sps
Location of vSphere Web Client service logs (KB 2004090)
For vSphere 5.0, all the logs for the vSphere Web Client service are located at:
Windows: C:\Program Files\VMware\Infrastructure\vSphere Web Client\DMServer\serviceability\
For vSphere 5.1, all the logs for the vSphere Web Client service are located at:
Windows: C:\ProgramData\VMware\vSphere Web Client\serviceability\
For vSphere 5.5, all the logs for the vSphere Web Client service are located at:
Windows: C:\ProgramData\VMware\vSphere Web Client\serviceability\
Location of vCenter Single Sign-On log files for vCenter Server 5.1 and 5.5 (KB 2033430)
vSphere 5.1 using vCenter Single Sign-On 5.1:
vCenter Server 5.1.x on Windows Server 2003 – C:\Program Files\VMware\Infrastructure\SSOServer\logs\
vCenter Server 5.1.x on Windows Server 2008/2012 – C:\Program Files\VMware\Infrastructure\SSOServer\logs\
vCenter Server Virtual Appliance 5.1.x – /var/log/vmware/sso/
vSphere 5.5 using vCenter Single Sign-On 5.5:
vCenter Server 5.5.x on 2003 – %ALLUSERSPROFILE%\Application Data\CIS\
vCenter Server 5.5.x and 2008, 2012 – C:\ProgramData\VMware\CIS\
vCenter Server Virtual Appliance 5.5.x – /var/log/vmware/sso/
Lately been getting a lot of service status failures for the following vCenter Server services:
VMware vCenter Storage Monitoring service.
VMware vSphere Profile-driven Storage service
The monitoring service was the most frequent and non-impacting but now and then the profile-drive storage failed which caused large impact since users could not deploy or start vApps in vCloud director.
Turns out when we installed vCenter server for the first time we sized it for a small environment and current this is not the case anymore so with the heap sizes set to small for all services we started running into problems.
The only way to resolve this temporarily was to restart the vCenter server. Restart just the specific service did not always resolve the problem for us.
Looked in dslog files and found errors as follows:
Update the vCenter Server heap memory sizes for specified services to reflect the current size of your environment.
This table provides the JVM heap size recommendations:
vCenter Server 5.5:
|vCenter Server Inventory||VMware VirtualCenter Management Webservices (tc Server)||Inventory Service||Profile-Driven Storage Service|
|Small inventory (1-100 hosts or 1-1000 virtual machines)||512 MB||3 GB||1 GB|
|Medium inventory (100-400 hosts or 1000-4000 virtual machines)||512 MB||6 GB||2 GB|
|Large inventory (More than 400 hosts or 4000 virtual machines)||1024 MB||12 GB||4 GB|
Note:After adjusting the JVM heap size in the
wrapper.conf file, VMware recommends restarting the VirtualCenter Management Web services. For more information, see Stopping, starting, or restarting vCenter services (1003895).
Recently I logged into vCenter Operations Manager (vCOPS) custom UI and found that all objects stopped collecting stats.
Logged into vCenter server and tried health status tab but received connection error.
In Custom UI select Environment tab -> Configuration -> Adapter instances. Edit a vcenter instance and selected test. Received the following error
“Test was not successful. Connection refused to host: Secondvm-internal;nested exception is: java.net.ConnectionException: Connection refused”
I ran the same test on our VNX and Brocade adapter instances and received the exact same error.
In vCops Administration page under registration tab i selected the update bottom on vCenter Server registration and re-entered the password. After a long while i received an exception error.
I went to status tab and saw that some of the vCenter Operations Manager Statuses was not running.
I tried to start the service but did not work and status did not change nor did i get an error message.
I SSH into the Analytics VM and tried to manually restart the service “vcops-admin restart”. showed that the database was not coming online on which i though about looking at space.
Ran “df -h” and found that the /data drive was out of space.
Shut down vCops vapp container from vCenter server.
Edit the VM and add new disk.
Power on the vapp container.
vCops will automatically extend the /data drive with the newly added disk.