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
4 Run the following command to delete the existing Disk 1 partitions and create a 44-GB root
partition and a 6-GB swap partition.
(echo d; echo 2; echo d; echo 1; echo n; echo p; echo ; echo ; echo '+44G'; echo n; echo
p; echo ; echo ; echo ; echo w; echo p; echo q) | fdisk /dev/sda
5 Run the following command to change the swap partition type.
(echo t; echo 2; echo 82; echo w; echo p; echo q) | fdisk /dev/sda
6 Run the following command to set the Disk 1 bootable ag.
(echo a; echo 1; echo w; echo p; echo q) | fdisk /dev/sda
7 Run the following command to register the partition changes with the Linux kernel.
partprobe
If you see a message prompting you to reboot before you make further changes, ignore the
message. Rebooting the system before step 10 corrupts the upgrade process.
8 Run the following command to format the new swap partition.
mkswap /dev/sda2
9 Run the following command to mount the swap partition.
swapon -a
10 Reboot the vRealize Automation appliance.
11 After the appliance reboots, run the following command to resize the Disk 1 partition table.
resize2fs /dev/sda1
12 To verify that the disk expansion is successful, run df -h and check that the available disk space
on /dev/sda1 is greater than 3 GB.
Manual PostgreSQL Database Merge
The external PostgreSQL database merge with the embedded PostgreSQL database does not succeed.
Problem
If the PostgreSQL database upgrade merge does not succeed, you can perform a manual merge.
Solution
1 Revert the vRealize Automation virtual appliance to the snapshot you made before upgrade.
2 Log in to the vRealize Automation virtual appliance and run this command to allow upgrade to
complete if the database merge does not succeed.
touch /tmp/allow-external-db
The command does not disable auto merge.
3 On the remote PostgreSQL database host, connect to the PostgreSQL database using the psql tool and
run these commands.
CREATE EXTENSION IF NOT EXISTS "hstore";
CREATE EXTENSION IF NOT EXISTS "uuid-ossp";
CREATE SCHEMA saas AUTHORIZATION vcac;
Upgrading from vRealize Automation 6.2.x to 7.1
VMware, Inc. 49