Observe the proper procedures when starting or shutting down vRealize Automation.

The recommended manner to shut down and start vRealize Automation components is to use the Power OFF and ON functionality provided in Lifecycle Operations > Environments section of vRealize Suite Lifecycle Manager. The following procedures outline manual methods to shut down and start vRealize Automation components in case vRealize Suite Lifecycle Manager is not available for some reason.

Shut down vRealize Automation

To preserve data integrity, shut down the vRealize Automation services before powering off the virtual appliances. Using SSH or VMRC, you can shut down or start all nodes from any individual appliance.

Note: Avoid using vracli reset vidm commands if at all possible. This command resets all configurations of Workspace One Access and breaks the association between users and provisioned resources.
  1. Log in to the console of any vRealize Automation appliance using either SSH or VMRC.
  2. To shut down the vRealize Automation services on all cluster nodes, Run the following set of commands.
    Note: If you copy any of these commands to run and they fail, paste them into notepad first, and then copy them again before running them. This procedure strips out any hidden characters and other artifacts that might exist in the documentation source. 
    /opt/scripts/deploy.sh --shutdown
  3. Shut down the vRealize Automation appliances.

Your vRealize Automation deployment is now shut down.

Start vRealize Automation

Following an unplanned shutdown, a controlled shutdown, or a recovery procedure, you must restart vRealize Automation components in a specific order. vRLCM is a non-critical component, so you can start it at any time. VMware Workspace ONE Access, formerly VMware Identity Management, components must be started before you start vRealize Automation.

Note: Verify that applicable load balancers are running before starting vRealize Automation components.
  1. Power on all vRealize Automation appliances and wait for them to start.
  2. Log into the console for any appliance using SSH or VMRC and run the following command to restore the services on all nodes.
    /opt/scripts/deploy.sh
  3. Verify that all services are up and running with the following command.
    kubectl get pods --all-namespaces
    Note: You should see three instances of every service, with a status of either Running or Completed.

    When all services are listed as Running or Completed, vRealize Automation is ready to use.

Restart vRealize Automation

You can restart all vRealize Automation services centrally from any of the appliances in your cluster. Follow the preceding instructions to shut down vRealize Automation, and then use the instructions to start vRealize Automation. Before restarting vRealize Automation, verify that all applicable load balancer and VMware Workspace ONE Access components are running.

When all services are listed as Running or Completed, then vRealize Automation is ready to use.

Run the following command to verify that all services are running:

kubectl -n prelude get pods