Overview of the Maintenance Snapshot

Every day, during the operational maintenance of the environment, Oracle backs up the content of the environment to create a maintenance snapshot, named Artifact Snapshot, of existing artifacts and data.

Service Administrators can use the maintenance snapshot to recover artifacts and data; for example, form definitions, reports, and so on, from the previous day that were deleted from the service after the last operational maintenance window. They can also, if needed, use it to restore the environment to the state it was in during the last operational maintenance. See Setting the Maintenance Start Time for an Environment.

Note:

  • An environment does not create a maintenance snapshot if it has not been in use since the last maintenance window. If an environment has not been in use for 14 days, however, a new maintenance snapshot is created.
  • Generally, you can migrate maintenance snapshots from the test environment to the production environment and vice versa.

    Account Reconciliation and Oracle Enterprise Data Management Cloud do not support migration of snapshots from the latest service update to an earlier service update (for example, when moving snapshots between test and production environments during the window when the test environment is upgraded before the production environment).

  • You can create a backup of your environment at any time by exporting artifacts using Migration. See "Backing up Artifacts and Applications" in Administering Migration for Oracle Enterprise Performance Management Cloud.
  • Because OCI (Gen 2) environments report the noncompressed size of the maintenance snapshots while Classic environments report the compressed size, a Classic snapshot copied to an OCI (Gen 2) environment will show a larger size.
  • The business process is placed in the maintenance mode when the daily maintenance of the environment starts. See Managing Daily Maintenance.

These Artifacts are Not Included in the Maintenance Snapshot

  • Files that were uploaded to the environment, including snapshots that you uploaded.
  • Files that you created by exporting artifacts from the environment.
  • Audit data. Snapshots of all business processes other than Planning, Planning Modules, Profitability and Cost Management, and Enterprise Profitability and Cost Management include audit information.
  • Job Console data. For Planning, Planning Modules, FreeForm, and Enterprise Profitability and Cost Management, job console data is not included in the snapshot.
  • Data Management Staging Table Data. Using the LCM Mode feature, customers can take a snapshot of staging table data from the Workbench. To export and import this data, use the exportDataManagement and importDataManagement EPM Automate commands or the Data Management System Maintenances Scripts interface.

To create an identical copy of an environment, including audit data, job console data, Data Management staging table data, and stored snapshots and files, use the cloneEnvironment EPM Automate command or the Clone Environment feature.

About the XML Files in the Snapshot

The XML files included in Oracle Enterprise Performance Management Cloud snapshots use an Oracle defined proprietary format. This format may change to accommodate changes that occur over EPM Cloud releases. Any custom process or utility that you use should not depend on the XML format remaining unchanged across EPM Cloud releases.