Loading...

Advanced Restore - Oracle RAC iDataAgent

Table of Contents

Restoring and Recovering an Entire Database

When the RAC 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). Make sure to bring all the RAC instances offline except on the client configured in CommCell when you restore an entire database.

To the Same Host

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 | <RAC Client>
  2. Right-click the <Instance>, point to All Tasks and then click Browse and Restore.
  1. Select  Latest Backup and click View Content.
  2. Select all the databases and click Recover All Selected.
  3. On the Restore Options dialog box, navigate to the General tab.
    • Verify that the Restore Data and Recover check boxes are selected.
    • Select the Restore Control File check box.
  4. On the Restore Options dialog box, navigate to the Stream tab.
    1. In the Streams column, specify the number of streams for each RAC instance.
    2. Click Advanced.
  5. On the Advanced Restore Options dialog box, navigate to the Options tab.
    1. Select the Switch Database Mode for Restore check box.
    2. Select the Set DBID check box.
  6. On the Advanced Restore Options dialog box, navigate to the Ctrl &SP Files tab, in the Restore Control File section, select the Restore From check box.
  7. Click OK to close the  Advanced Restore Options dialog box.
  8. Click OK to close the  Restore Options dialog box.

To a New Host with the Same Directory Structure

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

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

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

Prerequisites

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

Setting Up the Source and Destination Hosts

  1. Create a new user account with recovery catalog owner permission within the Recovery Catalog for the destination computer. Use a different <username>

    Example:

    SQL>create user <username> identified by <password>
    2>temporary tablespace <temp_tablespace_name>
    3>default tablespace <default_tablespace_name>
    4>quota unlimited on <default_tablespace_name>;
    Statement processed.
    SQL>grant connect, resource, recovery_catalog_owner to <username>;
    Statement processed.

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

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

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

    Example using IMPORT CATALOG Command::

    RMAN>IMPORT CATALOG user1/user1@src;

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

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

    Example::
    For UNIX:
    #export ORACLE_SID= <target database SID>
    #export ORACLE_HOME= <Oracle home directory>

    For Windows:
    C:\set ORACLE_SID= <target database SID>
    C:\set ORACLE_HOME= <Oracle home directory>

  1. Create the Oracle RAC client and configure it as a client in the same CommServe in which the source machine resides.
  1. Create and configure a new Oracle instance in the RAC Client on the destination computer, similar to the one existing in the source computer. Ensure that this instance is in NOMOUNT mode.

Restoring the Database

  1. From the CommCell Browser, navigate to Client Computers | <RAC Client>
  2. Right-click the <Instance>, point to All Tasks and then click Browse and Restore.
  1. Select  Latest Backup and click View Content.
  2. Select all the databases and click Recover All Selected.
  3. On the Restore Options dialog box, navigate to the General tab.
    • Select the Destination Client.
    • Verify that the Restore Data and Recover check boxes are selected.
    • Select the Restore Control File check box.
  4. On the Stream tab of the Restore Options for Client dialog box:
    1. Specify the number of streams to use for each Oracle RAC instance in the Stream column.
    2. Click Advanced.
  5. On the Advanced Restore Options dialog box, navigate to the Options tab.
    • If the database is in NOARCHIVELOG mode, then select No Redo Logs.
  6. Click OK.

To a New Host with a Different Directory Structure

If the shared computer on which you hosted a RAC database is damaged or destroyed, you can restore and recover the lost database on a new standalone host computer with a different directory structure. You can restore a database either in ARCHIVELOG or NOARCHIVELOG mode on a new host.

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

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

Prerequisites

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

Configuring the Init <SID>.ora File

  1. Copy the init<SID>.ora from the old host to the new host.
  2. Edit the init<SID>.ora file on the new host to reflect all the directory structure changes (change the path for control files, archivelog destination and *dump destinations).
  3. Create the directory structures as defined in init<SID>.ora file for all paths.

Setting Up the Source and Destination Hosts

  1. Create a new user account with recovery catalog owner permission within the Recovery Catalog for the destination computer. Use a different <username>

    Example:

    SQL>create user <username> identified by <password>

    2>temporary tablespace <temp_tablespace_name>

    3>default tablespace <default_tablespace_name>

    4>quota unlimited on <default_tablespace_name>;

    Statement processed.

    SQL>grant connect, resource, recovery_catalog_owner to <username>;

    Statement processed.

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

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

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

    Example using IMPORT CATALOG Command:

    RMAN>IMPORT CATALOG user1/user1@src;

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

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

    Example:

    For UNIX:

    #export ORACLE_SID= <target database SID>

    #export ORACLE_HOME= <Oracle home directory>

     

    For Windows:

    C:\set ORACLE_SID= <target database SID>

    C:\set ORACLE_HOME= <Oracle home directory>

  1. Create the Oracle RAC client and configure it as a client in the same CommServe in which the source machine resides.
  1. Create and configure a new Oracle instance in the RAC Client on the destination computer, similar to the one existing in the source computer. Ensure that this instance is in NOMOUNT mode.

Restoring the Database

  1. From the CommCell Browser, navigate to Client Computers | <RAC Client>
  2. Right-click the <Instance>, point to All Tasks and then click Browse and Restore.
  1. Select  Latest Backup and click View Content.
  2. Select all the databases and click Recover All Selected.
  3. On the Restore Options dialog box, navigate to the General tab.
    • Select the Destination Client.
    • Verify that the Restore Data and Recover check boxes are selected.
    • Select the Restore Control File check box.
  4. On the Stream tab of the Restore Options for Client dialog box:
    1. Specify the number of streams to use for each Oracle RAC instance in the Stream column.
    2. Click Advanced.
  5. On the Advanced Restore Options dialog box, navigate to the Options tab.
    • If the database is in NOARCHIVELOG mode, then select No Redo Logs.
  6. Click OK.

To a Previous Point-in-Time

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

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

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

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

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

  1. From the CommCell Browser, navigate to Client Computers | <RAC Client>
  2. Right-click the <Instance>, point to All Tasks and then click Browse and Restore.
  1. Select  Latest Backup and click View Content.
  2. Select all the databases and click Recover All Selected.
  3. On the Restore Options dialog box, navigate to the General tab, select the Restore Control File check box to restore the control files.
  4. On the Stream tab of the Restore Options for Client dialog box:
    1. Specify the number of streams to use for each Oracle RAC instance in the Stream column.
    2. Click Advanced.
  5. On the Advanced Restore Options dialog box, navigate to the Restore tab.
    • Select the To Point-in-Time  option and enter the data and time.
  6. On the Advanced Restore Options dialog box, navigate to the Recover tab.
    • Select the To Point-in-Time  option and enter the data and time.
  7. On the Advanced Restore Options dialog box, navigate to the Ctrl&SP Files tab, when you selected that option.
    • Select the To Point-in-Time  option and enter 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.

  8. On the Advanced Restore Options dialog box, navigate to the Options tab.
    • 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.
    • Click OK.
  9. Click OK.

Using RMAN Backup Tag

If you have assigned unique identification tags (RMAN backup tags) for the data, you can restore and recover an entire database from a specific backup using the tags.

Use the following steps to restore the database with specific identification tags:

  1. From the CommCell Browser, navigate to Client Computers | <RAC Client>
  2. Right-click the <Instance>, point to All Tasks and then click Browse and Restore.
  1. Select  Latest Backup and click View Content.
  2. Select all the databases and click Recover All Selected.
  3. On the Restore Options dialog box, navigate to the General tab, select the Restore Control File check box to restore the control files.
  4. On the Stream tab of the Restore Options for Client dialog box:
    1. Specify the number of streams to use for each Oracle RAC instance in the Stream column.
    2. Click Advanced.
  5. On the Advanced Restore Options dialog box, navigate to the Restore tab.
    • By Tag  and type the Tag name that is assigned for a specific data backup that you want to restore.
    • Click OK.
  6. Click OK.

Restoring Individual Datafiles and Tablespaces to the Same Location

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.

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 RAC.
  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. 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.
  7. On the Stream tab, specify the number of streams to use for each Oracle RAC instance in the Stream column.
  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 Redo Logs, RMAN restores the data from the incremental backup and not the archived redo logs.

    On the Options tab, select the No Redo 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 Redo 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.

    For more information on modifying the copy precedence of a storage policy copy, see Copy Precedence.

    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.

Redirecting to a New Location

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.

Before You Begin

  1. Perform a full backup with a subclient configured for Oracle datafiles and tablespaces.
  2. When you do not want to update the control file with the restore, follow Disabling the Oracle Datafile Switch.

Procedure

  1. From the CommCell Browser, expand Client Computers > client > Oracle RAC
  2. .
  3. Right-click the instance, point to All Tasks and then click Browse and Restore.
  4. On the Browse and Restore dialog box, select Latest Backup and click View Content.
  5. From the Browse window, select the data to restore in the right pane and click Recover All Selected.
  6. On the Restore Options dialog box click Advanced.
  7. On the Redirect tab of the Restore Options dialog box:
    1. Select the Redirect check box.
    2. Select each object and type the new path in New Path box. Repeat for all objects you want to change. To confirm the new path, click Apply.
    3. Select the tablespaces to redirect.

      To redirect all the objects displayed in the Object column to a new location, select the Redirect All Table Spaces.

      To select individual tablespaces, click the New Path column associated with the tablespace type the path in the New Path box.

      To redirect multiple tablespaces, click Find & Replace, and enter the new path in the New Path box.

  8. Move the database to the correct mode prior to the restore. On the Options tab of the Advanced Restore Options dialog box, select the Switch Database Mode for Restore check box.
  9. 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.
  10. On the Stream tab, specify the number of streams to use for each Oracle RAC instance in the Stream column.
  11. 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 Redo Logs, RMAN restores the data from the incremental backup and not the archived redo logs.

    On the Options tab, select the No Redo 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 Redo 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.

    For more information on modifying the copy precedence of a storage policy copy, see Copy Precedence.

    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.

  12. Click OK to close the Advanced Restore Options dialog box.
  13. Click OK to close the Restore Options dialog box and start the restore.

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

Restoring Archive Logs

You can restore archive logs separately or in addition to the database.

Restore an archive log when you are restoring any of the following data items:

  • A database to the most recent state after a database failure.
  • Specific logs which are identified using a serial number or identification tag, that are missing in the database.
  • Logs from a specific time range that were lost due to a hard disk corruption. You can use a point-in-time option, to restore the archive logs.

Before You Begin

  1. Perform an Oracle RAC Log Backup.

Procedure

  1. From the CommCell Browser, expand Client Computers > client > Oracle RAC.
  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. Optional: Use non-default Browse and Restore options. See Browse and Restore.
  5. From the Browse window, select the data to restore in the right pane and click Recover All Selected.
  6. On the Restore Options dialog box:
    1. Select the Restore Archive Log check box.
    2. To restore the log files without the database, clear the Restore Data check box.
    3. On the Stream tab, specify the number of streams to use for each Oracle RAC instance in the Stream column.
    4. Click Advanced.

      The Advanced Restore Options dialog box appears.

  7. On the Restore tab, select the restore log option.
    Expand All

    Restore all logs

    Select the All option

    Restore logs by a specific log time

    Select By Log Time and enter the Start and End time in the boxes.

    If you only specify the start log time and not the end log time, the system restores all logs from the start time to the current time.

    If the restore includes the database, see Restoring to a Point-in-Time to restore the database to a specific point-in-time.

    Restore by specifying a tag

    Select the By Tag check box and type the tag in the By Tag box.

    Restore by specifying a serial number

    Select the By Log Serial Number option.

    Check the Start or End check boxes and enter the serial numbers.

    The following are the rules for specifying the serial number.

    • The end serial number must be greater than or equal to the start serial number
    • The start and the end serial number cannot be 0
    • The range of serial numbers restore can be from one or more backup jobs or from a part of a job and from one or more cycles
    • When you specify only the start sequence number, logs starting from that sequence number to the current sequence number are restored
  8. To restore logs to a different location from the original location, enter the new path in the Target Directory box.
  9. 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.
  10. 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 Redo Logs, RMAN restores the data from the incremental backup and not the archived redo logs.

    On the Options tab, select the No Redo 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 Redo 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.

    For more information on modifying the copy precedence of a storage policy copy, see Copy Precedence.

    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.

  11. Click OK to close the Advanced Restore Options dialog box.
  12. Click OK to close the Restore Options dialog box and start the restore.

Restoring Control and SP Files

Control and SP files are required to recover a database to the current state. Restoring a control/sp file is useful in the following scenarios:

  • If you want to restore the backup repository contained in the control file when the Control file is lost.
  • If the recovery catalog is lost.
  • If the recovery catalog was never used.
  • If the catalog connect string is not specified for the instance during the backup.

Place the database in NOMOUNT mode when you restore the control/sp files.

Note: The database remains in NOMOUNT mode after the restore.

The SnapProtect software uses OS authentication (/) and not the connect string for control and sp file restores. You can use the connect string in place of OS authentication. For more information see Using the Connect String Instead of OS Authentication to Connect to the Oracle RAC Database.

When you restore control files, be sure to select only one node for the restore. During control file restores, Oracle puts the database in a state where other processes may not be able to access the database. Therefore, if you select more than one node, the job may fail if the database is inaccessible by all the nodes. Make sure to bring all the RAC instances offline except on the client configured in CommCell when you restore a Control/SP file.

From the Latest Backup

By default, the Control/SP files are restored from the latest backup. Use the following steps to restore a Control/SP file from a latest backup:

  1. From the CommCell Browser, navigate to Client Computers | <RAC Client>
  2. Right-click the <Instance>, point to All Tasks and then click Browse and Restore.
  3. Select Latest Backup and click View Content.
  4. Select all the databases and click Recover All Selected.
  5. On the Restore Options dialog box, navigate to the General tab.
    • Select the Restore Control File check box.
    • Select the Restore SP File check box
  6. On the Stream tab of the Restore Options for Client dialog box, specify the number of streams to use for each Oracle RAC instance in the Stream column.
  7. Click OK.

From a Specific Backup

If the control file and recovery catalog are lost, you can restore the control file from a specific backup piece using a backup piece number. (Backup piece references the backup of one or several database files)

You can obtain the backup piece value from the RMAN logs of the backup job. Use the following steps to restore a control/sp file from a specific backup:

  1. From the CommCell Browser, navigate to Client Computers | <RAC Client>
  2. Right-click the <Instance>, point to All Tasks and then click Browse and Restore.
  3. Select Latest Backup and click View Content.
  4. Select all the databases and click Recover All Selected.
  5. On the Restore Options dialog box, navigate to the General tab.
    • Select the Restore Control File check box.
    • Select the Restore SP File check box.
  6. On the Stream tab of the Restore Options for Client dialog box:
    1. Specify the number of streams to use for each Oracle RAC instance in the Stream column.
    2. Click Advanced.
  7. On the Advanced Restore Options dialog box, navigate to the Ctrl &SP Files tab.
    • Select the Restore Control File check box.
    • Select the Restore From check box.
    • Select the From backup piece option and enter the backup piece.
    • Click OK.
  8. Click OK.

From a Copy of the Control File

If your database consists of multiple copies of control files, you can replace a corrupted control file by manually copying from an existing control file and restoring it.

Follow the steps given below to restore a control file from an existing control files:

  1. Shutdown the database.

    SQL> shutdown

  2. Manually copy one of the existing control files to the missing control file location.
  3. Assign the same owner, group and file permissions to the new control file as that of the original missing control file.
  4. Startup the database.

    SQL> startup nomount;

To a Point-in-Time

If you are certain that the control file was corrupted, lost at or after a specific time, you can restore the control file to such a point-in-time.

Follow the steps given below to restore a control/sp file to a point-in-time:

  1. From the CommCell Browser, navigate to Client Computers | <RAC Client>
  2. Right-click the <Instance>, point to All Tasks and then click Browse and Restore.
  3. Select Latest Backup and click View Content.
  4. Select all the databases and click Recover All Selected.
  5. On the Restore Options dialog box, navigate to the General tab.
    • Select the Restore Control File check box.
    • Select the Restore SP File check box.
  6. On the Stream tab of the Restore Options for Client dialog box:
    1. Specify the number of streams to use for each Oracle RAC instance in the Stream column.
    2. Click Advanced.
  7. On the Advanced Restore Options dialog box, navigate to the Ctrl &SP Files tab.
    • Select the Restore Control File check box.
    • Select the To Point-in-Time check box and enter the start and end time.
    • Select the Restore SP File check box.
    • Select the To Point-in-Time check box and enter the start and end time.
  8. On the Advanced Restore Options dialog box, navigate to the Options tab.
    • 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.
    • Click OK.
  9. Click OK.

To a New Location

By default, the Control file/SP File is restored to the original location. Use the following steps to restore the control files to a new location:

  1. From the CommCell Browser, navigate to Client Computers | <RAC Client>
  2. Right-click the <Instance>, point to All Tasks and then click Browse and Restore.
  3. Select Latest Backup and click View Content.
  4. Select all the databases and click Recover All Selected.
  5. On the Restore Options dialog box, navigate to the General tab.
    • Select the Restore Control File check box.
    • Select the Restore SP File check box.
  6. On the Stream tab of the Restore Options for Client dialog box:
    1. Specify the number of streams to use for each Oracle RAC instance in the Stream column.
    2. Click Advanced.
  7. On the Advanced Restore Options dialog box, navigate to the Ctrl &SP Files tab.
    • Select the Restore Control File as check box.
    • Type the path or click Browse to specify the new location to restore the control file.
    • Select the Restore SP File as check box.
    • Type the path or click Browse to specify the new location to restore the control file.
    • Click OK.
  8. Click OK.

Recovering a Database

You can recover the database to a point other than the current time when the current database is inconsistent.

Procedure

  1. From the CommCell Browser, expand Client Computers > RAC client .
  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 to restore in the right pane, and click Recover All Selected.
  6. On the Restore Options dialog box, clear the Restore Data check box and click the Advanced button.
  7. On the Recover tab of the Advanced Restore Options dialog box, select the database recover option:
    Choice Description
    Current Time Recover to the current time
    Point-in-Time Enter the date and time.

    Note: If the time zone is different on the CommServe computer and client, in the Time Zone box, select the client computer time zone.

    SCN The System Change Number (SCN) tracks the timing of transactions in the Oracle database. The SCNs 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, which is the last consistent database state.
    Latest Backup Time Recover to the latest backup job's completion time, which gets passed to the recover operation.

    This value is the Completion Time on the General Tab of the Job Details dialog box. To view the value, right-click the job, and then select View Job Details. For instructions, see Job Controller - Getting Started.

    Latest SCN Number Recover to the latest SCN.

    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. To view the value, right-click the job and then select View Job Details. For instructions, see Job Controller - Getting Started.

    Relative to System Date Recover to the number of days or hours relative to the current system date. The default option is to recover relative to the days,.

    If you select the Days option, the valid values are 0-7.

    If you select the Hours option, the valid values are 0-23.

  8. Click OK to close the Advanced Restore Options dialog box.
  9. Optional: View or customize the RMAN script that is generated from the selected options. See Viewing Oracle Restore RMAN Scripts and Customizing Oracle Restore RMAN Scripts.
  10. Click OK to close the Restore Options dialog box and start the restore.

Restoring Container and Pluggable Databases

Oracle 12c supports container and pluggable databases. SnapProtect supports the restore of container and pluggable databases.

If you have backed up an entire container database you can restore the entire container database, a single pluggable database, or multiple pluggable databases.

Restoring a Container Database

Container databases can be restored like any full database. See Restoring and Recovering an Entire Database.

Once the restore is done, manually open all the PDBs from the sql command line.

Sql> alter pluggable database <PDB_NAME1>, <PDB_NAME2> open;

Restoring Pluggable Databases from a Container Backup

  1. Before running the restore, enter the following on the command line:

     Sql> alter pluggable database <PDB_NAME> close;

  2. Create and customize an RMAN script file on the client computer, where the last line in the script specifies the pluggable databases to restore. The line has the following format, with "pluggable_database_name1" through "pluggable_databaseN". Each database must be separated by a "," and must be part of the backup.

restore pluggable database pluggable_database_name1, ..pluggable_database_nameN;

Example: RMAN script restoring the pluggable database "SINGLE_PDB".

run
{
    restore pluggable database SINGLE_PDB ;
}
exit;

  1. Execute the RMAN script.  See Running RMAN Scripts from Third Party Command Line.
  2. Once the restore is done, manually open the PDB from the sql command line.

    Sql> alter pluggable database SINGLE_PDB open;

Restoring Pluggable Databases from a Pluggable Backup

  1. Before running the restore, enter the following on the command line:

 Sql> alter pluggable database <PDB_NAME> close;

  1. Create and customize an RMAN script file on the client computer where the last line in the script specifies the pluggable database to restore. The line has the following format, with "pluggable_database_name1" through "pluggable_databaseN". Each database must be separated by a "," and must be part of the backup.

    restore pluggable database pluggable_database_name1, ..pluggable_database_nameN;

    recover pluggable database pluggable_database_name1, ..pluggable_database_nameN;

       Example: RMAN script backing up the pluggable databases "PLUG_DB1" and "PLUG_DB2".

run
{
    restore pluggable database PLUG_DB1, PLUG_DB2;
    recover pluggable database PLUG_DB1, PLUG_DB2;
}
exit;

  1. Execute the RMAN script.  See Running RMAN Scripts from Third Party Command Line.
  2. Once the restore is done, manually open all the PDBs from the sql command line.

    Sql> alter pluggable database PLUG_DB1, PLUG_DB2 open;

Creating a Duplicate Database

A duplicate (auxiliary) database is a copy or 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.

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

  1. On Windows clients, restart Oracle services.

    Skip this step, if you are using an 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.
  1. 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)

    )

    )

  1. Restart the Listener.

    $ lsnrctl reload

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

    Example:

    sys/sys@<SID name>

  1. Startup the duplicate database instance in NOMOUNT mode.
  2. From the CommCell Browser, navigate to Client Computers | <RAC Client>
  3. Right-click the <Instance>, point to All Tasks and then click Browse and Restore.
  4. Select  Latest Backup and click View Content.
  5. Select all the databases and click Recover All Selected.
  6. On the Restore Options dialog box, navigate to the General tab, select the Duplicate DB check box.
  7. On the Stream tab of the Restore Options for Client dialog box:
    1. Specify the number of streams to use for each Oracle RAC instance in the Stream column.
    2. Click Advanced.
  8. On the Advanced Restore Options dialog box, navigate to the Duplicate tab.
    • Select the Duplicate To check box.
    • Type the name of duplicate database in Database Name box
    • Click OK.
  9. On the Restore Options dialog box, navigate to the General tab.
    • Select the name of the client computer from the Destination Client list.
    • Click Advanced.
  10. On the Advanced Restore Options dialog box, navigate to the Duplicate tab.
    • Type the name of startup Parameter file in Pfile box or click Browse to locate it.
    • Click OK.
  11. On the Restore Options dialog box, navigate to the General tab.
    • Under The latest Database View box, click Refresh to verify that the status of the duplicate database is STARTED.
  12. Click OK.

On a Different Host without an 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.
  1. Create a duplicate database instance on the destination host.
  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.)

  1. On Windows clients, restart Oracle services.

    Skip this step, if you are using an 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.
  1. 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)

    )

    )

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

    Example:

    sys/sys@<SID name>

  4. Startup the duplicate database instance in NOMOUNT mode.
  5.  When using a different host without configuring an instance, the install path in the source and destination clients must be the same. For information on how to set the additional setting, see Setting the sNOSBTLIBNAME Additional Setting to Skip Passing SBT_LIBRARY to the Allocate Channel Command.
  6. Run the Ora_install.sh on the auxiliary client.
  7. From the CommCell Browser, navigate to Client Computers | <RAC Client>
  8. Right-click the <Instance>, point to All Tasks and then click Browse and Restore.
  9. Select  Latest Backup and click View Content.
  10. Select all the databases and click Recover All Selected.
  11. On the Restore Options dialog box, navigate to the General tab.
    • Select the Duplicate DB check box.
    • Select the name of the client computer from the Destination Client list.
    • Under The latest Database View box, click Refresh to verify that the status of the duplicate database is STARTED.
  12. On the Stream tab of the Restore Options for Client dialog box:
    1. Specify the number of streams to use for each Oracle RAC instance in the Stream column.
    2. Click Advanced.
  13. On the Advanced Restore Options dialog box, navigate to the Duplicate tab.
    • Select the Duplicate To check box.
    • Type the name of duplicate database in Database Name box.
    • Type the name of startup Parameter file in Pfile box or click Browse to locate it.
    • Click OK.
  14. 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.)

  1. On Windows clients, restart Oracle services.

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

  1. Add the duplicate database instance name in the Listener.ora file and Tnsnames.ora files.
  1. 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)

    )

    )

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

    Example:

    sys/sys@<SID name>

  1. Startup the duplicate database instance in NOMOUNT mode.
  2. Right-click the <Instance>, point to All Tasks and then click Browse and Restore.
  3. Select  Latest Backup and click View Content.
  4. Select all the databases and click Recover All Selected.
  5. On the Restore Options dialog box, navigate to the General tab.
    • Select the Duplicate DB check box.
    • Under The latest Database View box, click Refresh to verify that the status of the duplicate database is STARTED.
  6. On the Stream tab of the Restore Options for Client dialog box:
    1. Specify the number of streams to use for each Oracle RAC instance in the Stream column.
    2. Click Advanced.
  7. On the Advanced Restore Options dialog box, navigate to the Duplicate tab.
    • Select the Duplicate To check box.
    • Type the name of duplicate database in Database Name box.
    • Type the name of startup Parameter file in Pfile box or click Browse to locate it.
    • Click OK.
  8. 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.)

  1. On Windows clients, restart Oracle services.

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

  1. Add the duplicate database instance name in the Listener.ora file and Tnsnames.ora files.
  1. 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)

    )

    )

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

    Example:

    sys/sys@<SID name>

  1. Startup the duplicate database instance in NOMOUNT mode.
  1. Right-click the <Instance>, point to All Tasks and then click Browse and Restore.
  2. Select  Latest Backup and click View Content.
  3. Select all the databases and click Recover All Selected.
  4. On the Restore Options dialog box, navigate to the General tab.
    • Select the Duplicate DB check box.
    • Under The latest Database View box, click Refresh to verify that the status of the duplicate database is STARTED.
  5. On the Stream tab of the Restore Options for Client dialog box:
    1. Specify the number of streams to use for each Oracle RAC instance in the Stream column.
    2. Click Advanced.
  6. On the Advanced Restore Options dialog box, navigate to the Duplicate tab.
    • Select the Duplicate To check box.
    • Type the name of duplicate database in Database Name box.
    • Type the name of startup Parameter file in Pfile box or click Browse to locate it.
    • Click OK.
  7. 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. Right-click the <Instance>, point to All Tasks and then click Browse and Restore.
  2. Select  Latest Backup and click View Content.
  3. Select all the databases and click Recover All Selected.
  4. On the Restore Options dialog box, navigate to the General tab.
    • Select the name of the client computer from the Destination Client list.
    • Select the Duplicate DB check box.
  5. On the Stream tab of the Restore Options for Client dialog box:
    1. Specify the number of streams to use for each Oracle RAC instance in the Stream column.
    2. Click Advanced.
  6. On the Advanced Restore Options dialog box, navigate to the Duplicate tab.
    • Select the Duplicate To check box.
    • Type the name of duplicate database in Database Name box.
    • Type the name of startup Parameter file in Pfile box or click Browse to locate it.
    • Select Duplicate To Skip Read Only check box.
    • Click OK.
  7. 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. Right-click the <Instance>, point to All Tasks and then click Browse and Restore.
  2. Select  Latest Backup and click View Content.
  3. Select all the databases and click Recover All Selected.
  4. On the Restore Options dialog box, navigate to the General tab.
    • Select the name of the client computer from the Destination Client list.
    • Select the Duplicate DB check box.
  5. On the Stream tab of the Restore Options for Client dialog box:
    1. Specify the number of streams to use for each Oracle RAC instance in the Stream column.
    2. Click Advanced.
  6. On the Advanced Restore Options dialog box, navigate to the Duplicate tab.
    • Select the Duplicate To check box.
    • Type the name of duplicate database in Database Name box.
    • Type the name of startup Parameter file in Pfile box or click Browse to locate it.
    • Select Duplicate To Open Restricted check box.
    • Click OK.
  7. 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. Right-click the <Instance>, point to All Tasks and then click Browse and Restore.
  2. Select  Latest Backup and click View Content.
  3. Select all the databases and click Recover All Selected.
  4. On the Restore Options dialog box, navigate to the General tab.
    • Select the name of the client computer from the Destination Client list.
    • Select the Duplicate DB check box.
    • Click Advanced.
  5. On the Advanced Restore Options dialog box, navigate to the Duplicate tab.
    • Select the Duplicate To check box.
    • Type the name of duplicate database in Database Name box.
    • Type the name of startup Parameter file in Pfile box or click Browse to locate it.
    • Select the Duplicate To Skip TableSpaces check box.
    • Click Add
    • Select the tablespaces that appear in the TableSpaces box to exclude from the duplicate database.
    • Click OK.
  6. 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. Right-click the <Instance>, point to All Tasks and then click Browse and Restore.
  2. Select  Latest Backup and click View Content.
  3. Select all the databases and click Recover All Selected.
  4. On the Restore Options dialog box, navigate to the General tab.
    • Select the name of the client computer from the Destination Client list.
    • Select the Duplicate DB check box.
  5. On the Stream tab of the Restore Options for Client dialog box:
    1. Specify the number of streams to use for each Oracle RAC instance in the Stream column.
    2. Click Advanced.
  6. On the Advanced Restore Options dialog box, navigate to the Duplicate tab.
    • Select the Duplicate To check box.
    • Type the name of duplicate database in Database Name box.
    • Type the name of startup Parameter file in Pfile box or click Browse to locate it.
    • Select the Duplicate To Log File check box.
    • Select the File option.
    • Click Add to include the specifications for an online redo log file
    • In the Spec Dialog for Oracle Redo Log File box, type the name or click Browse to select the redo log file.  Enter the Size and select the Reuse check box. Click OK.
    • Click OK.
  7. 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. Right-click the <Instance>, point to All Tasks and then click Browse and Restore.
  2. Select  Latest Backup and click View Content.
  3. Select all the databases and click Recover All Selected.
  4. On the Restore Options dialog box, navigate to the General tab.
    • Select the name of the client computer from the Destination Client list.
    • Select the Duplicate DB check box.
  5. On the Stream tab of the Restore Options for Client dialog box:
    1. Specify the number of streams to use for each Oracle RAC instance in the Stream column.
    2. Click Advanced.
  6. On the Advanced Restore Options dialog box, navigate to the Duplicate tab.
    • Select the Duplicate To check box.
    • Type the name of duplicate database in Database Name box.
    • Type the name of startup Parameter file in Pfile box or click Browse to locate it.
    • Select the Duplicate To Log File check box.
    • Select the Group option.
    • Click Add to include the specifications for an online redo log file
    • In the Spec Dialog for Oracle Redo Log File box, type the name or click Browse to select the redo log file.  Enter the Size and select the Size Specifications from SizeSpec list.. Click OK.
    • Click OK.
  7. Click OK.

Disabling File Name Validation during a Restore

By default, when you create a duplicate 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. Right-click the <Instance>, point to All Tasks and then click Browse and Restore.
  2. Select Latest Backup and click View Content.
  3. Select the database and click Recover All Selected.
  4. On the Restore Options dialog box, navigate to the General tab.
    • Type the connect string name in the Catalog String box.
    • Select the Duplicate DB check box.
  5. On the Stream tab of the Restore Options for Client dialog box:
    1. Specify the number of streams to use for each Oracle RAC instance in the Stream column.
    2. Click Advanced.
  6. On the Advanced Restore Options dialog box, navigate to the Duplicate DB Options tab.
    • Select the No FileName Check check box.
    • Click OK.
  7. Click OK.

Creating a Standby Database

Standby databases are useful when a primary database experiences a disaster such as hardware related failure or data corruption and it is not configured for a cluster failover. A standby database is a replicated copy of the primary database. It is updated by applying archived redo logs from the primary database. A standby database will not have a unique DBID.

On a Different Host without the Instance Configured

Use the following steps to create a standby database on a different host without the configured instance:

Setting Up a Standby database

  1. Perform an online full backup of the primary database with current control file.
  2. Set the following initialization parameters in init<standbydb>.ora (Startup PFile) on source (primary) host.

    LOG_ARCHIVE_DEST_1='LOCATION=

    C:\Oracle\Oradata\TSH1\Archive MANDATORY REOPEN=30'

    LOG_ARCHIVE_DEST_2='SERVICE=stby1 LGWR SYNC AFFIRM'

  3. Create an initialization parameter file, init<standbydb>.ora for the standby database and set the following initialization parameters on the standby host:

    *.log_archive_dest_1='LOCATION=/ LOCATION_OF_DESTINATION_DB_ARCHIVELOG /arch'

       *.STANDBY_ARCHIVE_DEST='/ LOCATION_OF_STANDBY_DB_ARCHIVELOG /stdbyarch'

       *.STANDBY_FILE_MANAGEMENT=auto

         DB_FILE_NAME_CONVERT=('/DATA_FILE_PATH_ON_SOURCE_MACHINE/stdby', '/ORACLE_DATA_FILE_PATH_ON_STANDBY_MACHINE/stdby/')

        LOG_FILE_NAME_CONVERT=('/ DATA_FILE_PATH_ON_SOURCE_MACHINE /stdby', '/ ORACLE_DATA_FILE_PATH_ON_STANDBY_MACHINE /stdby/')

  4. Configure the listner.ora and $TNS_ADMIN/tnsnames.ora files on the destination computer for the standby database.

    On Source computer:

    <Standbydb1_use_diff_connection_string> =

    (DESCRIPTION =

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

    (CONNECT_DATA =

    (SERVER = DEDICATED)

    (SERVICE_NAME = <standbydb_use_same_db_name_as_primary>)

    )

    )

    <Standbydb_primary> =

    (DESCRIPTION =

    (ADDRESS = (PROTOCOL = TCP)

    (HOST = primary_host_name)(PORT = 1521))

    (CONNECT_DATA =

    (SERVER = DEDICATED)

    (SERVICE_NAME =

    <standbydb_same_as_destination><)

    )

    )

    On Standby Computer:

    <standbydb1_destination_connection_string> =

    (DESCRIPTION =

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

    (CONNECT_DATA =

    (SERVER = DEDICATED)

    (SERVICE_NAME = <standbydb_destination_db_name_same_as_primary>)

    (UR = A)

    )

    )

    <standbydb_primary_connection> =

    (DESCRIPTION =

    (ADDRESS = (PROTOCOL = TCP)

    (HOST = primary_host_name)(PORT = 1521))

    (CONNECT_DATA =

    (SERVER = DEDICATED)

    (SERVICE_NAME = <standbydb_primary_db>)

    )

    )

  5. Use a connect string to connect to the auxiliary database when the instance is not configured.

    While creating password file for standby database on destination host, make sure to use the change_on_install password file for auxiliary channel.

  6. Startup the standby database instance in NOMOUNT mode.

    When using a different host without configuring an instance, the install path in the source and destination clients must be the same.

    1. Run the Ora_install.sh on the auxiliary client.
    2. Create the Oracle RAC client and configure it as a client on the Destination host.
    3. Set the Standby Role Initialization parameter, DB_FILE_NAME_CONVERT,to add all the temp datafiles from the primary database location to the standby database location.

      DB_FILE_NAME_CONVERT=

      '<primary_database_temp_datafile_old _location>',

      '<standby_database_temp_datafile_new_location>'

    Creating a Standby Database

    1. Right-click the <Instance> point to All Tasks and then click Browse and Restore.
    2. Select  Latest Backup and click View Content.
    3. Select the database and Click Recover All Selected.
    4. Type the connect string name in the Catalog String box.
    5. Select Duplicate DB check box.
    6. On the Stream tab of the Restore Options for Client dialog box:
      1. Specify the number of streams to use for each Oracle RAC instance in the Stream column.
      2. Click Advanced.
    7. Click Duplicate DB Options tab.
    8. Click Duplicate For Standby.
    9. Type the Oracle <SID> name in Oracle SID box.
    10. Click OK.
    11. Once the job is completed, the new database will be on MOUNT mode for the standby database. You must enable the log shipping to maintain the standby database up-to-date.

      Alter database recover managed standby database disconnect;

    On a Different Host with the Instance Configured

    Use the following steps to create a standby database on a different host with the configured instance:

    Setting up a Standby Database:
    1. Perform an online full backup with current control file.
    2. Set the following initialization parameters in the primary initialization parameter file init<standbydb>.ora (Startup PFile) on source (primary) host.

      LOG_ARCHIVE_DEST_1='LOCATION=C:\Oracle\Oradata\TSH1\Archive MANDATORY REOPEN=30'

      LOG_ARCHIVE_DEST_2='SERVICE=stby1 LGWR SYNC AFFIRM'

    3. Create an initialization parameter file, init<standbydb>.ora for the standby database and set the following initialization parameters on Standby host:

      *.log_archive_dest_1='LOCATION=/ LOCATION_OF_DESTINATION_DB_ARCHIVELOG /arch'

         *.STANDBY_ARCHIVE_DEST='/ LOCATION_OF_STANDBY_DB_ARCHIVELOG /stdbyarch'

         *.STANDBY_FILE_MANAGEMENT=auto

           DB_FILE_NAME_CONVERT=('/DATA_FILE_PATH_ON_SOURCE_MACHINE/stdby', '/ORACLE_DATA_FILE_PATH_ON_STANDBY_MACHINE/stdby/')

          LOG_FILE_NAME_CONVERT=('/ DATA_FILE_PATH_ON_SOURCE_MACHINE /stdby', '/ ORACLE_DATA_FILE_PATH_ON_STANDBY_MACHINE /stdby/')

    4. Perform any Oracle Net setup and configuration required to connect to the standby database.

      For example, set up the listener and configure the destination computer's $TNS_ADMIN/tnsnames.ora file for the standby database.

      On Source computer:

      <Standbydb1_use_diff_connection_string> =

      (DESCRIPTION =

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

      (CONNECT_DATA =

      (SERVER = DEDICATED)

      (SERVICE_NAME = <standbydb_use_same_db_name_as_primary>)

      (UR = A)

      )

      )

      <Standbydb_primary> =

      (DESCRIPTION =

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

      (CONNECT_DATA =

      (SERVER = DEDICATED)

      (SERVICE_NAME = <standbydb_same_as_destination><)

      )

      )

      On standby computer:

      <standbydb1_destination_connection_string> =

      (DESCRIPTION =

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

      (CONNECT_DATA =

      (SERVER = DEDICATED)

      (SERVICE_NAME = <standbydb_destination_db_name_same_as_primary>)

      (UR = A)

      )

      )

      <standbydb_primary_connection> =

      (DESCRIPTION =

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

      (CONNECT_DATA =

      (SERVER = DEDICATED)

      (SERVICE_NAME = <standbydb_primary_db>)

      )

      )

    5. Use a connect string to connect to the auxiliary database when the instance is not configured. Make sure to use the password change_on_install when you create the password file for auxiliary channel while creating password file for standby database on destination host.
    6. Startup the standby database instance in NOMOUNT mode. Configure the Oracle instance for the destination host in the CommCell Browser.
    7. Run the Ora_install.sh on the auxiliary client.
    8. Create the Oracle RAC client and configure it as a client on the Destination host.
    9. Ensure that you set the Standby Role Initialization parameter, DB_FILE_NAME_CONVERT,to add all the temp datafiles from the primary database location to the standby database location.

      DB_FILE_NAME_CONVERT='<primary_database_temp_datafile_old _location>','<standby_database_temp_datafile_new_location>'

    Creating a Standby Database:
    1. Right-click the <Instance>, point to All Tasks and then click Browse and Restore.
    2. Select  Latest Backup and click View Content.
    3. Select the database and click Recover All Selected.
    4. On the Restore Options dialog box, navigate to the General tab.
      • Type the connect string name in the Catalog String box.
      • Select the Duplicate DB check box.
      • Under The latest Database View box, click Refresh to verify that the status of the standby database is STARTED.
    5. On the Stream tab of the Restore Options for Client dialog box:
      1. Specify the number of streams to use for each Oracle RAC instance in the Stream column.
      2. Click Advanced.
    6. On the Advanced Restore Options dialog box, navigate to the Duplicate DB Options tab.
      • Select the Duplicate For Standby check box.
      • Type the Oracle <SID> name in Oracle SID box.
      • Select the Do Recover check box to recover the standby database.
      • Click OK.
    7. Click OK.

Restoring Database Tables

By default, the database tables can be restored from an online full backup, provided the table browse was enabled in the associated subclient before performing the backup. See Enabling Table Browse for Restores for information on configuring the subclient for table browse.

When restoring database tables, by default an auxiliary instance is automatically created. Hence, make sure that there is enough disk space on the client for the auxiliary instance.

Note: The SnapProtect software uses OS authentication (/) and not the connect string for table level restores. You can use the connect string in place of OS authentication. For more information see Using the Connect String Instead of OS Authentication to Connect to the Oracle RAC Database.

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

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 using the following steps:

  1. Right-click the <Instance>, point to All Tasks and then click Browse and Restore.
  2. Select  Latest Backup check the Table View check box and click View Content.
  3. Select  the tables and click Recover All Selected.
  4. On the Table Restore Options dialog box, navigate to the Table Restore tab.
    • In the Staging Path box, type the location where the auxiliary instance will be created.
  5. On the Table Restore Options dialog box, navigate to the Advanced Options tab.
    • Select the Import to Source DB option.
  6. Click OK.

Restoring Tables to a Different Database on the Same Host

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. Right-click the <Instance>, point to All Tasks and then click Browse and Restore.
  3. Select  Latest Backup check the Table View check box and click View Content.
  4. Select  the tables and click Recover All Selected.
  5. On the Table Restore Options dialog box, navigate to the Table Restore tab.
    • In the Staging Path box, type the location where the auxiliary instance will be created.
  6. On the Table Restore Options dialog box, navigate to the Advanced Options tab.
    • Select the Import to a different DB option.
    • In the Enter Import Oracle Instance: box, type the destination instance name.
    • In the Select a Client box, select the source client.
  7. Click OK.

Restoring Tables to a Different Host

When restoring the tables to a different host, ensure the following:

  • Both the source and the destination host should have the same database schema.
  • 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.
  • Add the source database name in the Tnsnames.ora file on the destination host.
  • Ensure that both the source and destination clients use a different connection name in the tnsnames.ora file.

    For example:

    // db1_table = <--- Name of the source database

    db1_table =

    (DESCRIPTION =

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

    (CONNECT_DATA =

    (SERVER = DEDICATED)

    (SERVICE_NAME = db1)

    )

    )

    //db1 = <--- Name of the destination database

    db1 =

    (DESCRIPTION =

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

    (CONNECT_DATA =

    (SERVER = DEDICATED)

    (SERVICE_NAME = db1)

    )

    )

    Use the following steps to restore the tables to a different host:

    1. Add the destination instance name in the Listener.ora and Tnsnames.ora files.
    2. Right-click the <Instance>, point to All Tasks and then click Browse and Restore.
    3. Select  Latest Backup check the Table View check box and click View Content.
    4. Select  the tables  and click Recover All Selected.
    5. On the Table Restore Options dialog box, navigate to the Table Restore tab.
      • In the Staging Path box, type the location where the auxiliary instance will be created.
    6. On the Table Restore Options dialog box, navigate to the Advanced Options tab.
      • Select the Import to a different DB option.
      • In the Enter Import Oracle Instance: box, type the destination instance name.
      • In the Select a Client box, select the destination client.
    7. Click OK.

Restoring Tables Using a User-Defined Auxiliary Instance

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

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

When restoring tables to a different host, if an 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.

Using a User-Defined Auxiliary Instance When the Selected Client Is Not the Source

When the database client selected is one other than the source on Table Restore,  you must select the Auxiliary Instance and provide user a defined Auxiliary  database name. If you do not do this, the Auxiliary database will be created on source client itself and ignore database client provided.

Setting Up the Auxiliary Instance

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

    Windows Clients:
    DB_FILE_NAME_CONVERT=('sourcE_of_df_path/','dup_of_df_path/
    ','source_of_temp_path/','dup_of_temp_path/',...)
    LOG_FILE_NAME_CONVERT=('source_of_log_path/redo','dup_of_log_path/redo')
    UNIX Clients:
    DB_FILE_NAME_CONVERT=(source_of_df_path/,dup_of_df_path/
    ,source_of_temp_path/,dup_of_temp_path/,...)
    LOG_FILE_NAME_CONVERT=(source_of_log_path/redo,dup_of_log_path/redo)

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

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

  7. Restart the Listener.

    $lsnrctl reload

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

    sql> startup nomount;

Restoring the Tables Using the Auxiliary Instance

  1. Right-click the <Instance>, point to All Tasks and then click Browse and Restore.
  2. Select  Latest Backup check the Table View check box and click View Content.
  3. Select  the tables  and click Recover All Selected.
  4. On the Table Restore Options dialog box, navigate to the Table Restore tab.
    • Select the Auxiliary Instance checkbox.
    • In the Database Instance box, type the auxiliary instance name.
    • In the Database Client box, select the destination client for the auxiliary instance.
    • In the PFile box, type the path to the PFile of the auxiliary instance. Alternatively, click Browse to select the path.
    • In the Staging Path box, type the location where the auxiliary instance will be created.
  5. On the Table Restore Options dialog box, navigate to the Advanced Options tab.
    • Select the Import to a different DB option.
    • In the Enter Import Oracle Instance: box, type the destination instance name.
    • In the Select a Client box, select the destination client.
    • Click Advanced.
  6. On the Advanced Table Restore Options dialog box, navigate to the Recover tab.
    • Select the Recover check box.
    • Select Point-in-Time option and specify the time range to which the database need to be recovered.
    • In the Select a Client box, select the destination client.
    • Click OK.
  7. Click OK.

Restoring Tables from an Oracle RAC client to a Non-Oracle RAC Client

You can restore the Oracle RAC tables to a non-Oracle RAC client.

The SnapProtect software creates an auxiliary instance on a source Oracle RAC node. The tables are imported to a non-Oracle RAC client that you specify (Table Restore Options dialog box, Select a Client list)

Before You Begin

  1. Configure Oracle Subclients for Table Level Restores.
  2. Perform a full backup of the subclient.
  3. Verify the following configuration:
    • The source and destination hosts have the same schema
    • The source and destination clients use a different connection name in the tnsnames.ora file
    • The database names in the table are included in the files
    Database Name tnsnames.ora on source tnsnames.ora on destination listner.ora on destination
    duplicate database name
    source database name    
    Expand All

    Example

    The following are examples of the tnsnames.ora files for the source and destination clients. The source database name is db1_table and the destination database name is db1.

    Source client tnsnames.ora file

    db1_table =
    (DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = M1)(PORT = 1521))
    (CONNECT_DATA =
    (SERVER = DEDICATED)
    (SERVICE_NAME = db1)
    )
    )

    Destination client tnsnames.ora file

    db1 =
    (DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = M2)(PORT = 1521))
    (CONNECT_DATA =
    (SERVER = DEDICATED)
    (SERVICE_NAME = db1)
    )
    )

Procedure

  1. From the CommCell Browser, expand Client Computers > client > Oracle RAC.
  2. Right-click the instance, point to All Tasks and then select Browse and Restore.
  3. Select the Table View check box and click View Content.
  4. Optional: You can include or exclude any of the following tables in the restore, dependent, referenced and recursively dependent tables.

    Right-click the table, and choose whether to include or exclude dependent or referenced tables.

    Option Description
    Deselect All Dependent Tables Exclude all dependent tables
    Select All Dependent Tables Include all dependent tables
    Deselect All Dependent Tables Exclude all recursive referenced tables
    Select All Dependent Tables Include all recursive referenced tables
    Deselect All Referenced Tables Exclude all referenced tables
    Select All Referenced Tables Include all referenced tables
  5. From the Browse window, select the tables to restore and click Recover All Selected.

    The Table Restore Options dialog box appears.

  6. On the General tab, select the Oracle RAC pseudo client from the Destination Client list.
  7. On the Stream tab, select a physical Oracle RAC node. Click the Stream column and type the number of streams that the SnapProtect  software uses for the restore.
  8. On the Table Restore tab, in the Staging Path box, type the path on the Oracle RAC physical client where the auxiliary instance is created.
  9. On the Advanced Options tab:
    1. Select the Import to a Different DB check box.
    2. In the Select a Client list, select a non-Oracle RAC client.
    3. In the Enter Import Oracle Instance box, type the destination instance name.

      Note: this must be the same as the Oracle RAC client instance.

    4. To delete the existing tables on the destination before the restored tables are imported, select the Drop Table for Import check box.
  10. Optional: Export table procedures and table additional parameters.

    Select the Use additional export parameters check box and type the parameters to export.

    When you restore Oracle tables, you can restore table objects other than triggers, constraints, indexes, and grants.

    Note: Stored procedures are restored from the schema level. If one table within the schema is selected for restore, all the stored procedures for that schema are restored.

    The object export uses the Data Pump Export utility. If your Oracle version does not support the Data Pump Export utility, you cannot include stored procedures when you export tables.

  11. Click OK to close the Table Restore Options dialog box.

Disabling Clean Up of Auxiliary Instance after Restore

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

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

  1. Right-click the <Instance>, point to All Tasks and then click Browse and Restore.
  2. Select  Latest Backup check the Table View check box and click View Content.
  3. Select  the tables  and click Recover All Selected.
  4. On the Table Restore Options dialog box, navigate to the Table Restore tab.
    • Clear the Cleanup Auxiliary checkbox.
  5. 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. Right-click the <Instance>, point to All Tasks and then click Browse and Restore.
  2. Select  Latest Backup check the Table View check box and click View Content.
  3. Select  the tables  and click Recover All Selected.
  4. On the Table Restore Options dialog box, navigate to the Table Restore tab.
    • In the Staging Path box, type the location where the auxiliary instance will be created.
  5. On the Table Restore Options dialog box, navigate to the Advanced Options tab.
    • Select the Include Stored Procedures option.
    • Select the Use additional export parameters checkbox and type the parameters to be exported.
  6. 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. Right-click the <Instance>, point to All Tasks and then click Browse and Restore.
  2. Select  Latest Backup check the Table View check box and click View Content.
  3. Right-click the <table> and click Select All Dependent Tables to exclude all the dependent tables.

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

  4. Click Recover All Selected.
  5. On the Table Restore Options dialog box, navigate to the Table Restore tab.
    • In the Staging Path box, type the location where the auxiliary instance will be created.
  6. 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. Right-click the <Instance>, point to All Tasks and then click Browse and Restore.
  2. Select  Latest Backup check the Table View check box and click View Content.
  3. Right-click the <table> and click Select All Dependent Tables Recursively to exclude all the dependent tables.

    Similarly, click Select All Referenced Tables Recursively to exclude all the referenced tables

  4. Click Recover All Selected.
  5. On the Table Restore Options dialog box, navigate to the Table Restore tab.
    • In the Staging Path box, type the location where the auxiliary instance will be created.
  6. 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. Right-click the <Instance>, point to All Tasks and then click Browse and Restore.
  2. Select  Latest Backup check the Table View check box and click View Content.
  3. Select the tables and click Recover All Selected.
  4. On the Table Restore Options dialog box, navigate to the Table Restore tab.
    • In the Staging Path box, type the location where the auxiliary instance will be created.
  5. On the Table Restore Options dialog box, navigate to the Advanced tab.
    • In the Staging Path box, type the location where the auxiliary instance will be created.
    • Select Import to Source DB option.
    • Select the Drop Table for Import checkbox.
  6. Click OK.

Viewing RMAN Scripts from the CommCell Console

Prior to running a restore operation from the CommCell Console, you can preview the corresponding RMAN script for the restore job. This is useful to determine whether the selected restore options will yield the desired result in the script. You can also manually copy and save the generated RMAN script to your computer and later execute the script from the command line.

  1. From the CommCell Browser, expand Client Computers > client > Oracle RAC.
  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 database, and click Recover All Selected.
  5. On the Restore Options dialog box, click Script Preview.
  6. On the Rman Scrpt for Restore Job dialog box, click OK.
  7. Click OK to close the Restore Options dialog box.

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 the RMAN commands that is not supported by the software.

  1. From the CommCell Browser, expand Client Computers > client > Oracle RAC.
  2. Right-click the subclient and then click Backup.
  3. Click Advanced.
  4. On the Custom Rman Script tab of the Advanced Restore Options dialog box:
  5. Select the Customize script check box.
  6. On the Control File or Database tab, edit the RMAN script and then click OK.
  7. Click OK to close the Advanced Backup Options dialog box.
  8. Click OK to close the Backup Options dialog box.

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, expand Client Computers > client > Oracle RAC.
  2. Right-click the instance, point to All Tasks and then click Browse and Restore.
  3. Click View Content.
  4. From the Browse window, select the data to restore in the right pane and click Recover All Selected.
  5. From the Restore Options dialog box, click Advanced.
  6. On the Customize Rman Script tab of the Restore Options dialog box:
    1. Select the Customize Rman Script check box.
    2. Click the Database tab to view the script for the database restore.
    3. Update the existing custom script by clicking the Update Script button with the selected advanced restore options. A confirmation dialog appears asking you to confirm the updated script. Click Yes.
    4. Click OK to close the Advanced Restore Options dialog box.
  7. Click OK to close the Restore Options dialog box.

Restoring to Disk (App Free Restore)

You can restore a specific backup job or multiple backup jobs at a time directly to a location on a disk using CommCell console without the intervention of the Oracle RAC. This is useful for restoring multiplexed data on the same media. These restores are also useful for troubleshooting network errors. The data from different backup jobs are passed back to the client so that all of the interleaved backup jobs can be restored in parallel. You can restore the data associated with a specific backup job (s) such as full, incremental, archive log, in parallel streams. You can also submit multiple restore jobs from full and incremental backups.

Use the following steps to restore a backup piece on a disk using CommCell console :

  1. From the CommCell Browser, navigate to Client Computers | <RAC Client>
  2. Right-click the <Instance>, point to All Tasks and then click Restore to Disk.
  3. On the Restore to Disk filter dialog box:
    • Select the filters.
    • Click OK.
  4. Select the backup job that you want to restore to a disk. Right click on the job and select Restore to Disk.

    You can select multiple backup jobs at a time and restore them to disk.

  5. On the Restore Options dialog box, navigate to the General tab.
    • Select the Destination client.
    • Click OK.
  6. Type the path or click Browse to specify the location of the disk to restore the application data.
  7. The backup pieces will be restored to the disk location specified in the Restore Options for All Selected Items dialog box.

Recovering the Database after a Restore

You can recover the RAC database after restoring the application data and logs from the disk using the RMAN script through the command line. Make sure to install an Oracle iDataAgent with a Restore only option on the nodes of the RAC and configure the Oracle RAC client  that you are using for recovering the database.

Use the following parameters in the RMAN script for device type SBT_TAPE to recover the RAC database from the backup pieces restored to disk:

  • CV_media : This parameter is used to specify RMAN to use backup pieces on disk for device type sbt_tape.
  • BACKUP_DIR :This parameter is used along with CV_media to specify the directory from which backup pieces can be read.

RMAN Script example:

run {
allocate channel ch1 type 'sbt_tape'
PARMS="ENV=(CV_media=FILE,BACKUP_DIR=C:\RestoreToDisk\783406\Data)";
allocate channel ch2 type 'sbt_tape'
PARMS="ENV=(CV_media=FILE,BACKUP_DIR=C:\RestoreToDisk\783406\Data)";}
restore database;
recover database ;
alter database open resetlogs;
}

Setting the Restore Order for Streams

The Oracle RAC iDataAgent allows you to perform parallel restores across multiple RAC nodes. You can set a requisite number of allocated streams for each node and set the order to perform parallel restores. This will allow you to load-balance your restores across all or selected nodes of your RAC database.

Use the following steps to allocate the streams and set the restore order for each client (node):

  1. From the CommCell Browser, navigate to Client Computers | <RAC Client>
  2. Right-click the <Instance>, point to All Tasks and then click Browse and Restore.
  1. Select  Latest Backup and click View Content.
  2. Select the databases and click Recover All Selected.

    The Restore Options dialog box is displayed.

  3. On the Stream tab.
    • Select the RAC Client (node) for which you want to allocate streams and set the restore order.
    • Double-click the Streams box and type the number of streams.
  4. Click OK.

Restoring RAC One Node

Best Practice: Use the Switch Database Mode for Restore option for restores.

Automatically Switching the Database Mode before a Restore

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

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

  1. From the CommCell Browser, navigate to Client Computers | <RAC Client>
  2. Right-click the <Instance>, point to All Tasks and then click Browse and Restore.
  1. Select  Latest Backup and click View Content.
  2. Select the databases and click Recover All Selected.

    The Restore Options dialog box is displayed.

  3. On the General tab, click Advanced.

    The Advanced Restore Options dialog box is displayed.

  4. On the Options tab.
    • Select the Switch Database Mode for Restore check box.
    • Click OK.
  5. Click OK.

Opening the Database after a Restore

After a restore operation, you need to open the database for recording further transactions.

Use the following steps to open the database:

  1. From the CommCell Browser, navigate to Client Computers | <RAC Client>
  2. Right-click the <Instance>, point to All Tasks and then click Browse and Restore.
  1. Select  Latest Backup and click View Content.
  2. Select the databases and click Recover All Selected.

    The Restore Options dialog box is displayed.

  3. On the General tab, click Advanced.

    The Advanced Restore Options dialog box is displayed.

  4. On the Options tab.
    • Select the Open DB check box.
    • Click OK.
  5. 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 | <RAC Client>
  2. Right-click the <Instance>, point to All Tasks and then click Browse and Restore.
  1. Select  Latest Backup and click View Content.
  2. Select the databases and click Recover All Selected.

    The Restore Options dialog box is displayed.

  3. On the General tab, click Advanced.

    The Advanced Restore Options dialog box is displayed.

  4. On the Options tab:
    • Select the Open DB check box.
    • Select the following options from Reset Logs list.
      • None - Open the database without RESETLOGS option.
      • No - Open the database with NORESETLOGS option.
      • 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 | <RAC Client>
  2. Right-click the <Instance>, point to All Tasks and then click Browse and Restore.
  1. Select  Latest Backup and click View Content.
  2. Select the databases and click Recover All Selected.

    The Restore Options dialog box is displayed.

  3. On the General tab, click Advanced.

    The Advanced Restore Options dialog box is displayed.

  4. On the Options tab:
    • Select the Set DB Incarnation check box.
    • Click OK.
  5. 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 | <RAC Client>
  2. Right-click the <Instance>, point to All Tasks and then click Browse and Restore.
  1. Select  Latest Backup and click View Content.
  2. Select the databases and click Recover All Selected.

    The Restore Options dialog box is displayed.

  3. On the General tab, click Advanced.

    The Advanced Restore Options dialog box is displayed.

  4. On the Options tab.
    • Select the Open DB check box.
    • Select Yes from the Reset Logs list.
    • Select the Reset Database check box.
    • Click OK.
  5. 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 | <RAC Client>
  2. Right-click the <Instance>, point to All Tasks and then click Browse and Restore.
  1. Select  Latest Backup and click View Content.
  2. Select the databases and click Recover All Selected.

    The Restore Options dialog box is displayed.

  3. On the General tab, click Advanced.

    The Advanced Restore Options dialog box is displayed.

  4. On the Options tab:
    • Select the Disable Oracle Channel Restore Failover check box.
    • Click OK.
  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 | <RAC Client>
  2. Right-click the <Instance>, point to All Tasks and then click Browse and Restore.
  1. Select  Latest Backup and click View Content.
  2. Select the databases and click Recover All Selected.

    The Restore Options dialog box is displayed.

  3. On the General tab, click Advanced.

    The Advanced Restore Options dialog box is displayed.

  4. On the Options tab:
    • Select the  Validate check box.
    • Click OK.
  5. 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 and differentiate the database:

  1. From the CommCell Browser, navigate to Client Computers | <RAC Client>
  2. Right-click the <Instance>, point to All Tasks and then click Browse and Restore.
  1. Select  Latest Backup and click View Content.
  2. Select the databases and click Recover All Selected.

    The Restore Options dialog box is displayed.

  3. On the General tab, click Advanced.

    The Advanced Restore Options dialog box is displayed.

  4. On the Options tab.
    • Select the Set DBID check box.
    • Click OK.
  5. Click OK.

Setting Up Online Redo Log Files

The 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 redo logs after applying incremental backup data. Setting No Redo Logs will enable the RMAN to suppress the archived redo logs so that only data from incremental backups is restored. Enable No Redo 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 Redo Logs and perform a restore operation:

  1. From the CommCell Browser, navigate to Client Computers | <RAC Client>
  2. Right-click the <Instance>, point to All Tasks and then click Browse and Restore.
  3. Select Latest Backup and click View Content.
  4. Select the databases and click Recover All Selected.

    The Restore Options dialog box is displayed.

  5. On the General tab, click Advanced.

    The Advanced Restore Options dialog box is displayed.

  6. On the Options tab:
    • Select the No Redo Logs check box.
    • Click OK.
  7. 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 | <RAC Client>
  2. Right-click the <Instance>, point to All Tasks and then click Browse and Restore.
  1. Select  Latest Backup and click View Content.
  2. Select  the databases and click Recover All Selected.
  3. On the Restore Options dialog box, navigate to the General tab.
    • Click Advanced.
  4. On the Restore Options dialog box, navigate to the General tab.
    • Click Advanced.
  5. On the Advanced Restore Options dialog box, navigate to the Options tab.
    • Select the number of open files from Max Open Files list.
    • Click OK.
  6. Click OK.

Scheduling a Restore

For information on how to configure a restore schedule, see Schedule Restores.

Managing Restore Jobs

For information on how to manage the job, see Job Controller Overview.

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 modifications to the data since the snapshot creation. This option is only available if the storage array used for SnapProtect Backup supports the revert operation.
  1. From the CommCell Browser, navigate to Client Computers | <RAC Client>
  1. Right-click the <Instance> point to All Tasks, and then click Browse Backup Data.
  2. Click OK.
  3. In the right pane of the Browse window, select the data you want to restore and click Recover All Selected.
  4. Click Advanced.
  1. Select Use hardware revert capability if available check box.
  2. Click OK.
 
Startup Options

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

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

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

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

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

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

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

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

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

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

    The Report Selection dialog box appears.

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

    The report appears in your default Web browser.

Refer to CommCell Readiness Report.
Restore Job Summary Report

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

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

    The Report Selection dialog box appears.

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

    The report appears in your default Web browser.

Refer to Restore Job Summary Report.