Restore and Recover your Autonomous Database

From the Oracle Cloud Infrastructure Console you can restore the database using the Restore operation, where you initiate recovery for your database.

Perform the following prerequisite steps as necessary:

  • Open the Oracle Cloud Infrastructure console by clicking the navigation icon next to Oracle Cloud.

  • From the Oracle Cloud Infrastructure left navigation list click Autonomous Data Warehouse.

  • On the Autonomous Databases page select an Autonomous Database from the links under the Display Name column.

To restore and recover your database, do the following:

  1. On the Autonomous Database Details page, from the More Actions drop-down list, select Restore to display the Restore prompt.
  2. In the Restore prompt, select Enter Timestamp or Select Backup to restore to a point in time or to restore from a specified backup.
  3. Click Restore.

    Note:

    Restoring Autonomous Data Warehouse puts the database in the unavailable state during the restore operation. You cannot connect to a database in that state. The only lifecycle management operation supported in unavailable state is Terminate.

    The details page shows Lifecycle State: Restore In Progress

  4. When the restore operation finishes your Autonomous Data Warehouse instance opens in read-only mode and the Autonomous Database Details page Lifecycle State shows Available Needs Attention.
  5. At this point you can connect to your database and check your data to validate that the restore point you specified was correct:
    • If the restore point you specified was correct and you want to open your database in read-write mode click Stop and after the database stops, click Start to start the database. After stopping and starting, the database opens in read-write mode.

      Note:

      After the instance is opened in read-write mode some of your backups are invalidated. See the notes below for details.
    • After checking your data if you find that the restore date you specified was not the one you needed you can initiate another restore operation to another point in time.

Notes:

  • When you restore your database and open it in read-write mode, all backups between the date the restore completes and the date you specified for the restore operation, the restore time, are invalidated. After the database is opened in read-write mode after a restore, you cannot initiate further restore operations to any point in time between the restore time and restore completion time. You can only initiate new restore operations to a point in time older than the restore time or more recent than the time when the actual restore succeeded.

    For example, assume you initiate a restore operation on Oct 8, 2018, 2 pm and specify Oct 1, 2018, 2 pm as the point in time to restore to and the restore completes on Oct 8, 2018, 2:30 pm. If you open your database in read-write mode at this point, backups between Oct 8, 2018, 2:30 pm and Oct 1, 2018, 2 pm will be invalidated. You will not be able to restore to any date between Oct 1, 2018, 2 pm and Oct 8, 2018, 2:30 pm. If you initiate a restore to a point in time between these dates the restore will fail with an error.

  • The restore operation also restores the DATA_PUMP_DIR directory and user defined directories to the timestamp you specified for the restore; files that were created after that timestamp would be lost.

  • When you restore, the Oracle Machine Learning workspaces, projects, and notebooks are not restored.

  • For external tables, partitioned external tables, and the external partitions of hybrid partitioned tables a backup does not include the external files that reside on your Object Store. Thus, for operations where you use a backup to restore your database, such as Restore or Clone from a backup it is your responsibility to backup, and restore if necessary, the external files associated with external tables, external partitioned tables, or the external files for a hybrid partitioned table.

    See Clone Autonomous Data Warehouse from a Backup for information on using Clone from a backup.