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.
- Start all instances of vRealize Automation appliance at the same time and wait for approximately 15 minutes for the appliances to startup. Verify that the vRealize Automation appliance services are up and running.
If you have more than one node and you start only one node, you may have to wait for extra 35 minutes. However, the extra wait time would be canceled out as soon as you start the second node.
- 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 node and wait for 2 to 5 minutes, depending on your site configuration.
- 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.
- Navigate to the vRealize Automation appliance management console by using its fully qualified domain name, https://vra-va-hostname.domain.name:5480/.
- 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.