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 Service Maintenance Time.

Because Oracle stores only the snapshots created in the most recent maintenance window, the artifacts and data available for restoration depend on their state during the last maintenance window. Maintenance snapshots are created primarily to restore your environment in the case of a catastrophic failure.

Oracle recommends that you download the maintenance snapshots regularly to a local machine. Service Administrators are responsible for backing up the maintenance snapshot and then restoring the service environment if needed.

Files and snapshots that you create or upload to an Oracle Enterprise Performance Management Cloud environment are deleted after 60 days. The daily maintenance process monitors environments and automatically removes snapshots older than 60 days. If the total size of all remaining snapshots exceeds 150 GB, it deletes snapshots from the last 60 days, oldest first, until the total size of snapshots is less than 150 GB. The daily maintenance snapshot, irrespective of its size, is always retained. If your maintenance snapshot is larger than 150 GB, then only the maintenance snapshot is retained; all other snapshots are deleted.

Data Management process log files are retained for seven days only.


  • 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.

    For Account Reconciliation only: Account Reconciliation does 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 .

The daily maintenance snapshot is stored in the environment.

These Artifacts are Not Included in the Maintenance Snapshot

  • Data Management data that is not managed by Migration.
  • Files that were uploaded to the environment, including snapshots that you uploaded.
  • Files that you created by exporting artifacts from the environment.
  • For services other than Financial Consolidation and Close : Audit records available in the environment. Audit records of Financial Consolidation and Close are included in the maintenance snapshot.

About the XML Files in the Snapshot

The XML files included in EPM 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.