Creating a Clone for Instant Application Recovery
When you want to use Instant Application Recovery, create a clone of the instance that contains the subclient that is configured for Volume Copy.
You can create a clone from a backup or a backup copy. When you create a clone from the backup copy, the destination client does not need to have access to the hardware array.
When you create a clone, you can specify a reservation period. When the reservation period expires the system automatically shuts down the clone database and frees up all resources.
Schedule clones to run periodically so that they have the latest production data.
You cannot clone an Oracle 12c container database or pluggable databases.
You can run a script after the software creates the clone that masks the data on the clone. Use this option when you want to protect the production database clone. The SnapProtect software is integrated with the following vendors:
- Data Masker
Before You Begin
- Verify that the Oracle database version on both the source destination databases are the same.
- Verify that the Oracle user in both the source and destination database servers have the same user ID.
- Install the Oracle Agent and the MediaAgent on the proxy.
- On the destination client where you 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.
- Do one of the following:
- If the Oracle database version is 184.108.40.206.0, 220.127.116.11.1, or 18.104.22.168.2, install Oracle patch 13366202 or the latest Oracle 11gR2 Patch Set Update on the destination database.
- If the Oracle database version is Oracle 12c, you install at a minimum version of Oracle 22.214.171.124 with patch 19404068.
- Optional: Create an additional instance on the destination client with the same name (for example, ORACLE_HOME) as the clone database so that you can store the clone instance properties. When you specify the clone options in the CommCell Console, the software pre-populates these properties.
- 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 version on the source database.
- The proxy computer must have access to the storage array that contains 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 the source database.
- Optional: To perform data masking, see Configuring Third-Party Data Masking for Oracle Database Clones.
Make sure to note the name and location of the script.
- From the CommCell Browser, expand Client Computers > client > Oracle.
- Right-click the instance, point to All Tasks and then click Clone.
- On the Clone Options dialog box, select Latest Backup and click View Content.
- In the right pane of the CommCell Browser window, select the entire database to clone, and click Clone.
The Restore Options dialog box appears.
- On the General tab, specify the destination details.
- From the Destination Client list, select the clone destination.
- To use the RMAN Recovery catalog, clear the NO CATALOG check box, and then in the Catalog Connect boxes, type the connect string.
- On the Clone Options tab, specify the clone details.
- Specify the destination database.
Option Steps Use a pre-defined instance
- From the Instance list, select the destination.
Use a database that is not in the list
- In the Instance list, type the database name.
- In the ORACLE HOME box, type the location of the Oracle HOME directory.
- In the ORACLE User box, type the database user ID .
- Specify the location of the startup parameter file in the PFile box (for example /oracle/clone/initdup1.ora).
If the file that you enter does not exist, the software creates the file and sets the parameters. The Oracle user must have writer permission for the startup file parameter directory.
If the file that you enter does exist, the dump and control files must exist and have writer permissions for the Oracle user. The specified server parameter file must meet the following criteria:
- The file must contain all the require Oracle initialization parameters
- The file must be able to be read by the Oracle user
- Specify the path that will contain the Oracle database mounted snapshots, in the Snap Mount Location box (for example, /oracle/clone).
Note: The Oracle user must have write permissions to this directory. If you chose the option to create the server parameter file, the dump files are created in this directory, so there must be disk space to hold the logs until the reservation period expires.
- To have the software clean up any existing clone on the destination that has the same clone SID, regardless of the reservation period, select the Overwrite if clone exists check box.
- Specify time to retain the test environment in the Reservation Period box.
Note: The default time to retain the clone is 1 hour. When this time expires, the software dismounts the database and deletes the mount point.
- By default, the system sets up two redo log groups, with one log file in each group. To override this configuration (location, number of groups, files), select the Online Log Files check box and then select the Group option.
- Click Add.
- In the Type the Size of the online redo log file.
- Select the Size Specifications of the file from SizeSpec list.
- To allow the database to reuse an existing file, select the Reuse check box.
- Specify the destination database.
- Optional: On the Pre/Post tab, in the Post Recovery Command box, type the full path to the data masking script.
- On the Job Initiation tab, have the software automatically refresh the clone with the latest backup:
- Select Schedule.
- Click Configure Schedule Pattern.
For information on how to configure a restore schedule, see Schedule Restores.
- Click OK.