Restart redundant platforms

Redundant AppEngines are hosted on redundant platform objects. Some maintenance tasks, such as applying security updates, may require that you shut down and restart redundant platforms. Additional information about redundancy and redundancy states can be found under Manage engines.

Before proceeding, close any open System Platform applications on the redundant platforms, such as the IDE, InTouch WindowMaker, InTouch WindowViewer, and AVEVA OMI ViewApps. In this example, the primary node is Platform_1A which hosts Engine_1A, and the backup node is Platform_2B which hosts Engine_2B. Engine_1A is active and Engine_2B is standby.

Note: The redundancy message channel (RMC) allows the redundant platforms to communicate directly with each other. For more information, see the Application Server User Guide.

To restart redundant platforms

1. In the console tree, select the platform that hosts the active engine.

2. In the details pane, select the engine.

3. When the engine is highlighted, select the Force Failover button or right-click and then select the failover option from the context menu. See Redundancy state descriptions for details.

   The partner engine status will show "Switching to Active."

   Engine Status: Running On Scan

   Partner Status: Switching to Active

   After failover, the primary engine status changes to Standby - Ready and the partner engine status changes to "Active."

   Engine Status: Standby - Ready

   Partner: Active

4. Stop the selected platform.

   After stopping the platform, the status of the primary engine changes to shutdown, and no partner status is shown, even though the partner engine is now active on scan. Since the platform is not running, it cannot see the status of its partner. See Shut down a platform for details about stopping the platform.

   Engine Status: Shutdown

   Partner Status: No status shown

5. Maintenance: Peform any required maintenance tasks on the node that is shutdown.

6. Restart the platform by setting the platform On Scan. See Start a platform for details.

   After restarting the platform, the status of the primary engine changes to back to "Standby - Ready," and the partner status shows again as "Active."

   Engine Status: Standby - Ready

   Partner Status: Active

   Note: If there are additional engines hosted on the platform that are running Off Scan, set them to On Scan.

7. When all engines are running on scan, force failover back to the primary engine(s). The status of the primary engine changes to "Running On Scan" and the partner engine status changes to "Standby - Ready."

   Engine Status: Running On Scan

   Partner Status: Standby - Ready

8. In the console tree, select the platform that hosts the standby engine. In the example above, this Platform_2B. Repeat steps 4, 5, and 6 to update the Backup Node.