Restoring and recovering tablespaces using point-in-time recovery

You can restore a subset of tablespaces that has been corrupted or dropped without impacting the other tablespaces in the database. SnapCenter uses RMAN to perform point-in-time recovery (PITR) of the tablespaces.

Before you begin

The backups that are required to perform PITR of tablespaces should be cataloged and mounted.

About this task

During PITR operation, RMAN creates an auxiliary instance at the specified auxiliary destination. The auxiliary destination could be a mount point or ASM disk group. If there is sufficient space in the mounted location, you can reuse one of the mounted locations instead of a dedicated mount point.

You should specify the date and time or SCN and the tablespace is restored on the source database.

You can select and restore multiple tablespaces residing on ASM, NFS, and SAN environments. For example, if tablespaces TS2 and TS3 reside on NFS and TS4 reside on SAN, you can perform on single PITR operation to restore all the tablespaces.

In a RAC setup, you can perform PITR of tablespaces from any node of the RAC.

Procedure

In the left navigation pane, click Resources, and then select the appropriate plug-in from the list.
In the Resources page, select either Database or Resource Group from the View list.
Select the database of type single instance (multitenant) either from the database details view or the resource group details view.
The database topology page is displayed.
From the Manage Copies view, select Backups from either the primary or the secondary (mirrored or replicated) storage systems.
If the backup is not cataloged, you should select the backup and click Catalog.
Select the cataloged backup, and then click .
On the Restore Scope page, perform the following tasks:
1. If you have selected a backup of a database in a Real Application Clusters (RAC) environment, select the RAC node.
2. Select Tablespaces, and then specify the tablespaces you want to restore.
  
  Note: You cannot perform PITR on SYSAUX, SYSTEM, and UNDO tablespaces.
3. Select Change database state if needed for restore and recovery to change the state of the database to the state required to perform restore and recovery operations.
On the Recovery Scope page, perform one of the following actions:
- If you want to recover to a specific System Change Number (SCN), select Until SCN and specify the SCN and auxiliary destination.
- If you want to recover to a specific date and time, select Date and Time and specify the date and time and the auxiliary destination.
When you specify the SCN or date and time, SnapCenter lists the backups that are required to perform PITR but are not cataloged and mounted.
On the PreOps page, enter the path and the arguments of the prescript that you want to run before the restore operation.
You should store the prescripts either in the /var/opt/snapcenter/spl/scripts path or in any folder inside this path. By default, the /var/opt/snapcenter/spl/scripts path is populated. If you have created any folders inside this path to store the scripts, you must specify those folders in the path.
You can also specify the script timeout value. The default value is 60 seconds.
On the PostOps page, perform the following steps:
1. Enter the path and the arguments of the postscript that you want to run after the restore operation.
2. Select the check box if you want to open the database after recovery.
On the Notification page, from the Email preference drop-down list, select the scenarios in which you want to send the email notifications.
Review the summary, and then click Finish.
Monitor the operation progress by clicking Monitor > Jobs.