When you start vRealize Automation 7.x, such as after a power outage, a controlled shutdown, or after recovery, you must start components in a specified order.

Prerequisites

Verify that the load balancers that your deployment uses are running.

Procedure

  1. Start the MS SQL database machine. If you are using a legacy PostgreSQL standalone database, start that machine as well.
  2. (Optional) (Optional) If you are running a deployment that uses load balancers with health checks, disable the health check before you start the vRealize Automation appliance. Only ping health check should be enabled. Only the ping health check option must be enabled.
  3. Start all instances of vRealize Automation appliance at the same time and wait for approximately 15 minutes for the appliances to start up.
    After startup, verify that the vRealize Automation appliance services are up and running.
  4. Start the primary Web node and wait for the start up to finish.
  5. (Optional) If you are running a distributed deployment, start all secondary Web nodes and wait 5 minutes.
  6. Start the primary Manager Service machine and wait for 2–5 minutes, depending on your on-site configuration.
  7. (Optional) If you are running a distributed deployment, start secondary Manager Service machines and wait 2–5 minutes .
    On the secondary machines, do not start or run the Windows service unless you are configured for automatic Manager Service failover.
  8. Start the DEM Orchestrator and Workers and all vRealize Automation proxy agents.
  9. If you disabled health checks for your load balancers, re-enable them.
  10. Verify that the startup succeeded.
    1. Open a Web browser to the vRealize Automation appliance management interface URL.
    2. Select the Services tab.
    3. Select the Refresh tab to monitor the progress of the startup of the application services.

Results

When all services are listed as registered, the deployment is ready.