Restore from a Snapshot
If something goes wrong, you can easily restore your content to a previous working state from a snapshot. You also restore snapshots when you migrate content between environments.
Before you start, read these tips about restoring snapshots.
-
As you start to restore the snapshot, users currently signed in have their session terminated.
-
After you restore from a snapshot, allow time for the restored content to refresh (for example, approximately 15 to 30 minutes for a large snapshot).
-
Delivery schedules aren’t automatically restored or activated when you restore catalog content from a snapshot. This is so you can restore and activate deliveries at a time that suits you. See Restore and Enable Delivery Schedules.
-
You can restore snapshots taken at the same version (or earlier version) as the target environment. For example, if you take a snapshot of an Oracle Analytics environment that includes the May 2022 update, you can restore it on other Oracle Analytics environments that include the May 2022 update or a later update (such as July 2022).
You might experience unexpected results if you try to restore from a snapshot that was taken from a more recent update of Oracle Analytics. For example, if you take a snapshot of an Oracle Analytics environment that includes the September 2022 update, don't restore this snapshot in Oracle Analytics environments that include an earlier update, such as June 2022.
-
When you restore a snapshot taken from a different environment, you must upload the data associated with your file-based datasets to the target environment.
-
You can take and restore snapshots using the Console or REST API. The Snapshots page in the Console lists the snapshots that you take using the Console. Snapshots that you take and register using the REST API don't display in the Snapshots page. See Manage Snapshots using REST APIs.
To restore a snapshot: