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
Reconfigure Disk 1 on All vRealize Automation Appliance Nodes
You must reconfigure Disk 1 on the vRealize Automation version you are upgrading from before
beginning the upgrade.
Perform this procedure for each replica appliance node sequentially, and then for the master node.
Note When you perform this procedure, you might see these warning messages:
n
WARNING: Re-reading the partition table failed with error 16:
Device or resource busy. The kernel still uses the old table. The
new table will be used at the next reboot or after you run
partprobe(8) or kpartx(8) Syncing disks.
n
Error: Partition(s) 1 on /dev/sda have been written, but we have been unable to inform the kernel
of the change, probably because it/they are in use. As a result, the old partition(s) will remain
in use. You should reboot now before making further changes.
Ignore this message: You should reboot now before making further changes. If you reboot your system
before step 10, you will corrupt the upgrade process.
Procedure
1 Power on and SSH login to the vRealize Automation appliance.
2 Stop all vRealize Automation services.
a service vcac-server stop
b service vco-server stop
c service vpostgres stop
3 Unmount the swap partition:
swapoff -a
4 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 Change the swap partition type.
(echo t; echo 2; echo 82; echo w; echo p; echo q) | fdisk /dev/sda
6 Set the Disk 1 bootable flag:
(echo a; echo 1; echo w; echo p; echo q) | fdisk /dev/sda
Upgrading from vRealize Automation 6.2 to 7.0.1
VMware, Inc. 24