7.0
Table Of Contents
- Upgrading from vRealize Automation 6.2 to 7.0.1
- Contents
- Upgrading to vRealize Automation 7.0
- 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
- Backing up and Saving Your Existing Environment
- Shut Down vCloud Automation Center Services on Your IaaS Windows...
- Prepare a Clustered PostgreSQL Environment for Upgrade
- Increase vCenter Server Hardware Resources for Upgrade
- (Optional) Reconfigure Disk 1 on All vRealize Automation Appliance Nodes
- Create a SaaS Schema and Citext Extension for External vRealize...
- Downloading vRealize Automation Appliance Updates
- Updating the vRealize Automation Appliance
- (Alternative Option) Upgrade the External PostgreSQL Virtual Appliance
- Install the Update on the vRealize Automation Appliance
- Update Your Single Sign-On Password for VMware Identity Manager
- Update the License Key
- Migrate Identity Stores to the VMware Identity Manager
- Install the Update on Additional vRealize Automation Appliances
- 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
- Port Configuration for High-Availability Deployments
- Enabling the Connect to Remote Console Action for Consumers
- Reconfigure External Workflow Timeouts
- Verify That vRealize Orchestrator Service is Available
- Restore Embedded vRealize Orchestrator Endpoint
- Configure an External PostgreSQL Database to Merge into an Embedded PostgreSQL Environment
- Restore Changes to Logging
- Ensure Deployed Virtual Machines Register With Software Service
- 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
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.
Upgrading from vRealize Automation 6.2 to 7.0.1
VMware, Inc. 15