When you start vRealize Automation from the beginning, such as after a power outage, a controlled shutdown or after recovery, you must start its components in a specified order.
Verify that the load balancers that your deployment uses are running.
- Start the MS SQL database machine. If you are using a legacy PostgreSQL standalone database, start that machine as well.
- (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.
- In vSphere, start the master vRealize Automation appliance.
- Wait until the licensing service is running and REGISTERED in the master appliance management interface.
- Start the remaining vRealize Automation appliances at the same time.
- Wait for the appliances to start, and verify that services are running and listed as REGISTERED in the appliance management interface.
It might take 15 or more minutes for appliances to start.
- Start the primary Web node and wait for the startup to finish.
- (Optional) If you are running a distributed deployment, start all secondary Web nodes and wait 5 minutes.
- Start the primary Manager Service machine and wait for 2 to 5 minutes, depending on your site configuration.
- (Optional) If you are running a distributed deployment, start secondary Manager Service machines and wait 2 to 5 minutes.
On secondary machines, do not start or run the Windows service unless you are configured for automatic Manager Service failover.
- Start the Distributed Execution Manager Orchestrator and Workers and all vRealize Automation proxy agents.
You can start these components in any order and you do not need to wait for one startup to finish before you start another.
- If you disabled health checks for your load balancers, reenable them.
- Verify that the startup succeeded.
- Open a Web browser to the vRealize Automation appliance management interface URL.
- Click the Services tab.
- Click the Refresh tab to monitor the progress of service startup.
When all services are listed as registered, the system is ready to use.