7.4

6 Run the following command to set the Disk 1 bootable flag.
(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 30 GB.
Backup Copies of .xml Files Cause the System to Time
Out
vRealize Automation registers any file with an .xml extension in
the \VMware\vCAC\Server\ExternalWorkflows\xmldb\ directory. If this directory contains backup files with
an .xml extension, the system runs duplicate workflows that cause the system to time out.
Solution
Workaround: When you back up files in this directory, move the backups to another directory, or change
the extension of the backup file name to something other than .xml.
Delete Orphaned Nodes on vRealize Automation
An orphaned node is a duplicate node that is reported on the host but does not exist on the host.
Problem
When you verify that each IaaS and virtual appliance node is in a healthy state, you might discover that a
host has one or more orphaned nodes. You must delete all orphaned nodes.
Solution
1 On your primary vRealize Automation appliance, log in to vRealize Automation Appliance
Management as root using the password you entered when you deployed the vRealize Automation
appliance.
Upgrading from vRealize Automation 6.2.5 to 7.4
VMware, Inc. 88