VMware vRealize Automation automates the delivery of personalized infrastructure, applications and custom IT services. It automates the end-to-end delivery and management of infrastructure, and accelerates application deployment and releases. It lets you deploy across a multi-vendor hybrid cloud infrastructure, giving you both flexibility and investment protection for current and future technology choices.
- Take an offline snapshot of the virtual appliances and IaaS virtual machines.
- Keep a cold clone copy of the virtual appliances and IaaS virtual machines.
- Ensure there is a most recent successful image level backup available for the virtual appliances and IaaS virtual machines.
- Backups for vRealize Appliance configuration files in the following directories for each appliance.
- Backups for all databases.
- Backups for any files you have customized, such as "DataCenterLocations.xml"
- Perform the upgrade at a time when the system has an approved downtime.
- If the deployment uses an external vRealize Orchestrator appliance and it is connected to the Identity Appliance, upgrade vRealize Orchestrator before you upgrade vRealize Automation.
- If you don’t have Identity appliance in your environment, instead you are using vSphere SSO for authentication then the above step is not critical to follow any order.
- If the root password is 365 days old or older, we must change the password before we run the upgrade. If a root password is 364 days old or newer, we can proceed with the upgrade (#chage -l)
Procedure to Stop the Following Services:
- vRealize Appliance:
- service vcac-server stop
- service rabbitmq-server stop
- IaaS Windows Services: (Stop services in all servers in the following order)
- All VMware vCloud Automation Center agents
- All VMware DEM workers
- All VMware DEM orchestrator
- All VMware vCloud Automation Center Manager Service
Package Download Procedure:
- Download the update ISO file from the VMware web site.
- Connect the CD-ROM drive for the virtual appliance you are updating to the ISO file you downloaded.
- Go to VAMI by using its fully qualified domain name "https://myvra.lab.com:5480/"
- Log in with the user name root, Click the Update tab, Click Settings, Under Update Repository, select Use CDROM Updates and Click Save Settings.
Prerequisites for Upgrading vRealize Automation Appliance:
- If your deployment uses a load balancer, disable one vRealize Appliance for load balancer traffic. The first appliance you plan to upgrade must be connected to the load balancer.
- Before you trigger the upgrade for the appliance that use load balancers, disable traffic for all nodes except the first node that you plan to upgrade in order to prevent cache errors.
- If you are using a vRealize Appliance as a dedicated appliance database server, update it before you update a vRealize Appliance used as an application server.
- Verify that the identity server is running.
- Login to VAMI by using its fully qualified domain name "https://myvra.lab.com:5480/" then Click on the Update tab, Click Status, Click Check Updates, Click on Details, Click on Install Updates, Click on OK and then reboot the virtual appliance.
- If the deployment uses a load balancer, repeat these steps for each vRealize Appliance. Leave the second and subsequent vRealize Appliance disabled for load balance traffic when you apply the update.
- Reconnect all virtual appliances to the load balancer.
- Login to VAMI and check if all services are registered now (if you are using an external orchestrator appliance then ignore the local VCO services)
Prerequisites for Upgrading the IaaS Components:
- If you are using multiple IaaS components in one server, then upgrade the services in the proper order. For example, if you have Website and manager services on the same server, select both for update. You must complete the upgrade on one server before you begin an upgrade on another.
- If the IaaS deployment uses a load balancer, the first IaaS server you plan to upgrade must be connected to the load balancer. All other instances of IaaS server must be disabled for load balancer traffic before you apply the upgrade to avoid caching errors.
- First upgrade the Website on which Model Manager Data is installed. Finish the upgrade on one server before upgrading the next server that is running a Website service.
- If you have a distributed environment under load balancers then perform the upgrade in the following order so that services are upgraded properly.
- Websites - (If you are using a load balancer, disable all Websites for load balancer traffic except the Website on which Model Manager Data is install.
- Manager Services - (Upgrade the active manager service before you upgrade the passive manager service and first reboot the system where the passive manager service is installed.)
- DEM Orchestrator and DEM Workers - (Upgrade all DEM orchestrators and workers. Finish the upgrade on one server before you upgrade the next server.)
- Agents - (Finish the upgrade on one server before you upgrade the next server that is running an agent like vSphere proxy agent.)
- The below listed details will definitely be there in all existing environment but it’s still good to verify.
o 64-bit Java version 1.7 or later is installed. 32-bit versions are not supported.
o The environment variable JAVA_HOME is set to the Java install folder.
o The %JAVA_HOME%injava.exe file is available.
o Microsoft .NET Framework 4.5.1 is installed.
- Upgrade the database component (i.e. Model Manager Data)
- Download the database upgrade script from "https://myvra.lab.com:5480/i"
- Extract the contents of the "DBUpgrade.zip" archive file to a local folder on the vRealize Automation database host.
- Set the current directory to the folder where you have extracted the contents of the "DBUpgrade.zip" archive file.
- Open the command prompt by using run as admin.
- Enter a DBUpgrade command string in below format.
- #DBUpgrade.exe -S ,1443 -d -E -U -P
Procedure to Upgrade IaaS Components:
- Login to IaaS server as an Administrator and Enhanced Security Configuration should be enabled in IE and there should be no proxy setting enabled in any browsers.
- Download the new installer from "https://myvra.lab.com:5480/i/" and check if it’s the different version as compared to earlier one i.e. new file version 6.2.5.x
- Run the downloaded installer file as administrator.
- Accept Certificates, Select Upgrade, choose the appropriate option as per the order mentioned above to precede further.
- Click on Next, Upgrade, Next, Finish.
- Repeat these steps for each IaaS server in your deployment in the recommended order.
- If your deployment uses a load balancer, re-enable load balancer traffic for any unconnected nodes.
- After all components are upgraded, verify that all servers are restarted.
- Wait for 10-15 minutes then log in to VAMI "https://myvra.lab.com:5480/" and verify that all services, including IaaS, are now registered.
Post Upgrade Tasks for vRealize Automation:
- After finishing an upgrade in a distributed deployment, you must configure the load balancer to pass traffic on port 8444 to the vRealize Appliance to support remote console features.
- SSH to vRA appliance and check if all of their services are running
- Login to VAMI and check if all the services are registered.
- Login to vRO appliance by using vRO client and check if any error it has.
- Login to the vRO configurator and check if all the plugin and services has any error.
- Check all the databases if it has any errors like vCAC SQL DB, vRA postgres DB, vRO postgres etc.
- Login to vRA self-service portal and check the functionality and behavior of all the published catalogs etc.
- Check all the log files in case of any error.
- Monitor the health of vRealize environment for some time, post successful upgrade.
- You can follow any one of the below listed restoration procedure.
- Revert to the previous snapshot which was taken just before the upgrade activity.
- Or Reuse the clone which was taken offline, just before the upgrade activity.
- Or Restore from the recent successful image level backup which has been verified, just before the upgrade activity.
- Ensure all the services are running as needed and all portals are accessible as well.
- Model manager is the master workflow - "https://dev-iaas.ce.dst.com/vmps2"
- It should not show any error. It will be showing a XML coded page.
- The VMPS workflow is the master workflow in which the other provisioning workflows are embedded.
- The VMPS master workflow life cycle states represent an IaaS virtual machine life cycle, from the state of “request machine” to “destroy”
Most Expected Resolved Issues in vRA 6.2.5:
- Resource not found for the segment 'VirtualMachines' System.Data.Services. DataServiceException
- Reconfiguration failure leaves SCVMM virtual machine in a power off state.
- Changing the owner or description of a provisioned machine result in failure.
- Windows 10 and SLES 12 Guest OS support.