Configuring Oracle Subclients That Use Image Copy Followed by IntelliSnap

You can configure the subclient to create a clone from an image copy. When you perform a backup operation on the subclient, the software uses RMAN to back up the incremental database changes to a non-production image copy volume that can be snapped, and then takes a snap of the volume. The target of the RMAN image copy can be a hardware array or NFS ObjectStore.

If you have a UNIX configuration, you can use an ASM diskgroup for the Oracle image copy location. The location must be the base name of the ASM diskgroup, for example, +ASMDISKGROUP. You cannot use a subdirectory. If you use an ASM diskgroup for your image copy location, then the MediaAgent must have a UNIX operating system.

Before You Begin

If you are going to use NFS ObjectStore as the target of the RMAN image copy and haven't configured it, configure it. For more information, see Getting Started with NFS ObjectStore.


  1. From the CommCell Browser, go to Client Computers > client > Oracle.
  2. Right-click the instance, then go to All Tasks > New Subclient.

    The Creating New Subclient dialog box appears.

  3. On the General tab, in the Subclient Name box, enter a name for the subclient.
  4. On the Content tab, make the following selections:
    • Select the Data check box.
    • Click the Online Database option.
  5. On the Log Backup tab, select the Backup Archive Log check box.
  6. On the Storage Device tab, from the Storage Policy list, select the storage policy name.

    If you are going to use NFS ObjectStore as the target of the RMAN image copy, the storage policy created during NFS ObjectStore configuration must be used in this subclient's configuration. In addition, the data and log backups must be written to the same storage policy.

  7. On the IntelliSnap Operations tab, configure the IntelliSnap options:
    1. Select the IntelliSnap check box.

      A message appears that states that the next backup will be a full backup.

    2. Click OK.
    3. From the Available Snap Engines list, select the storage engine that applies to the image copy volume. To use the NFS ObjectStore snap engine, select Commvault NFS ObjectStore Snap.
    4. To use a proxy server, from the Use Proxy list, select the appropriate MediaAgent.

      This is the MediaAgent that is used to perform the IntelliSnap and backup copy operations.

      Note: Make sure that the operating system version on the proxy server is either the same version or a later version than the operating system version on the client computer.

    5. To have the backup copy operation fall back to the source if the proxy is unreachable, select the Use source if proxy is unreachable check box.

      This prevents the interruption of the backup schedule when the proxy cannot be reached.

    6. Optional: To perform an integrity check of the hardware, select the Enable Snap Integrity Check check box.
    7. Select the Use RMAN Image Copy check box.
    8. In the Path box, enter the image copy path, or if you are using the NFS ObjectStore snap engine, enter the NFS ObjectStore mount point.

      Note: The path must have the following properties:

      • It must be a mount path that can be snapped.
      • It must have enough space to store the maximum size of all the datafiles and one incremental backup.
      • If you use a file system (and not an ASM diskgroup), it must have UNIX 750 permissions
  8. Select the Backup Copy Interface:
    • If you are using NFS ObjectStore as the snap engine, click either File System or RMAN.
    • If you are using other snap engines, click Volume Copy (Block-Level Backup - Supports Instant Database Recovery).

      This option allows clones to be made from the backup copy.

  9. To turn on synchronization of data on the source disk and the index, select Reconcile Backup, and then enter the number of days from the previous backup. This option makes the backup job compare the data blocks on the disk to the data on the index. Data blocks that do not match with the index are included in the backup.
  10. Optional: Run scripts before or after the backup. On the Pre/Post Process tab configure the options:
    1. In the PreBackup process box, type the full path name for the script.
    2. In the PostBackup process box, type the full path name for the script.
    3. To run the post backup process regardless of the job's outcome, select the Run Post Backup Process for all attempts check box.
  11. Click OK to close the Creating New Subclient dialog box.

Last modified: 4/29/2020 7:56:51 PM