VCSA

Overview A few weeks ago VMware released vSphere 6.7U1, and in that release comes a tool that has been desired by many customers and partners, which is the vCenter Converge Tool, or in other words, a tool to convert an external vCenter and PSC architecture in to an embedded deployment. In the last few releases of vCenter Server, VMware have supported replication of the PSC functionality between embedded deployment models, including Enhanced Linked Mode (named Embedded Linked Mode for an embedded deployment). It has been clear that the embedded model should now be the default model and it is the recommended model from VMware, in fact last week VMware announced their plans to deprecate the external PSC, but until today we did not have a way to automatically converge an external model in to an embedded model. ...

Update 27th October 2018: I was meant to provide this update last weekend, but it has been a hectic week. Within a few hours of posting this issue, a few people at VMware reached out to me to understand more about my configuration, asked me to upload the logs and a few of the smart guys and gals at VMware had been able to reproduce the issue. As it turns out, the key in the APPLMGMT_PASSWORD vecs store is used when a file based backup of the VCSA is scheduled. I believe a KB is on the way, but the workaround is to delete the VCSA backup schedule, perform the converge and you can then re-enable the schedule after the converge is complete. ...

This one will be a quick post, but I wanted to alert people to a new minor but useful feature that’s included in the vCenter 6.7 appliance, which is the ability to schedule backups natively within the appliance management interface. If you wanted to schedule an appliance based backup in 6.5, you would have to schedule a task to do so. Thankfully this was made easier by Brian Graf’s script, but now we have a way to build this in to the appliance configuration with no reliance on an external script. ...

[toc] Introduction Starting from VMworld US 2017, VMware announced their plans to support PSC replication and Enhanced Linked Mode with the vCenter Embedded deployment model, simplifying overall deployment and management requirements for a multi-vCenter environment. This feature is now included in the release of vSphere 6.7. In this post, I go over a little history for common deployment models, as well as what the new “vCenter Embedded Linked Mode” brings to the table. I also compare a couple of topologies between vSphere 6.0/6.5 and vSphere 6.7 to show the savings in the amount of nodes and in some cases, the complexity, that can be saved by using this new deployment topology. ...

I’ve recently been doing a lot of work in my home lab, which has involved me moving from a flat /24 network (yeah, I know) to a somewhat more realistic lab environment with a Cisco SG300 switch and Ubiquiti EdgeRouterx. Due to these networking changes, as I build out the environment I’ve been creating a lot of VLANs and subnets between my physical ESXi host, the Cisco switch and the ERx. ...

The post below will walk through the deployment of an embedded vCenter Server Appliance 6.5 using the GUI installer, where the PSC and VC roles are installed on the same servers. This deployment model is perfect for smaller environment where Enhanced Linked Mode is not required. The PSC Topology Decision Tree is a great read if you aren’t sure on how you should deploy these core components given your requirements. If you are interested in also seeing other GUI/CLI deployments, please see my post here which has links off to other individual articles for different deployment methods. ...

The post below will walk through the deployment of an embedded vCenter Server Appliance (VCSA) 6.5 node to a target ESXi server using the command line interface (CLI) deployment method. If you are interested in also seeing the GUI deployment or other GUI/CLI deployments, please see my post here which has links off to other individual articles for different deployment methods. For each of the deployment methods I am providing a video as well. Please find the video for the VCSA Embedded CLI deployment below. This has been recorded in FullHD, so best to watch it in Full Screen! ...

The post below will walk through the deployment of an external vCenter Server Appliance (VCSA) 6.5 node and Platform Services Controller (PSC) to a target ESXi server using the command line interface (CLI) deployment method. If you are interested in also seeing the GUI deployment or other GUI/CLI deployments, please see my post here which has links off to other individual articles for different deployment methods. For each of the deployment methods I am providing a video as well. Please find the video for the VCSA External CLI deployment below. This has been recorded in FullHD, so best to watch it in Full Screen! ...

[toc] Introduction So I’ve finally had some spare time to download and have a look at some of the vSphere 6.5 components and I’ll be planning to do a few blog posts in early 2017 on some of the cool new features that have been added in this release. I’ve decided to start with a few posts on the deployment of the vCenter Server Appliance (VCSA) using both the new GUI installer and the CLI option as well. I’ve put the links immediately below, but I’ve also written a little about the VCSA below in this article which you may like to read as well. I’ll walk through the deployment of an embedded VCSA as well as an external deployment with 1 PSC and 1VC node. The individual posts below include both a video and text with screenshots. ...

A long last, VMware have made a tool available and supported to migrate from a Windows installation of vSphere 5.5 across to the vCenter Server Appliance (VCSA) 6.0U2. VMware gave us a teaser with a fling in 2015, but this was taken down and there have been hints dropped via Social Media and most recently some good sessions for the migration tool at VMworld 2016. Prior to this tool, migrating from a Windows install to the VCSA was not a trivial task. I undertook this at my previous employer, where we had 2 vCenter Servers, around 10 clusters and approx 70 hosts. While a lot of it was scripted, it was still a very involved process, as we had distributed switches, a number of cluster, host and VC advanced settings etc. Along with that, the historical data was not transferred across so we had to be OK with not migrating that data. ...