When you start vRealize Automation from the beginning, such as after a power outage or a controlled shutdown, you must start its components in a specified order.
Verify that the load balancers that your deployment uses are running.
- Start the MSSQL database machine. If you are using a legacy PostgreSQL standalone database, start that machine as well.
- Start your Identity Appliance or vSphere SSO appliance and wait for the startup to finish.
- Start the primary vRealize Appliance instance and wait for the startup to finish.
The primary vRealize Appliance instance contains the writeable Appliance Database, if applicable, and is the last appliance that you shut down in an ordered shutdown procedure.
- (Optional) If you are running a distributed deployment, start the secondary virtual appliances and wait for the startup to finish.
You must wait for one appliance to boot before you start up another appliance. Make sure that all services, besides IaaS and vRealize Orchestrator, are running on the appliance before you start another appliance.
- 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 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.
- Verify that the startup succeeded.
- Navigate to the vRealize 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 start up.
When all services are listed as registered, the system is ready to use.