You can configure the vRealize Automation IaaS Manager Service to fail over to a backup when the primary Manager Service stops.

Starting in vRealize Automation 7.3, you no longer have to manually start or stop the Manager Service on each Windows server, to control which serves as primary or backup. Automatic Manager Service failover is enabled by default in the following cases.

  • When you install vRealize Automation silently or with the Installation Wizard.
  • When you upgrade IaaS through the administration interface or with the automatic upgrade script.

Failover is not enabled when you use the standard Windows-based installer to add a Manager Service host or upgrade IaaS. To enable it, see Enable Automatic Manager Service Failover.

When automatic failover is enabled, the Manager Service automatically starts on all Manager Service hosts, including backups. The automatic failover feature allows hosts to transparently monitor each other and fail over when necessary. The feature requires that the Windows service is running on all hosts.

Note: You are not required to use automatic failover. You may disable it and continue to manually start and stop the Windows service to control which host serves as primary or backup. If you take the manual failover approach, you must only start the service on one host at a time. With automatic failover disabled, simultaneously running the service on multiple IaaS servers makes vRealize Automation unusable.

Do not attempt to selectively enable or disable automatic failover. Automatic failover must always be synchronized as on or off, across every Manager Service host in an IaaS deployment.

If automatic failover does not appear to be working, see Automatic Manager Service Failover Does Not Activate for troubleshooting tips.

For information about how to load balance Manager Service hosts, see vRealize Automation Load Balancing.