SnapProtect - Advanced Restore - Oracle

Table of Contents

Restoring Data from a Snapshot

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.
  • In a Windows cluster environment, restore operations must be performed using the proxy computer.

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 Using RMAN

Use the following steps to restore data from a snapshot using RMAN scripts. Note that logs are not restored using RMAN.

  1. From the CommCell Browser, expand 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.
  6. From the Restore Options for All Selected Items window, select the Use Snap Restore checkbox.
  7. Click Advanced.
  8. Select the Use RMAN Restore checkbox.
  9. Click OK to save the settings and close the Advanced Restore Options window.
  10. Click OK to close the Restore Options dialog box and initiate the restore job.

Restore Using a Proxy Computer

  1. From the CommCell Browser, expand 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.
  6. From the Restore Options for All Selected Items window, select the Use Snap Restore checkbox.
  7. Click Advanced.
  8. Click the Data Path tab.
  9. From the Use Proxy box, select the server that you want to use as proxy.

    The Oracle restore will use the file system restore from snap if this option is selected.

  10. Click OK to save the settings and close the Advanced Restore Options window.
  11. Click OK to close the Restore Options dialog box and initiate the restore job.

Restoring Data from Backup Copy

You can perform a restore from the backup copy by setting the appropriate copy precedence number.

Restore Data Using File System

If the backup copy operation was performed using File system, then restore from backup copy will be performed using only the File System. Use the following steps to restore the data from backup copy using the File System backup:

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

  1. Select the General tab.
  2. Select the Use File System Restore checkbox.
  3. Click OK.

Restore Data Using RMAN

If the backup copy operation was performed using RMAN, then restore from backup copy will also be performed using the RMAN.

Use the following steps to restore the data from backup copy using RMAN:

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

Creating a Duplicate Database

A duplicate (auxiliary) database is a copy or a subset of the target database and has a unique DBID. It is independent of the primary database and can be registered in the same recovery catalog as the primary database. The duplicate database will be useful for testing and demo purposes.

If the duplicate (auxiliary) database already exists in the destination computer, it will be overwritten. Duplicate database is created from the full backup of the database with the logs. If you want the latest data in the duplicate database, make sure to perform a full backup with the log files before creating the duplicate database.

Note: You must have a RMAN backup copy in order to create a duplicate database.

On a Different Host with the Instance Configured

Use the following steps to create a duplicate database on a different host with the configured instance. Make sure that the instance is configured on a different host in the CommCell Console.

  1. Perform a full backup along with the log files on the original database.
  1. On the destination host, make sure to remove the temp.dbf file from the existing database instance.
  1. Manually, copy the init<SID>.ora file from the source computer to the destination computer.
    • On Unix:

      $ORACLE_HOME

    • On Windows:

      %ORACLE_HOME%

  1. Update the database name, dump files, archive logs and the control file locations in the init<SID>.ora file for the duplicate database instance.
  1. 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.

    Make sure that all the other parameters in the init<SID>.ora file are same as that in the original database.

    • On Unix:

      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)

    • On Windows:

      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')

      When using these parameters on a Windows computer, the file paths should be entered in uppercase.

      On the Windows clients, restart Oracle services. Skip this step, if you are using a Unix client.

  1. Add the duplicate database instance name in the Listener.ora file on the destination host and add TNS entry on Tnsnames.ora files on the source and destination hosts.
  2. Add the source 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)
    )
    )

  3. Restart the Listener.

    $ lsnrctl reload

  4. Provide a valid connect string for the auxiliary channel.

    Example:

    sys/sys@<SID name>

  5. Startup the duplicate database instance in NOMOUNT mode.
  6. From the CommCell Browser, navigate to Client Computers | <Client> | Oracle.
  7. Right-click the <Instance>, point to All Tasks and then click Browse and Restore.
  8. Click View Content.

  9. Select the database and click Recover All Selected.
  10. Select the Duplicate DB check box.

  11. Click Advanced.
  12. Click the Copy Precedence tab and select the Restore from Copy Precedence checkbox.
  13. In the Copy Precedence box, type the copy precedence number for the RMAN backup copy.
  14. Click the Duplicate tab.
  15. Select the Duplicate To checkbox.
  16. Type the name of duplicate database in Database Name box.
  17. Type the name of startup Parameter file in Pfile box or click Browse to locate it.
  18. Click OK.

  19. Under The Latest Database View box, click Refresh to verify that the status of the duplicate database is STARTED.
  20. Click OK.

On a Different Host without the Instance Configured

In order to create duplicate database on a different host without a configured instance, we need the following installed on the destination computer:

  • Base client
  • Oracle iDataAgent

Use the following steps to create a duplicate database on a different host without the configured instance. Make sure that the duplicate instance is not configured from the CommCell console.

  1. Perform a full backup along with the log files on the original database.
  2. Create a duplicate database instance on the destination host.
  3. Manually, copy the init<SID>.ora file from the source computer to the destination computer.
    • On Unix:

      $ORACLE_HOME

    • On Windows:

      %ORACLE_HOME%

  1. Update the database name, dump files, archive logs and the control file locations in the init<SID>.ora file for the duplicate database instance.
  1. 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.

    Make sure that all the other parameters in the init<SID>.ora file are same as that in the original database. Copy the destination computer init<SID>.ora to source computer.

    • On Unix:

      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)

    • On Windows:

      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')

      When using these parameters on a Windows computer, the file paths should be entered in uppercase.

      On the Windows clients, restart Oracle services. Skip this step, if you are using a Unix client.

  1. Add the duplicate database instance name in the Listener.ora file on the destination host and add TNS entry on Tnsnames.ora files on the source and destination hosts.

    Make sure that Static listener is configured. Add the duplicate database instance name in the Listener.ora file on the destination host. Add TNS entry on Tnsnames.ora files and destination host.

  2. Add the auxiliary database name in the Tnsnames.ora file on the source host. Make sure to use the password change_on_install when you create the password file for auxiliary database.

    DUPDB =
    DESCRIPTION =
    ADDRESS = (PROTOCOL = TCP)(HOST = powerpc02)(PORT = 1521))
    (CONNECT_DATA =
    (SERVER = DEDICATED)
    (SERVICE_NAME = dupdb)
    )
    )

  3. Restart the Listener.

    $ lsnrctl reload

  4. Provide a valid connect string for the auxiliary channel.

    Example:

    sys/sys@<SID name>

  5. Startup the duplicate database instance in NOMOUNT mode.
  6. When using a different host without configuring an instance, the install path in the source and destination clients must be the same.

    Use the following steps to set the same install path in the source and destination clients.

    • From the CommCell Browser, right-click the <CommServe> and then click Properties.
    • Click the additional setting Settings tab.
    • Click Add.
    • In the Name field, type sNOSBTLIBNAME.
    • In the Category list, select CommServe from the list.
    • In the Type list, select String.
    • In the Value field, type Y.
    • Click OK.

  7. Ensure to run the Ora_install.sh on the auxiliary client.
  8. From the CommCell Browser, navigate to Client Computers | <Client> | Oracle.
  9. Right-click the <Instance>, point to All Tasks and then click Browse and Restore.
  10. Select  Latest Backup and click View Content.

  11. From the Browse window, select the data you want to recover in the right pane and click Recover All Selected.
  12. Select the Duplicate DB check box.
  13. Click Advanced.

  14. Click the Copy Precedence tab and select the Restore from Copy Precedence checkbox.
  15. In the Copy Precedence box, type the copy precedence number for the RMAN backup copy.
  16. Click the Duplicate tab.
  17. Select the Duplicate To check box.
  18. Type the name of duplicate database in Database Name box.
  19. Type the name of startup Parameter file in Pfile box or click Browse to locate it.
  20. Click OK.

    After restoring to a duplicate database, change the sNOSBTLIBNAME value to N.

On the Same Host without the Instance Configured

Use the following steps to create a duplicate database on the same host without the configured instance:

  1. Perform a full backup along with the log files on the original database.
  1. Create a duplicate database instance on the destination host. If the database already exists on the destination host, make sure to remove the temp.dbf file before performing a restore operation.
  1. Manually, copy the init<SID>.ora file from the source computer to the destination computer.
    • On Unix:

      $ORACLE_HOME

    • On Windows:

      %ORACLE_HOME%

  1. Update the database name, dump files, archive logs and the control file locations in the init<SID>.ora file for the duplicate database instance.
  1. 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.

    Make sure that all the other parameters in the init<SID>.ora file are same as that in the original database.

    • On Unix:

      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)

    • On Windows:

      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')

      When using these parameters on a Windows computer, the file paths should be entered in uppercase.

      On the Windows clients, restart Oracle services. Skip this step, if you are using a Unix client.

  1. Add the duplicate database instance name in the Listener.ora file and Tnsnames.ora files.
  2. Add the source database name in the Tnsnames.ora file on the destination host.

    Make sure to use the password change_on_install when you create the password file for auxiliary database.

    DUPDB =
    DESCRIPTION =
    ADDRESS = (PROTOCOL = TCP)(HOST = powerpc02)(PORT = 1521))
    (CONNECT_DATA =
    (SERVER = DEDICATED)
    (SERVICE_NAME = dupdb)
    )
    )

  3. Restart the Listener.
  4. Provide a valid connect string for the auxiliary channel.

    Example:

    sys/sys@<SID name>

  5. Startup the duplicate database instance in NOMOUNT mode.
  6. From the CommCell Browser, navigate to Client Computers | <Client> | Oracle.
  7. Right-click the <Instance>, point to All Tasks and then click Browse and Restore.
  8. Select  Latest Backup and click View Content.

  9. Select the database and click Recover All Selected.
  10. Select the Duplicate DB check box.
  11. Under The Latest Database View box, click Refresh to verify that the status of the duplicate database is STARTED.
  12. Click Advanced.

  13. Click the Copy Precedence tab and select the Restore from Copy Precedence checkbox.
  14. In the Copy Precedence box, type the copy precedence number for the RMAN backup copy.
  15. Click the Duplicate tab.
  16. Click the Duplicate To check box.
  17. Type the name of duplicate database in the Database Name box.
  18. Type the name of the startup parameter file in Pfile box or click Browse to locate it.
  19. Click OK.

On the Same Host with the Instance Configured

Use the following steps to create a duplicate database on the same host with the configured instance:

  1. Perform a full backup along with the log files on the original database.
  1. Create a duplicate database instance on the destination host. If the database already exists on the destination host, make sure to remove the temp.dbf file before performing a restore operation.
  1. Manually, copy the init<SID>.ora file from the source computer to the destination computer.
    • On Unix:

      $ORACLE_HOME

    • On Windows:

      %ORACLE_HOME%

  1. Update the database name, dump files, archive logs and the control file locations in the init<SID>.ora file for the duplicate database instance.
  1. 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.

    Make sure that all the other parameters in the init<SID>.ora file are same as that in the original database.

    • On Unix:

      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)

    • On Windows:

      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')

      When using these parameters on a Windows computer, the file paths should be entered in uppercase.

      On the Windows clients, restart Oracle services. Skip this step, if you are using a Unix client.

  1. Add the duplicate database instance name in the Listener.ora file and Tnsnames.ora files.
  2. Add the source database name in the Tnsnames.ora file on the destination host.

    Make sure to use the password change_on_install when you create the password file for auxiliary database.

    DUPDB =
    DESCRIPTION =
    ADDRESS = (PROTOCOL = TCP)(HOST = powerpc02)(PORT = 1521))
    (CONNECT_DATA =
    (SERVER = DEDICATED)
    (SERVICE_NAME = dupdb)
    )
    )

  3. Restart the Listener.
  4. Provide a valid connect string for the auxiliary channel.

    Example:

    sys/sys@<SID name>

  5. Startup the duplicate database instance in NOMOUNT mode.
  6. From the CommCell Browser, navigate to Client Computers | <Client> | Oracle.
  7. Right-click the <Instance>, point to All Tasks and then click Browse and Restore.
  8. Select Latest Backup and click View Content.
  9. Optional: Use non-default Browse and Restore options. See Browse and Restore.
  10. Select the database and click Recover All Selected.
  11. Select the Duplicate DB check box.
  12. Click Advanced.
  13. Click the Copy Precedence tab and select the Restore from Copy Precedence checkbox.
  14. In the Copy Precedence box, type the copy precedence number for the RMAN backup copy.
  15. Click the Duplicate tab.
  16. Click the Duplicate To check box.
  17. Type the name of duplicate database in Database Name box.
  18. Type the name of startup parameter file in Pfile box or click Browse to locate it.
  19. Click OK.

Excluding Read-Only Tablespaces during Restore

By default, the read only tablespaces are not verified for consistency and are restored from the backup. You can skip the consistent tablespaces and restore the tablespaces that are not consistent or missing. This will save the time taken for the restore.

Use the following steps to exclude read only table spaces during 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.
  3. Select  Latest Backup and click View Content.
  4. Optional: Use non-default Browse and Restore options. See Browse and Restore.
  5. Select the database and Click Recover All Selected.
  6. Select the name of the client computer from the Destination Client list.
  7. Select Duplicate DB check box.
  8. Click Advanced.
  9. Click Duplicate tab.
  10. Click Duplicate To.
  11. Type the name of duplicate database in Database Name box.
  12. Type the name of startup Parameter file in Pfile box or click Browse to locate it.
  13. Select Duplicate To Skip Read Only check box.
  14. Click OK.

Opening the Database in Restricted Mode after a Restore

By default, a duplicated database is opened without any restricted access. If necessary, you can open the db in restricted mode for administrative tasks. This will restrict access to other users.

Use the following steps to open the duplicate database in restricted mode:

  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. Select Latest Backup and click View Content.
  4. Optional: Use non-default Browse and Restore options. See Browse and Restore.
  5. Select the database and Click Recover All Selected.
  6. Select the name of the client computer from the Destination Client list.
  7. Select Duplicate DB check box.
  8. Click Advanced.
  9. Click Duplicate tab.
  10. Click Duplicate To.
  11. Type the name of duplicate database in Database Name box.
  12. Type the name of startup Parameter file in Pfile box or click Browse to locate it.
  13. Select Duplicate To Open Restricted check box.
  14. Click OK.

Excluding Tablespaces from a Restore

While creating a duplicate database, you can exclude some tablespaces from the duplicate database. Use the following steps to exclude the tablespaces from the duplicate database:

  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. Select  Latest Backup and click View Content.
  4. Optional: Use non-default Browse and Restore options. See Browse and Restore.
  5. Select the database and Click Recover All Selected.
  6. Select the name of the client computer from the Destination Client list.
  7. Select Duplicate DB check box.
  8. Click Advanced.
  9. Click Duplicate tab.
  10. Click Duplicate To.
  11. Type the name of duplicate database in Database Name box.
  12. Type the name of startup Parameter file in Pfile box or click Browse to locate it.
  13. Select the Duplicate To Skip TableSpaces check box.
  14. Click Add
  15. Select the tablespaces that appear in the TableSpaces box to exclude from the duplicate database.
  16. Click OK.

Setting Up the Redo Log Files

You can create online redo logs for duplicate database and apply them to restore the database in case of corruption. Use the following steps to create an online redo log file:

  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. Select Latest Backup and click View Content.
  4. Optional: Use non-default Browse and Restore options. See Browse and Restore.
  5. Select the database and Click Recover All Selected.
  6. Select the name of the client computer from the Destination Client list.
  7. Select Duplicate DB check box.
  8. Click Advanced.
  9. Click Duplicate tab.
  10. Click Duplicate To.
  11. Type the name of duplicate database in Database Name box.
  12. Type the name of startup Parameter file in Pfile box or click Browse to locate it.
  13. Select Duplicate To Log File check box.
  14. Click File to select a file containing the online redo log.
  15. Click Add to include the specifications for an online redo log file.
  16. In the Spec Dialog for Oracle Redo Log File box, type the name or click Browse to select the redo log file.
  17. Type the Size of the online redo log file.
  18. Select the Size Specifications of the file from SizeSpec list.
  19. Select Reuse check box to allow the database to reuse an existing file.
  20. Click OK.

To Add a Redo Log File for a Group

By default, groups are created to include specific online redo log members. Use the following steps to add specifications for each of these online redo log groups:

  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. Select Latest Backup and click View Content.
  4. Optional: Use non-default Browse and Restore options. See Browse and Restore.
  5. Select the database and Click Recover All Selected.
  6. Select the name of the client computer from the Destination Client list.
  7. Select Duplicate DB check box.
  8. Click Advanced.
  9. Click Duplicate tab.
  10. Click Duplicate To.
  11. Type the name of duplicate database in Database Name box.
  12. Type the name of startup Parameter file in Pfile box or click Browse to locate it.
  13. Select Duplicate To Log File check box.
  14. Click Group to select a group containing the online redo log members.
  15. Click Add.
  16. In the Spec Dialog for Oracle Redo Log Group box, add the Size of the Group.
  17. Select the Size Specifications from SizeSpec list.
  18. Select Reuse check box to allow the database to reuse an existing file.
  19. Click OK.

Disabling File Name Validation during a Restore

By default, when you create a duplicate or standby database, RMAN will verify the target datafiles for duplicate files (files sharing the same names). This verification job may consume more time. Hence, use the following steps to prevent RMAN from performing this verification:

  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. Select Latest Backup and click View Content.
  4. Optional: Use non-default Browse and Restore options. See Browse and Restore.
  5. Select the database and Click Recover All Selected.
  6. Select Duplicate DB check box.
  7. Type the connect string name in the Catalog String box.
  8. Click Advanced.
  9. Click Duplicate DB Options tab.
  10. Select No FileName Check check box.
  11. Click OK.

Redirecting Datafiles and Tempfiles during a Restore

If you want to restore all data and temp files to a different directory structure than the source database and do not want to use DB_FILE_NAME_CONVERT, you can redirect these data and temp files to a duplicate database during the restore. Please refer Customizing RMAN Script from the CommCell Console to update the script and to submit a duplicate restore.

Use the following steps to redirect all data and temp files:

  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. Select Latest Backup and click View Content.
  4. Optional: Use non-default Browse and Restore options. See Browse and Restore.
  5. Select the database and Click Recover All Selected.
  6. Select the name of the client computer from the Destination Client list.
  7. Select Duplicate DB check box.
  8. Click Advanced.
  9. Click Duplicate tab.
  10. Click Duplicate To.
  11. Type the name of duplicate database in Database Name box.
  12. Type the name of startup Parameter file in Pfile box or click Browse to locate it.
  13. Select Redirect tab.
  14. Select Redirect All Table Spaces/Database to and type the path or click Browse for the path to redirect all data files.
  15. Select Redirect Temp Table Spaces To and type the path or click Browse for the path to redirect temp tablespaces.

    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.

  16. Click OK.

Resetting the Database after a Restore

By default, the database is not reset. After resetting the logs to open state, you can reset the database. Use the following steps to reset the database after a 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.
  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. Click Advanced.
  2. Click Options tab.
  3. Select Open DB check Box.
  4. Select Yes from the Reset Logs list.
  5. Select Reset Database check box.
  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 OK.

Disabling Failovers during Restores

During restore operations, RMAN automatically looks for another copy of the file under the following circumstances:

  • a backup piece is corrupted or deleted
  • a MediaAgent is offline
  • a block in the backup is corrupted within the latest full backup

If it is not available in the other copy, RMAN will use older versions of the file, if available. When multiple channels are available for the same device type, RMAN will automatically retry on another channel. RMAN continuously searches all prior backups until it has exhausted all possibilities. This process will delay the restore jobs.

Use the following steps to disable the failovers during restore and prevent job delays:

  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. Click Advanced.
  2. Click Options tab.
  3. Select Disable Oracle Channel Restore Failover check box.
  4. Click the Copy Precedence tab and select the Restore from Copy Precedence checkbox.
  5. In the Copy Precedence box, type the copy precedence number for the backup copy.
  6. Click OK.

Restoring the Server Parameter (SP) File

If a Server Parameter (SP) File is lost, you can choose to restore from SnapProtect backup, auto backup, or backup piece. Ensure that the database is in SHUTDOWN mode while restoring the SP file. If you are trying to restore the SP file from a VSS SnapProtect backup, the database is automatically set to STARTED mode after the SP file is restored.

Use the following steps to restore an SP file from a backup:

  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  Restore SP File check box.
  2. 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.
  3. Click OK.

Restoring the Control File

You can restore control file from SnapProtect backup, auto backup, or backup piece.

Control files are required to recover a database to the current state. Ensure that the database is in STARTED mode while restoring the Control file to the same location.

Use the following steps to restore a Control file from a backup:

  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 Restore Control File check box.
  2. 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.
  3. Click OK.

Restoring Individual Datafiles and Tablespaces

Recover a missing or corrupted datafile and tablespace when:

  • A datafile or tablespace is corrupted after you have restored the database
  • A datafile or tablespace is the only lost data that must be restored. You can restore the datafile or tablespace instead of the entire database.

You must place the datafiles and tablespaces that you want to restore offline, before you start the restore. The database can remain online, unless you restore Oracle SYSTEM tablespaces.

When you perform a restore, the SnapProtect ASM diskgroup is mounted and the data file copy is cataloged on the mounted ASM diskgroup. The restore restore uses RMAN scripts.

Before You Begin

  1. Perform a full backup with a subclient configured for Oracle datafiles and tablespaces.
  2. Place the tablespace you want to restore in OFFLINE mode, or set the SnapProtect software to automatically move the database to the correct mode before the restore.

    ALTER TABLESPACE users OFFLINE IMMEDIATE

Procedure

  1. From the CommCell Browser, expand Client Computers > client > Oracle.
  2. Right-click the instance, point to All Tasks and then click Browse and Restore.
  3. Select Latest Backup and click View Content.
  4. In the right pane of the CommCell Browser window, select the datafiles and tablespaces to restore, and click Recover All Selected.
  5. On the General tab of the Restore Options dialog box, click Advanced.

    The Advanced Restore Options dialog box appears.

  6. On the Options tab, select the Switch Database mode for Restore check box.
  7. To set the SnapProtect software to automatically move the database to the correct mode before the restore, select the Switch Database mode for Restore check box.
  8. Optional: Select the restore options.
    Expand All

    Set the Oracle Database ID

    The Oracle DBID is an internal, uniquely generated number that distinguishes the target database from the rest of the databases with the same name, in the recovery catalog. Oracle creates this number automatically when you create the database.

    You can use this option when:

    • There is no control file and you need to restore the control file or SP file from the autobackup
    • Multiple databases exist in the recovery catalog and you need to restore the control file

    On the Options tab, select the Set DBID check box.

    Open the database after the restore

    After a restore, set the SnapProtect software to automatically open the Oracle database. When the database is open, it records transactions.

    On the Options tab, select the Open DB check box.

    Reset the database and logs.

    By default, the database is automatically set to open, and the logs are reset.

    If you reset the logs to an open state, you can then reset the database.

    On the Options tab, select the Reset Database check box and one of the following Reset Log options:

    • To open the database without the RESETLOGS option, select None.
    • To open the database with the RESETLOGS option, select Yes.
    • To open the database with the NORESTLOGS option, select No.

    Perform a point-in-time restore of a database that was backed up in NOARCHIVELOG mode

    If the database was backed up in NOARCHIVELOG mode, enable the redo logs.

    When the no redo log is disabled, RMAN searches archived redo logs after applying the incremental backup data during a restore. When you set No Re-do Logs, RMAN restores the data from the incremental backup and not the archived redo logs.

    On the Options tab, select the No Re-do Logs check box.

    Prevent RMAN failovers to the previous backup for Oracle 10g databases or higher

    Select this option if you want to increase the speed.

    During restore operations, RMAN automatically looks for another copy of the backup file under the following circumstances:

    • A backup piece is corrupted or deleted
    • A MediaAgent is offline
    • A block in the backup is corrupted within the latest full backup

    If another copy is not available in the other copy, RMAN uses an older version of the file. When multiple channels are available for the same device type, RMAN automatically retries on another channel and searches all prior backups until it has exhausted all possibilities.

    On the Options tab, select the Disable Oracle Channel Restore Failover check box.

    Validate the restore

    Validation verifies that the backup copies of the data and logs are intact and usable for restores. RMAN simulates the restore job without the media to determine whether the restore can be successfully performed.

    When a validate job is complete, you can view the job log files to identify and correct any issues.

    On the Options tab, select the Validate check box.

    Perform a point-in-time restore when the database is in NOARCHIVELOG mode

    When you set this feature, RMAN restores only the data from the incremental backup and not the archived redo logs.

    On the Options tab, select the No Re-do Logs check box.

    Configuring Pre- and Post-Processes

    Run scripts before or after the restore.

    Enter the full path for the pre-recovery and post-recovery script.

    You can choose to run the post-process script even if the restore job failed. You can use the post-process script to bring a database online or to release a snapshot.

    On the Pre/Post tab:

    1. In the Pre-Recovery Command box, type the full path name for the script.
    2. In the Post-Recovery Command box, type the full path name for the script.
    3. To run the post recovery process regardless of the job's outcome, select the Run Post Process for all attempts check box.
    4. In Windows configurations, specify the user that runs the process, in the Pre/Post Impersonation section, select one of the options:

      if the local account has permission to execute the processes on the destination client, select the Use Local Accounts option.

      To impersonate another user with permission, select the Impersonate User option and enter the credentials.

    Restore from a copy precedence

    If the backup is corrupted, restore from a storage policy copy instead of the backup.

    On the Copy Precedence tab, select the Restore from Copy Precedence number check box and enter a copy precedence number.

    Restore from a specific backup

    On the Restore tab, select the By Tag check box and enter the tag.

  9. Click OK to close the Advanced Restore Options dialog box.
  10. Click OK to close the Restore Options dialog box and start the restore.

If your restore includes Oracle SYSTEM tablespaces, switch the database mode to MOUNT.

Restoring the Archive Logs

Archive logs can be restored separately or along with the database. If there is a database failure and you need to recover the database to the recent state, you will be able to restore all the logs along with the database.

If the logs from a specific time range were lost due to a hard disk corruption, you can restore them by performing a point-in-time restore of the logs.

Use the following steps to restore all the archived logs (note that this is the default option:

  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 Restore Archive Log check box.
  2. Click Advanced.
  1. In the Snap Restore Options group, select the Use FileSystem Restore check box.
  2. If you are using a backup copy for the restore do the following:

    • 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.
  3. Click OK.

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.
  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. Click View Content.
  2. From the Browse window, select the data you want to restore in the right pane and click Recover All Selected.
  3. Verify that the Restore Data and Recover options are selected.
  4. Select the Restore Control File check box.
  5. 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.
  6. Click OK.

Restoring and Recovering an Entire Database to a New Host

You can restore entire production database to different destination host which will be used by development, testing or reporting applications.

Prerequisites

Verify the following in both the source and destination computers:

  1. Both the source and destination computers should have the same:
    • Operating systems
    • Oracle version
    • ORACLE_SID
    • init <SID>.ora file
    • Processor (32-bit or 64-bit)
  2. The destination host should be zoned to the Array (Snap Engine) where snaps for the source database exist. Assign one device from that array and verify that is visible on destination host.
  3. When restoring to the same directory structure as the source, make sure those directories exist on the destination host. When using ASM storage make sure the corresponding ASM disk groups are mounted.
  4. Verify sufficient disk space is available on the destination host to accommodate the restored database.
  5. When using VSS SnapProtect backup for restore on Windows clients, install the VSS Provider and Oracle VSS Writer on the destination host.

Setting up the Destination Host

  1. Create the pfile or copy it from the source machine and change the required parameters including the dump locations and recovery destinations.
  2. 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.
  3. 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>)))

  4. Install the Oracle iDataAgent and configure it as a client in the same CommServe where the source computer resides.
  5. Create and configure a new Oracle instance, similar to the one existing in the source computer on the destination computer.
  6. Put the Destination Instance in NOMOUNT mode.

Restoring the Database

  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 Latest Backup and click View Content.
  2. In the right pane of the CommCell Browser window, select all the database, and click Recover All Selected.
  3. On the General tab of the Restore Options dialog box:
    • Select the name of the client computer from the Destination Client list.
    • Select the Restore Control File check box.
    • Click Advanced.
  4. On the General tab of the Advanced Restore Options dialog box:
    • If the source and destination are not ASM, select Use FileSystem Restore, otherwise use the default, Use Rman Restore.
  5. If the restore is to a different directory structure, see Redirecting Datafiles during a Restore.
  6. On the Options tab of the Advanced Restore Options dialog box:
    • If the database is in NOARCHIVELOG mode, select the No Redo Logs check box.
    • Set the Reset Logs option to Yes.
    • Select the Switch Database mode for Restore check box.
  7. On the Copy Precedence tab of the Advanced Restore Options dialog box:
    • When a backup copy is being used for the restore, select the Restore from Copy Precedence checkbox and type the Copy Precedence number for the backup copy.
    • Click OK.
  8. Click OK.

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 | <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 Restore Control File check box, if you want to restore the control file(s).

  2. Click Advanced.

  3. Click the Restore tab.

  4. Click To Point-in-Time  and select the data and time.

  1. Click the Recover tab.

  2. Click the Point-in-Time  and select the data and time.

  1. Click Ctrl&SP Files Tab, if you have selected to restore the control file(s).

  2. Select Restore From check box.

  3. Click the Point-in-Time  and select the data and time.

    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.

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

    • 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.
  5. 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.

  • On Windows clients, disable automount using the following command:

    diskpart> automount disable

  • Revert operations cannot be performed in a Windows cluster environment.
  • On Unix clusters, use pre/post scripts to freeze and unfreeze the cluster for revert operations. For example, on Red Hat Linux cluster, use the following command in the pre/post scripts:

    clusvcadm -Z <group> to freeze the cluster

    clusvcadm -U <group> to unfreeze the cluster

    This is required because during revert the application is shut down and corresponding volumes are unmounted. In that case, the cluster will automatically failover to another node thus preventing the revert operation.

Before You Begin

  • Shut the database down, or set the SnapProtect software to automatically move the database to the correct mode before the restore (Advanced Restore dialog box, Options tab, Switch Database mode for Restore check box).

Procedure

  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. From the Restore Options for All Selected Items window, select the Use Snap Restore checkbox.
  2. Click Advanced.
  3. 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.

  4. To set the SnapProtect software to automatically move the database to the correct mode before the restore, on the Options tab, select the Switch Database mode for Restore check box.
  5. Click OK to confirm the revert operation.

If you are using ONTAP version 8.3 and OCUM 6.2, revert is supported from the secondary snap for restores on NFS volumes.

Restoring from an 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.

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. If you use an auxiliary instance for the restore:
    1. In the Database Name text box, type the auxiliary database name.
    2. In the PFile textbox, type the path to the PFile. Alternatively, click Browse to locate the PFile.
    3. In the Database Client box, select the client for the auxiliary instance.
    4. Note: Place the database is in NOMOUNT mode, and remove the tempfiles and default temporary tablespaces (for example, temp.dpf) from the operating system.

  6. In the Staging path box, enter the full path to the staging directory, where the tables are exported. If you did not select the auxiliary instance option, the SnapProtect software automatically creates one in staging path.
  7. To have the SnapProtect software shut down and remove the auxiliary instance after the table restore, select the Cleanup Auxiliary Instance check box.
  8. 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.
  9. Click OK.

Restoring Tables 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 select Browse and Restore.
  3. Select the Table View check box and click View Content.
  4. Optional: Use non-default Browse and Restore options. See Browse and Restore.
  5. 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.
  3. Click the Advanced Options tab.
  1. Select Import to Source DB.
  2. Click OK.

Restoring Tables 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 OK.
  5. Optional: Use non-default Browse and Restore options. See Browse and Restore.
  6. From the Browse window, navigate and select the tables to be restored and click Recover All Selected.
  7. Click the Table Restore tab.
  8. In the Staging Path box, type the location where the tables will be restored.
  9. Click the Advanced Options tab.
  10. Select Import to a Different DB.
  11. In the Enter Import Oracle Instance: box, type the destination instance name.
  12. In the Select a Client box, select the source client.
  13. 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.

Windows:

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')

Restart the Oracle Services, if using Windows clients.

Unix:

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)

  1. Add the log_archive_dest_1 parameter is added to the init<SID>.ora file on the auxiliary instance.
  1. 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) ) )

  2. Restart the Listener.

    $lsnrctl reload

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

    sql> startup nomount;

With 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

    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')

    Restart the Oracle Services, if using Windows clients.

    Unix

    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)

  1. Add the log_archive_dest_1 parameter is added to the init<SID>.ora file on the auxiliary instance.
  2. 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) ) )

  3. Restart the Listener.

    $lsnrctl reload

  4. 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 select Browse and Restore.
  3. Select the Table View check box and click View Content.
  4. Optional: Use non-default Browse and Restore options. See Browse and Restore.
  5. From the Browse window, navigate and select the tables to be restored and click Recover All Selected.
  6. On the Table Restore tab of the Table Restore Options dialog box:
    1. Select the Auxiliary Instance checkbox.
    2. In the Database Instance box, type the auxiliary instance name.
    3. In the Database Client box, select the destination client for the auxiliary instance.
    4. In the PFile box, type the path to the PFile of the auxiliary instance. Alternatively, click Browse to select the path.
    5. In the Staging Path box, type the location where the auxiliary instance will be created. Alternatively, click Browse to select the path.
    6. To leave the auxiliary instance intact after the table restore, clear the Cleanup Auxiliary check box.
  7. On the Advanced Options tab of the Table Restore Options dialog box:
    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.
    4. Click Advanced.
  8. On the Advanced Options tab of the Advanced Table Restore Options dialog box:
    1. Select the Point-in-Time check box and specify the time range to which the database need to be recovered.
    2. Click OK.
  9. Click OK.

Restoring Tables with Non-English Characters

By default, you can browse and restore tables with English characters. If the Oracle database uses a different character set (other than US7ASCII), use the following steps to enable browse and restore for tables with non-English characters.

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

    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 select Browse and Restore.
  3. Select the Table View check box and click View Content.
  4. Optional: Use non-default Browse and Restore options. See Browse and Restore.
  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 auxiliary instance will be restored.
  8. Click the Advanced Options tab.
  9. Select the Include Stored Procedures checkbox.
  10. Select Use additional export parameters checkbox and type the parameters to be exported.
  11. Click OK.

Selecting Dependent and Referenced Tables

When you browse using the table view, you can also view the dependent and referenced tables associated with the tables selected for the restore.

Dependent tables are the parent tables (containing the primary key) that the selected table (containing the foreign key) depends upon. Similarly, Referenced tables are the child tables (containing the foreign key) that references the selected table (containing the primary key).

By default, all the dependent and referenced tables will be included in the restore operation. Use the following steps to exclude the dependent/referenced tables:

  1. From the CommCell Browser, navigate to Client Computers | <Client> | Oracle.
  2. Right-click the <Instance>, point to All Tasks and select Browse and Restore.
  3. Select the Table View check box and click View Content.
  4. From the Browse window, navigate to the table to be restored.
  5. Right-click the <table> and click Select/Deselect All Dependent Tables to exclude all the dependent tables.

    Similarly, click Deselect All Referenced Tables to exclude all the referenced tables.

  6. Click Restore All Selected.
  7. Click the Table Restore tab.
  8. In the Staging Path box, type the location where the auxiliary instance will be restored.
  9. Click OK.

Including All Dependencies to the Dependent and Referenced Tables

When restoring tables, you can include recursive dependency relationship of all the dependent/referenced tables.

Use the following steps to include all the dependent/referenced tables recursively:

  1. From the CommCell Browser, navigate to Client Computers | <Client> | Oracle.
  2. Right-click the <Instance>, point to All Tasks and select Browse and Restore.
  3. Select the Table View check box and click View Content.
  4. From the Browse window, navigate to the table to be restored.
  5. Right-click the <table> and click Select All Dependent Tables Recursively to include recursive dependency of dependent tables.

    Similarly, click Deselect All Referenced Tables Recursively to include recursive dependency of referenced tables.

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

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 | <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. 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 Current Time option.
  3. On the Advanced Restore Options dialog box, navigate to the Options tab, select the Switch Database Mode for Restore check box.
  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 | <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. 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 Point-in-Time option and enter date and time.

    The time selected is specific to the CommServe time zone.

  3. On the Advanced Restore Options dialog box, navigate to the Options tab, In the Reset Logs box, select Yes and select the Switch Database Mode for Restore check box.

    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.

  4. Click OK.
  5. Click OK.

Recovering a Database Using the System Change Number

The System Change Number (SCN) keeps track of the timing of transactions in the Oracle database. The SCN's are stored in the control files and the datafile headers. You can recover the database to the last existing SCN number in the control file. (The last SCN number denotes the last consistent state of the database.)

Use the following steps to recover a database using SCN:

  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. 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 SCN option and enter the System Change Number.
  3. On the Advanced Restore Options dialog box, navigate to the Options tab, In the Reset Logs box, select Yes and select the Switch Database Mode for Restore check box
  4. Click OK.
  5. 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.
  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. 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 Backup Time option.
  3. Click OK.
  4. Click OK.

Recovering a Database Using the Latest SCN Number

The latest backup job's Next SCN number is passed to the recover operation. This is the Next SCN 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 to the last backup time.

  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. 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

When using NetApp or Pure Storage storage arrays, you can duplicate the source database by cloning the 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.

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.

Create the Clone Environment

Use the following steps to create a clone environment from existing snapshots:

  1. From the CommCell Browser navigate to the Client Computers | <Client> | Oracle.
  2. Right-click the <Instance> and then click All Task | Clone.
  3. From the Clone Options dialog box, click View Contents.
  4. From the browse window, select the database to be cloned on the left pane and then click Clone.
    • Select the entire database and not individual tablespaces.
  5. From the Oracle Restore 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. 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.
  8. Specify the location of the startup Parameter file in the PFile box, for example /oracle/clone/initdup1.ora.

    Alternatively, you can click Browse to locate the PFile.

    • 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.
  9. Specify the mount path location in the Snap Mount Location box, for example, /oracle/clone. This mount path will contain mounted snapshots from the Oracle database.

    The Oracle user must 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. You must have enough disk space to hold the logs until the reservation period expires.

  10. 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.

  11. By default, the system will set up two redo log groups, with one log file in each group. To override this configuration (location, number of groups, files), select the Online Log Files check box and the n select the Group option.
    1. Click Add.
    2. In the Type the Size of the online redo log file.
    3. Select the Size Specifications of the file from SizeSpec list.
    4. To allow the database to reuse an existing file, select the  Reuse check box
  12. 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 | <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. Click Advanced.
  2. Click the Options tab.
  3. Select Switch Database mode for Restore.
  4. If you are using a backup copy for the restore do the following:

    • 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.
  5. 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 | <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. Click Advanced.
  1. Click Options tab.
  2. Select the database incarnation value from Set DB Incarnation list.
  3. If you are using a backup copy for the restore do the following:

    • 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.
  4. Click OK.

Setting the Log State after a Restore

By default, the database is automatically set to open and the logs are reset. Use the following steps to prevent resetting the logs:

  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. Click Advanced.
  2. Click Options tab.
  3. Select Open DB check Box.
  4. Select the following options from Reset Logs list.
    • None - Open the database without RESETLOGS option.
    • No - Open the database with NORESETLOGS option.
  5. Click OK.

Setting Up Pre-Post Processes

You can run batch files or shell scripts before and/or after restore jobs. Use the following steps to setup a process before or after a restore job:

  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. Click Advanced.
  2. Click Pre/Post tab.
  3. Type the path for the batch file in the Pre Recovery Command box or click Browse to select the batch file to perform a process before the restore job.
  4. Type the path for the batch file in the Post Recovery Command box or click Browse to select the batch file to perform a process after the restore job.
  1. On Windows, select one of the following options:
    • Use Local Accounts  - Select this option if the local account has permissions to execute the processes on the destination client.
    • Impersonate User  - Select this option and enter the username and password, that has the permissions to execute the processes on the destination client.

      Skip this step, if you are using an Unix client.

  2. Click OK.

Setting Up a Pre-Post Process to Run after Each Attempt

By default, a specified post process command is executed only on successful completion of the restore operation.

To send the database instance name to the script, see Passing the Instance Name to Pre and Post Scripts for Databases.

Perform a restore operation even if the restore operation did not complete successfully. This may be useful to bring a database online or release a snapshot. Use the following steps to run a post process:

  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. Click Advanced.
  2. Click the Pre/Post tab.
  3. Enter the path for the batch file in the Post Recovery Command box or click Browse to select the batch file.
  4. Select the Run Post Process for all attempts check box.
  5. Click OK.

Validating Restores

If you perform a validating restore job, the RMAN will simulate a restore job and verifies whether the backup copies of data and logs required for the restore are intact and usable.

Use the following steps to validate a restore job:

  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. Click Advanced.
  2. Click the Options tab.
  3. Select the Validate check box. This validates previously run backups to ensure the integrity of the data for successful restores.
  4. Click the Copy Precedence tab and select the Restore from Copy Precedence checkbox.
  5. In the Copy Precedence box, type the copy precedence number for the backup copy.
  6. Click OK.

Setting the Database Identifier (DBID)

The Database Identifier (DBID) is an internal, uniquely generated number that will distinguish the target database from the rest of the databases that have the same name in the recovery catalog. Oracle creates this number automatically when you create the database. The DBID is set while restoring the control file to differentiate the database for which the control file is restored.

Use the following steps to set the DBID:

  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. Click Advanced.
  2. Click Options tab.
  3. Select the Set DBID check box.
  4. Click OK.

SnapProtect stores all the previous DBIDs as a point in time property. During the point-in-time control file restore from an autobackup, the correct DBID is automatically retrieved based on the point-in-time . If you manually change the DBID during the control file restore from an autobackup, the changed DBID will not match the retrieved DBID. As a result, the restore may fail. Hence, ensure that you do not manually change the DBID while restoring the control file to a point-in-time from an autobackup.

Setting Up Online Redo Log Files

Each Oracle database has a redo log. This redo log records all changes made in datafiles. When you run your database in NOARCHIVELOG mode, you disable the archiving of the redo log.

By default, the No Redo Log is disabled. Hence, While restoring the database, RMAN will search for archived re-do logs after applying incremental backup data. Setting No Re-do Logs will enable the RMAN to suppress the archived re-do logs so that only data from incremental backups is restored. Enable No Re-do logs when you perform a point-in-time restore of a database that was backed up in NOARCHIVELOG mode.

Use the following steps to enable No Re-do Logs and perform a restore operation:

  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. Click Advanced.
  2. Click Options tab.
  3. Select the No Re-do Logs check box.
  4. Click the Copy Precedence tab and select the Restore from Copy Precedence checkbox.
  5. In the Copy Precedence box, type the copy precedence number for the backup copy.
  6. 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. Use the following steps to enhance your restore operation:

  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. Click Advanced.
  2. Click Options tab.
  3. Select the number of open files from Max Open Files list.
  4. Click the Copy Precedence tab and select the Restore from Copy Precedence checkbox.
  5. In the Copy Precedence box, type the copy precedence number for the backup copy.
  6. Click OK to start the restore.

Scheduling a Restore

Follow the steps given below to schedule a restore job:

  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. Click Job Initiation tab and then click Schedule.
  2. Click Configure.

  1. Select the appropriate scheduling options.  For example:
    • Click Weekly.
    • Check the days you want the run the restore job.
    • Change the Start Time to 9:00 PM

  1. Click Options for the following advanced schedule options:
    • Range of recurrence
    • Repeat times
    • Time Zone

  2. Click OK.

The restore job will execute as per the schedule.

Command Line Restores Using RMAN

Viewing RMAN Scripts from the CommCell Console

Prior to running a snap restore operation from the CommCell Console, you can preview the corresponding RMAN script for the restore job. This is useful to see which snap restore job is used and the corresponding RMAN recovery script.

  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. On the General tab of the Restore Options dialog, click Script Preview.
  2. On the RMAN Script for Restore dialog, click OK.

Customizing RMAN Scripts from the CommCell Console

In addition to previewing the RMAN script, you can also modify the script from the CommCell Console. This is useful when you want to include RMAN commands that are not supported by the software.

  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. On the General tab of the Restore Options dialog, click Advanced.
  2. On the Advanced Restore Options dialog, navigate to the Custom Rman Script tab.
  3. In addition to previewing the RMAN script, you can also modify the recovery script from the CommCell Console. This is useful when you want to include the RMAN commands that are not supported by the software.
  4. On the Control file tab, check the Customize Script checkbox .

    The script for the control file restore is generated.

  5. Click the Database tab to view the script for the database restore.
  6. Click OK.

Updating the Customized RMAN Script

You can also modify the customized RMAN script from the CommCell Console. Use the following steps to modify the customized rman scripts from CommCell Console:

  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. From the Restore Options dialog box, click Advanced.
  2. Click the Customize Script tab.
  3. Select the Customize Script checkbox.
  4. Click the Database tab to view the script for the database restore.
  5. You can update the existing custom script by clicking the Update Script button with the selected advanced restore options. An Update Script confirmation dialog appears asking you to confirm the updated script. Click Yes.

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 for this Agent are resumed from the point-of-failure.

Configure Job Restartability at the CommServe Level

  1. From the CommCell Console toolbar, click Control Panel.
  2. Under the System section, click Job Management.
  3. Click Job Restarts tab and select a Job Type.
    • Select Restartable to make the job restartable.
    • You can change the value for Max Restarts to change the maximum number of times the Job Manager will try to restart a job.
    • You can 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
Use hardware revert capability if available

This option allow you to revert the data to the time when the snapshot was created. Selecting this option brings back the entire LUN to the point when the snapshot was created, overwriting all the modifications to data since the snapshot creation. This option is available if the snapshot engine used for SnapProtect Backup supports the revert operation.

  1. From the CommCell Browser, click Client Computers | Oracle | <instance name>. The default and other subclients (if available) are displayed on the right-hand windowpane.
  2. From the CommCell Browser, right-click the instance that contains the data you want to restore. Click All Tasks and then click Browse Backup Data.
  3. From the Browse Options window, click OK.
  4. From the browse window, select the data to be restored and click Recover all Selected.
  5. From the Restore Options for All Selected Items dialog box, click Advanced.
  6. From the Advanced Restore Options (General) tab, select Use hardware revert capability if available.

This option allow you to revert the data to the time when the snapshot was created. Selecting this option brings back the entire LUN to the point when the snapshot was created, overwriting all the modifications to data since the snapshot creation. This option is available if the snapshot engine used for SnapProtect Backup supports the revert operation.

  1. From the CommCell Browser, expand Client Computers > client > instance.
  2. Right-click the instance, point to All Tasks and then click Browse and Restore.
  3. On the Browse and Restore dialog box, select Latest Backup and click View Content.
  4. On the Browse view, select the data to restore in the right pane and click Recover All Selected.
  5. From the Browse window, select the data to restore in the right pane and click Recover All Selected.

    The Restore Options dialog box appears.

  6. On the General tab, select the data that you want to restore:
    1. Select the name of the client computer from the Destination Client list.
    2. To restore the control file, select the Restore Control File check box.
    3. To restore the archive log, select the Restore Archive Log check box.
    4. To restore the data, select the Restore Data check box.
    5. To recover the database, elect the Recover check box.
    6. Click Advanced.

      The Advanced Restore Options dialog box appears.

  7. On the General tab, select the Use hardware revert capability if available check box.
  8. Click OK to close the Advanced Restore Options dialog box.
  9. Click OK to close the Restore Options dialog box and start the restore.
 
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 | <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. 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 | <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. 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 | <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. 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 | <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. 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 | <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. 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.