After you upgrade the vRealize Automation, migrate your existing external vRealize Orchestrator cluster to a vRealize Orchestrator instance that is embedded in the vRealize Automation Appliance in Region A.

About this task

In this version of this validated design, the external vRealize Orchestrator cluster has been replaced with vRealize Orchestrator components that are embedded in the vRealize Automation appliances.

Note:

You must migrate vRealize Orchestrator from external to embedded configuration in the same maintenance window in which you are upgrading vRealize Automation.

Table 1. vRealize Orchestrator Nodes in the SDDC

Region

Role

IP Address

Fully Qualified Domain Name

Region A

vRealize Orchestrator VIP

192.168.11.65

vra01vro01.rainpole.local

vRealize Orchestrator

192.168.11.63

vra01vro01a.rainpole.local

vRealize Orchestrator

192.168.11.64

vra01vro01b.rainpole.local

Note:

VMware Validated Design 4.1 introduces a new convention for host and object names in the SDDC. The step-by-step upgrade guidance uses the new names for both the pre- and post-upgrade SDDC setups. For information about the new convention, see Mapping Component Names Between Versions 4.0 and 4.1 of VMware Validated Design.

Prerequisites

  • Upgrade to vRealize Automation 7.3.

  • Allocate 6 GB of memory to the primary and secondary vRealize Orchestrator virtual appliances (vra01vro01a.rainpole.local and vra01vro01b.rainpole.local).

  • Verify that the vRealize Orchestrator node configuration is valid using the Validate Configuration option of the vRealize Orchestrator Control Center at https://vra01vro01a.rainpole.local:8283/vco-controlcenter.

  • Verify that a backup of the vRealize Orchestrator nodes participating in the cluster exists. See the VMware Validated Design Backup and Restore documentation.

  • Verify that a backup of the vRealize Orchestrator vROCluster database from the Microsoft SQL server exists. See the VMware Validated Design Backup and Restore documentation and documentation of the Microsoft SQL server.

  • Verify that a backup of the vRealize Automation appliances and IaaS Windows virtual machines exists. ee the VMware Validated Design Backup and Restore documentation.

  • Verify that a backup of the vRealize Automation database from the appliance exists.

  • Direct the traffic to the primary vRealize Automation nodes if the Load Balancer has been reconfigured after the upgrade of vRealize Automation. See Direct Traffic to the Primary Nodes and Disable Health Monitoring for vRealize Automation on the Load Balancer.

  • Verify that the vRealize Automation environment has been quiesced of all activities, including but not limited to, users ordering new virtual machines and third-party integration that may automate the order of new virtual machines. Without quiescing the environment, rollback operations might be disrupted by generate orphaned objects. You might also have to extend the time of the maintenance window.

  • Verify that any third-party integration that might have been configured with vRealize Automation and vRealize Orchestrator is compatible with version 7.3. Contact the vendor of the third-party software to check compatibility and availability.

What to do next

  • Verify that the embedded vRealize Orchestrator is operational after the upgrade. See Validate the Cloud Management Platform in the VMware Validated Design Operational Verification documentation.