V11 SP8
Loading...

IntelliSnap - Advanced Configuration - SAP Oracle

Table of Contents

Enabling SAP Specific IntelliSnap Backups

When using SAP environments with BRTools version 7.1 and above, you can perform IntelliSnap backups using the util_vol or util_vol_online backup interfaces. SAP provides these interfaces to take volume level backups of the database.

Before You Begin

  • Configure the parameters in the init<SID>.sap file

    UNIX

    Parameter Value Description
    util_vol_access copy Specifies that the IntelliSnap backups can be copied to a different target location for verification purposes.
    util_vol_nlist no_check Deactivates the BACKINT check of the backup volumes. This check makes sure that the backup volumes do not contain non-database files or database files that belong to a database other than the one that you want to back up.

    You can set this parameter to disable a specific non-database file. For example, util_vol_nlist = (/oracle/oracle10g/CER/sapdata6/non_db_file)

    Warning: If the database volumes contain non-database files or database files from a database other than the one that you want to back up, the files can be overwritten without warning.

    util_file_unit all_data Specifies that the smallest unit for the IntelliSnap backup is the sapdata, origlog, or mirrorlog directories.

    Windows

    Parameter Value Description
    util_vol_access copy Specifies that the IntelliSnap backups can be copied to a different target location for verification purposes.
    util_vol_nlist no_check Deactivates the BACKINT check of the backup volumes. This check makes sure that the backup volumes do not contain non-database files or database files that belong to a database other than the one that you want to back up.

    You can set this parameter to disable a specific non-database file. For example, util_vol_nlist = (E:\oracle\oracle10g\CER\sapdata6\non_db_file)

    Warning: If the database volumes contain non-database files or database files from a database other than the one that you want to back up, the files can be overwritten without warning.

    util_file_unit all_data Specifies that the smallest unit for the IntelliSnap backup is the sapdata, origlog, or mirrorlog directories.

Procedure

  1. From the CommCell Browser, expand Client Computers.
  2. Right-click the client, and then click Properties.

    The Client Computer Properties dialog box appears.

  3. Click Advanced.

    The Advanced Client Properties dialog box appears.

  4. Select the Enable IntelliSnap check box.
  5. If you have not done so, click Manage to manage your storage array.

    For information on how to configure the array, see Array Management.

  6. Click OK.

Creating an Instance

Manually add a SAP for Oracle instance in the CommCell Console when you need to manage a database.

Note: Use the DDB for the instance for a RAC configuration.

For more information on SAP on Oracle users and their roles, go to the SAP website, Users and Roles.

About This Task

By default, when you discover or create a SAP for Oracle instance, the Commvault software automatically creates an archive log subclient. You can disable this feature by setting an additional setting. For more information, see Disabling Automatic Archive Log Subclient Creation.

If you run SAP Kernel 7.20, Patch 100 or later, you can use the SAP Secure Store feature. The SAP Store feature uses encryption to store user authentication credentials (for example, user name and password) on a Secure Storage File System (SSFS). For additional information, go to the SAP website, Secure Store.

Refer to the following SAP Notes that provide upgrade and installation information.

Note Description
1764043 BR*Tools SSFS Support
1622837 SAP Kernel and SFFS Patches
1639578 SFFS Setup
1764043 See the section titled "Storage of BR*Tools user/password in secure storage"

Procedure

  1. From the CommCell Browser, expand Client Computers > client.
  2. Right-click SAP for Oracle, point to All Tasks and then click New Instance (ORACLE SID).
  3. On the General tab of the Creating New Instance dialog box:
    1. In the Instance (ORACLE SID) box, enter the instance name.

      You can use the following commands to obtain the SAP on Oracle instance name.

      Expand All

      UNIX

      Log on to the SAP on Oracle server with the ora<SID> user.

      On the command line, type the following command:

      su - ora<SID>
      echo $ORACLE_SID

      Example

      su - ora<CER>
      echo $ORACLE_SID
      CER

      Windows

      Log on to the SAP on Oracle server with the <domain_name>\ora<SID> user.

      On the command line, type the following command:

      echo %ORACLE_SID%

      Example

      echo %ORACLE_SID%
      TRD

    2. In the User Account box, enter the login credentials to access the SAP for Oracle client.

      For UNIX configurations, use ora<SID> for this value, substituting the SID parameter with the Oracle SID of your database.

      For Windows configurations, use <domain_name>\ora<SID> for this value, substituting the domain_name parameter with your database domain name and the SID parameter with the Oracle SID of your database.

    3. In the ORACLE HOME box, enter the Oracle application install path.
      Expand All

      You can use the following commands to obtain the Oracle home path.

      UNIX

      Log on to the SAP on Oracle server with the ora<SID> user and retrieve the $ORACLE_HOME environment variable.

      On the command line, type the following command, substituting the SID parameter with the Oracle SID of your database:

      echo $ORACLE_HOME

      Example

      su - ora<TRD>
      echo $ORACLE_HOME
      /oracle/TRD/112_64

      Windows

      Log on to the SAP on Oracle server with the <domain_name>\ora<SID> user, substituting the domain_name parameter with your database domain name and the SID parameter with the Oracle SID of your database.

      On the command line, type the following command:

      echo %ORACLE_HOME%

      Example

      echo %ORACLE_HOME%
      I:\oracle\product\10.2.0\dbhome_1

    4. In the SAP DATA PATH box, enter the SAP on Oracle $SAPDATA_HOME environment path. This is the path that contains the SAP on Oracle data and log files.

      The SAP server environment variables contain this information.

      You can use the following commands to obtain the SAP data path.

      Expand All

      UNIX

      Log on to the SAP on Oracle server with the ora<SID> user, substituting the SID parameter with the Oracle SID of your database.

      On the command line, type the following command:

      echo $SAPDATA_HOME

      Example

      su - ora<TRD>
      echo $SAPDATA_HOME
      /oracle/TRD

      Windows

      Log on to the SAP on Oracle server with the <domain_name>\ora<SID> user, substituting the domain_name parameter with your database domain name and the SID parameter with the Oracle SID of your database.

      On the command line, type the following command:

      echo %SAPDATA_HOME%

      Example

      echo %SAPDATA_HOME%
      I:\oracle\TRD

    5. In the SAP EXE PATH box, enter the path to the SAP EXE path. This is the path that contains the executable files.

      You can use the following commands to obtain the SAP EXE path.

      Expand All

      UNIX

      Log on to the SAP on Oracle server with the ora<SID> user, substituting the SID parameter with the Oracle SID of your database.

      On the command line, type the following command, substituting the domain_name parameter with your database domain name and the SID parameter with the Oracle SID of your database:

      echo $SAPEXE

      Example

      su - ora<DCT>
      echo $SAPEXE
      /usr/sap/DCT/SYS/exe/run

      Windows

      Log on to the SAP on Oracle server with the <domain_name>\ora<SID> user.

      On the command line, type the following command, substituting the domain_name parameter with your database domain name and the SID parameter with the Oracle SID of your database:

      echo %SAPEXE%

      Example

      echo %SAPEXE%
      I:\usr\sap\TRD\SYS\exe\uc\NTAMD64

    6. In the Storage Policy used for the data of default subclient list, select a storage policy name.
  4. If you have a SAP Secure Store environment, on the Details tab, select the Use Sap Secure Store check box.
  5. On the Details tab, In the Connect String box, enter the credentials to connect to the Oracle database. For example "sys/pwd12@orcl4".
  6. In the Block Size box, type the size of the block for backup and restore operations.
  7. On the Storage Device tab, enter storage policy information:
    1. In the Storage Policy used for user command backup of data list, select a storage policy.
    2. In the Storage Policy used for all Archive Log backups list, select a storage policy name.
  8. Click OK to close the Creating New Instance dialog box.

Configuring Subclients for Offline Backups

Configure the SAP for Oracle subclient to perform a full backup of the database when it is offline. Full backups include all datafiles, tablespaces, and the Oracle database control file. Offline backups do not include the archived log files.

You can perform offline backups when the database is in either offline or online mode.

The following table describes the available backup interfaces.

Interface Description
util_file The software locks the Oracle database until the backup completes.
util_vol The software locks the entire Oracle database until the backup completes.
util_vol_online The software locks each volume that is being backed up and releases it when the backup completes.

Before You Begin

Procedure

  1. From the CommCell Browser, expand Client Computers > client > Agent.
  2. Right-click the instance, point to All Tasks and then click New Subclient.

    The Create New Subclient dialog box is displayed.

  3. On the General tab, in the Subclient name box, enter a name for the subclient.
  4. On the Content tab:
    • Select the Data check box.
    • Select the Offline Database option.
    • In the Backup Device section, select the backup interface.
  5. On the Storage Device tab, select the name of the Data Storage Policy.
  6. On the  IntelliSnap Operations tab.
    • Select the IntelliSnap check box.
    • From the Available Snap Engines list, select the appropriate engine.
  7. Optional: Run scripts before or after the backup.

    You can choose to run the post-process script even if the backup job failed.

    On the Pre/Post tab:

    1. In the Pre-Backup Command box, type the full path name for the script.
    2. In the PostBackup Command 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 Process for all attempts check box.
  8. Click OK to close the Create New Subclient dialog box.

Configuring Subclients for Online Backups

In some environments, you cannot bring down a database to perform an offline backup. In such situations, you can perform an online backup, where the database is up and running during the backup.

You can perform either a full backup or incremental backup of the SAP for Oracle database when it is online.

The following table describes the available backup interfaces.

Interface Description
util_file The software locks the Oracle database until the backup completes.
util_vol The software locks the entire Oracle database until the backup completes.
util_vol_online The software locks each volume that is being backed up and releases it when the backup completes.

Before You Begin

Procedure

  1. From the CommCell Browser, expand Client Computers > client > Agent.
  2. Right-click the instance, point to All Tasks and then click New Subclient.

    The Create New Subclient dialog box is displayed.

  3. On the General tab, in the Subclient name box, enter a name for the subclient.
  4. On the Content tab:
    • Select the Data check box.
    • Select the Online Database option.
    • In the Backup Device section, select the backup interface.
  5. On the Storage Device tab, select the name of the Data Storage Policy.
  6. On the  IntelliSnap Operations tab.
    • Select the IntelliSnap check box.
    • From the Available Snap Engines list, select the appropriate engine.
  7. Optional: Run scripts before or after the backup.

    You can choose to run the post-process script even if the backup job failed.

    On the Pre/Post tab:

    1. In the Pre-Backup Command box, type the full path name for the script.
    2. In the PostBackup Command 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 Process for all attempts check box.
  8. Click OK to close the Create New Subclient dialog box.

Configuring Subclients for Log Backups

You use archive logs backups to recover database transactions that have been lost due to an operating system or disk failure or to recover lost database transactions.

You apply the archive logs to an online backup to recover the database.

When you perform an IntelliSnap backup, select the Use Traditional Backup for Logs check box to have the software run a traditional backup of the logs after the IntelliSnap data backup is complete. Use this option when you want to reduce the total number of snapshots that are taken during the backup operation. When you use this option with the snap optimization feature (see Optimizing IntelliSnap Backups), the number of snapshots is reduced. The Use Traditional Backup for Logs check box is only available when you have selected the IntelliSnap check box on the IntelliSnap Operations tab.

Best Practice: Create separate subclients to back up log files because they are mandatory for recovering data.

Note: If the archive log destination is different than the default $SAPDATA_HOME/saparch location, set the <SID>_sSAPARCH additional setting to enable the CommCell Console backup to obtain the new SAPARCH location.

The following table describes the available backup interfaces.

Interface Description
util_file The software locks the Oracle database until the backup completes.
util_vol The software locks the entire Oracle database until the backup completes.
util_vol_online The software locks each volume that is being backed up and releases it when the backup completes.

Before You Begin

Procedure

  1. From the CommCell Browser, expand Client Computers > client > SAP for Oracle.
  2. Right-click the instance, point to All Tasks and then click New Subclient.

    The Create New Subclient dialog box is displayed.

  3. On the General tab, in the Subclient name box, enter a name for the subclient.
  4. On the Content tab, clear the Data check box.
  5. In the Backup Device section, select the backup interface.
  6. On the Log Backups tab:
    • Select the Backup Archive Log check box.
    • Optional: Select the Archive Delete check box to delete the logs after the backup completes.
    • Optional: Select the Disable Switch Current Log check box to disable log switching for the current redo log.
    • Optional: Select the Archive Log Second Copy check box to create a second copy of the archived offline redo log files.
    • Optional: To run a traditional log backup after the data backup completes, select the Use Traditional Backup for Logs check box.

      The Job Controller first displays a snap backup job for data. Once this job completes, The software automatically starts an incremental log backup.

      Note: This option disables the Selective Online Full check box on the Content tab.

      Select the IntelliSnap check box on the IntelliSnap Operations tab.

      If you select this option and try to restore the data by using a copy precedence, the restore job fails. For more information, see SAPOR0001.

  7. On the  IntelliSnap Operations tab.
    • Select the IntelliSnap check box.
    • From the Available Snap Engines list, select the appropriate engine.
  8. On the Storage Device tab, from the Log Storage Policy list, select the storage policy name for the log backups.
  9. Optional: Run scripts before or after the backup.

    You can choose to run the post-process script even if the backup job failed.

    On the Pre/Post tab:

    1. In the Pre-Backup Command box, type the full path name for the script.
    2. In the PostBackup Command 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 Process for all attempts check box.
  10. Click OK to close the Creating New Subclient dialog box.

Configuring Subclients for Consistent Online Backups

A consistent online backup includes the data and the offline redo logs that are generated during the data backup. When you perform a backup on a consistent online data subclient, the data is consistent because the offline redo log files created by BRBACKUP backed up with the database files on the same volume. The logs that are part of the consistent online backup are part of the data backup and included in the BRBACKUP summary file.

You can perform either a full backup or incremental backup of the SAP for Oracle database when it is online.

The following table describes the available backup interfaces.

Interface Description
util_file The software locks the Oracle database until the backup completes.
util_vol The software locks the entire Oracle database until the backup completes.
util_vol_online The software locks each volume that is being backed up and releases it when the backup completes.

Before You Begin

Procedure

  1. From the CommCell Browser, expand Client Computers > client > Agent.
  2. Right-click the instance, point to All Tasks and then click New Subclient.

    The Create New Subclient dialog box is displayed.

  3. On the General tab, in the Subclient name box, enter a name for the subclient.
  4. On the Content tab:
    • Select the Data check box.
    • Select the Consistent Online option.
    • Select the backup interface. If this subclient will be used for incremental backups, in the Backup Device section, select the Rman_util option.
  5. On the Storage Device tab, select the name of the Data Storage Policy.
  6. Optional: Include the logs. On the Log Backups tab:
    • Select the Backup Archive Log check box.
    • Optional: To delete the logs after the backup completes, select the Archive Delete check box.
    • Optional: To disable log switching for the current redo log, select the Disable Switch Current Log check box.
    • Optional: To create a second copy of the archived offline redo log files, select the Archive Log Second Copy check box.
  7. On the  IntelliSnap Operations tab.
    • Select the IntelliSnap check box.
    • From the Available Snap Engines list, select the appropriate engine.
  8. On the Storage Device tab, in the Log Storage Policy list, select the storage policy name for the log backups.
  9. Optional: Run scripts before or after the backup.

    You can choose to run the post-process script even if the backup job failed.

    On the Pre/Post tab:

    1. In the Pre-Backup Command box, type the full path name for the script.
    2. In the PostBackup Command 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 Process for all attempts check box.
  10. Click OK to close the Creating New Subclient dialog box.

Configuring Subclients for Datafiles and Tablespaces Backups

SAP on Oracle datafiles store the physical data. SAP on Oracle tablespaces contain the logical information (indexing and mapping) for datafiles.

You can create subclients for specific datafiles and tablespaces that frequently change or have a different backup schedule than the entire database.

The following table describes the available backup interfaces.

Interface Description
util_file The software locks the Oracle database until the backup completes.
util_vol The software locks the entire Oracle database until the backup completes.
util_vol_online The software locks each volume that is being backed up and releases it when the backup completes.

Before You Begin

Procedure

  1. From the CommCell Browser, expand Client Computers > client > Agent.
  2. Right-click the instance, point to All Tasks and then click New Subclient.

    The Create New Subclient dialog box is displayed.

  3. On the General tab, in the Subclient name box, enter a name for the subclient.
  4. On the Content tab.
    • Select the Online Subset option.
    • Click Yes on the Warning dialog box.
    • From the Current Database View, select the database objects you want to include.
    • Select the backup interface. If this subclient will be used for incremental backups, in the Backup Device section, select Rman_util.
  5. On the  IntelliSnap Operations tab.
    • Select the IntelliSnap check box.
    • From the Available Snap Engines list, select the appropriate engine.
  6. On the Storage Device tab, in the Log Storage Policy list, select the storage policy name for the log backups.
  7. Optional: Run scripts before or after the backup.

    You can choose to run the post-process script even if the backup job failed.

    On the Pre/Post tab:

    1. In the Pre-Backup Command box, type the full path name for the script.
    2. In the PostBackup Command 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 Process for all attempts check box.
  8. Click OK to close the Creating New Subclient dialog box.

Specifying the Location for the SAPBACKUP Directory

Set the <SID>_sSAPBACKUP additional to specify the location of the SAPBACKUP directory that is under the SAPDATA directory.

Procedure

IntelliSnap Backup for SAP Split-Mirror Disks (Splitint Support)

You can perform IntelliSnap backups on the SAP Oracle database files of the split-mirror disks. You must perform these backups on a backup (proxy) server instead of a production server using BRBACKUP tool through the Splitint Interface. This will allow you to offload your production server from data protection operations as these operations are now moved and performed on the proxy server. You can control the splitting and synchronization of the split-mirror disks using BRBACKUP. BRBACKUP also communicates with the production database to obtain the information about the database structure and stores all results of the backups. This process allows the Computing Center Management System (CCMS) to monitor the backups in the SAP production system.

You can use the backint util_file interface to perform an IntelliSnap backup of the split-mirror disks on the production server. Later, you can even mount these snapshots on the proxy or production server and copy any data file needed. You can also perform restores on the production or proxy server either from the snapshots or the snap copies depending upon the selected copy precedence.

Configuring BRBACKUP for Split-Mirror Disk Backups

You must configure a SAP Oracle instance for both the source and proxy client. You must configure the following on the production and proxy servers before performing split-mirror disk backups using BRBACKUP: 

  1. We would need to create the SAP Instance from CommCell GUI for both Source and Proxy client. Install the Oracle SID on both the production and proxy servers. Make sure to install the same Oracle SID and maintain the same directory structure on both the production and proxy servers.

    Add the following parameter in the $ORACLE_HOME/dbs/init<SID>.utl file:

    CvSrcClient

    <Source_Client_Name>

    Example:

    Production=tigersnap
    Proxy=tigersnap2

    $ORACLE_HOME/dbs/init<SID>.utl file on the Proxy
    CvSrcClient
    tigersnap

  2. Configure the Snap-able volumes on the production server.

    Example:

    [root@tigersnap ~]# df -k
    Filesystem 1K-blocks Used Available Use% Mounted on
    /dev/mapper/VolGroup00-LogVol00
    32408432 30528060 207568 100% /
    /dev/sda1 101086 14827 81040 16% /boot
    tmpfs 972264 0 972264 0% /dev/shm
    /dev/sdj1 1031888 17736 961736 2% /home/oracle/product/10g/dbs
    /dev/sdg1 5156292 1373028 3521336 29% /home/oracle/product/10g/CER
    /dev/sdh1 3093976 831496 2105312 29% /home/oracle/product/10g/CER/DATA
    /dev/sde1 2062716 118036 1839900 7% /home/oracle/product/10g/CER/LOG
    [root@tigersnap ~]# ls -l /home/oracle/product/10g/CER
    total 48
    drwxrwx--- 9 oracle oracle 4096 Apr 27 17:52 DATA
    drwxrwx--- 7 oracle oracle 4096 May 29 16:34 LOG
    drwxrwxrwx 2 oracle oracle 16384 Apr 27 10:56 lost+found
    drwxrwxr-x 3 oracle oracle 4096 May 30 02:00 saparch
    drwxrwxr-x 2 oracle oracle 4096 May 29 16:37 sapbackup
    drwxrwxr-x 2 oracle oracle 4096 Apr 27 11:13 sapcheck
    drwxrwxr-x 2 oracle oracle 4096 Apr 30 11:11 sapreorg
    drwxrwxr-x 3 oracle oracle 4096 Apr 27 11:13 sapscripts
    drwxrwxr-x 4 oracle oracle 4096 Apr 27 11:13 saptrace
    [root@tigersnap ~]# ls -l /home/oracle/product/10g/CER/LOG
    total 76
    drwxrwxr-x 2 oracle oracle 4096 May 29 16:34 mirrlogA
    drwxrwxr-x 2 oracle oracle 4096 May 29 16:34 mirrlogB
    -rw-r----- 1 oracle oracle 2560 Oct 22 2010 orapwCER
    drwxrwx--- 2 oracle oracle 4096 May 29 16:34 origlogA
    drwxrwx--- 2 oracle oracle 4096 May 29 16:34 origlogB
    -rw-r----- 1 oracle oracle 2560 May 29 11:59 orapwCER
    [root@tigersnap ~]#

  3. Configure the volumes on the proxy server. Make sure that the data, logs, control files and the mirror are configured on separate volumes. This is to ensure that the sapbackup directory on the proxy is not replaced when you mount the snapshots /split-mirror disks on the proxy server.
  4. Configure the SSH with user equivalence (RSA Key sharing) between OraSID's on both the proxy server and production server. If you do not configure the SSH sharing, you will be prompted for the account passwords multiple times.

    You should meet the following User equivalency requirements:

    • You should have the same user name, UID and password on both the production and proxy servers
    • You should belong to the same group with the same group ID.
    Example:

    Make sure you get the same results on the production and the proxy:

    [oracle@tigersnap 10g]$ id oracle uid=501(oracle) gid=501(oracle) groups=501(oracle),502(dba)
    [oracle@tigersnap2 10g]$ id oracle
    uid=501(oracle) gid=501(oracle) groups=501(oracle),502(dba)

  5. Configure the Oracle Parameters on SID of both the production and proxy servers. Setup *.ora, *.sap, *.utl parameters on both the Production and Proxy servers.
  6. Configure the TNS names on the production and proxy servers.

    Example:

    [oracle@tigersnap admin]$ pwd
    /home/oracle/product/10g/network/admin
    [oracle@tigersnap admin]$ more tnsnames.ora
    # tnsnames.ora Network Configuration File: /home/oracle/product/10g/network/admin/tnsnames.ora
    # Generated by Oracle configuration tools.

    ORCL =
    (DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = tigersnap.commvault.com)(PORT = 1521))
    (CONNECT_DATA =
    (SERVER = DEDICATED)
    (SERVICE_NAME = orcl)
    )
    ) CER =
    (DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = tigersnap.commvault.com)(PORT = 1521))
    (CONNECT_DATA =
    (SERVER = DEDICATED)
    (SERVICE_NAME = CER)
    )
    ) CER.tigersnap =
    (DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = tigersnap.commvault.com)(PORT = 1521))
    (CONNECT_DATA =
    (SERVER = DEDICATED)
    (SERVICE_NAME = CER)
    )
    ) CER.tigersnap2 =
    (DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = tigersnap2.commvault.com)(PORT = 1521))
    (CONNECT_DATA =
    (SERVER = DEDICATED)
    (SERVICE_NAME = CER)
    )
    ) EXTPROC_CONNECTION_DATA =
    (DESCRIPTION =
    (ADDRESS_LIST =
    (ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1))
    )
    (CONNECT_DATA =
    (SID = PLSExtProc)
    (PRESENTATION = RO)
    )
    )

  7. Add the service name entries on the production server.

    Example:

    [oracle@tigersnap 10g]$ lsnrctl stop
    LSNRCTL for Linux: Version 10.2.0.1.0 - Production on 06-OCT-2011 03:00:02
    Copyright (c) 1991, 2005, Oracle. All rights reserved.
    Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC1)))
    The command completed successfully

    [oracle@tigersnap 10g]$ sqlplus "/ as sysdba" SQL*Plus: Release 10.2.0.1.0 - Production on Thu Oct 6 03:00:13 2011
    Copyright (c) 1982, 2005, Oracle. All rights reserved.
    Connected to:
    Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
    With the Partitioning, OLAP and Data Mining options
    SQL> shutdown immediate;
    Database closed.
    Database dismounted.
    ORACLE instance shut down.
    SQL> startup nomount
    ORACLE instance started.
    Total System Global Area 88080384 bytes
    Fixed Size 1217836 bytes
    Variable Size 79694548 bytes
    Database Buffers 4194304 bytes
    Redo Buffers 2973696 bytes
    SQL> show parameters service_names
    NAME TYPE VALUE
    ------------------------------------ ----------- ------------------------------
    service_names string CER
    SQL> alter system set service_names='CER,CER.tigersnap'
    2 ;
    System altered.
    SQL> show parameters service_names; NAME TYPE VALUE
    ------------------------------------ ----------- ------------------------------
    service_names string CER,CER.tigersnap
    SQL> shutdown immediate
    ORA-01507: database not mounted
    ORACLE instance shut down.
    SQL> startup
    ORACLE instance started.
    Total System Global Area 88080384 bytes
    Fixed Size 1217836 bytes
    Variable Size 79694548 bytes
    Database Buffers 4194304 bytes
    Redo Buffers 2973696 bytes
    Database mounted.
    Database opened.
    SQL> quit
    Disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
    With the Partitioning, OLAP and Data Mining options
    [oracle@tigersnap 10g]$ lsnrctl start
    LSNRCTL for Linux: Version 10.2.0.1.0 - Production on 30-MAY-2012 21:12:37
    Copyright (c) 1991, 2005, Oracle. All rights reserved.
    Starting /home/oracle/product/10g/bin/tnslsnr: please wait...
    TNSLSNR for Linux: Version 10.2.0.1.0 - Production
    System parameter file is /home/oracle/product/10g/network/admin/listener.ora
    Log messages written to /home/oracle/product/10g/network/log/listener.log
    Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC1)))
    Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=tigersnap.commvault.com)(PORT=1521)))
    Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC1)))
    STATUS of the LISTENER
    ------------------------
    Alias LISTENER
    Version TNSLSNR for Linux: Version 10.2.0.1.0 - Production
    Start Date 30-MAY-2012 21:12:39
    Uptime 0 days 0 hr. 0 min. 0 sec
    Trace Level off
    Security ON: Local OS Authentication
    SNMP OFF
    Listener Parameter File /home/oracle/product/10g/network/admin/listener.ora
    Listener Log File /home/oracle/product/10g/network/log/listener.log
    Listening Endpoints Summary...
    (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC1)))
    (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=tigersnap.commvault.com)(PORT=1521)))
    Services Summary...
    Service "CER" has 1 instance(s).
    Instance "CER", status UNKNOWN, has 1 handler(s) for this service...
    Service "PLSExtProc" has 1 instance(s).
    Instance "PLSExtProc", status UNKNOWN, has 1 handler(s) for this service...
    The command completed successfully
    [oracle@tigersnap 10g]$

  8. Configure the InitSID.* on the Production server.
    1. Add the following to initCER.sap

      RMAN_PARMS="BLKSIZE=1048576,SBT_LIBRARY=/opt/commvault/Base/libobk.so,
      ENV=(CvClientName=tigersnap,CvInstanceName=instance001)"
      _rman_sess_stmt = ("alter session set optimizer_mode=RULE")

    2. Add the following to initCER.ora

      remote_login_passwordfile = EXCLUSIVE
      control_file_record_keep_time = 100

    3. Add the following to initCER.utl

      CvInstanceName
      Instance001
      snapBackup
      1
      numstreams
      1
      CV_restCopyPrec
      0

  9. Configure the InitSID.* on the Proxy server.
    1. Add the following to initCER.sap

      primary_db = CER.tigersnap
      stage_copy_cmd = scp
      pipe_copy_cmd = ssh
      rman_channels = 1
      rman_filesperset = 64

      Example

      RMAN_PARMS="BLKSIZE=1048576,SBT_LIBRARY=/opt/commvault/Base/libobk.so,
      ENV=(CvClientName=tigersnap2,CvInstanceName=instance001,CvSrcClient=tigersnap)"
      _rman_sess_stmt = ("alter session set optimizer_mode=RULE")

    2. Add the following to initCER.ora

      control_file_record_keep_time = 100

    3. Add the following to initCER.utl

      CvInstanceName
      Instance001
      snapBackup
      0
      numstreams
      1

  10. The Snapshots/Split-mirror disks will be mounted (in place) on the proxy server. Make sure that those pertinent directories are empty on the proxy.
  11. Install the SAP Oracle iDataAgent on both the production and proxy servers.
  12. Configure the instance for the production server in the CommCell Console. See Configuration for instructions on how to configure an instance,

Additional Configuration Required for Offline Mirror on the Production Server:

  1. Create an Oracle password file using the following command.

    orapwd file=<ORACLE_HOME>/dbs/orapw<DBSID> password=<SYS password> entries=10

    Example

    oracle@tigersnap 10g]$ orapwd file=/home/oracle/product/10g/dbs/orapwCER password=manager entries=10 force=Y

  2. Configure the remote_login_passwordfile parameter to exclusive in the init<DBSID>.ora profile.
  3. Authorize the system user with SYSOPER authorization in the production server.
  4. Start the SQLPLUS as user SYS and execute the Oracle command:

    If needed, change the password for the system user.

    SQL> connect / as sysdba SQL> grant sysoper to system;

    Change the password for the system user:

    SQL> alter user system identified by <password>;

Performing Split-Mirror Disk Backups Using BRBACKUP

Use the BRBACKUP tool through Splitint interface on the proxy server instead of production server with either an online_mirror or offline_mirror for performing split-mirror disk backups. Use the util_file interface to perform these backups.

  • Use the following BRBACKUP command to perform split-mirror disk backups with online_mirror using util_file interface:

    brbackup -d util_file -t online_mirror -m all -c

  • Use the following BRBACKUP command to perform split-mirror disk backups with offline_mirror using util_file interface:

    brbackup -d util_file -t offline_mirror -m all -c

IntelliSnap Backup on NFS Volume

You can perform IntelliSnap backup of SAP for Oracle when the database is on a NFS Volume. However, you will require a root access in the storage device's NFS configuration to be able to read and write on the accessible SAP for Oracle files i.e., the host on which the NFS Volume is mounted.

You can also perform IntelliSnap backup of SAP for Oracle if the database resides on a Direct NFS volume. IntelliSnap backup supports volumes using the Oracle Direct NFS (dNFS) protocol.

File level revert is performed by default when revert restore is run on NFS volumes. For Volume Level revert on NFS volumes, use the sUSE_FILE_LEVEL_REVERT Additional Setting. File level revert cannot be performed when the database resides on regular SAN Volumes (LUNs).

Consider the following while performing an IntelliSnap backup for data or databases that reside on an NFS Volume:

  • The export name on the storage device should be the same as the storage path on the storage device.

    E.g., if the storage path of the storage device is /vol/Volume/Qtree, use /vol/Volume/Qtree as the export name and not an alias such as /ExportName.

  • You can use the exports both at the root of a NetApp volume and at subdirectory levels below the root of the volume.
  • Make sure that the storage device is accessible from the source and proxy machine (even if they exist in different domains) using the storage device's short name while mounting NFS exports from the storage device. Make sure to enter the storage device credentials using its short name. Do not use an IP address or the fully qualified domain name.

    E.g., use a short name for the server such as server1 or server2.

Enabling Volume Level Reverts on NFS Volumes

  1. From the CommCell Browser, navigate to Client Computers.
  2. Right-click the <Client>, and then click Properties.
  3. Click Advanced and then click Additional Settings tab.
  4. Click Add.
  5. In the Name field, type sUSE_FILE_LEVEL_REVERT.

    The Category and Type fields are populated automatically.

  6. In the Value field, type N.
  7. Click OK.