> Essential > Databases > Oracle RAC > Restores

Cloning an Oracle RAC Database

You can create an instant clone of an Oracle RAC database.

The instant clone will be a single-instance database. Since the clone will be a single instance database, if you specify your own pfile then the pfile must include the following startup parameter:

clustered_database=false

Note

You cannot clone an Oracle 12c container database or pluggable database.

Before You Begin

  1. Have the backup administrator configure a client, and a subclient for the clone feature.

  2. Verify that the Oracle database version on the destination database is the same as the one on the source database.

  3. Verify that the Oracle user in both the source and destination database servers has the same user ID.

  4. Install the Oracle Agent and the MediaAgent on the proxy.

  5. On the destination client where want to create the clone database, create a directory for the mount path for the database clone files. This directory must be writable by the Oracle user.

  6. If the Oracle database version is 11.2.0.3.0, 11.2.0.3.1, or 11.2.0.3.2, install Oracle patch 13366202 or the latest Oracle 11gR2 Patch Set Update on the destination database.

  7. If the Oracle database version is Oracle 12c, install a minimum version of Oracle 12.1.0.2 with patch 19404068.

  8. Optional: Create an additional instance on the destination server with the same name as of the clone database so that you can store the clone instance properties (for example, ORACLE_HOME).

  9. You can clone a database to the same or different computer. If you clone a database to an instance that resides on a proxy computer, the following criteria must be met:

    • The Oracle database version on the proxy computer must be the same as the one in the source database.

    • The proxy computer must have access to the storage array containing the source database volumes.

    • The Oracle user in both the source and destination computers must have the same user ID.

    • The Oracle Agent and the MediaAgent must be installed on the proxy.

    • You must create a dummy Oracle instance with the same name as of the source database.

  10. Perform a full backup.

  11. Set the database to the correct mode defined in the table.

Control File in the Restore

Required Database Mode

Control file is included in the restore

NOMOUNT

Control file is not included in the restore

MOUNT

Procedure

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

    The database overview page appears.

  2. On the Instances tab, click the instance.

    The instance properties page appears.

  3. Click Clone.

    The Add Oracle instant clone page appears.

  4. In the Destination details section, provide the destination information.

    1. From the Destination server list, select the client that you want the clone to be on.

    2. In the Instance name box, type a name for the new instance.

    3. In the Oracle home box, type the full path to the destination Oracle home directory.

      If you have access to the destination client Oracle database, then the Oracle home path is populated automatically.

  5. From the Recover to type list, select the type of recovery, and then enter any related values.

  6. Under Clone options, in the Delete clone after boxes, type the number of days and hours that the software retains the test environment.

  7. To overwrite a clone if it already exists, move the Overwrite if already exists toggle to the right.

  8. From the Clone from copy list, select the type of copy.

  9. To specify the staging path, in the Staging path box, type the full path to the location that the Oracle software uses to stage the clone.

  10. To specify the Pfile location, in the PFile box, type the full path to the destination startup parameter file.

  11. To specify the GA and SGA size, in the PGA + SGA size box, type the memory size (in MB) that you want to allocate for the Post Global Area (PGA) and System Global Area (SGA). The default value is 2048 MB.

  12. To specify the redo log size, in the REDO log size box, type the minimum permitted size (in MB) for the redo log file. The default value is 50 MB.

  13. To use the access node as an iSCSI target, under Advanced options move the Use access node as iSCSI target toggle to the right, and then from the Access node list select the server that is the access node.

  14. To run a script after the clone operation, type the full path to the script in the Command file path box.

  15. Click SUBMIT.

Loading...