Suspending or Unsuspending an Enterprise

You can suspend an enterprise to take an online backup before planned upgrades or deployments, no longer requiring to shut down the enterprise, thus avoiding disruptions in business continuity.

Suspending an enterprise suspends the processing of actions such as deployment, upgrade, or user actions that may lead to changes in ActiveMatrix entities, but it does not affect the normal functioning of business logic in the runtime. After an enterprise is suspended and before it is unsuspended, ActiveMatrix UI and CLI actions that may lead to a change in ActiveMatrix entities cannot be performed.

Prior to this release, TIBCO recommended that you shut down the enterprise before taking an offline backup as different states of applications are maintained in two different places (the ActiveMatrix database and the runtime file system). A backup without a shutdown could result in the database and the file system being out of sync leading to issues. Hence, shutting down the enterprise was recommended.

Starting with this release, you can suspend an enterprise and then perform tasks such as backing up the entire enterprise without having to shut down the enterprise. For example, consider that you want to upgrade a number of applications in your enterprise. Using this feature, you no longer need to shut down all the hosts (and nodes being managed by the hosts) before taking a backup. You can suspend the enterprise and then take a backup. After the backup is completed, all actions that were suspended will resume.

Note: Only a root user can put an enterprise in one of the above states. For more information about root users or super users, refer to Users, Groups, and Permissions.