1. Essbase Stack Deployment on Oracle Cloud Infrastructure
  2. Back Up and Restore Essbase
  3. Back Up and Restore Applications

Back Up and Restore Applications

Routine backup of Essbase applications ensures that you can recover from any sort of disruption to applications without affecting the other applications running on the same Essbase instance.

LCM export and import operations allow you to move applications on and off your Essbase instance or between Essbase instances. Export and import operations can be run sequentially in instance migration use cases, exporting from the source instance and importing into the target instance. However, to protect from unexpected application-level failures a routine backup cadence is required. The frequency of your application backups should correspond to the acceptable loss (recovery-point objective or RPO) specified by the application’s users. At the time of any application-specific failure, the latest LCM export file can be used to recover all or part of the application.

Note:

Use LCM export option --application to export a single application to a zip file. Use option (case-sensitive) --allApp (or -aa), instead of --application, to export all applications to a single zip file. The --allApp option does not export users and groups.

By default, LCM export exports your application and its cubes without an itemized inventory of artifacts. When executing an LCM export, consider generating an artifact list. Only if you have included this artifact list on export will you have the option to selectively import specific components of your application and its cubes. To ensure backup consistency, make sure that the application is stopped before taking an LCM export.

Note:

For example, if using the CLI LcmExport command, you can use the optional -generateartifactlist parameter.

To back up applications, do an LCM export operation. To restore them, do an LCM import operation. You have various options, detailed below:

  1. Back up your 19c applications using one of the methods listed below to initiate the LCM export operation. To do an LCM export, you need at least user role with Application Manager permission, or, you must be the power user who created the application.

  2. If you will use the CLI to perform the LCM export, first download it to your compute, from the Console in the Essbase web interface, and set it up. See: Access Tools and Tasks from the Console and Download and Use the Command-Line Interface.

  3. Restore applications from backup using one of the methods listed below to initiate the LCM Import operation.

Note:

If your application is on 11g, you must first migrate to the current release using the EssbaseLCMUtility.zip before you can back up using LCM export and LCM import commands. Download the utility from the Console in the Essbase web interface, and see the enclosed README for usage instructions.

Note:

Location aliases are migrated with the cube. LCM doesn't support Location alias credentials migration. After you migrate your applications from 11g you must replace your location aliases. See Location Aliases section in Prepare to Migrate from Essbase 11g On-Premise.

Back Up Cube Files Using LCM

Use one of these tools to initiate an LCM Export operation, which backs up application and cube artifacts to a Lifecycle Management (LCM) .zip file:

Note:

This topic applies if you are backing an application from a release after 11g. If your application is on 11g, you must first migrate that application using the 11g Export utility, before you can back it up. For backups, you use one of the tools listed in this topic to initiate the LCM Export operation. To migrate from 11g, you must use the 11g Export utility.

Requires at least user role with Application Manager permission, or, you must be the power user who created the application.

Restore Cube Files Using LCM

Use one of these tools to initiate an LCM Import operation, which restores application and cube artifacts from a Lifecycle Management (LCM) .zip file:

Requires at least user role with Application Manager permission, or, you must be the power user who created the application.