Start, Shut Down or Restart vRealize Automation

vRA-Logo

The start, shut down or restart sequence of vRealize Automation (vRA) isn’t that difficult, but if you throw in a load balancer or if you have a bigger distributed vRA environment then things get interesting.

Load Balancer

When you are using a load balancer in your configuration you need to check your load balancer for what kind of “health monitor” you are using for the vRA Appliances. Because if you are using the vRA Appliance service “health monitor”, you need to change it to just plain old ICMP or the vRA service won’t come online after a cold boot.

vRA-LB

Start vRealize Automation

When you start vRA after a power outage or a controlled shut down, you must start the vRA components in this specified order :

  1. Boot the MSSQL Server / Cluster
    • Wait until Service is up
  2. Boot the PostgresSQL Server / Cluster
    • Wait until Service is up
  3. Boot the Identity Appliance or SSO Server
    • Wait until Service is up
  4. Boot the Primary vRealize Appliance
    • Wait until VM is up
  5. Boot the optional Secondary vRealize Appliance
    • Wait until VM is up
  6. Boot the Primary Web Server
    • Wait until VM is up
  7. Boot the optional Secondary Web Server
    • Wait until VM is up and wait 5 minutes
  8. Boot all the Manager Servers
    • Wait until VMs are up and wait 2-5 minutes
  9. Boot all the vRealize Automation Agent Servers
    • Wait until VMs are up
  10. Boot all the Distributed Excecution Manager Orchestrator / Worker Servers
    • Wait until VMs are up

Shut Down vRealize Automation

When you want to do a controlled shut down of vRA, you must shut down the vRA components in this specified order :

  1. Shut Down all the Distributed Excecution Manager Orchestrator / Worker Servers
    • Wait until VMs are down
  2. Shut Down all the vRealize Automation Agent Servers
    • Wait until VMs are down
  3. Shut Down all the Manager Servers
    • Wait until VMs are down
  4. Shut Down the optional Secondary Web Server
    • Wait until VM is down
  5. Shut Down the Primary Web Server
    • Wait until VM is down
  6. Shut Down the optional Secondary vRealize Appliance
    • Wait until VM is down
  7. Shut Down the Primary vRealize Appliance
    • Wait until VM is down
  8. Shut Down the MSSQL Server / Cluster
    • Wait until VM is down
  9. Shut Down the PostgresSQL Server / Cluster
    • Wait until VM is down
  10. Shut Down the Identity Appliance or SSO Server
    • Wait until VM is down

Restart vRealize Automation

I noticed that the documentation of VMware says that it is possible to restart the different components, but in the field I had some “challenges” with this method… So nowadays I just shut everything down and start everything from scratch. This way I know for sure all the services will come online OK.

To do this just follow the shut down sequence and the start sequence above. Or use this simple PowerCLI script below that shuts down the VMs and starts them again in the appropriate order. Because almost no vRA deployment is the same please check the VM names and maybe add or remove some lines if necessary.

Marco van Baggum

Marco van Baggum

Marco works as a Staff Consulting Architect at VMware. Want to learn more about Marco? Check out Marco's About page.

3 thoughts on “Start, Shut Down or Restart vRealize Automation

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.