When you upgrade the vRealize Orchestrator Cluster in the SDDC, start the update process by verifying the resource requirements of the vRealize Orchestrator Cluster and then taking snapshots of both the vRealize Automation and vRealize Orchestrator virtual machines.

About this task

Region

Folder

Role

Virtual Machine Name

Regoin A

sfo01-m01fd-vra

vRealize Automation Appliance

vra01svr01a.rainpole.local

sfo01-m01fd-vra

vra01svr01b.rainpole.local

sfo01-m01fd-vra

vRealize Orchestrator Appliance

vra01vro01a.rainpole.local

sfo01-m01fd-vra

vra01vro01b.rainpole.local

sfo01-m01fd-vra

vRealize Automation IaaS Web Server

vra01iws01a.rainpole.local

sfo01-m01fd-vra

vra01iws01b.rainpole.local

sfo01-m01fd-vra

vRealize Automation Model Manager Service

vra01ims01a.rainpole.local

sfo01-m01fd-vra

vra01ims01b.rainpole.local

sfo01-m01fd-vra

vRealize Automation DEM Workers

vra01dem01a.rainpole.local

sfo01-m01fd-vra

vra01dem01b.rainpole.local

sfo01-m01fd-vra

Microsoft SQL Server

vra01mssql01.rainpole.local

sfo01-m01fd-vraias

vRealize Automation Proxy Agent

sfo01ias01a.sfo01.rainpole.local

sfo01-m01fd-vraias

sfo01ias01b.sfo01.rainpole.local

Region B

lax01-m01fd-vraias

vRealize Automation Proxy Agent

lax01ias01a.lax01.rainpole.local

lax01-m01fd-vraias

lax01ias01b.lax01.rainpole.local

Procedure

  1. Log in to vCenter Server by using the vSphere Web Client.
    1. Open a Web browser and go to https://sfo01m01vc01.sfo01.rainpole.local/vsphere-client.
    2. Log in using the following credentials.

      Setting

      Value

      User name

      administrator@vsphere.local

      Password

      vsphere_admin_password

  2. From the Home menu of the vSphere Web Client, click VMs and Templates.
  3. Shut down the vRealize Orchestrator and vRealize Automation nodes in the environment according to Shutdown Order of the Management Virtual Machines.
    1. In the Navigator, expand the sfo01m01vc01.sfo01.rainpole.local > sfo01-m01dc > sfo01-m01fd-vra tree .
    2. Right-click the vra01dem01a virtual machine, select Power > Shut Down Guest OS and click Yes in the confirmation dialog box that appears.
    3. Repeat the steps on the other vRealize Orchestrator and vRealize Automation nodes.
  4. Verify that both vRealize Orchestrator nodes vra01vro01a.rainpole.local and vra01vro01b.rainpole.local have their memory increased to 6 GB.
    1. In the Navigator, click VMs and Templates and navigate to the vra01vro01a.rainpole.local virtual machine.
    2. Right-click the vra01vro01a.rainpole.local virtual machine and select Edit Settings.
    3. In the Edit Settings dialog box, ensure the following resources have been allocated to the virtual machine and click OK.

      Setting

      Value

      CPU

      2

      Memory

      6144 MB (6 GB)

    4. Repeat these steps for vra01vro01b.rainpole.local.
  5. Take a snapshot of each node in the vRealize Orchestrator cluster and vRealize Automation components.
    1. In the Navigator, click VMs and Templates and navigate to the vra01vro01a.rainpole.local virtual machine.
    2. Right-click the vra01vro01a.rainpole.local virtual machine and select Snapshot > Take Snapshot.
    3. In the Take VM Snapshot dialog box, enter the following settings and click OK.

      Setting

      Value

      Name

      VMware Validated Design 4.1 Cloud Management Platform vRealize Orchestrator Migration

      Description

      -

      Snapshot the virtual machine's memory

      Deselected

      Quiesce guest file system (Needs VMware Tools installed)

      Deselected

    4. Repeat these steps for vra01vro01b.rainpole.local and for the other components of the vRealize Automation components.

      Performing this operation results in having two layers of snapshots for the vRealize Automation components: VMware Validated Design 4.1 Cloud Management Platform Upgrade and VMware Validated Design 4.1 Cloud Management Platform vRealize Orchestrator Migration. In this way, you can perform a rollback to vRealize Automation stack version 7.3 with external vRealize Orchestrator if the vRealize Orchestrator migration fails. In addition, if the allocated maintenance window is exceeded, you must roll the entire vRealize Automation stack back to version 7.2 and then perform the upgrade again later.

  6. Power the vRealize Automation and vRealize Orchestrator nodes back on in the environment according to Startup Order of the Management Virtual Machines.
    1. In the Navigator, expand the sfo01m01vc01.sfo01.rainpole.local > sfo01-m01dc > sfo01-m01fd-vra tree .
    2. Right-click the vra01mssql01 virtual machine, select Power > Power On and click Yes in the confirmation dialog box that appears.
    3. Repeat the steps on the other vRealize Automation and vRealize Orchestrator nodes.
  7. Log in to the vRealize Automation appliance and run the following commands to start the vRealize Orchestrator services.
    1. Open an SSH client to the primary vRealize Orchestrator virtual appliance vra01svr01a.rainpole.local
    2. Log in using the following credentials.

      Setting

      Value

      User name

      root

      Password

      vra_appA_root_password

    3. Start the Control Center service of the built-in vRealize Orchestrator server.  
      service vco-configurator start