7.2
Table Of Contents
- Upgrading from vRealize Automation 6.2.4 or 6.2.5 to 7.2
- Contents
- Updated Information
- vRealize Automation 6.2.4 or 6.2.5 Prerequisites, Considerations, and Process
- Prerequisites for Upgrading from vRealize Automation 6.2.4 or 6.2.5
- 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
- Checklist for Upgrading vRealize Automation 6.2.4 or 6.2.5
- Preparing to Upgrade vRealize Automation 6.2.4 or 6.2.5
- Updating the vRealize Automation 6.2.4 or 6.2.5 Appliance
- Upgrading the IaaS Server Components After Upgrading vRealize Automation 6.x to 7.2
- Updating vRealize Orchestrator After Upgrading from vRealize Automation 6.x to 7.2
- Add Users or Groups to an Active Directory Connection
- Enable Your Load Balancers
- Post-Upgrade Tasks for Upgrading vRealize Automation 6.2.4 or 6.2.5
- Port Configuration for High-Availability Deployments
- Enabling the Connect to Remote Console Action for Consumers
- Restore External Workflow Timeout Files
- Verify That vRealize Orchestrator Service Is Available
- Restore Embedded vRealize Orchestrator Endpoint
- Restore Changes to Logging in the app.config File
- Troubleshooting the vRealize Automation 6.2.4 or 6.2.5 Upgrade
- Migration of Identity Store Fails Because the Active Directory is not Synchronized
- 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 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 But Are Not Available to Request
- User Migration Batch Files Are Ineffective
- 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
- Upgrade Fails to Upgrade the Management Agent or Certificate Not Installed on a IaaS Node
- Unable to Create New Directory in vRealize Automation
- Index
f Verify that the Independent option is deselected for Mode and SCSI (0:2) is selected for Virtual
Device Mode, and click Next.
If prompted to accept recommended seings, accept the recommended seings.
g Click Finish.
h Click OK.
7 If there is an existing virtual Disk 4 from a previous vRealize Automation release, complete these steps.
a Power on the virtual machine.
b Open a new command prompt and navigate to /etc/fstab.
c Open the fstab le, and remove lines starting with /dev/sdd that contain the Wal_Archive write
ahead logs.
d Save the le.
e Power o the virtual machine.
f Right-click the cloned vRealize Automation appliance icon and select Edit .
g Delete Disk 4 on the cloned virtual machine and complete the next step to create a new Disk 4 with
a disk size of 50 GB.
8 Complete these steps to add a Disk 4 with a disk size of 50 GB.
a Click Add above the Resources table to add a virtual disk.
b Select Hard Disk for the Device Type, and click Next.
c Select Create a new virtual disk, and click Next.
d Set disk size value to 50 GB.
e Select Store with the virtual machine and click Next.
f Verify that the Independent option is deselected for Mode and SCSI (0:3) is selected for Virtual
Device Mode, and click Next.
If prompted to accept recommended seings, accept the recommended seings.
g Click Finish.
h Click OK.
9 Create a snapshot of the virtual machine.
What to do next
“Power On the Entire System,” on page 20.
Power On the Entire System
After you increase the vCenter hardware resources for upgrade, you power on the system before you
perform the upgrade.
Prerequisites
n
“Back Up Your Existing vRealize Automation 6.2.4 or 6.2.5 Environment,” on page 18
n
“Increase vCenter Server Hardware Resources for vRealize Automation 6.2.4 or 6.2.5,” on page 19
Upgrading from vRealize Automation 6.2.4 or 6.2.5 to 7.2
20 VMware, Inc.