VMware vRealize Automation - 7.0.1 User’s Manual
Upgrading from vRealize
Automation 7.0 to 7.0.1
vRealize Automation 7.0
Upgrading from vRealize Automation 7.0 to 7.0.1
You can find the most up-to-date technical documentation on the VMware website at:
https://docs.vmware.com/
If you have comments about this documentation, submit your feedback to
docfeedback@vmware.com
VMware, Inc.
3401 Hillview Ave.
Palo Alto, CA 94304
www.vmware.com
Copyright © 2008–2018 VMware, Inc. All rights reserved. Copyright and trademark information.
VMware, Inc. 2
Contents
Updated Information 5
Upgrading vRealize Automation 6
1
Checklist for Upgrading vRealize Automation Components 7
Prerequisites for Upgrading vRealize Automation 8
Preparing to Upgrade vRealize Automation 11
2
Backing up and Saving Your Existing Environment 11
Shut Down vCloud Automation Center Services on Your IaaS Windows Server 13
Increase vCenter Server Hardware Resources for Upgrade 14
Reconfigure Disk 1 on All vRealize Automation Appliance Nodes 14
Downloading vRealize Automation Appliance Updates 16
Updating the vRealize Automation Appliance 18
3
Install the Update on the vRealize Automation Appliance 18
Install the Update on Additional vRealize Automation Appliances 19
Upgrading the IaaS Server Components 22
4
Download the IaaS Installer 22
Upgrade the IaaS Components 23
Add Users or Groups to an Active Directory Connection 27
5
Enable Your Load Balancers 29
6
Post-Upgrade Tasks for vRealize Automation 30
7
Port Configuration for High-Availability Deployments 30
Enabling the Connect to Remote Console Action for Consumers 30
Reconfigure External Workflow Timeouts 31
Verify That vRealize Orchestrator Service is Available 31
Restore Embedded vRealize Orchestrator Endpoint 32
Configure an External PostgreSQL Database to Merge into an Embedded PostgreSQL
Environment 32
Ensure Deployed Virtual Machines Register With Software Service 33
Restore Changes to Logging 34
Troubleshooting the Upgrade 35
8
Installation or Upgrade Fails with a Load Balancer Timeout Error 35
VMware, Inc.
3
Upgrading from vRealize Automation 7.0 to 7.0.1
Upgrade Fails for Website Component During IaaS Upgrade 36
Incorrect Tab Names Appear Intermittently 36
Manager Service Fails to Run Due to SSL Validation Errors During Runtime 36
Log In Fails After Upgrade 37
Catalog Items Appear in the Service Catalog But Are Not Available to Request 37
VMware, Inc. 4
Updated Information
This Upgrading vRealize Automation guide is updated with each release of the product or when
necessary.
This table provides the update history of this Upgrading vRealize Automation guide.
Revision Description
EN-002047-02
EN-002047-01 Updated topics to address reported problems.
EN-002047-00 Initial release.
n
Updated Configure an External PostgreSQL Database to Merge into an Embedded PostgreSQL Environment
to revise previous commands.
n
Added Ensure Deployed Virtual Machines Register With Software Service to address a reported problem.
n
Updated Reconfigure Disk 1 on All vRealize Automation Appliance Nodes to provide warning about not
restarting the system prematurely.
n
Updated Install the Update on Additional vRealize Automation Appliances to add additional steps to the end of
the procedure.
n
Updated Downloading vRealize Automation Appliance Updates to remove the second method of downloading
updates.
n
Updated Configure an External PostgreSQL Database to Merge into an Embedded PostgreSQL Environment
to add additional commands.
n
Updated Install the Update on the vRealize Automation Appliance to add prerequisite about running the
required script described in Knowledge Base 2144876.
VMware, Inc. 5
Upgrading vRealize Automation 1
Upgrading is a multi-stage process in which procedures must be performed in a particular order. Follow
the suggested processes to ensure a smooth upgrade with a minimum of system downtime. You must
upgrade all product components to the same version.
Note vRealize Automation features and innovations introduced in 7.0 required several platform-level
enhancements. As a result, certain upgrade scenarios will require additional assistance. To ensure the
best possible upgrade experience, it is recommended that you visit the vRealize Automation Upgrade
Assistance webpage at http://www.vmware.com/products/vrealize-automation/upgrade-center before you
begin the upgrade process.
Locate your currently installed version in the table and then follow the steps in the documents on the right
to incrementally upgrade your vRealize Automation environment to the latest release. You can find links
to the documentation for all versions of vCloud Automation Center and vRealize Automation at
https://www.vmware.com/support/pubs/vcac-pubs.html.
You can upgrade to vRealize Automation 7.0.1 from any supported vRealize Automation 6.2.x or
vRealize Automation 7.0 release.
Table 1‑1. Supported Upgrade Paths to 7.0.1
Your Currently Installed Version Documentation for Incremental Upgrades
vRealize Automation 7.0 Upgrade to the 7.0.1 release as described in Upgrading
from vRealize Automation 7.0 to 7.0.1.
vRealize Automation 6.2.0, 6.2.1, 6.2.2, 6.2.3, and 6.2.4 Upgrade directly to the 7.0.1 release as described in
Upgrade from vRealize Automation 6.2 to 7.0.1.
Note Beginning in 6.2.0, vCloud Automation Center is rebranded to vRealize Automation. Only the user
interface and service names are changed. Directory names and program names that contain vcac are not
affected.
This chapter includes the following topics:
n
Checklist for Upgrading vRealize Automation Components
n
Prerequisites for Upgrading vRealize Automation
VMware, Inc.
6
Upgrading from vRealize Automation 7.0 to 7.0.1
Checklist for Upgrading vRealize Automation Components
When you perform an upgrade, you update all vRealize Automation components in a specific order.
The order of upgrade varies depending on whether you are upgrading a minimal installation or a
distributed installation with multiple vRealize Automation appliances.
Use the checklists to track your work as you complete the upgrade. Complete the tasks in the order in
which they are given.
You must upgrade components in the prescribed order and upgrade all components. Using a different
order can result in unexpected behavior after the upgrade or failure of the upgrade to complete.
For information about all supported upgrade paths, see the release notes for vRealize Automation,
available on the VMware vRealize Automation Documentation landing page.
Table 1‑2. Checklist for Upgrade of a Minimal vRealize Automation Deployment
Task Instructions
Backup your current installation. This is a critical step.
Shut down vRealize Automation Windows services on your
Iaas server.
If the Common Components Catalog is installed, you must
uninstall it before you upgrade.
Configure your hardware resources.
Download updates to the vRealize Automation appliance.
Install the update on the vRealize Automation appliance.
Download and install updates for IaaS.
For more information on how to back up and restore your
system, see Back Up Your Environment.
For general information, see Configuring Backup and Restore by
Using Symantec Netbackup at
http://www.vmware.com/pdf/vrealize-backup-and-restore-
netbackup.pdf
See Shut Down vCloud Automation Center Services on Your
IaaS Windows Server.
For information about how to uninstall, install, and upgrade the
Common Components Catalog, see the Common Components
Catalog documentation.
See Increase vCenter Server Hardware Resources for Upgrade.
See Downloading vRealize Automation Appliance Updates.
See Install the Update on the vRealize Automation Appliance.
See Chapter 4 Upgrading the IaaS Server Components.
VMware, Inc. 7
Upgrading from vRealize Automation 7.0 to 7.0.1
Table 1‑3. Upgrade to vRealize Automation Distributed Installation Checklist
Task Instructions
Backup your current installation. This is a critical step.
Shut down vRealize Automation services on your Iaas
Windows server.
If the Common Components Catalog is installed, you must
uninstall it before you upgrade.
Configure your hardware resources for the upgrade.
Download updates to the vRealize Automation appliance.
Install the update on the first vRealize Automation
appliance in your installation. If you have designated an
appliance as a master, upgrade this appliance first.
Install the update on the rest of your vRealize Automation
appliances.
For more information on how to back up and restore your
system, see Back Up Your Environment.
For detailed information, see Configuring Backup and Restore by
Using Symantec Netbackup at
http://www.vmware.com/pdf/vrealize-backup-and-restore-
netbackup.pdf
See Shut Down vCloud Automation Center Services on Your
IaaS Windows Server.
For information about how to uninstall, install, and upgrade the
Common Components Catalog, see the Common Components
Catalog documentation.
See Increase vCenter Server Hardware Resources for Upgrade.
See Downloading vRealize Automation Appliance Updates.
See Install the Update on the vRealize Automation Appliance.
Install the Update on Additional vRealize Automation Appliances
Download and install updates for IaaS.
Enable your load balancers.
See Chapter 4 Upgrading the IaaS Server Components.
Chapter 6 Enable Your Load Balancers
Prerequisites for Upgrading vRealize Automation
Before you run the upgrade, review the prerequisites.
System Configuration Requirements
Make sure the following system requirements are met before you begin an upgrade.
n
Verify that you are following a supported upgrade path. See the vRealize Automation release notes
for a list of supported upgrade paths.
n
Verify that all appliances and servers that are part of your deployment meet the system requirements
for the version you are upgrading to. See the vRealize Automation Support Matrix on the VMware
Web site at https://www.vmware.com/support/pubs/vcac-pubs.html.
n
Consult the VMware Product Interoperability Matrix on the VMware Web site for information about
compatibility with other VMware products.
n
Verify that the vRealize Automation you are upgrading from is in stable working condition. Correct any
issues before upgrading.
VMware, Inc. 8
Upgrading from vRealize Automation 7.0 to 7.0.1
n
Record your vCloud Suite license key if you used it for your the vRealize Automation installation you
are upgrading from. Upon upgrade, existing license keys are removed from the database.
Hardware Configuration Requirements
Make sure the following hardware requirements are met before you begin an upgrade.
n
You must have at least 18 GB of RAM space before you run the upgrade.
If the virtual machine is on vCloud Networking and Security, your might need to allocate more RAM
space.
n
To avoid upgrade failures due to insufficient free space in future vRealize Automation upgrades, Disk
1 must be re-sized to 50 GB on all vRealize Automation appliances. See "Re-size Disk 1 for Upgrade"
on page 19.
n
Your CPU must have four virtual sockets and one core. See Increase vCenter Server Hardware
Resources for Upgrade.
n
Your IaaS Server nodes must have the Microsoft .NET Framework 4.5.2 version and at least 5 GB of
free disk space.
n
You must have at least 7 GB of free disk space on each vRealize Automation appliance of the root
partition to download and run the upgrade.
n
Check the /storage/log subfolder and remove any older archived zip files to cleanup space.
General Prerequisites
Verify that the following prerequisites are finished before you begin an upgrade.
n
You have access to an Active Directory account that has a username@domain format with
permissions to bind to the directory.
n
You have access to an account that has a SAMaccountName format with sufficient privileges to join
the system to the domain by creating a computer object dynamically or to merge into a pre-created
object.
n
You have access to all databases and all load balancers impacted by or participating in the
vRealize Automation upgrade.
n
You make the system unavailable to users while you perform the upgrade.
n
You have disabled any applications that query vRealize Automation.
n
You have followed the instructions in Shut Down vCloud Automation Center Services on Your IaaS
Windows Server.
n
Verify that Microsoft Distributed Transaction Coordinator (MSDTC) is enabled on all
vRealize Automation and associated SQL servers. For instructions, see the VMware Knowledge Base
article Various tasks fail after upgrading or migrating to VMware vCloud Automation Center (vCAC)
6.1.x (2089503) at http://kb.vmware.com/kb/2089503.
VMware, Inc. 9
Upgrading from vRealize Automation 7.0 to 7.0.1
n
If the Common Components Catalog is installed, you must uninstall it before you upgrade. For
information about how to uninstall, install, and upgrade the Common Components Catalog, see the
Common Components Catalog documentation.
VMware, Inc. 10
Preparing to Upgrade
vRealize Automation 2
You must perform various listed tasks and procedures in preparation for upgrading vRealize Automation.
Perform the tasks required for upgrade in the order in which they appear in the checklist. See Checklist
for Upgrading vRealize Automation Components.
This chapter includes the following topics:
n
Backing up and Saving Your Existing Environment
n
Shut Down vCloud Automation Center Services on Your IaaS Windows Server
n
Increase vCenter Server Hardware Resources for Upgrade
n
Reconfigure Disk 1 on All vRealize Automation Appliance Nodes
n
Downloading vRealize Automation Appliance Updates
Backing up and Saving Your Existing Environment
Before you begin an upgrade process, you complete the backup prerequisites.
Prerequisites
n
Verify that your source installation is fully installed and configured.
n
Backup vRealize Automation appliance configuration files in the following directories for each
appliance.
n
/etc/vcac/
n
/etc/vco/
n
/etc/apache2/
n
/etc/rabbitmq/
n
Backup all databases.
n
Create a snapshot of your tenant configuration and the users assigned.
n
Backup any files you have customized, such as DataCenterLocations.xml.
n
Create a snapshot of your virtual appliances and IaaS servers. Adhere to regular guidelines for
backing up the entire system in case vRealize Automation upgrade fails for whatever reason. See
Configuring vRealize Suite 6.0 for Backup and Restore topics in vRealize Suite documentation.
VMware, Inc.
11
Upgrading from vRealize Automation 7.0 to 7.0.1
Back Up Your Environment
Before you begin to upgrade, shut down the vRealize Automation IaaS Windows Server and all Manager
machines and identity virtual appliance machines and take a snapshot. If the upgrade fails, you can use
the snapshot to return to the last known good configuration and attempt another upgrade.
Prerequisites
n
As of vRealize Automation 7.0, the PostgreSQL database is always configured in high-availability
mode. Log in to the management console and navigate to vRA settings > Database to locate the
current master node.
n
If the vRealize Automation MSSQL database is not hosted on the IaaS server, create a database
backup file.
n
Verify that you have completed the backup prerequisites. See Backing up and Saving Your Existing
Environment.
n
Verify that you have taken snapshot of your system while it is shut down. See the vSphere 6.0
Documentation.
If you cannot shut down your system, take an in-memory snapshot of all the nodes.
n
Verify that you have a backup of your entire system. See Configuring vRealize Suite 6.0 for Backup
and Restore by Using Symantec NetBackup 7.6 at
http://www.vmware.com/pdf/vrealize-suite-60-backup-and-restore-netbackup.pdf.
Procedure
1 Log in to vCenter Server.
2 Locate the vRealize Automation 7.0 IaaS Windows machines, and vRealize Automation appliance
nodes.
3 Select a machine and click Shutdown guest in the following order.
a IaaS Windows Server machines
b vRealize Automation appliance nodes
4 Take a snapshot of all the vRealize Automation 7.0 machines.
5 Extend Disk 1 to 50 GB for each vRealize Automation appliance. To create a full backup, clone each
appliance node and perform the upgrade on the cloned machines. Keep the original, in case system
restore is required later on.
6 Power on the system.
For instructions, see the vRealize Automation 6.2 version of the Start Up vRealize Automation topic at
http://pubs.vmware.com/vra-62/topic/com.vmware.vra.system.administration.doc/GUID-4A4BD979-61
EF-4590-AEDF-6A9BA42426B6.html.
Note The topic should have vra-62 in the URL.
VMware, Inc. 12
Loading...