VCSA – The default choice. Always.

I’ve been a big proponent of the VMware vCenter Appliance for a long time, I even did a talk called VCS to VCSA Converter or How a Fling Can Be Good for You! on migrating to the VCSA at the Nordic VMUG last year.

The VCSA has gone through a few iterations and versions by now, coinciding with the vSphere releases.

History

vCenter Server Appliance 5.0 August 2011
vCenter Server Appliance 5.1September 2012
vCenter Server Appliance 5.5 September 2013
vCenter Server Appliance 6.0 March 2015
vCenter Server Appliance 6.5 TBA

Since v6.0 scaling has been on par with it’s Windows based counterpart, supporting the same number of  hosts and VMs.

When it comes to features, VCSA 6.5 surpasses the Windows version. New tools like the Migration Tool, vCenter High Availability, Backup / Restore and the new Management Interface are all exclusively available on the VCSA.

In my opinion, the most noteworthy of these are vCenter High Availability and the Backup / Restore options.

vCenter High Availability adresses one of the main concerns with vCenter in general since the discontinuation of vCenter Server Heartbeat in June 2014. This new HA setup enables you to have a passive VCSA ready if your active one should fail, with the added protection of a witness that keeps track of it all. This is a native feature of the VCSA, and not available in it’s Windows counterpart (or little brother as it is now…)

The Backup / Restore feature is very nice as well. One of the (few) arguments I’ve heard surrounding running the VCSA vs the Windows vCenter is surrounding backup. Thankfully the myth regarding image level backups of it was debunked in v6, but the new backup / restore functionality takes that a step further. Native backup is now available in the VCSA, either via the management interface or via a public API. The backup files (HTTP(s), FTP(s), and SCP transfer protocols are supported) make up the entire VCSA configuration, and you can restore those directly from the VCSA 6.5 ISO image in case of an emergency. This means that you can image level backups of the VCSA as usual, and script the backup file generation as added protection.

Also worth noting is that in v6.5, VMware Update Manager has been included in the VCSA, and runs natively on the appliance. The last argument for keeping your Windows vCenter has just disappeared.

With the upcoming vSphere 6.5 release it’s clear that the VCSA should be the default deployment model for a new vCenter. There is really no question about it anymore. #migrate2vcsa you should.

#vDM30in30 progress:

 

1 Comment

Leave a Reply