7.4
Table Of Contents
- Upgrading from vRealize Automation 6.2.5 to 7.4
- Contents
- Upgrading vRealize Automation 6.2.5 to 7.4
- Prerequisites for Upgrading vRealize Automation
- 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 Price Information
- Upgrade and Catalog Items
- Checklist for Upgrading vRealize Automation
- vRealize Automation Environment User Interfaces
- Upgrading VMware Products Integrated with vRealize Automation
- Preparing to Upgrade vRealize Automation
- Updating the vRealize Automation Appliance
- Upgrading the IaaS Server Components After Upgrading vRealize Automation
- Upgrading vRealize Orchestrator After Upgrading vRealize Automation
- Add Users or Groups to an Active Directory Connection
- Enable Your Load Balancers
- Post-Upgrade Tasks for Upgrading vRealize Automation
- Port Configuration for High-Availability Deployments
- Reconfigure Built-In vRealize Orchestrator for High Availability
- Enabling the Connect to Remote Console Action for Consumers
- Restore External Workflow Timeout Files
- Verify That vRealize Orchestrator Service Is Available
- Reconfigure Embedded vRealize Orchestrator Endpoint
- Restore Changes to Logging in the app.config File
- Enable Automatic Manager Service Failover After Upgrade
- Run Test Connection and Verify Upgraded Endpoints
- Troubleshooting the vRealize Automation Upgrade
- Installation or Upgrade Fails with a Load Balancer Timeout Error
- Upgrade Fails for IaaS Website Component
- Manager Service Fails to Run Due to SSL Validation Errors During Runtime
- Log In Fails After Upgrade
- Catalog Items Appear in the Service Catalog After Upgrade But Are Not Available to Request
- PostgreSQL External Database Merge Is Unsuccessful
- Join Cluster Command Appears to Fail After Upgrading a High-Availability Environment
- Upgrade Is Unsuccessful if Root Partition Does Not Provide Sufficient Free Space
- Backup Copies of .xml Files Cause the System to Time Out
- Delete Orphaned Nodes on vRealize Automation
- Unable to Create New Directory in vRealize Automation
- Some Virtual Machines Do Not Have a Deployment Created During Upgrade
- Certificate Not Trusted Error
- Installing or Upgrading to vRealize Automation Fails
- Update Fails to Upgrade the Management Agent
- Management Agent Upgrade is Unsuccessful
- vRealize Automation Update Fails Because of Default Timeout Settings
- Upgrading IaaS in a High Availability Environment Fails
- Work Around Upgrade Problems
You successfully migrated an external vRealize Orchestrator 6.x installed on Windows to a
vRealize Orchestrator instance embedded in vRealize Automation 7.4.
What to do next
Set up the built-in vRealize Orchestrator server. See Configure the Built-In vRealize Orchestrator Server.
Migrate an External vRealize Orchestrator 6.x Virtual Appliance to
vRealize Automation 7.4
After you upgrade your vRealize Automation from version 6.x to version 7.4, you can migrate your
existing external Orchestrator 6.x Virtual Appliance to the Orchestrator server that is built into
vRealize Automation 7.4.
Note If you have a distributed vRealize Automation environment with multiple vRealize Automation
appliance nodes, perform the migration procedure only on the primary vRealize Automation node.
Prerequisites
n
Successful migration to vRealize Automation 7.4.
n
Stop the Orchestrator server service on the external Orchestrator.
n
Back up the database, including the database schema, of the external Orchestrator server.
Procedure
1 Download the migration tool from the target Orchestrator server to the source Orchestrator.
a Log in to the vRealize Orchestrator 6.x Virtual Appliance over SSH as root.
b Under the /var/lib/vco directory, run the scp command to download the migration-
tool.zip archive.
scp root@vra-va-hostname.domain.name:/var/lib/vco/downloads/migration-tool.zip ./
c Run the unzip command to extract the migration tool archive.
unzip migration-tool.zipy7
2 Export the Orchestrator configuration from the source Orchestrator server.
a In the /var/lib/vco/migration-cli/bin directory, run the export command.
./vro-migrate.sh export
This command combines the VMware vRealize Orchestrator configuration files and plug-ins into
an export archive.
An archive with file name orchestrator-config-export-orchestrator_ip_address-
date_hour.zip is created in the /var/lib/vco folder.
Upgrading from vRealize Automation 6.2.5 to 7.4
VMware, Inc. 60