Before you begin to upgrade, shut down and take a snapshot of the vRealize Automation IaaS Windows Server, all Model Manager machines, and the identity virtual appliance machines. If the upgrade fails, you can use the snapshot to return to the last known good configuration and attempt another upgrade.
Verify that the embedded PostgreSQL database is in high-availability mode. If it is, locate the current Master node. See the knowledge base article http://kb.vmware.com/kb/2105809.
If the vRealize Automation Microsoft SQL database is not hosted on the IaaS server, create a database backup file.
Verify that you have completed the backup prerequisites. See Backing up and Saving Your Existing Environment .
Verify that you have taken a snapshot of your system while it is shut down. See the vSphere 6.0 Documentation.
If you cannot shut down your system, take an in-memory snapshot of all the nodes.
Verify that you have a backup of your entire system.
- Log in to vCenter Server.
- Locate the vRealize Automation 6.2.x IaaS Windows Server, all Manager machines, and Identity virtual appliance machines.
- Select a machine and click Shutdown guest in the following order.
IaaS proxy agent virtual machines
DEM Worker virtual machines
DEM Orchestrator virtual machine
Manager Service virtual machine
WEB Service virtual machines
Secondary vRealize Automation virtual appliances
Primary vRealize Automation virtual appliance
Manager machines (if any)
- Take a snapshot of all vRealize Automation 6.2.x machines.
- Clone the vRealize Automation appliance nodes and perform the upgrade on the cloned machines. Keep the original, in case system restore is required later on.