Loading...

Configuring Multiple Instances Using Shared Storage on a Client

You can configure multiple instances using a shared storage on a client:

  1. Ensure that you have installed the Oracle iDataAgent and MediaAgent on all the source and proxy clients. See Oracle iDataAgent and MediaAgent deployment for step-by-step procedure on how to install the oracle iDataAgent and MediaAgent.
  2. Configure the client and instance using the steps described in Getting Started - Oracle Configuration. Ensure that you perform a manual discovery of instances.
  3. Create a storage policy to perform IntelliSnap operations. Create a Snapshot Copy to enable a snapshot on the copy.
  4. Create an agent-specific schedule policy to perform IntelliSnap operations. For instructions, see Creating Data Protection Schedule Policies.
  5. Create and configure a new subclient manually as follows:
    • From the CommCell Browser, navigate to Client Computers | <Client>| Oracle.
    • Right-click the <Instance>, point to All Tasks, and then click New Subclient.
    • In the SubclientName box, type the subclient name.
    • Click the IntelliSnap Operations tab.
    • Click IntelliSnap option to enable IntelliSnap backup for the selected subclient.
    • Select the storage array from the Available Snap Engine drop-down list.
    • By default, the system will perform a File System backup copy. Select Use RMAN for backup copy if you want to use RMAN backup copy.

      Notes:

      If you use a NoArchiveLog mode Database, do not select Use RMAN for backup copy.

      The Volume Copy option is not supported for multiple instance snap optimization.

    • Select the proxy client from the Use Proxy drop-down list.

      See Configuring Proxy for RMAN Backup Copy, if you want to use a proxy for RMAN backup copy.

  6. Select the storage policy from the storage device tab of the subclient created for snaps.
    • From the CommCell Browser, navigate to Client Computers | <Client>| Oracle|<Instance>. 
    • Right-click thesubclientcreated for snaps andthen click Properties
    • Click the Storage Device tab.
    • In the Data Storage Policy list, select a Storage Policy name.
    • Click OK to convert the next backup as a full backup.
    • Click OK.
  7. You must create and configure a subclient as shown above for all the instances included in the shared storage on a client.

    Once the subclients for snaps are created for other instances, you must assign a storage policy as shown above to them.

  8. Add all the subclients that are included in this shared storage environment to the schedule policy. See Automatic Subclient Creation and Configuration to automatically create and configure subclients using the qscripts.
  9. Ensure that all the following additional requirements are satisfied on all the clients for successful snap or clone operations in a shared LUN environment:

    To add or edit an additional setting, follow the steps in Adding or Modifying Additional Settings from the CommCell Console.

    • All the subclients of a client in the same schedule policy should use the same storage policy.
    • All the subclients of a client in the same schedule policy should use the same proxy client.
    • Use the sMULTIAPPCONSISTENTSNAP additional setting set to Y on all the clients to perform a snap for multiple databases in the same job.
    • Configure the nDECLUSTER_LVM additional setting on all the nodes and Proxy machine if cluster is configured and set it to 1.
    • If the storage array is EMC clariion or EMC Symmetrix, use the SYMAPI_HOME_DIR additional setting to the directory where the Symmetrix SYMAPI library is present on all the clients and restart the Commvault services. In case of EMC Symmetrix, all the source devices should be in the same device group for consistency.
    • REDO Log for No archive log database should be on the volume for which snap should be supported.
    • Data and log volumes should not be shared and each database should have unique paths on the volumes like /data/db1, /data/db2, /log/db1, /log/db2 etc.
    • Enable the multi-instance snap optimization.
      • On the CommServe computer, add the EnableOracleMultiInstanceSnap additional setting  and configure the following values:

        Property

        Value

        Name

        EnableOracleMultiInstanceSnap

        Category

        CommServDB.GxGlobalParam

        Type

        Integer

        Value

        1 - to enable multi-instance snap optimization

        0 - to disable multi-instance snap optimization

        For instructions on how to add additional settings from the CommCell Console, see Adding or Modifying Additional Settings from the CommCell Console.

  10. For clone operations, perform the following in addition to the above configuration:
    • While creating a new subclient, select the clone engine from the Available Snap Engine drop-down list in the IntelliSnap Operations tab.
    • Create a separate schedule policy for clone operations.

Last modified: 8/31/2018 6:45:30 PM