Skip to main content
NetApp Backup and Recovery

Restore Oracle Database workloads with NetApp Backup and Recovery

Contributors netapp-mwallis
PDFs

Restore Oracle Database workloads from snapshots, replicated backups on secondary storage, or backups stored in object storage by using NetApp Backup and Recovery.

Restore from these locations

You can restore databases from different starting locations:

  • Restore from a primary location (local snapshot)

  • Restore from a replicated resource on secondary storage

  • Restore from an object storage backup

Restore to these points

You can restore data to the original location; restoring to an alternate location is not available in this private preview release.

  • Restore to the original location

How Oracle Database restore works

When you restore Oracle Database workloads, the following occurs:

  • When you restore a database from a local snapshot, NetApp Backup and Recovery creates a new resource using the data from the backup.

  • When you restore from replicated storage, you can restore it to the original location.

  • When you restore a backup from object storage, you can restore the data to the source storage or to an on-premises ONTAP system and recover the database from there.

From the Restore page (also known as Search & Restore), you can restore a database, even if you don't remember the exact name, the location in which it resides, or the date when it was last in good shape. You can search for the database using filters.

Restore an Oracle database

Depending on your needs, restore an Oracle database to a specific point in time, to a specific system change number (SCN), or to the last good state. You can also restore the database from snapshots and skip the automated recovery process, for example, if you want to perform recovery manually. You can search for the database using its name or with specific filters.

Required NetApp Console role
Backup and Recovery super admin or Backup and Recovery restore admin role. Learn about NetApp Console access roles for all services.

Note

If restoring PDBs or tablespaces to a specific point in time or SCN:

  • Select only one PDB. Point-in-time recovery is not compatible with restoring multiple PDBs.

  • PDB$SEED cannot be selected for point-in-time recovery.

  • Control file restore cannot be combined with point-in-time recovery of PDBs or PDB tablespaces.

  • Ensure the data backup and the required log backups are cataloged.

  • The SYSTEM, SYSAUX, and UNDO tablespaces cannot be selected.

  • Verify that the data backup and required log backups are cataloged.
Steps

  1. From the NetApp Console menu, select Protection > Backup and Recovery.

  2. From the NetApp Backup and Recovery menu, select Restore.

  3. From the drop-down list to the right of the name search field, select Oracle.

  4. Enter the name of the database you want to restore or filter for the database host where the database that you want to restore is located.

    A list of snapshots appears that match your search criteria.

  5. Select the Restore button for the database that you want to restore.

  6. Choose a restore option:

    Restore to specific point in time

    1. Select Restore to specific point in time.

    2. Select Next.

    3. Choose a date from the dropdown, and select Search.

      The closest snapshot to the specified date and time is displayed.

    4. Optionally, select View log backups to see the associated log backups.

      1. Verify that the log backups are mounted.

    5. If the snapshot is stored in more than one location, select a source location to use and add or review location details.

    6. Select Next.

    Restore to a specific system change number (SCN)

    1. Select Restore to a specific system change number (SCN).

    2. Select Next.

    3. Enter the SCN to use as a restore point, and select Search.

      The closest snapshot for the specified SCN is displayed.

    4. Optionally, select View log backups to see the associated log backups.

      1. Verify that the log backups are mounted.

    5. If the snapshot is stored in more than one location, select a source location to use and add or review location details.

    6. Select Next.

    Restore to the latest backup (last good state)

    1. Select Restore to the latest backup.

    2. Select Next.

      The latest snapshot is displayed. The restore operation recovers the last good state using all available log backups.

    3. Optionally, select View log backups to see the associated log backups.

      1. Verify that the log backups are mounted.

    4. If the snapshot is stored in more than one location, select a source location to use and add or review location details.

    5. Select Next.

    Restore from snapshots with no recovery

    1. Select Restore from snapshots with no recovery.

      Selecting this option means that the database will be restored from snapshots, but recovery is skipped (log backups are not applied).

    2. Select Next.

      Available snapshots are displayed.

    3. Select a snapshot from the list and select Next.

    4. If the snapshot is stored in more than one location, select a source location to use and add or review location details.

    5. Select Next.

  7. Choose the restore destination and settings:

    Restore to original location

    1. In the Destination settings section, do the following:

      1. For RAC databases, select the RAC node on which to run the restore. This option appears only for RAC databases.

      2. Select what you want to restore:

        • Select All datafiles to restore the entire database or container database (CDB).

        • Select Pluggable databases (PDBs) to restore one or more PDBs from a CDB without affecting the other PDBs in the container. Then select the PDBs from the list.

        • Select Pluggable database (PDB) tablespaces (shown as Tablespaces for a non-CDB database) to restore specific PDB tablespaces. Then, select the PDB and the tablespaces.

      3. Optionally, enable the Control files option to also restore the database control files. This option cannot be selected for point-in-time or SCN recovery of PDBs or PDB tablespaces.

      4. Optionally, enable the Change database state if needed for restore and recovery option to allow Backup and Recovery to manage the database state depending on the type of recovery.

      5. Optionally, enable the Force in place restore option to to perform an in-place restore when new datafiles were added after the backup, or when LUNs were added, deleted, or re-created in an LVM disk group. This overrides the foreign-files check; database recovery proceeds using the restore option you selected.

      6. Specify external archive log file locations in the External archive log files locations field if restoring PDBs or tablespaces to a specific point in time or SCN, the archive logs are not in the configured location. Enter a file system path that starts with / or an ASM disk group that starts with +. Use the "plus" and "minus" buttons next to the text entry field to add or remove locations. This field does not appear when you restore from snapshots with no recovery.

      7. Optionally, enable the Open the database or container database in READ-WRITE mode after recovery option and select a sub-option that matches the restore scope (these options don't appear when restoring from snapshots with no recovery):

        • All datafiles: Open the database or container database in READ-WRITE mode after recovery.

        • PDBs or PDB tablespaces: Open the pluggable databases in READ-WRITE mode after recovery.

        • Non-CDB tablespaces: Bring the tablespaces online after recovery.

    2. In the Prescripts and postscripts section, do the following:

      1. Prescript: Optionally, enable this option and enter the full path for a script that should be run before the restore operation and any arguments that the script takes.

      2. Postscript: Optionally, enable this option and enter the full path for a script that should be run after the restore operation and any arguments that the script takes.

      3. Choose a timeout value for the script. If the script fails to execute within this time period, the restore will proceed anyway.

    Restore to alternate location

    Not available for Oracle Database workloads in this preview release.

  8. Select Restore.