Wow, its been way too long since I have posted something.  The upgrade from vCAC 6.0.1 to 6.1 is fairly straight forward but I figured it would be a good to get my feet wet again.  The first thing to make sure of is you have all the prerequisites full filled.

Prerequisites

1) You will need to be up to 6.0.1 before completing the upgrade

2) Like anything is always good to back things up, well this upgrade is no different.  You should backup the following:

  • The configuration files in /etc/vcac.  The config files that are in this location include configs around SSO admin credentials, vCAC Services that need to be registered at boot,  vPostgres DB details aka JDBC connection info, the vCAC key store, and vCO Endpoint config.  So its all pretty important, BACK IT UP!  In my case, I used WinSCP to connect to the vCAC Appliance, browsed to the location, and backed up the folder to my local box.

vcac folder

  •  The configuration files in /etc/vco.  The config files in this location include vCO password/connection info, web/tomcat configs, etc.  Yet again it pretty in important so back it up.  Used the same process via WinSCP to back it up.
  • All databases, this includes the vPostgres and MS SQL DBs.  Make sure to back up the vCAC DBs, to do this use whatever methods you normally use internally to do backups.

3) Snapshot all the virtual appliances and IaaS Servers.  So obviously if you have a distributed install this means all the distributed components.

4) If you’re using the vSphere SSO, make sure its a supported version.  You can check this on the vCloud Automation Center Support Matrix

5) If you have the old school vCAC Designer Installed, uninstall it.  You will install the newest version after the upgrade is complete. There isn’t an upgrade process for this, uninstall/install is the path forward.

6) If you and only IF you have a highly available setup deployed with multiple vCAC appliance behind a load balancer, you need to make sure the vco-server services is disabled.  Another thing to note is during the upgrade of the appliances you need to also stop the vcac-server serivce on all the appliances but the one currently be upgraded.  Make sure to not start back up any of these services until all the appliances are upgraded.

  • SSH to the appliance and log in
  • Run the following commands:
    • service vco-server stop
    • chkconfig vco-server off
  • If this isn’t the instance you are currently upgrading run the following:
    • service vcac-server stop
  • Once you are completed with the appliance upgrades you should SSH back into the appliance, run chkconfig vco-server on, and start the vco-server service back up.  This will insure that it starts back up appropriately on reboots.

7) Shut down the vCAC services on your IaaS Windows Server.  If its a distributed install these services/roles will be spread out across several IaaS servers.

  • Log in to the IaaS Server
  • Go to Start–>Administrative Tools–>Services
  • Stop the services in the following order:
    • All vCAC Agents
    • All vCAC DEM workers
    • All vCAC DEM Orchestrators
    • vCAC Manager Service

 Upgrading the Identity Appliance

If your running the Identity appliance, the next step is to upgrade it.

1) Log into to the identity appliance management interface by browsing to https://FQDN:5480

Identity login

2) Select the Update tab and then click Check Updates

Identity check updates

3) Once it updates you should see the new appliance version show up 2.1.0.0.  Click Install Updates.

Identity Install Updates

4) Once the update is completed you will be see a message stating the appliance needs to be rebooted.  Click on the System tab and then Reboot.

Note: If your appliance doesn’t have access to download the file you can use one of to methods. 

  • Download the update .zip, great a local http: repository, and pull the update from there
  • Download the update .iso, add a CD-ROM to the appliance, mount the .iso, and update from there.  In my lab, I did this as I only allow a few ports inbound. 

Upgrading the vCAC Appliance

Most of the process here is very similar to that of the identity appliance. Please remember there are additional steps that need to happen here if you are upgrading a highly available install, these steps are listed above under Prerequisites.

1)Log into to the vCAC appliance management interface by browsing to https://FQDN:5480

vcac login

2) Select the Update tab and then click Check Updates

vcac update

3) Once it updates you should see the new appliance version show up 6.1.0.0.  Click Install Updates.

vCAC Install update

4) Once the update is completed you will be see a message stating the appliance needs to be rebooted.  Click on the System tab and then Reboot.

vcac update complete

Note: If your appliance doesn’t have access to download the file you can use one of to methods. 

  • Download the update .zip, great a local http: repository, and pull the update from there
  • Download the update .iso, mount the .iso, and update from there.  In my lab, I did this as I only allow a few ports inbound. 

Upgrading the IaaS servers

There are a couple of prerequisites that need to be in place for this part of the install.

  • The box you are running the Database Upgrade from must have the 64-bit Java version 1.7 installed.  32-bit versions are not supported.  Environment variable JAVA_HOME is set to the Java install folder.  %JAVA_HOME%\bin\java.exe must be available.
  • .NET Framework 4.5.1 is required on the IaaS installation machine.  One thing to note is that you can not do a straight upgrade from 6.0 to 6.1.  You do have to be up to 6.0.1 before you can upgrade to 6.1.

Upgrading the Database

You can run this update from another server on the network long as there is appropriate access.  I went ahead and ran this from another box I had in my lab as I already had the Java components installed and configured.  One thing I did run into is that box that you run DBUpgrade from also needs to have .Net 4.x on it.  I received an error message saying it needed 4.0 but 4.5.1 worked fine.

1) Browse to https://vcac-appilance-FQDN:5480/installer

2) The fourth bullet down is a link to download the “database upgrade scripts” Click the link and download the DBUpgrade.zip file.

DB Install Script

3) Extract the DBUpgrade.zip file.

4) Open up a windows command prompt and change directories to the location you unzipped the file to

db changes directory

5) Run the following command:

DBUpgrade -S FQDN\Instance Name -d DB Name -E Forces Windows Auth  | -U DB owner username -l logfile location

Example

DBUpgrade -S IaaS.JonsDomains.local\SQLEXPRESS -d vCAC -E

DBUprade Success

 Upgrading the IaaS components

When performing the upgrade of the IaaS components if you have them distributed they should be upgraded in the following order: Websites, Manager Service, DEM Orchestrator and Workers, and finally the agents.  If there are multiple of any of the components do them one at a time.

1) Browse to https://vcac-appilance-FQDN:5480/installer

2) If you haven’t installed .NET Framework 4.5.1, download it from this page and install it. After the install you might be prompted to reboot the server.  If so please do, also remember to stop the vCAC services again when the server reboots.

2) The first bullet down is a link to download the “IaaS Installer” Click the link and download the setup_FQDN-of-vCAC-applinance@5480.exe.  Do not change the name of the file, it is needed during the install to pull down the appropriate packages.

3) Run the install, setup_FQDN-of-vCAC-applinance@5480.exe.  The installation wizard will launch, click next.

4) Accept the EULA and click next

5) Provide credentials to the vCAC Appliance and click next.

VCAC Appliance creds

6) Upgrade will be selected, click next.

7) What you will notice on the next screen is the installer detects what components are installed on the box.  This is nice, and I love how the installation/upgrades have gotten better and better with vCAC versions.  It will prompt for the service account password, DB instance, and DB name.  Click next and then Upgrade.

service upgrade detect

Another cool thing is there is a link to the installer log folder at the bottom of the install progress screen.  This is nice as you can click on it and look at logs to get progress or if you get an error.

vcac upgrade logs

Sit back and relax, it’s going to take a bit.  :) Once it completes click next and finish.  The you are done!

vcac Upgrade complete

So now you think your done, well think again.  The following KB was published:

Cannot find VMware vSphere virtual machines by unique identifier using the vCenter Orchestrator Plug-in for VMware vCloud Automation Center 6.1, or directly in vSphere API (2088838)

Basically there is an issue with version 6.1 and some of the vCO workflows that came with imbedded vCO.  The KB has you download a workflow package import it into the imbedded vCO appliance.

Keep a look out here on the blog, I will have one covering upgrading Application Director and ITBM Std shortly.