Backing Up the Existing ActiveMatrix BPM System

Back up the existing ActiveMatrix BPM system before upgrading it. Depending on your operational requirements, you can take an offline or online backup:

  • An offline backup requires you to shut down the ActiveMatrix enterprise that hosts the ActiveMatrix BPM system. You cannot use the ActiveMatrix BPM system until the backup has completed and you have restarted the system.
  • An online backup requires you to suspend the ActiveMatrix Enterprise that hosts the ActiveMatrix BPM system, but you do not need to shut down the ActiveMatrix BPM system. You can continue to use theActiveMatrix BPM system while the online backup is being performed. (This allows you to take a backup if your operational requirements do not allow for a suitable window in which to perform an offline backup.)

See "Backing up and Restoring the ActiveMatrix BPM System" in ActiveMatrix BPM Administration for more information about these backup types and how to perform them.

Important: Do not take a backup of the ActiveMatrix BPM system without first either shutting down (to take an offline backup) or suspending (to take an online backup) the ActiveMatrix enterprise. Taking a backup of a running ActiveMatrix BPM system while the ActiveMatrix enterprise is unsuspended can result in conflicts between the states of BPM applications as recorded in the backups of the CONFIG_HOME file system and the ActiveMatrix Administrator database. For example, an application's state could be recorded as READY_FOR_UNDEPLOY in the backup of the file system, but as PREPARING_FOR_UNDEPLOY in the backup of the ActiveMatrix Administrator database. If the ActiveMatrix BPM system were subsequently restored from this backup set, these conflicts may result in stuck or failed applications or process instances on the restored system.