Sequence for Start, Shutdown and Restart of VMware vRA 7.x Environment

Start Up vRealize Automation

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.

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) 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.
3	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.
4	Start the primary Web node and wait for the startup 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 node and wait for 2 to 5 minutes, depending on your site configuration.
7	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.
8	If you disabled health checks for your load balancers, reenable them.
9	Verify that the startup succeeded. a Navigate to the vRealize Automation appliance management console by using its fully qualified domain name, https://vra-va-hostname.domain.name:5480/. b Click the Services tab. c Click the Refresh tab to monitor the progress of service startup.

When all services are listed as registered, the system is ready to use. 

Shut Down vRealize Automation

To preserve data integrity, you must shut down vRealize Automation in a specified order.

If you are using vCenter Server to manage your virtual machines, use the guest shutdown command to shut down vRealize Automation.

Procedure

1	Shut down the Distributed Execution Manager Orchestrator and Workers and all vRealize Automation agents in any order and wait for all components to finish shutting down.
2	Shut down virtual machines that are running the Manager Service and wait for the shutdown to finish.
3	(Optional) For distributed deployments, shut down all secondary Web nodes and wait for the shutdown to finish.
4	Shut down the primary Web node, and wait for the shutdown to finish.
5	(Optional) For distributed deployments, shut down all secondary vRealize Automation appliance instances and wait for the shutdown to finish.
6	Shut down the primary vRealize Automation appliance and wait for the shutdown to finish. If applicable, the primary vRealize Automation appliance is the one that contains the master, or writeable, Appliance Database. Make a note of the name of the primary vRealize Automation appliance. You use this information when you restart vRealize Automation.
7	Shut down the MSSQL virtual machines in any order and wait for the shutdown to finish.
8	If you are using a legacy standalone PostgreSQL database, also shut down that machine.

You shut down your vRealize Automation deployment.

Restart vRealize Automation

When you restart more than one vRealize Automation component, you must restart the components in a specified order.

You might need to restart some components in your deployment to resolve anomalous product behavior. If you are using vCenter Server to manage your virtual machines, use the guest restart command to restart vRealize Automation.

If you cannot restart a component or service, follow the instructions in shutdown and Startup order

Prerequisites

Verify that load balancers that your deployment uses are running.

Procedure

1	Restart the all instances of the vRealize Automation appliance at the same time.
2	Restart the primary Web node and wait for the startup to finish.
3	If you are running a distributed deployment, start all secondary Web nodes and wait for the startup to finish.
4	Restart all Manager Service nodes and wait for the startup to finish.
5	Restart the Distributed Execution Manager Orchestrator and Workers and all vRealize Automation agents, and wait for the startup to finish for all components. You can restart these components in any order.
6	Verify that the service you restarted is registered. a Navigate to the vRealize Automation appliance management console by using its fully qualified domain name, https://vra-va-hostname.domain.name:5480/. b Click the Services tab. c Click the Refresh tab to monitor the progress of service startup.

When all services are listed as registered, the system is ready to use.