Importing Snapshot to Restore Environment
You can restore application artifacts and data from previous snapshots. For example, you can restore the artifacts and data to the state they were in a few days ago by importing a snapshot that you backed up to a local machine.
Before importing, you should upload the source snapshot to the Oracle Enterprise Performance Management Cloud environment. Snapshots that you create or upload to the service are stored for 60 days, after which they are automatically deleted. See these sources for information on uploading snapshots to an environment:
- The uploadFile EPM Automate command
- "Uploading Archives to the Service" in Administering Migration for Oracle Enterprise Performance Management Cloud
Key Considerations
- Oracle Enterprise Data Management Cloud and Narrative Reporting do not support the migration of snapshots from a monthly update to a previous monthly update (for example, when moving snapshots between test and production environments during the window when the test environment is upgraded before the production environment). It supports migration only across the same monthly update or to the next monthly update.
- Account Reconciliation supports the migration of individual artifacts to a previous monthly update, except for the Application Snapshot artifact.
- All other business processes support the migration of snapshots from a monthly update to the previous and next monthly updates.
-
Import operation may fail if Planning contains a renamed seeded period member that has been supplanted by a custom period member. For example, you renamed the seeded YearTotal Period member to unused_YearTotal and then added an alternate type period member with the original seeded member name (YearTotal in this example). In this scenario, import of snapshot into the business process may fail.
Note:
You cannot import Oracle Essbase data by itself. Essbase data can only be imported as part of full snapshot import.To restore artifacts from a snapshot: