Undeploying AppEngines
- Last UpdatedAug 14, 2025
- 1 minute read
Undeploying AppEngines in a redundant pair may trigger failover. The following description refers to non-cascade Undeploy operation of the AppEngine.
Executing a cascade Undeploy operation of the Primary AppEngine undeploys all objects from both engines.
The table below describes the expected behavior under the non-cascade condition:
|
Initial Condition |
Transition |
Final Condition |
||||
|
Primary |
Backup |
Primary |
Backup |
Primary |
Backup |
|
|
Scenario 1 |
||||||
|
Undeploy Backup AppEngine |
Deployed |
Deployed |
Deployed |
Undeployed |
Deployed |
Undeployed |
|
Red. Partner Status |
Standby Ready |
Unknown |
||||
|
Red. Status |
Active |
Active - Standby not Available |
||||
|
Scenario 2 |
||||||
|
Undeploy Primary Engine |
Deployed |
Deployed |
Undeployed |
Deployed |
Undeployed |
Deployed |
|
Red. Partner Status |
Standby Ready |
Unknown |
||||
|
Red. Status |
Active |
Active - Standby not available |
||||
|
Scenario 3 |
||||||
|
Deploy Primary Engine |
Undeployed |
Deployed |
Deployed |
Deployed |
Deployed |
Deployed |
|
Red. Partner Status |
Unknown |
Unknown |
||||
|
Red. Status |
Active - Standby not available |
Active |
Note: It may become necessary to relocate a Primary or Backup AppEngine. Ensure relocation is performed at a non-critical time (scheduled maintenance, plant shutdown.), and that Store Forward is not in operation during the relocation process (undeploy, relocate, redeploy). Data loss may occur if Store Forward is operational during the redeploy operation.