SnapProtect - Advanced Restore - Oracle RAC

Table of Contents

Restoring Data from an SnapProtect Backup

When restoring data from a snapshot, note the following:

  • If the selected backup (latest or point-in-time) was an SnapProtect backup, the subsequent restore will be an SnapProtect restore.
  • During Snapshot restore operations, the database is shutdown first and then the snapshots are restored. Once restored, the database is changed to mount mode for the recover operation.

Snapshots are mounted on the destination client where the restore is performed. Hence, destination client should have access to the storage array/filer where snapshot was taken. If the destination client does not have access to storage device, then you should restore the data from snapshot using proxy computer. You can restore an oracle database on a ASM disk group using RMAN.

Restore Data from Snapshot Using RMAN

Use the following steps to restore data from a snapshot using RMAN scripts:

  1. From the CommCell Browser, navigate to Client Computers | Oracle RAC
  2. Right-click the entity that contains the snapshots you want to restore, and point to All Tasks | Browse Backup Data.

    Restoring log data using RMAN is not supported.

  3. Click OK.
  4. From the Browse window, select the data you want to restore in the right pane and click Recover All Selected.
  5. From the Restore Options for All Selected Items window, select the Use Snap Restore checkbox.
  6. Click Advanced.
  7. Select the Use RMAN Restore checkbox.
  8. Click OK to save the settings and close the Advanced Restore Options window.
  9. Click OK to close the Restore Options window and initiate the restore job.

Restoring and Recovering an Entire Database to the same host

When the database is corrupted or lost, you can restore and recover it from the latest offline or online full backup (depending on how the subclient was configured for backups).

By default, the database is restored to the same location from where it was backed up. Once the database is restored, it is recovered to the current time.

Use the following steps to restore and recover a database to the same host:

  1. From the CommCell Browser, navigate to Client Computers | <Client> | Oracle.
  2. Right-click the <Instance>, point to All Tasks and then click Browse and Restore.
  1. Verify that the Restore Data and Recover options are selected.
  2. Select the Restore Control File check box.
  3. Click OK.

Reverting an Entire Database to the Same Host

You can use the revert operation to bring the oracle database back to the point in time when the SnapProtect backup was taken. However, the log volume will not be reverted. You can use either the file system or RMAN to restore the logs after you revert the data volume.

  1. From the CommCell Browser, navigate to Client Computers | <Client> | Oracle.
  2. Right-click the <Instance>, point to All Tasks and select Browse Backup Data.
  3. From the Browse window, navigate and select the database to be restored and click Recover All Selected.
  4. From the Restore Options dialog box, click Advanced.
  5. Select the Use hardware revert capability if available option.

    Note: Restore control file option automatically selected once ‘use hardware revert capability’ option selected. It is because in most of the cases control file is present on data volumes. You can select control file restore from autobackup/backup piece in advanced options if you don’t want to restore from snap. If you don’t want to restore control file at all or it is outside of data and log volumes, you can unselect the restore control file option.

  6. Click OK to confirm the revert operation.

Restoring from a SnapProtect and RMAN Mixed Environment

Case 1: Jobs run as follows:

  1. Snap full job (data and log)
  2. Streaming archive log only jobs

Restore/Revert can be performed from the snap job and control file/SP file restore can be done from the Streaming archive log jobs using autobackup/backup piece option.

Considerations:

  1. If archive log only restore are submitted, then it also uses the snap job only and restore archive logs which were included in the snap job. To restore archive logs from Streaming RMAN archive log jobs, select the copy precedence as the Primary copy of archive log storage policy and submit the restore.

Case 2: Jobs run as follows:

  1. Snap full job (data and log)
  2. Streaming RMAN full job (data and log)
  3. Streaming archive log only jobs

Restore/Revert can be performed from the snap job and control file/SP File restore can be done from Streaming RMAN jobs using autobackup/backup piece option.

Considerations:

  1. Restore job will pick the latest job for the specified time (it could be either snap or traditional RMAN) and use that job for restore.
  2.  If both the snap full job and traditional RMAN full job run parallel and complete at the same time, then the restore always picks the snap job only if you do restore from the instance level. To use the traditional RMAN backup, submit the restore from backup history after browsing the traditional RMAN job.

Restoring and Recovering an Entire Database to a Previous Point-in-Time

The point-in-time restore is useful in the following scenarios:

  • If any undesired transaction occurs in the database, you can revert the database to a state just before the transaction.
  • If a database fails, you can restore to the state just before the point of failure.

When you restore and recover an entire database to a previous point-in-time from an online backup or offline backup (depending on how the subclient was configured for backups) to the original host, it is recommended to use the control files.

When you perform a point-in-time restore for a database, the next scheduled backup for that database will automatically convert to a full backup.

Use the following steps to restore and recover a database to a previous point-in-time:

  1. From the CommCell Browser, navigate to Client Computers | <RAC Client>.
  2. Right-click the <Instance>, point to All Tasks and then click Restore.
  3. Select Restore Control File check box, if you want to restore the control file(s).
  4. Click Advanced.

  5. Click the Restore tab.
  6. Click To Point-in-Time  and select the data and time.

  7. Click the Recover tab.
  8. Click the Point-in-Time  and select the data and time.

  9. Click Ctrl&SP Files Tab, if you have selected to restore the control file(s).
  10. Select Restore From check box.
  11. Click the Point-in-Time  and select the data and time.
  12. You must restore the control files to a point-in-time later than or equal to the point-in-time set in the Restore tab.
  13. Click OK.

Restoring and Recovering an Entire Database to a New Host

If the computer on which you hosted a database is damaged or destroyed, you can restore and recover the lost database with the same directory structure on to a new host.

By default, the database is restored in the ARCHIVELOG mode, You can also choose to restore the db in NOARCHIVELOG mode.

Use the following steps to restore and recover a database to a new host with the same directory structure:

Prerequisites

  1. The connection specifications (host, service name, port) in the tnsnames.ora file on both the source and destination computers should be different.
  2. The <username> you use for the destination computer is different than the username for the source computer.
  3. Sufficient disk space is available on the destination computer to accommodate the restored database.
  4. Both the source and destination computers should have the following similar features:
    • Operating systems
    • Oracle version
    • ORACLE_SID
    • init <SID>.ora file
    • Datafile directory structures

Setting Up the Source and Destination Hosts

  1. Manually transfer the Oracle password file orapw<Oracle SID name> from the source computer to the destination computer. Usually, this file resides in ORACLE_HOME/dbs.
  2. Export the recovery catalog data for the catalog user.

    For example, if the user ID for the recovery catalog owner is user1, you need to export the database backup information for user1.

  3. Import the recovery catalog data to the new user account for the destination computer.

    Example using IMPORT CATALOG Command:

    RMAN>IMPORT CATALOG user1/user1@src;

  4. Copy the recovery catalog’s connect string entry in the tnsnames.ora file from the source host to the destination host.

    <service_name> =

    (DESCRIPTION =

    (ADDRESS = (PROTOCOL = <protocol>)(HOST = <host>) (PORT = <##>))

    (CONNECT_DATA = (SID = <Recovery Catalog database>)))

  5. Make sure that the ORACLE_SID and ORACLE_HOME are appropriately configured on the destination computer.

    Example:

    For Unix:

    #export ORACLE_SID= <target database SID>

    #export ORACLE_HOME= <Oracle home directory>

  6. Install the Oracle iDataAgent and configure it as client in the same CommServe in which the source computer resides.
  7. Make sure to configure the destination instance on the RAC nodes in NOMOUNT mode. Create a RAC client from the CommCell Console and add this instance to the RAC client.

Restoring the Database

  1. From the CommCell Browser, navigate to Client Computers | <RAC Client>.
  2. Right-click the <Instance> point to All Tasks and then click Restore.
  3. Click View Content.
  4. Select the entities and click Recover All Selected.
  5. Select the name of the client computer from the Destination Client list.
  6. Select Restore Control File check box.
  7. Click Advanced.

  8. Select Use Rman Restore from the General tab.
  9. Click Options tab.
  10. If the database is in NOARCHIVELOG mode, then select No Redo Logs.
  11. Select Open DB.
  12. Select Switch Database mode for Restore.
  13. Click OK.

Restoring Individual Datafiles and Tablespaces

In addition to restoring a database, you can also restore specific tablespaces or datafiles that were lost due to an error or corruption. By default, the selected tablespaces/datafiles are restored to the original location from the latest online backup.

Use the following steps to restore the datafile(s) or tablespace(s):

  1. From the CommCell Browser, navigate to Client Computers | <RAC Client>.
  2. Right-click the <Instance>, point to All Tasks and then click Restore.
  3. Click OK.

  1. From the Restore options dialog box, Select Table View. Click View Content.

  2. In the right pane of the Browse window, select the datafiles or tablespaces you want to restore and click Recover All Selected.

  3. Click OK.

Redirecting Datafiles during Restore

When restoring the database, you can choose to redirect individual data files / tablespaces to a different path in the destination client. This is useful when the destination server has a different storage management solution (ASM or File System) or for troubleshooting purposes.

When redirecting datafiles, make sure the same instance is used on the source and destination client.

Use the following steps to redirect the files to a different path:

  1. From the CommCell Browser, navigate to Client Computers | <Client> | Oracle.
  2. Right-click the <Instance>, point to All Tasks and then click Browse and Restore.
  3. Click View Content.
  4. Optional: Use non-default Browse and Restore options. See Browse and Restore.
  5. From the Browse window, select the data you want to restore in the right pane and click Recover All Selected.
  1. Select the name of the client computer from the Destination Client list.
  2. Select Use Snap Restore check box.
  3. Click Advanced.

  1. Select Use Rman Restore. (This option is selected by default.)

    You can select Use FileSystem Restore if the source and destination are not ASM databases.

  2. Click the Redirect tab.
  1. Select Redirect All Table Spaces/Database to and type the path or click Browse for the path to redirect all data files.

    Alternatively, you can select individual table spaces and type the path in the New Path box.

    To redirect multiple table spaces simultaneously, click Find & Replace and provide the existing path and the new path to be replaced.

  2. Click the Options tab.
  3. Select the Switch Database mode for Restore checkbox. This will automatically switch the database to mount mode.
  4. Click OK.

Restoring Database Tables

Database tables can be restored from a SnapProtect backup using RMAN. In order to restore database tables, you need to perform a SnapProtect backup with table browse enabled.

Note: If you use Oracle 12c, you can only perform this procedure on non-Container Databases (CDB).

Use the following steps to restore database tables:

  1. From the CommCell Browser, navigate to Client Computers | <Client> | Oracle.
  2. Right-click the <Instance>, point to All Tasks and then click Browse and Restore.
  1. Select the Table View checkbox.
  2. Click View Content.
  3. In the Browse window, select the tables that you want to restore and click Recover All Selected.
  4. Click the Table Restore tab.
  5. Select the Auxiliary Instance checkbox if you want to specify an auxiliary instance for the restore.

    When specifying the auxiliary instance, ensure that the database is in NOMOUNT mode.

  6. In the Database Name text box, type the auxiliary database name.
  7. In the PFile textbox, type the path to the PFile. Alternatively, click Browse to locate the PFile.
  8. In the Database Client box, select the client for the auxiliary instance.

    When you provide an auxiliary instance, make sure that the temp.dbf file is removed from the operating system in the specified auxiliary instance datafile location.

  9. If you are using a backup copy for the restore do the following:

    • Click Advanced.
    • Click the Copy Precedence tab and select the Restore from Copy Precedence checkbox.
    • In the Copy Precedence box, type the copy precedence number for the backup copy and click OK.
  10. Click OK.

To the Source Database

If some of the tables in the database are lost or corrupted, you can restore those tables back to the same database.

Note: If you use Oracle 12c, you can only perform this procedure on non-Container Databases (CDB).

  1. From the CommCell Browser, navigate to Client Computers | <Client> | Oracle.
  2. Right-click the <Instance>, point to All Tasks and then click Browse and Restore.
  1. Select the Table View check box and click View Content.
  2. From the Browse window, navigate and select the tables to be restored and click Recover All Selected.
  1. Click the Table Restore tab.
  2. In the Staging Path box, click Browse and select the location where the auxiliary instance will be created.

  1. Click the Advanced Options tab.
  1. Select Import to Source DB.
  2. Click OK.

To a Different Database on the Same Host

Note: If you use Oracle 12c, you can only perform this procedure on non-Container Databases (CDB).

Use the following steps to restore tables to a different database on the same host:

  1. Add the destination instance name in the Listener.ora and Tnsnames.ora files.
  2. From the CommCell Browser, navigate to Client Computers | <Client> | Oracle.
  3. Right-click the <Instance>, point to All Tasks and select Browse and Restore.
  4. Select the Table View check box and click View Content.
  5. From the Browse window, navigate and select the tables to be restored and click Recover All Selected.
  6. Click the Table Restore tab.
  7. In the Staging Path box, type the location where the tables will be restored.
  8. Click the Advanced Options tab.
  9. Select Import to a Different DB.
  10. In the Enter Import Oracle Instance: box, type the destination instance name.
  11. In the Select a Client box, select the source client.
  12. Click OK.

Setting Up the Auxiliary Instance

By default, when you restore database tables to a target instance, the system automatically duplicates the source database to an auxiliary instance in a temporary staging location specified during the restore operation. The database will be automatically imported from this auxiliary instance after the restore.

Use the following steps to set up a specific database as an auxiliary instance. This is useful when you want to restore a table to a specific failure point.

  1. Copy the init<SID>.ora file from the source database to the auxiliary database instance.
  2. Update the database name and the database file locations in the init<SID>.ora file for the auxiliary database instance.
  3. Add the DB_FILE_NAME_CONVERT and LOG_FILE_NAME_CONVERT parameters in the init<SID>.ora file. These parameters will redirect the datafiles, temp files, and log files to the auxiliary instance.

Using a User-defined Auxiliary Instance

By default, when you restore database tables to a target instance, the system automatically duplicates the source database to an auxiliary instance in the specified temporary staging location. Once the database is duplicated, you can import the tables to the target instance.

However, if required, you can also use an user-defined auxiliary instance for the restore operation. This is used when you want to restore a table to a specific failure point.

When restoring tables to a different host, if a user-defined auxiliary instance option is selected for the restore, you need to recover the database to a specified point-in-time or SCN number. You cannot recover the database to the current time using an user-defined auxiliary instance.

Setting Up the Auxiliary Instance

  1. Copy the init<SID>.ora file from the source database to the auxiliary database instance.
  2. Update the database name and the database file locations in the init<SID>.ora file for the auxiliary database instance.
  3. Add the DB_FILE_NAME_CONVERT and LOG_FILE_NAME_CONVERT parameters in the init<SID>.ora file. These parameters will redirect the datafiles, temp files, and log files to the auxiliary instance.

    Windows Clients:

    DB_FILE_NAME_CONVERT=('sourcE_of_df_path/','dup_of_df_path/','source_of_temp_path/','dup_of_temp_path/',...)

    LOG_FILE_NAME_CONVERT=('source_of_log_path/redo','dup_of_log_path/redo')

    Unix Clients:

    DB_FILE_NAME_CONVERT=(source_of_df_path/,dup_of_df_path/,source_of_temp_path/,dup_of_temp_path/,...)

    LOG_FILE_NAME_CONVERT=(source_of_log_path/redo,dup_of_log_path/redo)

  4. Add the log_archive_dest_1 parameter is added to the init<SID>.ora file on the auxiliary instance.
  5. Restart the Oracle Services, if using Windows clients.
  6. Add the destination instance name in the Listener.ora and Tnsnames.ora files. If using a different host, add the duplicate database instance name in the Listener.ora file on the destination host and Tnsnames.ora files on the destination and source hosts. Also, add the original database name in the Tnsnames.ora file on the destination host.

    DUPDB = (DESCRIPTION =

    (ADDRESS = (PROTOCOL = TCP)(HOST = powerpc02)(PORT = 1521))

    (CONNECT_DATA = (SERVER = DEDICATED)

    (SERVICE_NAME = dupdb) (UR=A) ) )

  7. Restart the Listener.

    $lsnrctl reload

  8. Ensure that the auxiliary instance is in NOMOUNT mode.

    sql> startup nomount;

Restoring the Tables Using the Auxiliary Instance

  1. From the CommCell Browser, navigate to Client Computers | <Client> | Oracle.
  2. Right-click the <Instance>, point to All Tasks and then click Browse and Restore.
  1. Select the Table View check box and click View Content.
  2. From the Browse window, navigate and select the tables to be restored and click Recover All Selected.
  3. Click the Table Restore tab.
  4. Select the Auxiliary Instance checkbox.
  5. In the Database Instance box, type the auxiliary instance name.
  6. In the Database Client box, select the destination client for the auxiliary instance.
  7. In the PFile box, type the path to the PFile of the auxiliary instance. Alternatively, click Browse to select the path.
  8. In the Staging Path box, type the location where the auxiliary instance will be created. Alternatively, click Browse to select the path.
  9. Click the Advanced Options tab.

  1. Select Import to a Different DB.
  2. In the Enter Import Oracle Instance: box, type the destination instance name.
  3. In the Select a Client box, select the destination client.

  1. Click Advanced.
  2. Select the Recover tab.
  3. Select Point-in-Time checkbox and specify the time range to which the database need to be recovered.
  4. Click OK.

Disabling Clean Up of Auxiliary Instance after Restore

By default, the system generated auxiliary instance is deleted automatically once the  tables are imported to the destination instance.

Use the following steps to disable the clean-up of auxiliary instance after the restore:

  1. From the CommCell Browser, navigate to Client Computers | <Client> | Oracle.
  2. Right-click the <Instance>, point to All Tasks and then click Browse and Restore.
  1. Select the Table View check box and click View Content.
  2. From the Browse window, navigate and select the tables to be restored and click Recover All Selected.
  3. Click the Table Restore tab.
  4. In the Staging Path box, type the location where the tables will be restored.
  5. Clear the Cleanup Auxiliary checkbox.
  6. Click OK.

Restoring Tables with Non-English Characters

By default, you can restore the tables with English characters. Use the following steps to restore the non-English characters in the tables:

  1. From the CommCell Browser, navigate to Client Computers.
  2. Right-click the <Client>, and then click Properties.
  3. Click the Additional Settings tab.
  4. Click Add.
  5. In the Name box, type <ORACLE_SID>_NLS_LANG. For example, tsrst119_NLS_LANG
  6. In the Category box, select or type OracleAgent from the list.
  7. In the Type box, select String
  8. In the Value box, set the database's character set as per your database's character set and then click OK.

    For example, if the database’s nls character set value is ZHS16GBK, you can set NLS_LANG registry key to AMERICAN_AMERICA.ZHS16GBK. By default this value is set to AMERICAN_AMERICA.US7ASCII.

  1. Click OK.

Exporting Table Objects

During table restores, the tables are exported from the auxiliary instance to the destination client and later imported to the target database. By default, the following data objects are exported along with the tables:

  • Triggers
  • Constraints
  • Indexes
  • Grants

However, the stored procedures associated with the selected tables are not exported by default. Use the following steps to export the stored procedures and additional export parameters, such as (COMPRESS or PARALLEL):

Stored procedures are restored from the Schema level. Schema is the collection of data objects created by the user to contain or reference their data. Hence, if one of the table within the schema is selected for restore, all the stored procedures for that schema will also get restored.

When exporting the tables, the datapump export utility is used if it is supported by the Oracle application. The datapump utility facilitates the export of stored procedures. In oracle versions that do not support datapump export utility, you will not be able to include stored procedures during export.

  1. From the CommCell Browser, navigate to Client Computers | <Client> | Oracle.
  2. Right-click the <Instance>, point to All Tasks and then click Browse and Restore.
  1. Select the Table View check box and click View Content.
  2. From the Browse window, navigate and select the tables to be restored and click Recover All Selected.
  3. Click the Table Restore tab.
  4. In the Staging Path box, type the location where the auxiliary instance will be restored.
  5. Click the Advanced Options tab.
  6. Select the Include Stored Procedures checkbox.
  7. Select Use additional export parameters checkbox and type the parameters to be exported.
  8. Click OK.

Deleting Existing Tables during a Restore

By default, the restore operation will overwrite the existing tables in the destination database during the restore. You can also configure the restore operation to delete the existing tables before performing the restore.

Manually drop/delete the existing tables at the destination instance and then import the tables.

Use the following steps to automatically delete existing tables on the destination instance during restore. Note that you can also manually drop/delete the existing tables at the destination instance and perform the restore without enabling this option.

  1. From the CommCell Browser, navigate to Client Computers | <RAC Client>.
  2. Right-click the <Instance>, point to All Tasks and then click Browse and Restore.
  1. Select the Table View check box and click View Content.
  2. From the Browse window, navigate and select the tables to be restored and click Recover All Selected.
  3. Click the Table Restore tab.
  4. In the Staging Path box, type the location where the tables will be restored.
  5. Click the Advanced Options tab.
  6. Select Import to Source DB.
  7. Click Drop Table for Import checkbox.
  8. Click OK.

Automatically Switching the Database Mode before a Restore

In order to perform a restore operation, the database should be in the MOUNT mode. If the database is not in mounted state, you are prompted to switch the database to the mounted state and then perform the restore.

Use the following steps to automatically switch the database to mount mode prior to restore:

  1. From the CommCell Browser, navigate to Client Computers | <RAC Client>.
  2. Right-click the <Instance>, point to All Tasks and then click Browse and Restore.
  3. Click Advanced.
  1. Click the Options tab.
  2. Select Switch Database mode for Restore.
  3. Click OK.

Setting the Database Incarnation

When you perform a point-in-time recovery of an Oracle database with RESETLOGS, a new incarnation of the database is created. All archive log files generated after resetting the logs will be associated to the new incarnation. However, in order to perform a point-in-time recovery from a backup of a previous incarnation, you need to reset the current incarnation to the previous incarnation value. Use the following steps to set the incarnation value:

  1. From the CommCell Browser, navigate to Client Computers | <RAC Client>.
  2. Right-click the <Instance>, point to All Tasks and then click Browse and Restore.
  3. Click Advanced.
  1. Click Options tab.
  2. Select the database incarnation value from Set DB Incarnation list.
  3. Click OK.

Enhancing Restore Performance

You can perform a restore operation faster when you set a maximum number of concurrent open datafiles for RMAN to read simultaneously.

  1. From the CommCell Browser, navigate to Client Computers | <RAC Client>.
  2. Right-click the <Instance>, point to All Tasks and then click Browse and Restore.
  3. Click View Content.
  4. From the Browse window, select the data you want to restore in the right pane and click Recover All Selected.
  5. Click Advanced.
  1. Click Options tab.
  2. Select the number of open files from Max Open Files list.
  3. Click OK.
  4. Click OK to start the restore.

Recovering a Database

By default, the database is recovered along with the restore. However, you can also restore the data and then recover the database at a later point-in-time.

Recovering a Database to the Current Time

You can recover a database to the current time either to the original host or to a different host. Use the following steps to recover a database to the current time:

  1. From the CommCell Browser, navigate to Client Computers | <RAC Client>
  2. Right-click the <Instance>, point to All Tasks and then click Browse and Restore.
  1. Select the database and Click Recover All Selected.
  2. On the Restore Options dialog box, clear the Restore Data check box and click the Advanced button.
  3. On the Advanced Restore Options dialog box, navigate to the Recover tab and select the Current Time option.
  4. Click OK.
  5. Click OK.

Recovering a Database to a Point-in-Time

You can apply archived logs and recover a database to a previous point-in-time where it is consistent and stable. Use the following steps to recover a database to a point-in-time:

  1. From the CommCell Browser, navigate to Client Computers | <RAC Client>
  2. Right-click the <Instance>, point to All Tasks and then click Browse and Restore.
  1. Select the database and Click Recover All Selected.
  2. On the Restore Options dialog box, clear the Restore Data check box and click the Advanced button
  3. On the Advanced Restore Options dialog box, navigate to the Recover tab and select the Point-in-Time option and enter date and time.

    The time selected is specific to the CommServe time zone.

  4. On the Advanced Restore Options dialog box, navigate to the Options tab, In the Reset Logs box, select Yes.

    In the Time Zone box, select the time zone of the client computer. This is required if the time zone is different for the client and CommServe.

  5. Click OK.
  6. Click OK.

Recovering a Database Using the System Change Number

The latest backup job's completion time is passed to the recover operation. This is the Completion Time on the General Tab of the Job Details dialog box, which you can see by right-clicking the job and selecting View Job Details.

Use the following steps to recover a database using SCN:

  1. From the CommCell Browser, navigate to Client Computers | <RAC Client>
  2. Right-click the <Instance>, point to All Tasks and then click Browse and Restore.
  1. Select the database and Click Recover All Selected.
  2. On the Restore Options dialog box, clear the Restore Data check box and click the Advanced button
  3. On the Advanced Restore Options dialog box, navigate to the Recover tab and select the SCN option and enter the System Change Number.
  4. On the Advanced Restore Options dialog box, navigate to the Options tab, In the Reset Logs box, select Yes.
  5. Click OK.
  6. Click OK.

Recovering a Database Using the Latest Backup Time

The latest backup job's completion time is passed to the recover operation. This is the Completion Time on the General Tab of the Job Details dialog box, which you can see by right-clicking the job and selecting View Job Details.

  1. From the CommCell Browser, navigate to Client Computers | <Client> | Oracle RAC.
  2. Right-click the <Instance>, point to All Tasks and then click Browse and Restore.
  3. Click View Content.
  4. From the Browse window, select the data you want to restore in the right pane and click Recover All Selected.
  5. On the Restore Options dialog box, clear the Restore Data check box and click the Advanced button
  6. On the Advanced Restore Options dialog box, navigate to the Recover tab and select the Latest Backup Time option.
  7. Click OK.
  8. Click OK.

Recovering a Database Using the Latest SCN Number

You can recover the database to the last existing SCN number in the latest backup. This is the lowest Next SCN number between all the threads in the General tab of Job Details dialog box, which you can see by right-clicking the job and selecting View Job Details.

Use the following steps to recover a database to the last backup time.

  1. From the CommCell Browser, navigate to Client Computers | <Client> | Oracle RAC.
  2. Right-click the <Instance>, point to All Tasks and then click Browse and Restore.
  3. Click View Content.
  4. From the Browse window, select the data you want to restore in the right pane and click Recover All Selected.
  1. On the Restore Options dialog box, clear the Restore Data check box and click the Advanced button
  2. On the Advanced Restore Options dialog box, navigate to the Recover tab and select the Latest SCN Number option.
  3. Click OK.
  4. Click OK.

Creating a Clone Environment

You can duplicate the source database by cloning the NetApp snapshots created during backup.

This operation, referred as cloning, utilizes the cloning capability of the storage array hardware, which enables you to duplicate large databases within a short period of time. Clones can be used for multiple purposes, such as:

  • As test environments to troubleshoot issues found in the production database.
  • Quick data retrieval without running resource intensive restores on the production environment and without requiring additional space on destination server.
  • Alleviate load from the production servers for running reports and queries.

A clone can be created from any existing full backup job (data and log volume backup). During the clone creation, a reservation period is specified by the user. At the end of the period, the system automatically shuts down the clone database and frees up all resources, including snapshot clones on the storage array and ASM disk groups. The cloning operation can also be scheduled to run periodically to allow the clones to get refreshed from the latest backups on a regular basis.

When cloning a RAC database, consider the following:

  • The Clone environment for Oracle RAC only supports ASM databases.
  • RAC databases cannot be cloned to another RAC instance. The destination instance should be a regular Oracle database.

Prerequisites

Prior to creating a clone environment, ensure the following:

  • The Oracle database version on the destination database is the same as the one in the source database.
  • The Oracle user in both the source and destination database servers must have the same user ID.
  • The Oracle Agent and the MediaAgent must be installed on the proxy.
  • On the destination client where you plan to create the clone database, create a directory to be used as the mount path for the database clone files. This directory must be writable by the Oracle user.
  • If the Oracle database version is 11.2.0.3.0, 11.2.0.3.1, or 11.2.0.3.2, install Oracle patch 13366202 or the latest Oracle 11gR2 Patch Set Update on the destination database.

Configure Your Setup

Perform the following steps before creating the clone environment:

  • On the client where you plan to create the clone, create a directory to be used as the mount path for the database clone. This directory should be writable by the Oracle user.
  • Optionally, you can also create an additional instance on the destination client with the same name as of the clone database. This instance can be used to store the clone instance properties, such as ORACLE_HOME. These properties will be pre-populated when specifying the clone options in the CommCell Console.
  • You can clone a database to the same or different computer. If you are cloning a database to an instance residing in a proxy computer, ensure the following conditions are met:
    1. The Oracle database version on the proxy computer is the same as the one in the source database.
    2. The proxy computer has access to the storage array containing the source database volumes.
    3. The Oracle user in both the source and destination computers should have the same user ID.
    4. The Oracle iDataAgent and the MediaAgent must be installed on the proxy.
    5. Using the CommCell Console, a dummy Oracle instance is created with the same name as of the source database.

Create the Clone Environment

Follow the steps given below to create a clone environment from existing snapshots:

  1. From the CommCell Browser navigate to the Client Computers | <RAC Client>.
  2. Right-click the <Instance> and then click All Task | Clone.
  3. From the Clone Options dialog box, click OK.
  4. From the browse window, select an ASM database on the left pane and then click Clone.
    • Select the entire database and not individual tablespaces.
  5. From the Oracle Clone Options dialog box, select the client where you want to clone the database from the Destination Client list.
  6. Click the Clone Options tab.
  7. Select the destination database from the Instance Name list. Ensure the selected instance is an Oracle database not configured with ASM.

    If you want to specify a database that is not listed, type the instance name and provide the following details:

    • Specify the location of the Oracle HOME directory in the ORACLE HOME box.
    • Specify the database user ID in the ORACLE User box.
  1. Specify the location of the startup Parameter file in the PFile Path box e.g., /oracle/clone/initdup1.ora. You can also click Browse to locate the directory.
    • If the specified PFile does not exist, the system will create the file and will set all parameters needed. Ensure the Oracle user has write permissions for the directory where the PFile resides.
    • If the specified PFile exists, the file should have read permissions for the Oracle user and contain all initialization parameters required by the Oracle database version used. In addition, ensure the dump and control file directories exist and have write permissions for the Oracle user.
  2. Specify the mount path location in the Snap Mount Location box e.g., /oracle/clone. This mount path will contain mounted snapshots from the Oracle database.

    The Oracle user should have write permissions to this directory. Also, if you chose to let the system create the PFile, then all dump directories will be created under this directory. Enough disk space should be available to hold the logs until the reservation period expires.

  3. Specify the Reservation Period for which you would like to retain the test environment.

    By default the clone environment will be retained for one hour. Once the specified reservation period expires, the database will be dismounted and the mount point will be deleted.

  4. By default, the system will set up two Redo log groups with one log file on each group. If you want to override this configuration (location, number of groups, files), click the Online Log Files check box. Then select Group and add the group and files that you want to create.
  5. Click OK.

Restoring Data from Backup Copy

You can perform a restore from the backup copy by setting the appropriate copy precedence number. Use the following steps to restore the data from backup copy using RMAN. Refer the Advanced Restore - Oracle RAC iDataAgent for regular restore operations.

  1. From the CommCell Browser, navigate to Client Computers | <RAC Client>
  2. Right-click the entity that contains the snapshots you want to restore, and point to All Tasks and click Browse and Restore.
  3. Click View Content.
  4. From the Browse window, select the data you want to restore in the right pane and click Recover All Selected.
  5. From the Restore Options dialog box, click Advanced.
  6. Click the Copy Precedence tab and select the Restore from Copy Precedence checkbox.
  7. In the Copy Precedence box, type the copy precedence number for the backup copy.

  8. Click the General tab.
  9. Select the Use RMAN Restore checkbox.
  10. Click OK.

Managing Restore Jobs

Once you initiate the restore operation, a restore job is generated in the Job Controller. Jobs can be managed in a number of ways. The following sections provide information on the different job management options available:

Restarting Jobs

Jobs that fail to complete successfully are automatically restarted based on the job restartability configuration set in the Control Panel. Keep in mind that changes made to this configuration will affect all jobs in the entire CommCell.

To Configure the job restartability for a specific job, you can modify the retry settings for the job. This will override the setting in the Control Panel. It is also possible to override the default CommServe configuration for individual jobs by configuring retry settings when initiating the job. This configuration, however, will apply only to the specific job.

Restore jobs using RMAN and RMAN backup copy are resumed from the point-of-failure. Similarly, restore jobs from file system and file system backup copy are resumed from the beginning.

Configure Job Restartability at the CommServe Level

  1. From the CommCell Console, click Control Panel icon.
  2. Select Job Management.
  3. Click Job Restarts tab and select a Job Type.
    • Select Restartable to make the job restartable.
    • Change the value for Max Restarts to change the maximum number of times the Job Manager will try to restart a job.
    • Change the value for Restart Interval (Mins) to change the time interval between attempts for the Job Manager to restart the job.
  4. Click OK.

Controlling Jobs

The following controls are available for running jobs in the Job Controller window:

Suspend

Temporarily stops a job. A suspended job is not terminated; it can be restarted at a later time.

Resume

Resumes a job and returns the status to Waiting, Pending, Queued, or Running. The status depends on the availability of resources, the state of the Operation Windows, or the Activity Control setting

Kill

Terminates a job.

Suspending a Job

  1. From the Job Controller of the CommCell Console, right-click the job and select Suspend.
  2. The job status may change to Suspend Pending for a few moments while the operation completes. The job status then changes to Suspended.

Resuming a Job

  1. From the Job Controller of the CommCell Console, right-click the job and select Resume.
  2. As the Job Manager attempts to restart the job, the job status changes to Waiting, Pending, or Running.

Killing a Job

  1. From the Job Controller of the CommCell Console, right-click the job and select Kill.
  2. Click Yes when the confirmation prompt appears if you are sure you want to kill the job. The job status may change to Kill Pending for a few moments while the operation completes. Once completed, the job status will change to Killed and it will be removed from the Job Controller window after five minutes.

Resubmitting Jobs

If a restore job fails to complete successfully, you can resubmit the job without the need to reconfigure the original job's restore options using the Resubmit Job feature. When a job is resubmitted, all the original options, restore destinations, and other settings configured for the job remain in tact.

Resubmit a Restore Job

  1. From the CommCell Browser, right-click a client computer whose data recovery history you want to view, click View, then click to view a job history.
  2. From the Job History Filter dialog box, select Restore.
    • If you want to view more advanced options for restores, from the Job History Filter, select Restore, then click Advanced.
    • From the Data Recovery History Advanced Filter select the destination client computer of the restores you would like to view, then click OK.
  3. The system displays the results of the options you selected in the Data Recovery Job History window.
  4. Right-click on any job, and select Resubmit.
  5. Select the job options.
  6. Click OK.

Additional Restore Options

Several additional options are available to further refine your restore operations. The following table describes these options, as well as the steps to implement them.

Be sure to read the overview material referenced for each feature prior to using them.

Option Description Related Topics
Startup Options

The Startup Options are used by the Job Manager to set priority for resource allocation. This is useful to give higher priority to certain jobs. You can set the priority as follows:

  1. From the CommCell Browser, navigate to Client Computers | <RAC Client>
  1. Right-click the <Instance> point to All Tasks, and then click Browse Backup Data.
  2. Click OK.
  3. In the right pane of the Browse window, select the data you want to restore and click Recover All Selected.
  4. Click Advanced.
  1. Click Startup tab.
  2. Select Change Priority.
  3. Select a priority number - 0 is the highest priority and 999 is the lowest priority.
  4. Select the Start up in suspended State check box to start the job in a suspended state.
  5. Click OK.
Refer to Job Priority and Priority Precedence.
Copy Precedence By default, the system retrieves data from the storage policy copy with the lowest copy precedence. If the data was pruned from the primary copy, the system automatically retrieves data from the other copies of the storage policy in the lowest copy precedence to highest copy precedence order. Once the data is found, it is  retrieved, and no further copies are checked.

You can retrieve data from a specific storage policy copy (Synchronous Copy or Selective Copy). If data does not exist in the specified copy, the data retrieve operation fails even if the data exists in another copy of the same storage policy. Follow the steps given below to retrieve the data from a specific storage policy copy:

  1. From the CommCell Browser, navigate to Client Computers | <RAC Client>
  1. Right-click the <Instance> point to All Tasks, and then click Browse Backup Data.
  2. Click OK.
  3. In the right pane of the Browse window, select the data you want to restore and click Recover All Selected.
  4. Click Advanced.
  1. Click Copy Precedence tab.
  2. Select the Restore from copy precedence check box.
  3. Select the number from Copy Precedence list.
  4. Click OK.
Refer to Recovering Data From Copies.
Data Path Options

The data recovery operations use a default Library, MediaAgent, Drive Pool, and Drive as the Data Path. You can use this option to change the data path if the default data path is not available. Follow the steps given below to change the default data path:

  1. From the CommCell Browser, navigate to Client Computers | <RAC Client>
  1. Right-click the <Instance> point to All Tasks, and then click Browse Backup Data.
  2. Click OK.
  3. In the right pane of the Browse window, select the data you want to restore and click Recover All Selected.
  4. Click Advanced.
  1. Click Data Path tab.
  2. Select the MediaAgent from Use MediaAgent list.
  3. Select the Library from Use Library list.
  4. Select the drive pool and drive from Use Drive Pool and Use Drive lists for tape library.
  5. Select the name of the Proxy server  from Use Proxy list, if you wish to restore using a proxy server.
  6. Click OK.
Refer to Change Data Path.
Encryption

If the client's data is encrypted with a pass phrase, you must enter the pass-phrase to start the data recovery operation. Follow the steps given below to enter the pass-phrase:

  1. From the CommCell Browser, navigate to Client Computers | <RAC Client>
  1. Right-click the <Instance> point to All Tasks, and then click Browse Backup Data.
  2. Click OK.
  3. In the right pane of the Browse window, select the data you want to restore and click Recover All Selected.
  4. Click Advanced.
  1. Click Encryption tab.
  2. Type the pass phrase in Pass Phrase box.
  3. Re-type the pass phrase in Re-enter Pass Phrase box.
  4. Click OK.
Refer to Data Encryption.
Alerts

This option enables users or user groups to get automatic notification on the status of the data recovery job. Follow the steps given below to set up the criteria to raise notifications/alerts:

  1. From the CommCell Browser, navigate to Client Computers | <RAC Client>
  1. Right-click the <Instance> point to All Tasks, and then click Browse Backup Data.
  2. Click OK.
  3. In the right pane of the Browse window, select the data you want to restore and click Recover All Selected.
  4. Click Advanced.
  1. Click Alerts tab.
  2. Click Add Alert.
  3. From the Add Alert Wizard box, select the required threshold and notification criteria and click Next.
  4. Select the required notification types and click Next.
  5. Select the recipients and click Next.
  6. Click Finish.
  7. Click OK.
Refer to Alerts and Notifications.
CommCell Readiness Report The CommCell Readiness Report provides you with vital information such as connectivity and readiness of the Client, MediaAgent, and CommServe. It is useful to run this report before performing a backup or a recovery operation. Follow the steps given below to generate the report:
  1. On the CommCell Console menu bar, select the Reports tab.
  2. Click Readiness.

    The Report Selection dialog box appears.

  3. If necessary, select Reports | CommServe | CommCell Readiness in the left pane.
  4. Select the Computers tab, and then click Modify below the Computers list.
  5. In the dialog box that appears, clear Include All Client Computers and All Client Groups.
  6. Select the appropriate client from the Exclude list, and then click Include >.
  7. Click OK.
  8. Select the MediaAgent tab, and then clear Include All MediaAgents.
  9. Select the appropriate MediaAgent from the Exclude list, and then click Include >.
  10. Click Run.

    The report appears in your default Web browser.

Refer to CommCell Readiness Report.
Restore Job Summary Report

The Restore Job Summary Report provides you with information about all the data recovery jobs that are run in last 24 hours for a specific client and agent. You can get information such as failure reason, failed objects, job options, and so on. It is useful to run this report after performing the restore. Follow the steps given below to generate the report:

  1. On the CommCell Console menu bar, select the Reports tab.
  2. Click Summary.

    The Report Selection dialog box appears.

  3. If necessary, select Reports | Jobs | Job Summary in the left pane.
  4. On the General tab, select Data Recovery Jobs.
  5. Select the Computers tab.
  6. Select the appropriate client and the appropriate agent.
  7. Click Run.

    The report appears in your default Web browser.

Refer to Restore Job Summary Report.