Failover steps for Applications Manager

Products

• Automic Applications Manager

Issue/Introduction

This article describes the steps required to run Applications Manager on a secondary server in the event the primary master server becomes unavailable. This assumes the Applications Manager data and database have been synced or cloned to the secondary environment.

Symptoms

• Primary Applications Manager master server is down or unreachable.
• Need to resume operations on a disaster recovery or secondary node.

Environment

Applications Manager

Unix/Linux or Windows Master

Resolution

Perform the following steps on the secondary server to assume the role of the Master:

1. Navigate to the $AW_HOME (Unix) or %AW_HOME% (Windows) directory.
2. Execute the site environment script:
   • Unix: . site/sosite
   • Windows: .\site\sosite.bat
3. Run the installation utility: awinstall
4. Select Option 1 (Initial Install/Upgrade from Prior version).
5. When prompted for configuration parameters, update the Automation Engine IP/host value to reflect the new server.
6. Complete the process to update core files and database values. Refer to Running awinstall option 1 for detailed utility steps.
7. Update Remote Agents to recognize the new Master:
   • Manual Method: Edit each Remote Agent's awenv.ini file and update the Master_Ip_Address parameter to the new server name/IP.
   • Automated Method (Unix): Run the following command from the new Master server to automatically update and restart agents: $AW_HOME/exec/DRSSHClient [optional list of remote hosts] Note: This requires the AgentService and sshdserver process to be running on the remote nodes.

Additional Information

For comprehensive disaster recovery strategies, including fresh installations, refer to the Applications Manager Disaster Recovery Documentation.