> Software > Databases > Amazon Web Services > Amazon RDS > Amazon RDS Using Export > Oracle > Restores

Restoring the Amazon RDS Oracle Logical Dump Subclient Data

You can only run a job-based restore on the Oracle logical dump subclient data.

When you perform a restore operation on a logical subclient, the Commvault software invokes the Oracle data pump import utility to stage the dump file on the specified path, and then imports the dump file to the specified database on the destination client.

Restore Destinations

You can restore the data to any of the following destinations:

  • The same Amazon RDS instance

  • An Amazon RDS instance that is different from the source instance

  • An on-premises database instance

  • A different Oracle instance that runs in Amazon EC2

Prerequisites

  • The schema must be present on the destination before running the restore procedure. If it is not present, the database administrator must create the schema before restoring the data.

  • For cross-server restore, the connect string details of the destination database must be in the source's tnsnames.ora file and the connect string details of the source database must be in the destination's tnsnames.ora file.

  • Verify the following on the destination client:

    • The Oracle version must match AWS RDS Oracle version.

    • Staging path must have the Oracle permissions.

    • Oracle database on the access node must be running.

Procedure

  1. From the Command Center navigation pane, go to Protect > Databases.

    The databases Overview page appears.

  2. On the Instances tab, click the instance for which you want to run the job-based restore.

    The Overview page of the instance appears.

  3. On the Subclients tab, in the row of the logical dump subclient, click the action button action_button, and then click Backup history.

  4. Go to the backup job with Completed status, click the action button action_button, and then click Restore.

    The Backup content page appears.

  5. Select the folders that you want to restore, and the date and time from which to restore, and then click Restore.

    The Restore options dialog box appears.

  6. From the Destination server list, select the destination host.

  7. In the Staging path box, type the full path to the location on the destination where the software stages the data.

  8. In the Parallelism for import box, type the number of streams to use for the restore operation.

  9. Select the Import to database check box, and then do the following:

    1. From the Database name list, select the database that the software restores the tables to.

    2. In the Connect string box, select the existing credentials or add new credentials.

      Steps to add a credential

      1. Click the + icon beside the credentials list.

        The Add Credential dialog box appears.

      2. In the Credential name box, enter a unique name to access the credential.

      3. Under Connect string, enter the following details to access the Oracle server.

        • In the User name box, type the user name to access the RDS for Oracle application.

        • In the Password box, type the password to access the RDS for Oracle application.

        • In the Service name box, enter the Oracle service name.

      4. In the Description box, enter a brief description for the credential.

      5. Click Save.

    3. If you want to restore data to different tablespaces on the destination, use the Remap tablespace box to define how you want the tablespaces remapped. The format of the string is as follows, with a space character (:) between each source and destination pair:

      Tablespace1_source:Tablespace1_destination Tablespace2_source:Tablespace2_destination... TablespaceN_source:TablespaceN_destination

      Note

      If remapping of the tablespaces fails with Oracle errors, then the tablespaces cannot be remapped. If this occurs, the database administrator must create tablespaces in the destination database that are identical to those in the source database.

    4. To overwrite the existing tables on the destination, select the Overwrite if table exists check box.

  10. To specify pre or post commands, under Pre or Post options, do the following:

    1. In the Pre recovery command box, enter the path of the process to run before the restore.

    2. In the Post recovery command box, enter the path of the process to run after the restore.

    3. To run a post process for all restore operation attempts of a job phase, whether it is successful, interrupted, suspended, or when the job fails, select Run post restore process for all attempts.

    4. To specify the user to run the pre and post commands, move the Run as User toggle button to the right and enter the user name and password.

  11. You can configure a schedule to repeat this restore operation. To create a schedule, do the following:

    1. Click Schedule.

      The Add schedule dialog box appears.

    2. In the Name box, type a name for the schedule.

    3. Configure the Frequency and Repeat parameters.

    4. To specify exceptions to the schedule, click Exceptions.

      The Exceptions dialog box appears.

    5. Configure the exception parameters:

      • You can click Add Exception to save a set of exception parameters and continue adding sets of exception parameters.

      • Click Save when you have finished configuring the exception parameters.

    6. Under the Range of recurrence section, specify the Start date and End date to schedule the recurrence range of the restore operation.

    7. To save the schedule and return to the restore dialog box, click Schedule.

  12. Click Submit.

×

Loading...