This video demonstrates how to troubleshoot “SSO log directory full” warnings in vCenter Server Appliance 6.0. This is a known issue affecting vCenter Server Appliance 6.0, and currently, there is no resolution. You see that the /storage/log directory is highly utilized in an Embedded vCenter Server Appliance or Platform Controller Server Appliance 6.0.
To work around this issue, reduce the maximum backup size and the maximum backup index in the log4j.properties file.
Note: In external Platform Service Controller (PSC) environments, log in to the Platform Service Controller instead to make the suggested changes.
We thought a few more of you might have the same questions so we decided we would take the opportunity to explain the differences between vCenter server and vCenter appliance and under what situation which one should be opted for, over the other.
The vCenter Server Appliance (vCSA) is a preconfigured Linux-based virtual machine optimized for running vCenter Server and associated services. Versions 5.0.1 and 5.1 of the vCSA uses PostgreSQL for the embedded database instead of IBM DB2, which was used in vCenter Server Appliance 5.0 The vCSA embedded postSQL DB supports 5 hosts / 50 virtual machines, with an Oracle DB the vCSA can support 1000 hosts and 10,000 vms. If you configure your vCSA to use an external instance of Single Sign On (SSO), the external SSO instance must be hosted on another vCenter Server Appliance; it cannot be hosted on a Windows machine.
vCenter Server can be installed on a windows Guest OS and can be connected to Oracle or Microsoft SQL. SSO can be installed on the same Guest OS or can be on a different machine. It should be noted that patching of of the vCenter Appliance is not supported.
Below is a table listing more of the differences between the products.
vCenter Server Appliance
Any Supported Guest OS
Preconfigured Linux-based virtual machine (64-bit SUSE Linux Enterprise Server 11)
Supported Versions SQL Server and Oracle.
PostgreSQL (built-in ) can have 5 hosts and 50 Virtual Machines.Supported External Oracle database.
2 vCPU and 4 GB RAM
2 vCPU and 4 GB RAM
Physical or virtual machine
Using binary provided in .zip or .ISO
Can be installed on same vCenter Server or on separate Guest OS.
Single Sign On (SSO)
Can be installed on same vCenter Server or separate Guest OS.
IPv6 and IPv4 Support
SRM (Site Recovery Manager)
Compatible with SRM
Compatible with SRM
vSphere Web Client
Can be installed on same vCenter server or separate machine.
Can be installed on vCenter Server or separate server and configured using plug-in.
Pre-installed and does not have plug-in.
ESXi Dump collector
Can be installed on vCenter Server or on a separate Guest OS.
We have a new video for your viewing pleasure today and this video will be of specific interest to any of our vSphere vCenter Server Appliance users.
This video discusses and demonstrates upgrading the VMware vCenter Server Appliance from version 5.0.x to 5.1. This tutorial is based on VMware Knowledge Base article Upgrading vCenter Server Appliance from 5.0.x to 5.1 (2033990). All of the steps performed within this video demonstration are also documented in that KB.
The upgrade process is relatively straight forward and easy to follow.
Note: For best viewing results ensure that the 720p HD quality setting is selected and view in full screen mode.
We have a new video uploaded to our VMware KBTV YouTube channel today.
In this video tutorial you will see the process for downloading and deploying the vCenter Server appliance. The process is rather straight forward and easy to follow. In just a few steps you will be able to download the appliance and run it within your own VMware virtualized environments.
For the purpose of this demonstration we used an ESX 4.1 based host in order to deploy the appliance, which is a really old version at this stage, but the process is relatively the same across all of the more recent ESXi versions.