VMware vRealize Automation - 7.0 User’s Manual
Upgrading from vRealize
Automation 6.2 to 7.0.1
vRealize Automation 7.0
Upgrading from vRealize Automation 6.2 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
Upgrading from vRealize Automation 6.2.x to 7.0.1 5
Updated Information 5
Upgrading vRealize Automation 7
Checklist for Upgrading vRealize Automation Components 9
Considerations About Upgrading to This vRealize Automation Version 12
Prerequisites for Upgrading vRealize Automation 17
Preparing to Upgrade vRealize Automation 19
Backing up and Saving Your Existing Environment 19
Shut Down vCloud Automation Center Services on Your IaaS Windows Server 20
Prepare a Clustered PostgreSQL Environment for Upgrade 21
Increase vCenter Server Hardware Resources for Upgrade 22
Reconfigure Disk 1 on All vRealize Automation Appliance Nodes 24
Create a SaaS Schema and Citext Extension for External vRealize Automation Database 25
Downloading vRealize Automation Appliance Updates 26
Updating the vRealize Automation Appliance 27
Upgrade the External PostgreSQL Virtual Appliance 28
Install the Update on the vRealize Automation Appliance 29
Update Your Single Sign-On Password for VMware Identity Manager 30
Update the License Key 31
Migrate Identity Stores to the VMware Identity Manager 32
Install the Update on Additional vRealize Automation Appliances 36
Upgrading the IaaS Server Components 37
Download the IaaS Installer 37
Upgrade the IaaS Components 38
Upgrade Stand-Alone External vRealize Orchestrator for Use With vRealize Automation 41
Upgrade External vRealize Orchestrator Appliance Clusters 43
Add Users or Groups to an Active Directory Connection 44
Enable Your Load Balancers 46
Post-Upgrade Tasks for vRealize Automation 46
Port Configuration for High-Availability Deployments 46
Enabling the Connect to Remote Console Action for Consumers 46
Reconfigure External Workflow Timeouts 46
Verify That vRealize Orchestrator Service is Available 46
Restore Embedded vRealize Orchestrator Endpoint 47
Configure an External PostgreSQL Database to Merge into an Embedded PostgreSQL
Environment 48
Restore Changes to Logging 49
Ensure Deployed Virtual Machines Register With Software Service 49
VMware, Inc.
3
Upgrading from vRealize Automation 6.2 to 7.0.1
Troubleshooting the Upgrade 49
Migration of Identity Store Fails Because the Active Directory is not Synchronized 49
Migration of Identity Store Fails Because of Incorrect Credentials 50
Migration of Identity Store Fails With a Timeout Error Message 51
Installation or Upgrade Fails with a Load Balancer Timeout Error 52
Upgrade Fails for Website Component During IaaS Upgrade 52
Incorrect Tab Names Appear Intermittently 53
Manager Service Fails to Run Due to SSL Validation Errors During Runtime 53
Log In Fails After Upgrade 54
Catalog Items Appear in the Service Catalog But Are Not Available to Request 54
User Migration Batch Files Are Ineffective 55
VMware, Inc. 4
Upgrading from vRealize Automation
6.2.x to 7.0.1
Upgrading from vRealize Automation 6.2.x to 7.0.1 tells you how to download and install updates to
upgrade to the latest 7.0.x release.
It also describes differences between this release and the previous vRealize Automation release and
additional steps that you can perform to improve the upgrade.
Note Not all features and capabilities of vRealize Automation are available in all editions. For a
comparison of feature sets in each edition, see https://www.vmware.com/products/vrealize-automation/.
This information is intended for experienced Windows or Linux system administrators who are familiar
with virtual machine technology and datacenter operations.
VMware Technical Publications Glossary
VMware Technical Publications provides a glossary of terms that might be unfamiliar to you. For
definitions of terms as they are used in VMware technical documentation, go to
http://www.vmware.com/support/pubs.
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 the Upgrading vRealize Automation guide.
VMware, Inc.
5
Upgrading from vRealize Automation 6.2 to 7.0.1
Revision Description
EN-001900-06
n
Added User Migration Batch Files Are Ineffective to address reported problem.
n
Revised Update the License Key to provide workaround for unavailable text box.
n
Added Configure an External PostgreSQL Database to Merge into an Embedded PostgreSQL Environment for
upgrading environments with an external PostgreSQL database.
n
Added Ensure Deployed Virtual Machines Register With Software Service to address reported problem.
EN-001900-05 Updated topics to address reported problems.
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 Install the Update on the vRealize Automation Appliance to add information about Knowledge Base
2144876.
EN-001900-04 Upgrading from 6.2.x to 7.0.1
EN-001900-03 Clarifications and additions to earlier changes.
EN-001900-02
n
Updated Shut Down vCloud Automation Center Services on Your IaaS Windows Server to change the order of
shutting down the services and information about disconnecting secondary nodes from the VIP addresses.
Added information on how to verify that the IaaS service is running.
n
Updated Download vRealize Automation Appliance Updates from a VMware Repository.
n
Updated Upgrade Stand-Alone External vRealize Orchestrator for Use With vRealize Automation to add
information on how to stop the vRealize Orchestrator server service.
n
Updated Install the Update on the vRealize Automation Appliance to add prerequisite to disable the Message
Signature Check value and information about following the upgrade progress in a log file.
n
Updated Install the Update on Additional vRealize Automation Appliances to add information about following
the upgrade progress in a log file.
n
Updated Upgrade the IaaS Components to add information to verify that snapshots should exist if multiple
IaaS servers are present. Added a prerequisite to run the Prerequisite Checker and information about
disabling SSL encryption.
n
Updated Update Your Single Sign-On Password for VMware Identity Manager to add information about
verifying registered services with the exception of the iaas-service.
n
Created Migrate Identity Stores to the VMware Identity Manager, Create a Local User Account for Your
Tenants, Connect Your Active Directory to Synchronize Users and Groups, and Migrate Multiple Tenant and
IaaS Administrators to add information about migrating users and groups from a Native Active Directory store
to vRealize Automation.
VMware, Inc. 6
Upgrading from vRealize Automation 6.2 to 7.0.1
Revision Description
EN-001900-01
EN-001900-00 Initial release.
n
Updated Upgrading vRealize Automation to add a note about CCE support for upgrade considerations.
n
Updated Checklist for Upgrading vRealize Automation Components to change the order of the minimal and
distributed upgrade. Changes were also made to the order of topics in the table of contents and reference links
to the proceeding tasks were updated accordingly.
n
Updated Backing up and Saving Your Existing Environment to add the backup requirements for upgrade.
n
Updated Back Up Your Environment to add information about taking snapshots and taking in-memory
snapshots of nodes. Moved the power on the system task into the procedure.
n
Updated Increase vCenter Server Hardware Resources for Upgrade to add information about configuring the
resources if the user has only two disks.
n
Updated Install the Update on the vRealize Automation Appliance to add information about registered,
embedded, and external vco services.
n
Added a new Install the Update on Additional vRealize Automation Appliances topic.
n
Updated Upgrade External vRealize Orchestrator Appliance Clusters to clarify that the vRealize Orchestrator
cluster should be external.
Upgrading vRealize Automation
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.
To find out the considerations for the upgrade process, see Considerations About Upgrading to This
vRealize Automation Version.
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.
Note If you have customized your vRealize Automation 6.2.x deployment, contact your CCE support
staff for additional information about upgrade considerations.
VMware, Inc. 7
Upgrading from vRealize Automation 6.2 to 7.0.1
You can upgrade to vRealize Automation 7.0.1 from any supported vRealize Automation 6.2.x or
vRealize Automation 7.0 release.
Note To avoid a known issue when upgrading from vRealize Automation 6.2.0, perform the following
step sequence on every IaaS Web site node, before you start the upgrade procedure. This issue affects
6.2.0 only. Other 6.2.x versions are not affected.
1 Open Notepad with Administrative rights.
2 Open the following file:
C:\Program Files (x86)\VMware\vCAC\Server\Model Manager Web\web.config
3 Locate the following statement in the file:
<!-- add key="DisableMessageSignatureCheck" value="false"-->
4 Uncomment the statement and change the value from false to true.
<add key="DisableMessageSignatureCheck" value="true" />
5 Save the file.
If Notepad prompts you to Save As, you did not open Notepad as Administrator and must go back to
step 1.
6 Open a Command Prompt window with Administrative rights.
7 Run reset.
8 Repeat steps 1 - 7 for all Web site nodes.
Table 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.
See the following table for information about upgrading from an earlier vCloud Automation Center 6.x
release to vRealize Automation 6.2.x in preparation for upgrading to vRealize Automation 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.
VMware, Inc. 8
Upgrading from vRealize Automation 6.2 to 7.0.1
Table 2. Supported Upgrade Paths in 6.x
Your Currently Installed Version Documentation for Incremental Upgrades
vCloud Automation Center 6.0 Perform upgrades in the following order:
n
Upgrading vCloud Automation Center 6.0 to 6.0.1
n
Upgrading to vCloud Automation Center 6.1
n
Upgrading to vRealize Automation 6.2.x
vCloud Automation Center 6.0.1 Perform upgrades in the following order:
n
Upgrading to vCloud Automation Center 6.1
n
Upgrading to vRealize Automation 6.2.x
vCloud Automation Center 6.1.x Upgrading to vRealize Automation 6.2.x
vRealize Automation 6.2.x Upgrade directly to the latest 6.2.x release as described in
Upgrading to vRealize Automation 6.2.x
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 3. 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.
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-restorenetbackup.pdf
See Shut Down vCloud Automation Center Services on Your
IaaS Windows Server.
If the Common Components Catalog is installed, you must
uninstall it before you upgrade.
VMware, Inc. 9
For information about how to uninstall, install, and upgrade the
Common Components Catalog, see the Common Components
Catalog documentation.
Upgrading from vRealize Automation 6.2 to 7.0.1
Table 3. Checklist for Upgrade of a Minimal vRealize Automation Deployment (Continued)
Task Instructions
Review the considerations for upgrade so that you
understand what can be upgraded, what cannot be upgraded,
and how upgraded items might behave differently in the target
deployment than in the source.
Not all items, including blueprints, reservations, and endpoints
can be upgraded. The presence of some unsupported
configurations blocks upgrade.
Prepare and update the embedded PostgreSQL database if
your deployment includes one.
Configure your hardware resources.
For sites with external Postgres databases, create a SaaS
Schema and Citext. to use when you upgrade PostgreSQL.
Download updates to the vRealize Automation appliance.
Upgrade the External PostgreSQL virtual appliance, if your
deployment includes one.
Install the update on the vRealize Automation appliance.
See Considerations About Upgrading to This vRealize
Automation Version.
See Prepare a Clustered PostgreSQL Environment for Upgrade.
See Increase vCenter Server Hardware Resources for Upgrade.
See Create a SaaS Schema and Citext Extension for External
vRealize Automation Database
See Downloading vRealize Automation Appliance Updates.
See Upgrade the External PostgreSQL Virtual Appliance
See Install the Update on the vRealize Automation Appliance.
Update the Single-Sign On utility to the VMware Identity
Manager utility.
Update the license key.
Migrate the Identity Store to the VMware Identity Manager
Download and install updates for IaaS.
Upgrade the external vRealize Orchestrator.
Add users or groups to an Active Directory connection
See Update Your Single Sign-On Password for VMware Identity
Manager.
See Update the License Key.
Migrate Identity Stores to the VMware Identity Manager
See Upgrading the IaaS Server Components.
See Upgrade Stand-Alone External vRealize Orchestrator for
Use With vRealize Automation.
See Add Users or Groups to an Active Directory Connection.
Table 4. Upgrade to vRealize Automation Distributed Installation Checklist
Task Instructions
Backup your current installation. This is a critical step.
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-restorenetbackup.pdf
Shut down vRealize Automation services on your Iaas
Windows server.
VMware, Inc. 10
See Shut Down vCloud Automation Center Services on Your
IaaS Windows Server.
Upgrading from vRealize Automation 6.2 to 7.0.1
Table 4. Upgrade to vRealize Automation Distributed Installation Checklist (Continued)
Task Instructions
If the Common Components Catalog is installed, you must
uninstall it before you upgrade.
Prepare and update the embedded PostgreSQL database
if your deployment includes one.
Configure your hardware resources for the upgrade.
Create a SaaS Schema and Citext. to use when you
upgrade PostgreSQL.
Download updates to the vRealize Automation appliance.
Upgrade the External PostgreSQL virtual appliance, if your
deployment includes one.
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.
Update the Single-Sign On utility to the VMware Identity
Manager utility.
For information about how to uninstall, install, and upgrade the
Common Components Catalog, see the Common Components
Catalog documentation.
See Prepare a Clustered PostgreSQL Environment for Upgrade.
See Increase vCenter Server Hardware Resources for Upgrade.
See Create a SaaS Schema and Citext Extension for External
vRealize Automation Database
See Downloading vRealize Automation Appliance Updates.
See Upgrade the External PostgreSQL Virtual Appliance
See Install the Update on the vRealize Automation Appliance.
See Update Your Single Sign-On Password for VMware Identity
Manager.
Update the license key.
Migrate the Identity Store to the VMware Identity Manager
utility
Install the update on the rest of your vRealize Automation
appliances.
Download and install updates for IaaS.
Upgrade the external vRealize Orchestrator
Enable your load balancers.
See Update the License Key.
Migrate Identity Stores to the VMware Identity Manager
Install the Update on Additional vRealize Automation Appliances
See Upgrading the IaaS Server Components.
See Upgrade Stand-Alone External vRealize Orchestrator for
Use With vRealize Automation .
Enable Your Load Balancers
VMware, Inc. 11
Upgrading from vRealize Automation 6.2 to 7.0.1
Considerations About Upgrading to This vRealize Automation Version
vRealize Automation 7 introduces various functional changes during and after the upgrade process that
you must consider before you upgrade your vRealize Automation deployment.
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.
Review the considerations in the subtopics before you upgrade.
Upgrade and Identity Appliance Specifications
You configure identity appliance upgrade information in response to prompts that are generated by the
vRealize Automation upgrade executable.
The target deployment uses the VMware Identity Manager.
Upgrade and Licensing
During the upgrade, your existing vRealize Automation 6.x licenses, and any vCloud Suite 6.x licenses
that you have, are removed. You must reenter your licenses in the vRealize Automation 7 vRealize
Automation appliance.
You now use vRealize Automation licensing for virtual appliances and IaaS by entering license key
information in the vRealize Automation appliance. Licensing information is no longer available in the IaaS
user interface and IaaS no longer performs licensing checks. Endpoints and quotas are enforced through
the end-user license agreements (EULAs).
Note Write down your vCloud Suite 6.x license key if you used it for vRealize Automation 6.2.x before
the upgrade. Upon upgrade, existing license keys are removed from the database.
For more information about re-entering your license information during or after upgrade, see Update the
License Key .
Understanding How Roles Are Upgraded
When you upgrade vRealize Automation, your organization's existing role assignments are maintained.
The upgrade also creates some role assignments to support additional blueprint architect roles.
The following architect roles are used to support the blueprint definition in the design canvas:
n
Application architect. Assembles existing components and blueprints to create composite blueprints.
n
Infrastructure architect. Creates and manages machine blueprints.
n
XaaS architect. Creates and manages XaaS blueprints.
VMware, Inc. 12
Upgrading from vRealize Automation 6.2 to 7.0.1
n
Software architect. Creates and manages Software components.
In vRealize Automation 7, tenant administrators and business group managers cannot design blueprints
by default. Upgraded tenant administrators and business group managers are given the infrastructure
architect role.
All users with the ability to reconfigure a machine in the vRealize Automation 6.2 source version are
authorized to change machine ownership after upgrading to this vRealize Automation version.
The following role assignments are made during the upgrade. Roles that are not listed in the table are
upgraded to the same role name in the target deployment.
Table 5. Roles Assigned During Upgrade
Role in Source Deployment Role in Target Deployment
Tenant administrator Tenant administrator and Infrastructure architect
Business group manager Business group manager and Infrastructure architect
Service architect XaaS architect
Application architect Software architect
For more information about tenant roles, see Foundations and Concepts.
Understanding How Blueprints Are Upgraded
As a rule, published blueprints are upgraded as published blueprints.
However, there are exceptions to that rule. Multi-machine blueprints are upgraded as composite
blueprints that contain blueprint components. Multi-machine blueprints that contain unsupported settings
are upgraded as unpublished.
For related information see Upgrade and vApp Blueprints, vCloud Endpoints, and vCloud Reservations
and Understanding How Multi-Machine Blueprints Are Upgraded.
Upgrade and vApp Blueprints, vCloud Endpoints, and vCloud Reservations
You cannot upgrade a deployment that contains vApp (vCloud) endpoints. The presence of endpoints of
type vApp (vCloud) prevent upgrade to vRealize Automation 7.0.1.
When upgrade encounters a vApp (vCloud) endpoint in the source deployment, upgrade fails on the
master virtual appliance and reports a message in the user interface and log. You can determine if your
source deployment contains vApp (vCloud) endpoint by logging in to vRealize Automation with Iaas
Administrator privileges, selecting Infrastructure > Endponts and noting the platform type value in the
Endpoints list. If the list contains endpoints of platform type vApp (vCloud), upgrade to 7.0.1is not
supported.
VMware, Inc. 13
Upgrading from vRealize Automation 6.2 to 7.0.1
Managed vApps for vCloud Air or vCloud Director resources are not supported in the target
vRealize Automation deployment.
Note A known issue exists where the following deprecated approval policy types appear in the list of
available approval policy types after upgrade is finished. These policy types are unusable.
n
Service Catalog - Catalog Item Request - vApp
n
Service Catalog - Catalog Item Request - vApp Component
You can create vCloud Air and vCloud Director endpoints and reservations in the target deployment. You
can also create blueprints that contain vCloud Air or vCloud Director machine components.
Understanding How Multi-Machine Blueprints Are Upgraded
You can upgrade managed service, multi-machine blueprints from a supported vRealize Automation 6.2.x
version deployment.
When you upgrade a multi-machine blueprint, component blueprints are upgraded as separate singlemachine blueprints. The multi-machine blueprint is upgraded as a composite blueprint in which its
previous children blueprints are nested as separate blueprint components.
The upgrade creates a single composite blueprint in the target deployment that contains one machine
component for each component blueprint in the source multi-machine blueprint. If the multi-machine
blueprint contains a setting that is not supported in the target vRealize Automation deployment, the
blueprint is upgraded but its status is changed to draft in the target deployment. For example, if the multimachine blueprint contains a private network profile, the private network profile setting is ignored during
upgrade and the blueprint is upgraded in a draft state. You can edit the draft blueprint to specify different
network profile information and publish it.
Note If a published blueprint in the source deployment is upgraded to a draft status blueprint, the
blueprint is no longer part of a service or entitlement. After you update and publish the blueprint in
vRealize Automation 7.0.1, you must recreate its needed approval policies and entitlements.
Some multi-machine blueprint settings are not supported in the target vRealize Automation deployment,
including private network profiles and routed network profiles with associated PLR edge settings. Note
that if you have used a custom property to specify PLR edge settings
(VCNS.LoadBalancerEdgePool.Names ), the custom property is upgraded.
If the multi-machine blueprint uses vSphere endpoints and NSX network and security settings, the
upgraded composite blueprint also contains NSX network and security components in the design canvas.
Note Routed gateway specifications for multi-machine blueprints, as defined in reservations, are
upgraded. However, the target vRealize Automation deployment does not support reservations for routed
profiles that contain associated PLR edge settings. If the source reservation contains a routed gateway
value for a PLR edge, the reservation is upgraded but the routed gateway setting is ignored. As a result,
the upgrade generates an error message in the log file and the reservation is disabled.
VMware, Inc. 14
Upgrading from vRealize Automation 6.2 to 7.0.1
During upgrade, spaces and special characters are removed from referenced network and security
component names.
Depending on the setting type, the network and security information is captured as several settings in the
new blueprint.
n
Settings for the overall blueprint on its properties page. This information includes app isolation,
transport zone, and routed gateway or NSX edge reservation policy information.
n
Available settings for vSphere machine components in NSX network and security components in the
design canvas.
n
Settings in the network and security tabs of individual vSphere machine components in the design
canvas.
Upgrade and Physical Endpoints, Reservations, and Blueprints
You cannot upgrade a deployment that contains physical endpoints. The presence of endpoints of type
physical prevents the vRealize Automation upgrade process from completing.
When upgrade encounters a physical endpoint in the source deployment, upgrade fails on the master
virtual appliance and reports a message in the user interface and log. You can determine if your source
deployment contains physical endpoints by logging in to vRealize Automation with Iaas Administrator
privileges, selecting Infrastructure > Endponts and noting the platform type value in the endpoints list. If
the list contains endpoints of Platform Type Physical, upgrade is not supported.
Physical endpoints, reservations, and machine components in blueprints are not currently supported in
the target vRealize Automation deployment.
Upgrade and Network Profile Settings
Private network profiles are not supported in the target deployment and are ignored during the upgrade.
Routed network profiles with associated PLR edge settings are also not supported in the target
deployment and are also ignored during the upgrade.
The private network profile type is not supported in the target vRealize Automation deployment. When the
vRealize Automation upgrade executable encounters a private network profile in the source deployment,
it ignores the network profile. Load balancers that reference those private networks are also ignored
during upgrade. The same upgrade conditions are true for a routed network profile with associated PLR
edge settings. Neither network profile configuration is upgraded.
If a reservation contains a private network profile, the private network profile setting is ignored during
upgrade and the reservation is upgraded as disabled in the target deployment.
If a reservation contains a routed network profile with associated PLR edge settings, the routed network
profile specification is ignored during upgrade and the reservation is upgraded as disabled in the target
deployment.
For information about upgrading a multi-machine blueprint that contains network settings, see
Understanding How Multi-Machine Blueprints Are Upgraded.
VMware, Inc. 15
Upgrading from vRealize Automation 6.2 to 7.0.1
Upgrade and Entitled Actions
You cannot upgrade machine actions.
The actions that you are entitled to perform on provisioned machines, based on blueprint specifications,
are not upgraded. To recreate allowed machine actions, customize the entitlements for blueprints to
enable only certain actions.
For related information, see Configuring vRealize Automation.
Upgrade and Custom Properties
All the custom properties that vRealize Automation supplies are available in the upgraded deployment.
Custom properties and property groups are upgraded.
Terminology and Related Changes
All the build profiles that you created in the source deployment are upgraded as property groups. The
term build profile has been retired.
The term property set has been retired and CSV property set files are no longer available.
Reserved Property Names
Several keywords are now reserved and some upgraded properties might be impacted. Some keywords
are used by the blueprint code that can be imported, for example by using vRealize CloudClient blueprint
import functions. These keywords are considered reserved and are not available for properties that are
being upgraded. The keywords include but are not limited to cpu, storage, and memory.
For more information about naming properties, see Custom Properties Reference.
Upgrade and Application Services
Application Services upgrade is not currently supported in the target vRealize Automation deployment.
Upgrade and Advanced Service Design
When you upgrade to the target vRealize Automation deployment, your Advanced Service Design items
are upgraded to XaaS elements.
XaaS components are available for use in the blueprint design canvas.
Upgrade and Blueprint Cost Information
As of 7.0, vRealize Automation cost profiles 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.
VMware, Inc. 16
Upgrading from vRealize Automation 6.2 to 7.0.1
vRealize Business is now tightly integrated with vRealize Automation and supports the following
enhanced costing features.
n
Unified location in vRealize Business to define flexible 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 configure vRealize Business
to handle costing.
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.
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 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.
If the virtual machine is on vCloud Networking and Security, you might need to allocate more RAM
space.
VMware, Inc. 17
Loading...