Total Pageviews

Starting Up and Shutting Down vRealize Automation


Starting Up and Shutting Down vRealize Automation

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.     In vSphere, start the master vRealize Automation appliance.
4.     Wait until the licensing service is running and REGISTERED in the master appliance management interface.
5.     Start the remaining vRealize Automation appliances at the same time.
6.     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.
7.     Start the primary Web node and wait for the startup to finish.
8.     (Optional) If you are running a distributed deployment, start all secondary Web nodes and wait 5 minutes.
9.     Start the primary Manager Service machine and wait for 2 to 5 minutes, depending on your site configuration.
10.  (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.
11.  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.
12.  If you disabled health checks for your load balancers, reenable them.
13.  Verify that the startup succeeded.
a.     Open a Web browser to the vRealize Automation appliance management interface URL.
b.     Click the Services tab.
c.     Click the Refresh tab to monitor the progress of service startup.

Results

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

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 OS restart command to restart vRealize Automation.
If you cannot restart a component or service, follow the instructions in Shut Down vRealize Automation and Start Up vRealize Automation.
Prerequisites
·       Verify that all load balancers that your deployment uses are running.
·       Verify that your vRealize Automation appliance database is operating in asynchronous mode. If it is operating in synchronous mode, use the Virtual Appliance Management Interface to change it to asynchronous mode. If applicable, return the appliance database to synchronous mode after you complete the procedure. See Managing the vRealize Automation Postgres Appliance Database for more information.

Procedure

1.     In vSphere, if the master vRealize Automation appliance is not running, start the master vRealize Automation appliance now.
2.     Wait until the licensing service is running and REGISTERED in the master appliance management interface.
3.     Start the remaining vRealize Automation appliances at the same time.
4.     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.
5.     Restart the primary Web node and wait for startup to finish.
6.     If you are running a distributed deployment, restart secondary Web nodes and wait for startup to finish.
7.     Restart Manager Service nodes and wait for startup to finish.
If running automatic Manager Service failover, and you want to keep the active and passive nodes the same, restart in the following order:
a.     Stop the passive Manager Service nodes without restarting them.
b.     Completely restart the active Manager Service node.
c.     Start the passive Manager Service nodes.
8.     Restart the Distributed Execution Manager Orchestrator and Workers and all vRealize Automation agents, and wait for startup to finish for all components.
You can restart these components in any order.
9.     Verify that the service you restarted is registered.
a.     Open a Web browser to the vRealize Automation appliance management interface URL.
b.     Click the Services tab.
c.     Click the Refresh tab to monitor the progress of service startup. 


 




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.

Results

You shut down your vRealize Automation deployment.

No comments:

Post a Comment

Deploy Windows VMs for vRealize Automation Installation using vRealize Suite Lifecycle Manager 2.0

Deploy Windows VMs for vRealize Automation Installation using vRealize Suite Lifecycle Manager 2.0 In this post I am going to describe ...