VMware vCenter Installable vs. Appliance
VMware vCenter Server Virtual Appliance (vCSA) is a VMware’s official VA that can be used as an alternative way to implement a full vCenter Server, instead to install on a Windows Server (that must be deployed first). Unlike the installable version, it does not need a Windows Server license and instance, but is rather based on a Linux distribution (SuSE Enterprise).
Across the various versions after the 5.0, this appliance has been improved to make it more effective and optmized, both in the deploy (available finally also in the form of single OVA file), both in the occupation of space (now the downloadable OVA is smaller also the ISO). Also the embedded database has been improved from the in-flexible IBM DB2 has changed to a more function PostgreSQL (or vPostgres as named by VMware). And finally the upgrade process has been improved and simplified.
With the release of vSphere 5.5, vCenter Server Appliance has become even more attractive not just for test environments or small installations, but also for medium and large size, because it introduces new limits(using the embedded database): maximum 100 hosts or 3000 VMs.
So vCenter Server Appliance could be the solution and the first option in your deployment? Here are the possible drawbacks:
- it’s a virtual appliance, this can be an advantage or a disadvantage depending on your point of view
- can only be deployed as a virtual machine
- it requires more memory rather than the installable version (minimum 8 GB RAM), however if you install the embedded database and put the vSphere Web Client Server on the installable version, it easy requires the same amount of memory
- it supports only its embedded database or an external Oracle database, Microsoft SQL Server is currently not supported
- it lacks of the linked mode support, that limits its use in large environments with multiple vCenter Server (actually could not then be a limit if these large environments are managed by vCloud Director or VMware Horizon View, where the management interface will be another one than and vCenter Server is just an infrastructure block)
- there isn’t a Linux version of vSphere Update Manager (VUM), so you need a Windows server for implement it (and then you lose the advantage of saving a Windows license and certainly no longer have the approach to single appliance that implements all services in a box)
- there isn’t a Linux version of VMware Horizon View Composer, so you need a Windows server for implement it (and then you lose the advantage of saving a Windows license and certainly no longer have the approach to single appliance that implements all services in a box)
- vCenter Server Linked Mode does not work (it is based on Active Directory Lightweight Directory Services instances)
- vCenter Server Heartbeat is not compatible with vCSA and the only solution for the vCenter Server high availability remain VMware HA (which may be fine for most cases, but does not meet some more strictly SLAs)
- there may be problems with some plugins, especially in the case of plug-ins for the old vSphere Client
Of course there are several pros:
- deployment is really faster (in 10 minutes you have a system ready to be configured)
- the download is simplified (and even more compact that the ISO vCenter install)
- update is relatively simpler than the installable version and can update/upgrade not just the vCenter Server but also the entire machine
- in version 5.5, its embedded database can cover many of the needs of SMB and medium-sized enterprise
- already includes an embedded database and all the components of vCenter Server (apart VUM), including the Dump and Syslog Collector
- the Web Client server part is already included and ready for use (more time saved in the deployment, although from version 5.5 this part became also a default component installed by Simple Mode)
- is a virtual appliance, with the advantages of a black box approach, but there could be also some disadvantage depending on your point of view
Leave your comments or questions.