V11 SP8
Loading...

Configuration - FlexFrame for SAP Oracle

Configuration

Once the SAP Oracle iDataAgent has been installed, create virtual client using cluster client configuration from the CommCell Console.

Then configure the instance and subclient for backups. Each instance references an Oracle database. Also it is recommended to create separate subclients for data and log backups.

The following sections provide the necessary steps required to create and configure these components for a first backup of an Oracle database.

Configuring the Cluster Group Client

After installing the software successfully on all the physical nodes that host the cluster group, you must configure the cluster group client from the CommCell Console. Use the following steps to configure the cluster group client.

  1. From the CommCell Browser, right-click the Client Computers node, point to New Client | Clustered Server and then click Unix Cluster.

  2. In the Client Name box, type a name for the cluster group. The client name can be any unique name.

    In the Host Name box, you can type either the fully qualified domain name of the cluster group or the IP address of the cluster group.

    • The Host name of the cluster group client should not be used by any existing client in your CommCell.
    • If you want to specify the IP address of the cluster group, ensure that the IP address is static.

  3. Review the cluster group information and click Finish.

    The Advanced Client Properties dialog box is displayed.

  4. On the Advanced Client Properties dialog box, click the Cluster Group Configuration tab.
    • All the Linux clients that are available in the CommCell will be listed in the Available list. Select the physical computers (nodes) where you installed the necessary agents from the Available list, and then click Add > to move the client to the Selected list.
    • Click the Agents tab.
      Select the agents you want to use in the cluster group client from the Available list and click Add > to move the Agent to the Selected list.

    If the client computer properties dialog box is not displayed automatically, then you need to open it manually: Right-click the  <Cluster Group Client>, and then click Properties. Click Advanced on the Client Computer Properties dialog box. Click Cluster Group Configuration tab on the Advanced Client Properties dialog box.

  5. Click the Agents tab.

    Select the agents you want to use in the cluster group client from the Available list and click Add > to move the agent to the Selected list.

    In order to configure a Cluster Group Client, the agents should be installed on all the clustered nodes for proper failover. If an agent is not installed on all the nodes, then the agents selection tab on the Advanced Client Properties window will display the agent name in plain text (not in bold). However, you can still configure the Cluster Group Client even when the Agents are not installed on a particular node; installation can be done later using remote install procedure.

  6. Click the Job Configuration tab.

    In the Job Results Directory box, type the path for the job results directory. Ensure that the directory resides on a shared clustered file system.

    • The Browse button does not work when you configure the cluster group client for the first time. After the initial configuration, you can use the button to update the directory (if required).
    • In the case of MediaAgent and ContinuousDataReplicator, the Job Result directory path will be used for both the Index Cache and CDR Log directories respectively unless another directory location is provided.

    Click OK.

  7. Click OK.

    The cluster group client is successfully created.

  • Ensure that the path provided for the Job Results Directory is an absolute path.

    For example, /addon/ commvault_pool/job_results/p22-dbsm1-se

  • If MediaAgent is installed on a physical node, ensure that the path provided for Index Cache is an absolute path. Else, post installation, edit the MediaAgent properties to provide a different path for Index Cache.

Creating an Instance

  1. From the CommCell Browser, navigate to <Client> | SAP for Oracle. Right-click SAP for Oracle | All Tasks and click New Instance (ORACLE SID).

  2. Specify the following details:
    • In the Instance (Oracle SID) box, type the Instance Name.
    • Browse or enter the path to the Oracle application files in Oracle Home.
    • Browse or enter the path to the Oracle data and control files in SAP DATA PATH.
    • Select a Storage Policy from the drop down list.

      If you do not have a Storage Policy created, follow the steps given below to create a Storage Policy.

      If you have already created a Storage Policy, then go to step 4.

  3. Create a Storage Policy:

    Note: The storage policy retention for the SAP Oracle IDA must be relative to the SAP recov_interval value. The SAP recov_interfval is set in the init<SID>.sap profile file and defines the time interval that the BRRESTORE and BRRECOVER commands search for the data and log backup details files in the summary file. By default, this value is 30 days. For more information, see FAQs.

    1. From the CommCell Browser, navigate to Policies.
    2. Right-click the Storage Policies and then click New Storage Policy.
    3. Follow the prompts displayed in the Storage Policy Wizard. The required options are mentioned below:
      • Select the Storage Policy type as Data Protection and Archiving and click Next.
      • Enter the name in the Storage Policy Name box and click Next.
      • From the Library list, click the name of a disk library to which the primary copy should be associated and then click Next.

        Ensure that you select a library attached to a MediaAgent operating in the current release.

      • From the MediaAgent list, click the name of a MediaAgent that will be used to create the primary copy and then click Next.
      • For the device streams and the retention criteria information, click Next to accept default values.
      • Select Yes to enable deduplication for the primary copy.
      • From the MediaAgent list, click the name of the MediaAgent that will be used to host the Deduplication Database (DDB).

        In the Location box, type the name of the folder in which the DDB must be located or click the Browse button to select the folder and then click Next.

      • Review the details and click Finish to create the Storage Policy.

  1. Enter the user name in ORACLE USER to access the Oracle application on a Unix client.

    Use <SID_name>adm in order to perform backup and restore operations from CommCell Console for the associated instance.

    Make sure that the user has administrator privileges to access the Oracle application.

  1. Click Details tab and add the following information:
    • Enter the target database connect string in Connect String.
    • Browse or enter the path to the SAP EXE folder in SAP EXE Folder (Required).

  2. Click Storage Device tab.

    Select a Storage Policy used for user command backup of data from the drop down list.

  3. Click Log Backup tab.
    • Select a Storage Policy used for all Archive Log backups from the drop down list.
    • Click OK.

Creating Subclient for Data Backup

  1. From the CommCell Browser, navigate to <Client> | SAP for Oracle | Instance.

    Right-click Instance | All Tasks and click New Subclient.

  2. Enter the Subclient Name.

  3. Click the Logs Backup tab and clear the check box for Backup Archive Log.

  4. Click the Storage Device tab.
    • Select a Data Storage Policy from the drop down list.
    • Click OK.

Creating Subclient for Log Backup

  1. From the CommCell Browser, navigate to <Client> | SAP for Oracle | Instance.

    Right-click Instance | All Tasks and click New Subclient.

  2. Enter the Subclient Name.

  3. Click the Content tab and clear the check box for Data.

  4. Click the Storage Device tab.
    • Select a Data Storage Policy from the drop down list.
    • Click OK.

    Make sure that the storage policy selected uses the same MediaAgent used by data and logs.