7.1
Table Of Contents
- Upgrading from vRealize Automation 6.2 to 7.1
- Contents
- Upgrading to vRealize Automation 7.1
- Updated Information
- Upgrading vRealize Automation
- Checklist for Upgrading vRealize Automation Components
- Considerations About Upgrading to This vRealize Automation Version
- Upgrade and Identity Appliance Specifications
- Upgrade and Licensing
- Understanding How Roles Are Upgraded
- Understanding How Blueprints Are Upgraded
- Upgrade and vApp Blueprints, vCloud Endpoints, and vCloud Reservations
- Understanding How Multi-Machine Blueprints Are Upgraded
- Upgrade and Physical Endpoints, Reservations, and Blueprints
- Upgrade and Network Profile Settings
- Upgrade and Entitled Actions
- Upgrade and Custom Properties
- Upgrade and Application Services
- Upgrade and Advanced Service Design
- Upgrade and Blueprint Cost Information
- Prerequisites for Upgrading vRealize Automation
- Preparing to Upgrade vRealize Automation
- Updating the vRealize Automation Appliance
- Upgrading the IaaS Server Components
- Upgrade Stand-Alone External vRealize Orchestrator for Use With vRealize Automation
- Upgrade External vRealize Orchestrator Appliance Clusters
- Add Users or Groups to an Active Directory Connection
- Enable Your Load Balancers
- Post-Upgrade Tasks for vRealize Automation
- Troubleshooting the Upgrade
- Migration of Identity Store Fails Because the Active Directory is...
- Migration of Identity Store Fails Because of Incorrect Credentials
- Migration of Identity Store Fails With a Timeout Error Message...
- Installation or Upgrade Fails with a Load Balancer Timeout Error...
- Upgrade Fails for Website Component During IaaS Upgrade
- Incorrect Tab Names Appear Intermittently
- Manager Service Fails to Run Due to SSL Validation Errors...
- Log In Fails After Upgrade
- Catalog Items Appear in the Service Catalog But Are Not...
- User Migration Batch Files Are Ineffective
- PostgreSQL External Database Merge is Unsuccessful
- Join Cluster Command Appears to Fail After Upgrading a High Availability Environment
- Increase Free Space on the Root Partition
- Manual PostgreSQL Database Merge
- Upgrade Fails to Upgrade the Management Agent or Certificate Not Installed on a IaaS Node
- Bad PostgreSQL Service State Stops Upgrade and Displays Error Message
- Backup Copies of .xml Files Cause the System to Time Out
- Index
Upgrade and Blueprint Cost Information
As of 7.0, vRealize Automation cost proles are no longer supported and are not migrated into the target
deployment during upgrade. However, you can leverage the enhanced integration with vRealize Business to
manage your vRealize Automation resource costs.
vRealize Business is now tightly integrated with vRealize Automation and supports the following enhanced
costing features.
n
Unied location in vRealize Business to dene exible pricing policies for:
n
Infrastructure resource, machine, and application blueprints
n
All types of endpoints in vRealize Automation
n
Any operational cost, one time cost, and cost on custom properties
n
Role-based showback reports in vRealize Business
n
Fully leverage new features in vRealize Business
Before you upgrade, you can export your existing cost reports from your source vRealize Automation
instance for reference. After you complete your upgrade, you can install and congure vRealize Business to
handle costing.
Prerequisites for Upgrading vRealize Automation
Before you run the upgrade, review the following 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 “Upgrading vRealize Automation,” on
page 6 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
athps://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
problems before upgrading.
n
If you are upgrading from vRealize Automation 6.2.x, record your vCloud Suite license key if you used
it for the vRealize Automation installation you are upgrading from. Upon upgrade, existing license
keys are removed from the database. You do not need to do this task if you are upgrading from
vRealize Automation 7.x.
Hardware Configuration Requirements
Make sure the following hardware requirements are met before you begin an upgrade.
n
You must create a disk with at least 50 GB of space and 18 GB of RAM space before you download the
upgrade. See “Increase vCenter Server Hardware Resources for Upgrade,” on page 17.
If the virtual machine is on vCloud Networking and Security, you might need to allocate more RAM
space.
If you have two disks in your vRealize Automation appliance, you must add a Disk 3 with 25 GB and a
Disk 4 with 50 GB of space. The virtual appliance must have Disk 3 and Disk 4 for the upgrade process
to succeed.
Upgrading from vRealize Automation 6.2 to 7.1
14 VMware, Inc.