Before you begin to upgrade, shut down the vRealize Automation IaaS Windows Server and all Manager machines and identity virtual appliance machines and take a snapshot. 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 server 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 MSSQL 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 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. See Configuring vRealize Suite 6.0 for Backup and Restore by Using Symantec NetBackup 7.6 at http://www.vmware.com/pdf/vrealize-suite-60-backup-and-restore-netbackup.pdf.
- 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 Windows Server machine
Manager machines (if any)
Identity virtual appliance
- Take a snapshot of all vRealize Automation 6.2.x machines.
- Clone the vRealize Automation appliance nodes that contain Disk 4 and use the new clones during the upgrade process.
- Power on the entire system.
For instructions, see the 6.2 version of the Start Up vRealize Automation topic at http://pubs.vmware.com/vra-62/topic/com.vmware.vra.system.administration.doc/GUID-4A4BD979-61EF-4590-AEDF-6A9BA42426B6.html.Note:
The topic should have vra-62 in the URL.
- Verify that the system is fully functional.