Loading...

Advanced Configuration - Oracle RAC iDataAgent

Table of Contents
  • Configuring Table Restores
  • Configuring Archive Log Destinations
  • Disabling Log Switch
  • Enabling Log Deletion after Backup
  • Configuring the Connect String with a Physical Hostname and Service Name
  • Changing the Oracle Home Directory
  • Changing the TNS ADMIN Directory
  • Configuring Shutdown and Startup Scripts for Offline Backups
  • Including the Server Parameter (SP) File during Backups
  • Enabling Backups of Flash Recovery Area
  • Configuring User Accounts for Backups
  • Using Recovery Catalog for Backups
  • Configuring Streams for Backups
  • Configuring Multiple Data Paths for Load Sharing
  • Enhancing Backup Performance
  • Assigning Unique Identification Tags for Backups
  • Excluding Data during Backups
  • Simulating a Backup
  • Specifying the Media Parameters for RMAN Command Line Operations
  • Disabling the RMAN Crosscheck
  • Enabling Multiple Backup Copies
  • Configuring the Backup Piece Format
  • Using the Connect String Instead of OS Authentication to Connect to the Oracle RAC Database
  • Specifying the Servers that Run Backups in an Oracle Data Guard Configuration
  • Modifying an Agent, Instance, or Subclient
  • Deleting an Agent, Instance or Subclient
  • Understanding the CommCell Console

    The Oracle RAC iDataAgent uses the following logical entities to manage backup and restore operations from the CommCell Console.

    Agent

    Facilitates Oracle instance discovery.

    Instance

    Defines the Oracle database to be backed up.

    Subclient

    Defines the Oracle database objects to be backed up.

    Creating a Pseudo-Client for Oracle RAC

    Once the Oracle Data Agent is installed on all the RAC database nodes, create a new Oracle RAC pseudo-client that  is a logical grouping of Oracle instances in the Oracle RAC instance.

    1. From the CommCell Bowser, right-click Client Computers, point to New Client > Application and then click Oracle RAC.

      The Create Oracle RAC Client dialog box is displayed.

    2. On the General tab, provide the pseudo-client details.
      1. In the Pseudo-client Name box, type a name for the RAC client.
      2. In the Database Name box, type the name of the RAC database to which you are assigning this client.

        The Database Name must be of the same case as the name of the Oracle RAC database.

        Example:

        SQL> select name from v$database;
        NAME
        ---------
        db1

      3. From the Storage Policy list, select the storage policy used for default subclient data.

        If you do not have a storage policy, Create a Storage Policy.

    3. On the Details tab, determine how you want to connect to Oracle.
      Option Configuration
      Oracle Wallet Auto Login

      You can use this option when you have configured the Secure External Password Store (Oracle Wallet) feature that stores password credentials, and you want to use those credentials during the data protection operations. For more information on the Secure External Password Store, go to the Oracle documentation website, Secure External Password Store.

      1. Select the Oracle Wallet Auto Login check box.
      2. Enter the Oracle Service Name in the Connect String third box.

      Note: If you provide the user name and password, the software ignores the Oracle Wallet feature.

      Use the Oracle Catalog Connect String Select the Use Connect String check box and in the Connect String box enter the Oracle connect string credentials.

      Note: If you want to use an account other than 'sys', you must grant the SYSDBA or SYSBACKUP (in Oracle version 12 or higher) privilege to the user account.

      Enter the Catalog Connect String to connect to the Oracle database.

      1. Enter the database user name in the Connect String first box.
      2. Enter the database user password in the Connect String second box.
      3. In the Confirm Password dialog box, re-enter the password, and click OK.
      4. Enter the Oracle service name in the Connect String third box.

      For example, in the following:

      sysdba/<password>@orcl

      sysdba is the database user id

      <password> is the database user id password

      orcl is the Oracle service name

    4. On the Details tab, add the Oracle instances.
      1. Click Add.

        The Add Instance dialog box is displayed.

      2. From the Instance Physical Client list, select the client name of the Oracle instance.
      3. In the Instance (ORACLE SID) box, type the name of the Oracle instance.
      4. Click Change User Account and type the Oracle user name and password.
      5. In the ORACLE HOME box, type or click Browse to locate the Oracle application install path.
      6. In the Connect String box, type the Oracle database user with privileges to access the Oracle database in the Oracle RAC node .

        Use the SYS login for example, sys/password@Service for the connect string. For example, sys/pwd12@orcl4.

      7. In the TNS_ADMIN Folder, type the path for the TNS_Admin directory.
      8. Click OK to close the Add Instance dialog box.
      9. Repeat the previous steps for each instance that you want to add.
    5. On the Storage Device tab, configure the storage policy information.
      1. From the Storage Policy used for user command backup of data list, select the data backup storage policy name.
      2. Click the Logs Backup tab.
      3. In the Storage Policy used for all Archive Log backups box, select the log backup storage policy name.
    6. Click OK.

    Managing Instances

    You create Oracle RAC instances as part of the procedure that you use to create an Oracle RAC pseudo-client. You can create multiple Oracle database instances in the CommCell Console by configuring an Oracle RAC pseudo-client. For information on how to configure a n Oracle RAC pseudo-client, see Creating an Oracle RAC Pseudo-Client.

    You must install the Oracle Agent on at least one node in the Oracle RAC instance. You cannot remove that node from the Oracle RAC instance unless you have more than 1 configured Oracle RAC node. When you delete a node from the Oracle RAC instance, the software does not delete the backup data. You can restore the data by using another eligible client.

    Creating Multiple Instances Under an Existing Oracle RAC Pseudo-Client

    You can use this procedure when you want to add multiple instances for an Oracle RAC pseudo-client.

    You must follow these rules when you add a new Oracle RAC instance:

    • Use the SYS login as the Connect string to connect to the database.
    • Do not include "/" when you select the Use SQL Connect option because there are multiple nodes.

    If you want to use a SCAN connect string for an instance, set the Connect string to: username/password@physical-nodename:1521/service name. The service name is the database name. Use the physical node name in the scan Connect string because the backup process requires a pre-identified node for backup resource reservation.

    Example: sys/sys@devrac11gr2-1.xyzcompany.com:1521/DEVRAC11.xyzcompany.com

    Before You Begin

    Procedure

    1. From the CommCell Bowser, right-click Client Computers > RAC_Client > instance and then click New RAC Database.

      The New RAC Instance dialog box is displayed.

    2. On the General tab, enter the database details.
      1. In the Database Name box, type the name of the Oracle RAC database.
      2. From the Storage Policy used for user command backup of data list, select the data backup storage policy name.
    3. On the Details tab, add the Oracle instances. Click Add.

      The Add Instance dialog box is displayed.

    4. From the Instance Physical Client list, select the physical client.
    5. In the Instance (ORACLE SID) box, type the Instance name.
    6. Click the Change User Account.
    7. In the User Account box, type the user account name.
    8. In the Enter Password box, type the password for the user account.
    9. In the Confirm Password box, type re-type the password for the user account.
    10. Click OK.
    11. In the TNS_ADMIN folder box, type the TNS_ADMIN folder name.
    12. Click OK.

    Manually Adding an Oracle RAC Node to an Existing Instance

    You can use this procedure when you want to add a new Oracle RAC node to an existing Oracle RAC instance.

    This procedure is similar to the one that you use to add a new database to the Oracle RAC pseudo-client. You add the Oracle RAC nodes in each procedure.

    You must follow these rules when you add a new Oracle RAC node:

    • Use the SYS login as the Connect string to connect to the database.
    • Do not include "/" when you select the Use SQL Connect option because there are multiple nodes.

    If you want to use a SCAN connect string for an instance, set the Connect string to: username/password@physical-nodename:1521/service name. The service name is the database name. Use the physical node name in the scan Connect string because the backup process requires a pre-identified node for backup resource reservation.

    Procedure

    1. From the CommCell Bowser, right-click Client Computers > RAC_Client.
    2. Right-click the instance and click Properties.

      The Instance Properties dialog box is displayed.

    3. On the Details tab, click Add.

      The Add Instance dialog box is displayed.

    4. From the Instance Physical Client list, select the physical client.
    5. In the Instance (ORACLE SID) box, type the Instance name.
    6. Click the Change User Account.
    7. In the User Account box, type the user account name.
    8. In the Enter Password box, type the password for the user account.
    9. In the Confirm Password box, type re-type the password for the user account.
    10. Click OK.
    11. In the TNS_ADMIN folder box, type the TNS_ADMIN folder name.
    12. Click OK.

    Configuring an Oracle RAC One Node

    In a RAC one node configuration, a single instance of an Oracle RAC database runs on one node of the cluster while the second instance is in a cold standby mode. If there is a failure or fault in the first node and the instance cannot be restarted on the same node, then RAC One node cluster detects it and relocates the instance to the other node. The benefit of this feature is that it automates the instance relocation without any downtime and manual intervention. In this configuration, you must use unique instance names while configuring instances on both nodes.

    See Creating a RAC Client for more information.

    The RAC one nodes can have multiple ways of running the instances.

    1st - Node 1 running instance_1

    2nd - Node 1 running instance_2

    3rd - Node 2 running instance_2

    4th - Node 2 running instance_1

    When you configure a RAC one database in SnapProtect, you must configure unique instances, by associating the instances with physical clients.  SnapProtect automatically detects the instances relocation and connects the available instance.

    Example of Instance and Client Combination

    1st - Node 1 running instance_1

    2nd - Node 1 running instance_2

    Example

    The RAC database name is "testracdb".

    The instances are "testracdb_1" and "testracdb_2".

    If Node 1 is active, the instance "testracdb_1" runs on Node 1. If the instance is relocated to Node 2 due to a failure or abnormal termination, then the instance "testracdb_1" runs on Node 2.

    Another option is to have Node 2 running "testracdb_2". If Node 2 fails to start "testracdb_2", it is relocated to Node 1. In this case, Node 1 runs "testracdb_2".

    The SnapProtect software supports the above configurations. In the CommCell Console, configure "testracdb_1" under Node 1 and "testracdb_2" under Node 2.

    Use the following steps to configure the RAC on one node:

    1. From the CommCell Browser, navigate to Client Computers > RAC_Client.
    2. Right-click the instance and click Properties.

      The Instance Properties dialog box is displayed.

    3. On the Details tab, click Add.

      The Add Instance dialog box is displayed.

    4. In the Instance Physical Client list, select the Instance Physical client name.
    5. In the Instance (ORACLE SID) box, type the instance names for the instances in the other nodes. For example, type the Instance name as testracdb_1 for Instance_1. Type the Instance name as testracdb_2 for Instance_2.
    6. In the Database Name box, type the name of the Oracle RAC database (for example, testracdb) to which you are assigning this client.
    7. In the Connect String box, type the Scan Connect String (SYS login).

      Best Practice: Use the physical node name in the scan connect because the backup process requires pre-identified node for backup resource reservation.

      Examples:

      Node 1 Connect String: sys/password1@node1:1521/testracdb

      Node 2 Connect String: sys/password1@node2:1521/testracdb

      You must use scan connect to configure the RAC one node in a multiple node environment.

       Click OK to close the warning dialog box.

    8. In the Oracle Home box, type the Oracle installed path.
    9. In the TNS_ADMIN Folder box, type the TNS ADMIN folder name.
    10. Click the Storage Device tab. in the Storage Policy used for user command backup of data box, select a storage policy.
    11. Click the Log Backup tab. in the Storage Policy used for all Archive Log backups box, select a storage policy name.
    12. Click OK.

    See Can you restore from a RAC One Node in a multiple node configuration for important considerations that you must follow when you restore from a RAC One Node.

    Note: Use the  for Restore option when you perform a restore.

    Configuring Policy Based Oracle RAC

    In an Oracle RAC policy based configuration, the resources run in a shared infrastructure. The infrastructure consists of a server stack that are logically split into groups that are referred to as server pools. Each pool can contain one or more servers.  In this configuration, instances run a respective node. The policy based Oracle RAC Cluster configuration detects when an instanced cannot be restarted on the same node due to a fault or failure and automatically relocates the instance to another node in the same server pool.

    You can use this configuration when you need automated instance relocation without any downtime or manual intervention.

    Note: You must use unique instance names for the instances on the original and relocation nodes.

    See Creating a RAC Client for more information.

    The RAC one nodes can have multiple ways of running the instances. Consider the following:

    1st - Node 1 running instance_1

    2nd - Node 1 running instance_2

    3rd - Node 2 running instance_3

    4th -No running instances

    When you configure a RAC Policy based database in SnapProtect, you must configure unique instances, by associating the instances with physical clients.  SnapProtect automatically detects the instances relocation and connects the available instance.

    Example of Instance and Client Combination

    1st - Node 1 running instance_1

    2nd - Node 1 running instance_2

    3rd - Down for maintenance

    4th - Node 4 running instance_3 that was relocated from the 3rd node

    Example

    The RAC database name is "testracdb".

    The instances are "testracdb_1" and "testracdb_2", "testracdb3", and "testracdb_4".

    If Node 1 is active, the instance "testracdb_1" runs on Node 1. If the instance is relocated to Node 2 due to a failure or abnormal termination, then the instance "testracdb_1" runs on Node 2.

    Another option is to have Node 2 running "testracdb_2". If Node 2 fails to start "testracdb_2", it is relocated to Node 1. In this case, Node 1 runs "testracdb_2".

    The SnapProtect software supports the above configurations. In the CommCell Console, configure "testracdb_1" under Node 1 and "testracdb_2" under Node 2.

    Use the following steps to configure the RAC on one node:

    1. From the CommCell Browser, navigate to Client Computers > RAC_Client.
    2. Right-click the instance and click Properties.

      The Instance Properties dialog box is displayed.

    3. On the Details tab, click Add.

      The Add Instance dialog box is displayed.

    4. In the Instance Physical Client list, select the Instance physical client name.
    5. In the Instance (ORACLE SID) box, type the Instance name as testracdb_1 for Instance_1. Type the Instance name as testracdb_2 for Instance_2
    6. In the Database Name box, type the name of the Oracle RAC database (testracdb) to which you are assigning this client.
    7. In the Connect String box, type the Scan Connect String (SYS login).

      Best Practice: Use the physical node name in the scan connect because the backup process requires pre-identified node for backup resource reservation.

      Examples:

      Node 1 Connect String: sys/password1@node1:1521/testracdb

      Node 2 Connect String: sys/password1@node2:1521/testracdb

      You must use scan connect to configure the RAC one node in a multiple node environment.

       Click OK to close the warning dialog box.

    8. In the Oracle Home box, type the Oracle installed path or click Browse to select the location.
    9. In the TNS_ADMIN Folder box, type the TNS ADMIN folder name or click Browse to select the location.
    10. Click the Storage Device tab. in the Storage Policy used for user command backup of data box, select a storage policy.
    11. Click the Log Backup tab. in the Storage Policy used for all Archive Log backups box, select a storage policy name.
    12. Click OK.

    See Can you restore from a RAC One Node in a multiple node configuration for important considerations that you must follow when you restore from a RAC One Node.

    Note: Use thefor Restore option when you perform a restore.

    Configuring the Client for Unified Oracle Data Guard

    An Oracle Data Guard configuration contains a production (primary) and standby database so that you can have high availability in the case of a disaster. The standby database becomes the primary database when the primary database has a planned or unplanned outage.

    Overview

    When you configure the SnapProtect software for Oracle Data Guard, the software discovers the instance role (primary or standby) and then picks the appropriate client storage policy or the appropriate instance storage policy for the data and the log backups. You can configure the software to run the database and the log backups on different instances that also have different roles.

    You configure an Oracle RAC pseudo-client that contains all the primary and standby nodes. The nodes can be on the same or different data centers. By default, the software uses the pseudo-client storage policies.

    You can configure storage policies for the physical clients that host the primary and standby servers. When the primary and standby servers are at different data centers and a failover occurs, the software cannot use the storage policies that you configured for the pseudo-client, because it needs access to a local MediaAgent. After a failover, the software uses the physical client storage policies and automatically reconfigures them to use the location aware MediaAgent.

    Before You Begin

    • Make sure that you have the list of all the primary instances and the standby instances that are part of the configuration along wit the user credentials for each instance.

    Procedure

    1. Allow the Oracle RAC nodes to Have the same database name.

    2. Specify the Servers that Run Backups in an Oracle Data Guard Configuration.

    3. Create a pseudo-client for Oracle RAC.

      Note: You must add all of the primary and standby databases to the pseudo-client.

    4. If your primary and standby databases are on different data centers, you must configure a storage policy for all clients that host the primary and standby databases.
      1. Allow storage policy configuration for physical clients.
      2. For each primary and standby client, configure the client storage policy.

    Configure a Client Storage Policy for Unified Oracle Data Guard

    If you use an Oracle Data Guard configuration that has the primary databases and the standby databases in different data centers, set the storage policies on each client so that the software uses the local MediaAgent after a failover.

    Procedure

    1. From the CommCell Browser, expand Client Computers > client.
    2. Right-click the client and then click Properties.
    3. On the General tab:
      1. From the Data Storage Policy list, select the data storage policy that the software uses for data backups when a failover occurs.
      2. From the Log Storage Policy list, select the data storage policy that the software uses for log backups when a failover occurs.
    4. Click OK.

    Adding Container Databases (CDB)

    In the CommCell Console each Oracle 12c container database (CDB) maps to an instance. Once you have added an instance for the container database, create subclients and backup sets as you would for any Oracle database instance.

    1. From the CommCell Browser, navigate to Client Computers |< Client >.
    2. Right-click Oracle, point to All Tasks, and then click New Instance (ORACLE SID).
    3. On the General tab of the Creating New Instance dialog box:
      • In the Instance (ORACLE SID) box, type the container database name.
      • In the User Account box, type the login credentials to access the Oracle container database.
      • In the ORACLE HOME box, type the Oracle container database application install path.
      • In the Storage Policy used for the data of default subclient box, select a storage policy name.
    4. On the Details tab of the Creating New Instance dialog box:
      • In the Connect String box, type the credentials to access the Oracle container database. For example, sys/pwd12@orcl4.
    5. On the Storage Device tab of the Creating New Instance dialog box:
      • In the Storage Policy used for user command backup of data box, select a storage policy.
      • In the Storage Policy used for all Archive Log backups box, select a storage policy name.
    6. Click OK.

    Managing Subclients

    The Oracle RAC iDataAgent is designed to back up and restore an Oracle RAC database (*.dbf) along with control files (*.ctl) and archived redo log files. After you create an Oracle RAC pseudo-client, a default subclient is created by the system only after you first configure an Oracle database instance from the CommCell Console. Since an Oracle RAC instance references a RAC database, the default subclient includes the entire database associated with that instance. However, you can use the CommCell Console to create user-defined subclients to include only some of the database content by configuring the Subclient Properties (Content) tab. Any content that is not included in the user-defined subclients will remain in the default subclient.

    You can create user-defined subclients to backup the specific components or conditions, such as the following:

    • Whether a backup will be offline or online.
    • Whether the entire database will be backed up, or only a subset of objects within the database should be backed up.
    • Whether the archive logs need to be backed up separately
    • Manage your archive log and control file backups.

    If a new database object is added to the database, and if none of the subclients contain that database object, then that object is automatically assigned to the content of the default subclient.

    When you choose not to select catalog database at the instance level, clear the Resync Recovery Catalog check box in the subclient level.

    Creating a Subclient for Offline Backups

    During an offline backup, the database is shutdown and is not available for use. The full backup includes all the datafiles, tablespaces, and control file of the Oracle database. Note that, offline backups do not include the archived log files.

    Offline backups can be performed when the database is in offline or online mode. If the database is online, it shuts down the database, performs the backup and then brings up the database back.

    In order to backup the Oracle database when it is offline, you need to create a separate user-defined subclient for offline backup. Make sure that the database is in the MOUNT mode during the backup.

    Before You Begin

    Procedure

    1. From the CommCell Browser, navigate to Client Computers | <RAC Client>.
    2. Right-click the <Instance>, point to All Tasks, and then click New Subclient.
    3. In the Subclient Name box, type the subclient name.
    4. Click the Content tab.
    5. Click Offline Database.
    6. Click the Storage Device tab.
    7. In the Data Storage Policy box, select the storage policy name.
    8. Click OK.

    Creating a Subclient for Online Backups

    In some environments, it may not be possible to bring down the entire database to perform an offline backup. In such situations, you can choose online backups, where the database will be up and running during the backup. 

    You can perform either a full backup or incremental backup of the Oracle database when it is online. Since full backups includes all the datafiles, tablespaces and logs, it is very time consuming, hence you can plan for a full online backup less frequently (say, on weekly basis). On the other hand, incremental backups includes the data and logs that have been changed after the last full backup, they are faster and can be performed more frequently (say, on a daily basis).

     If a new database object is added to the database, and if none of the subclients contain that database object , then that object is assigned to the content of the default subclient

    Before You Begin

    Procedure

    1. From the CommCell Browser, navigate to Client Computers | <RAC Client>.
    2. Right-click the <Instance>, point to All Tasks, and then click New Subclient.
    3. In the Subclient Name box, type the subclient name.
    4. Click the Content tab.
    5. Click Online Database.
    6. Click the Storage Device tab.
    7. In the Data Storage Policy box, select the Storage policy.
    8. Click OK.

    Creating a Subclient to Back Up Individual Datafiles and Tablespaces

    You can also create subclients to backup specific datafiles and tablespaces, which undergo frequent changes in the Oracle database.

    Use the following steps to create a subclient to backup individual datafiles and tablespaces:

    1. From the CommCell Browser, navigate to Client Computers | <RAC Client>.
    2. Right-click the <Instance>, point to All Tasks, and then click New Subclient.
    3. In the Subclient Name box, type the subclient name.
    4. Click the Content tab.
    5. Click Online Subset.
    6. Select the database objects to be included in the backup.
    7. Click the Storage Device tab.
    8. In the Data Storage Policy box, select the storage policy name.
    9. Click OK.

    Creating a Subclient for Log Backups

    Archive logs are required to recover database transactions that have been lost due to an operating system or disk failure. You can apply these archive logs to an online backup in order to recover a database.

    Though online full backups can include both data and logs, because of their importance in recovering data, it is recommended that you create separate subclients to backup archive log files.

    Before You Begin

    Procedure

    1. From the CommCell Browser, navigate to Client Computers | <RAC Client>.
    2. Right-click the <Instance>, point to All Tasks, and then click New Subclient.
    3. In the Subclient Name box, type the subclient name.
    4. Click the Logs Backup tab.
    5. Select the Backup Archive Log check box.
    6. Click the Storage Device tab.
    7. In the Data Storage Policy box, select the storage policy name.
    8. Click OK.

    Creating a Subclient for Selective Online Full Backups

    Before You Begin

    1. Create a Selective Copy.
    2. Optional: Run the script from the SnapProtect install base directory on the CommServe computer, to copy a full cycle of jobs to selective copy.

      Qscript -f SelectAdditionalJobs [storage policyName] [copy name] [backup types]

      The following are valid values for the backup types:

      • 0, disable selection of additional jobs
      • 2, include all non-full jobs

      Example

      qoperation execscript –sn SelectAdditionalJobs.sql –si storage_policy -si storage_policy_copy -si 2

    3. Optional: Decide if you want the software to force the parallel log backup to use the data storage policy. For more information, see Configuring the Storage Policy for a Parallel Log Backup.

    Procedure

    1. From the CommCell Browser, navigate to Client Computers | <RAC Client>.
    2. Right-click the <Instance>, point to All Tasks, and then click New Subclient.
    3. In the Subclient Name box, type the subclient name.
    4. Click the Content tab.
    5. Select the Selective Online Full check box. Click OK on the warning message dialog box.
    6. Click the Storage Device tab.
    7. In the Data Storage Policy box, select the storage policy name.
    8. Click OK.

    Managing Control Files

    As the Control file stores the status of the physical structure of the database. It is required when you want to recover the database to the current state. Hence it is important to include control files in your backups. By default, control files are included in the subclient for selective online full backups. You can also include/exclude control files for online or offline backups. The following sections describe the methods by which you can backup control files.

    Enabling Automatic Backup of Control Files for All Subclients

    You can configure the instance to automatically backup Control Files whenever you a backup the subclient in that instance.

    Use the following steps to enable automatic backup of control files for all the subclients in the instance.

    1. From the CommCell Browser, navigate to Client Computers | <RAC Client>.
    2. Right-click the <Instance>.
    3. Click the Details tab, in the Ctrl File Autobackup box,
      • Select Configure ON. This will backup the control file separately.
      • Alternatively, select Configure Off to backup the control file along with the datafile.
    4. Click OK.

     

    Enable or Disable Control File Backups for a Specific Subclient

    If the control file backup is enabled at the instance level, you can also include/exclude control files for backups from a specific subclient. Use the following steps to enable control file backups for a specific subclient.

    1. From the CommCell Browser, navigate to Client Computers | <RAC Client> | <Instance>.
    2. Right-click the <Subclient>, and then click Properties.
    3. Click the Content tab.
    4. Select the Backup Control File check box.

    5. Click OK.

    Enabling Automatic Backup of the Control Files from RMAN

    You can enable autobackup from RMAN command line to automatically backup the control file in every backup job operation.

    Enter the following commands/parameters at the RMAN prompt (the catalog connect string is optional):

    $rman target <connect string for target> catalog <connect string for catalog>RMAN>configure controlfile autobackup on;

    For Example:$rman target systemuser/systempass@rman92 RMAN>configure controlfile autobackup on;

    Configuring Table Restores

    By default, all data is backed up which includes tablespaces. If you want to restore individual tables, you need to enable table level backup.

    Enabling Table Browse for Restores

    In order to backup and restore database tables, you need to enable table level backups for the subclient. Use the following steps to enable backups at table level.

    1. From the CommCell Browser, navigate to Client Computers | <RAC Client> | <Instance>.
    2. Right-click the <Subclient>, and then click Properties.

      The Subclient Properties dialog box is displayed.

    3. On the Options tab, select the Enable Table Browse check box.
    4. Click OK.

    Setting Up the Auxiliary Instance

    By default, when you restore database tables to a target instance, the system automatically duplicates the source database to an auxiliary instance in a temporary staging location specified during the restore operation. The database will be automatically imported from this auxiliary instance after the restore.

    Use the following steps to set up a specific database as an auxiliary instance. This is useful when you want to restore a table to a specific failure point.

    1. Copy the init<SID>.ora file from the source database to the auxiliary database instance.
    2. Update the database name and the database file locations in the init<SID>.ora file for the auxiliary database instance.
    3. Add the DB_FILE_NAME_CONVERT and LOG_FILE_NAME_CONVERT parameters in the init<SID>.ora file. These parameters will redirect the datafiles, temp files, and log files to the auxiliary instance.

      Windows Clients:

      DB_FILE_NAME_CONVERT=('sourcE_of_df_path/','dup_of_df_path/',
      'source_of_temp_path/','dup_of_temp_path/',...)
      LOG_FILE_NAME_CONVERT=('source_of_log_path/
      redo','dup_of_log_path/redo')

      Unix Clients:

      DB_FILE_NAME_CONVERT=(source_of_df_path/,dup_of_df_path/
      ,source_of_temp_path/,dup_of_temp_path/,...)
      LOG_FILE_NAME_CONVERT=(source_of_log_path/redo,dup_of_log_path/redo)

    4. Add the log_archive_dest_1 parameter is added to the init<SID>.ora file on the auxiliary instance.
    5. Restart the Oracle Services, if using Windows clients.
    6. Add the destination instance name in the Listener.ora and Tnsnames.ora files. If using a different host, add the duplicate database instance name in the Listener.ora file on the destination host and Tnsnames.ora files on the destination and source hosts. Also, add the original database name in the Tnsnames.ora file on the destination host.

      DUPDB = (DESCRIPTION =
      (ADDRESS = (PROTOCOL = TCP)(HOST = powerpc02)(PORT = 1521))
      (CONNECT_DATA = (SERVER = DEDICATED)
      (SERVICE_NAME = dupdb) (UR=A) )
      )

    7. Restart the Listener.

      $lsnrctl reload

    8. Ensure that the auxiliary instance is in NOMOUNT mode.

      sql> startup nomount;

    Configuring Archive Log Destinations

    When you backup archive logs, you can specify the locations from where the log backups should be performed. This capability enables you to schedule backup operations from different log destinations on the same subclient. If necessary, you can also delete the logs after the backup.

    Setting Up the Log Destination for Deletion

    1. From the CommCell Browser, navigate to Client Computers | <RAC Client> | <Instance>.
    2. Right-click the <Subclient>, and then click Properties.
    3. Click the Log Destinations tab.
    4. Select the Select Archive Log Destinations for Backup check box.
    5. Click Add, type or select the Archive log file destination, and then click OK.
    6. Click OK.

    Deleting the Logs after a Backup

    Ensure that the logs in the specified location are backed up. This may cause data loss if those archive logs are not backed up.

    1. From the CommCell Browser, navigate to Client Computers | <RAC Client> | <Instance>.
    2. Right-click the <Subclient>, and then click Properties.
    3. Click the Log Destinations tab.
    4. Select the Select Archive Log Destinations for Delete check box.
    5. Click Yes to close the warning message.
    6. In the Confirmation box, type confirm.
    7. Click OK.
    8. Click Add.
    9. Type or select the Archive log file destination.
    10. Click OK.
    11. Click OK.

    Disabling the Log Switch

    When performing archive log backups, the current redo log file is closed (even if it is not filled up completely) and the next redo log file is used for writing using a log switch. The closed redo log file is then archived during the log phase. Use the following steps to disable the log switch:

    1. From the CommCell Browser, navigate to Client Computers | <RAC Client> | <Instance>.
    2. Right-click the <Subclient>, and then click Properties.
    3. Click the Content tab.
    4. Clear the Data checkbox.
    5. Click the Logs Backup tab.
    6. Select the Backup Archive Log check box.
    7. Select the Disable Log Switching check box.
    8. Click OK.

    Enabling Log Deletion after Backup

    When backing up archive logs, by default the logs are not deleted after the backup operation. Use the following steps to enable deletion of logs soon after the backup.

    1. From the CommCell Browser, navigate to Client Computers | <RAC Client> | <Instance>.
    2. Right-click the <Subclient>, and then click Properties.
    3. Click the Content tab.
    4. Select one of the following options to delete logs:
      Option Deleted archived Redo logs
      Archive Delete Select this check box to delete the archived logs that were backed up in the subclient.

      Note: The SnapProtect software inserts the DELETE INPUT command into the generated RMAN script. This only deletes the specific copy of the archived re-do log for the chosen backup set.

      Archive Delete All Select this check box to delete all backed up archived redo logs from all the archiving log destinations.

      Note: The SnapProtect software inserts the DELETE ALL INPUT command into the generated RMAN script. This deletes each backed up archived re-do log file from all the archive log destinations.

    5. Click OK.

    Configuring the Connect String with a Physical Hostname and Service Name

    The following configuration is needed to make SCAN connect work.

    1. Create the service as a Oracle user.  In the example it is "magic".

      $ srvctl add service -d magic -s mymagic -r magic1

    2. Start the service.

      $ srvctl start service -d magic -s mymagic

    3. Check to see if the service is registered with the listener.

      $lsnrctl status LISTENER_SCAN1
      $lsnrctl status LISTENER

    4. Add the entry in the tnsnames.ora file on the server and client sides.

      mymagic =
      (DESCRIPTION =
      (ADDRESS = (PROTOCOL = TCP)(HOST = dbserverac)(PORT = 1521))
      (CONNECT_DATA =
      (SERVER = DEDICATED)
      (SERVICE_NAME = mymagic)
      )
      )

    5. Make a connection.

      sqlplus scott/tiger@mymagic

    Changing the Oracle Home Directory

    Oracle HOME directory refers to the location where the Oracle application resides. When instances are discovered, the home path is automatically assigned to the instance. However, you can modify the home path location for an instance at any point of time. Use the following steps to configure the Oracle HOME directory:

    1. From the CommCell Browser, navigate to Client Computers | <RAC Client>.
    2. Right-click the <Instance>, and then click Properties.
    3. Click the Details tab, and select the desired RAC database instance, and then click Modify.
    4. In the ORACLE HOME box, type the path to Oracle Home directory. Alternatively, you can use Browse to locate the path.
    5. Click OK.

    Changing the TNS ADMIN Directory

    When an instance is configured, by default, the TNS_Admin directory is created in the Oracle HOME\network\admin path. Use the following steps to change the path for the TNS_ADMIN directory:

    1. From the CommCell Browser, navigate to Client Computers | <RAC Client>.
    2. Right-click the <Instance>, and then click Properties.
    3. Click the Details tab.
    4. Select the desired database instance, and then click Modify.
    5. In the TNS_ADMIN folder box, type the location for the TNS Admin directory. Alternatively, you can use Browse to locate the path.
    6. Click OK.

    Configuring Shutdown and Startup Scripts for Offline Backups

    In order to perform offline backups of the Oracle database, all users must be logged out of the database and it must be completely shut down. When the database is online, you can enable a graceful shutdown of the database using lights out script that will notify the users about the shutdown and set a specific wait time for the users to logout of the database. Use the following steps to configure lights out script for offline backups:

    1. From the CommCell Browser, navigate to Client Computers | <RAC Client> | <Instance>.
    2. Right-click the <Subclient>, and then click Properties.
    3. Click the Content tab, and then click Offline Database.
    4. Click the Advanced tab, and then click the Offline Arguments tab.
    5. Select the Run Shutdown/Startup Script check box.
    6. Select the Broadcast Warning Message to Users check box to display a warning message on the physical node.
    7. In the Delay Time After Warning Message (Min) box, select the delay time interval in minutes.
    8. Select the Use SQL Connect checkbox to connect to the oracle database using the SQL command connect <connect string> as sysdba.
    9. Click OK.
     

    Including Server Parameter (SP) File during Backups

    The Server Parameter file (SPFile) contains the database startup information. By default, the backups do not include the SPFile.

    Use the following steps to include SPFile during backups:

    1. From the CommCell Browser, navigate to Client Computers | <RAC Client> | <Instance>.
    2. Right-click the <Subclient>, and then click Properties.
    3. Click the Content tab.
    4. Select the Back up SP FILE check box.
    5. Click OK.

    Enabling Backups of Flash Recovery Area

    Flash Recovery Area is a specific area in the disk storage that exclusively holds a copy of all backup-related components, such as image copies, redo logs, and control file autobackups. This facilitates faster restores of backup data and minimizes restores from tapes during restore operations. Use the following steps to enable backup of flash recovery area:

    1. From the CommCell Browser, navigate to Client Computers | <RAC Client> | <Instance>.
    2. Right-click the <Subclient>, and then click Properties.
    3. Click the Content tab.
    4. Select the Backup Recovery Area check box.
    5. Click OK.

    Configuring User Accounts for Backups

    The Oracle RAC iDataAgent requires the following two user accounts in order to perform backup and restore operations:

    • An operating system account with administrator privileges for the Oracle application.

      The following table defines the user account requirements for each operating system:

      Operating System User Account
      Windows
      • The Local Administrator of the computer on which the Oracle database resides.
      • The user must be part of the ora_dba group with read and write permissions on the SnapProtect folder.

      Note: when using Oracle 12c, grant full control permission for the Oracle home user for the SnapProtect folder.

      UNIX Member of the user group assigned during the Agent installation. The operating system user account can also be used.
    • An Oracle user account with the SYSDBA or SYSBACKUP (in Oracle version 12 or higher) privilege can access the Oracle target database. Provide the account information as a connect string with the following connection details:
      • The database user ID and password
      • The Oracle Service Name (as defined in the tnsnames.ora file)

      Use separate accounts to access the target database and the recovery catalog database. The recovery catalog database user account must have RECOVERY_CATALOG_OWNER privileges, which are not required for the target database user.

      By default, the user account for the target database has administration privileges and must be established so the Oracle database administrator can configure additional accounts (except Impersonate User).

    Initially, the user account credentials are provided during the instance configuration after the installation of the Agent. You can subsequently change the user account information to access the Oracle database and application at the Instance level whenever the credentials are updated.

    Configuring User Account to Access the Oracle Application

    Use the following steps to configure the user account to access the Oracle application:

    1. From the CommCell Browser, navigate to Client Computers | <RAC Client>.
    2. Right-click the <Instance>, and then click Properties.
    3. Click the Details tab.
    4. Select the desired instance, and then click Modify.

      On Windows clients:

      • Click Change User Account.
      • In the User Account box, type the user account name.
      • In the Enter Password box, type the password for the user account.
      • In the Confirm Password box, retype the password, and then click OK.

       

      On Unix Clients:

      • Click Change User Account.
      • In the User Name box, type the user name, and then click OK.
    5. Click OK.

    Configuring User Account to Access the Oracle Database

    Use the following steps to configure the user account privileges to access the Oracle database:

    1. From the CommCell Browser, navigate to Client Computers | <RAC Client>.
    2. Right-click the <Instance>, and then click Properties.
    3. Click the Details tab.
    4. Select the desired instance, and then click Modify.
    5. In the Connect String box, type the connect string to connect to the Oracle database as follows:
      • Type the Database user ID.
      • Click the password box and type the password for the user ID in the Enter Password box.
      • In the Confirm Password box, retype the password, and then click OK.
      • Type the Oracle service name.

      For example:

      sys/<password>@winrac1

      where, sys is the Database User ID, <password> is the password of the Database User ID, and winrac1 is the Oracle service name.

    6. Click OK.

    Using Recovery Catalog for Backups

    By default, recovery catalog is not used for backup and restore. As the recovery catalog contains metadata about RMAN operations for each registered database, it is recommended to include recovery catalog in backups. The metadata information is useful when you want to restore and recover the database after a crash. Use the following steps to use the Recovery Catalog for backups:

    1. Verify that you have a recovery catalog database created using the following command:
    2. From the CommCell Browser, navigate to Client Computers | <RAC Client>.
    3. Right-click the <Instance>, and then click Properties.
    4. Click the Details tab.
    5. Select the Use Catalog Connect check box.

      In the Catalog Connect string box, type the credentials to connect to the desired Recovery Catalog. For example, sys2/pwd34@orcl2

      where sys2 is database user ID, pwd34 is password for the user ID and orcl2 is Oracle service name.

    6. Click OK.

    Synchronizing the Control File with the Recovery Catalog

    It is a good practice to synchronize the recovery catalog with the control file, as the control file contains the latest backup information, which is need to perform restores.

    Use the following steps to synchronize the control file with the recovery catalog:

    1. From the CommCell Browser, navigate to Client Computers | <RAC Client>|  <Instance>.
    2. Right-click the <Subclient>, and then click Properties.
    3. Click the Advanced tab, and then click the Options tab.
    4. Select the Resync Recovery Catalog check box.
    5. Click OK.

    Configuring Streams for Backups

    The Oracle RAC iDataAgent allows you to perform parallel backups across multiple RAC nodes as a matter of design. Unlike other agents, this agent requires just one subclient and one storage policy per type used (i.e., data, log) along with the requisite number of allocated streams to perform parallel backups. As such, you can load-balance your backups across all or selected nodes of your RAC database and thereby take advantage of the strengths of each node.

    Keep in mind that the same number of streams used for performing a backup will be needed to restore the data.

    Data Backups

    1. From the CommCell Browser, navigate to Client Computers | <RAC Client> | <Instance>.
    2. Right-click the <Subclient>, and then click Properties.
    3. Click the Storage Device tab.
    4. Double click the Stream box of the desired instance, and then type or select the number of streams.
    5. Click OK.

    Log Backups

    1. From the CommCell Browser, navigate to Client Computers | <RAC Client>.
    2. Right-click the <Instance>, and then click Properties.
    3. Click the Logs Backup tab.
    4. Double click the Stream box of the desired instance, and then type or select the number of streams.
    5. Click OK.

    Configuring Multiple Data Paths for Load Sharing

    In a primary copy, multiple streams of a backup job can share the load on multiple data paths. When you use multiple paths, the software releases the load on a single data path.

    Procedure

    1. Configure multiple data paths in the primary copy. For more information, see Copy Properties - Data Paths.
    2.  Configure the Resource Manager to use the Allow load-balance on multiple data paths within one backup job option. For more information see Media Management Configuration: Resource Manager.

    Example

    If you need to simultaneously back up to 8 drives of 2 or more libraries as part of one backup job, then you must configure the following to perform parallel backups by using the resources that are allocated on all the drives that were part of different data paths in a library:

    1. Configure a storage policy primary copy with multiple data paths, see Alternate Data Paths.
    2. Reserve resource allocation for these data paths by using media management's Resource Manager.

     

    This will allow the backup job to enforce reservations on multiple datapaths at the same time if the resources are limited from any single datapath. See Performing Parallel backups with Multiple DataPaths for Load Balancing for more information.

    Enhancing Backup Performance

    Several options are available for enhancing backup performance and reduce the network bandwidth used for performing backups. These options include:

    • Specifying the number of datafiles and archive files to be included in each RMAN backupset. The default value is 32.
    • Limiting the maximum size for each RMAN backupset. By default no limits are defined. By default no limits are defined.
    • Limiting the number of open datafiles that can be read by RMAN during the backup. The default value is 8.
    • Limiting the maximum size of data blocks used during backups. The default value is 262144 Kb.
    • Specifying the section size for Oracle 11g multisection backups. This enables you to divide large data files into multiple sections and simultaneously backup the data file across multiple channels.

      If the section size is larger than the data file size, multisection backup is not used for the file. If the section size is very small that more than 256 sections would be produced, RMAN increases the section size such that 256 sections are created.

    In addition to the above configurations, you can also enable distribution of data across disks during backup operations. See Performance Tuning for more details

    Use the following steps to enhance the backup performance:

    1. From the CommCell Browser, navigate to Client Computers | <RAC Client> | < Instance>.
    2. Right-click the <Subclient>, and then click Properties.
    3. Click the Advanced tab.
    4. In the Data Files (BFS) box, type or select the number of datafiles to be bundled in each RMAN backup set.
    5. In the Archive Files (BFS) box, type or select the number of archive files in each RMAN backup set.
    6. In the Backup Set Size group box, do one of the following:
      • Click Maximum Size and type or select the size of backup set allowed for RMAN backup set.
      • Click Section Size and type or select the size of each data file section used in an RMAN backup set for Oracle 11g backups.
    7. In the Maximum No. Of Open Files box, type or select the number of datafiles that RMAN can read from simultaneously during a backup operation.
    8. Click OK.
    9. From the CommCell Browser, navigate to Client Computers | <RAC Client>.
    10. Right-click the <Instance>, and then click Properties.
    11. Click the Details tab.
    12. In the Block Size box, type or select the size of the block for backup and restore operations.
    13. Click OK.

    Configuring the Failover Stream

    If any of the Oracle RAC nodes are not available, the backup can still run as long as the failover threshold is reached.

    Run the backup job immediately when the total number of reserved streams is greater than or equal to the specified value.

    1. From the CommCell Browser, expand Client Computers > client > Oracle RAC > instance.
    2. Right-click the subclient, point to All Tasks and then click Properties.

      The Subclient Properties dialog box appears.

    3. On the Storage Device tab:
      1. Click the Data Storage Policy tab.
      2. Select the Data threshold streams check box and then enter the number of streams.
    4. Click OK.

    Assigning Unique Identification Tags for Backups

    You can assign unique identification tags for all backup operations from a specific subclient. These tags can be used during a restore operation to easily identify a particular backup. Use the following steps to assign unique identification tag for backups.

    1. From the CommCell Browser, navigate to Client Computers | <Client> | Oracle | <Instance>.
    2. Right-click the <Subclient> and click Properties.
    3. on the Advanced Backup Options dialog, navigate to the Backup Arguments tab.
    4. In the Oracle Tag box, enter the tag name.
    5. Click OK.

    Excluding Data during Backups

    You can configure a subclient to skip the following data during backup operations:

    • Read-only tablespaces
    • Offline tablespaces
    • Inaccessible Datafiles and Archived redo log files

    Use the following steps to exclude data during backup operations:

    1. From the CommCell Browser, navigate to Client Computers | <RAC Client> | <Instance>.
    2. Right-click the <Subclient>, and then click Properties.
    3. Click the Advanced tab, and then click the Options tab.
    4. Select the Skip Read Only check box to exclude the read only tablespaces.
    5. Select the Skip Offline check box to exclude the offline tablespaces.
    6. Select the Skip Inaccessible Data and Archive Redo Log Files check box to exclude inaccessible data and log files.
    7. Click OK.

    Simulating a Backup

    Prior to running backup operations, you can check datafiles for physical and logical corruption.

    Prior to running backup operations, you can validate a backup job, which will cause RMAN to simulate the backup for the purpose of determining whether the backup can be successfully restored. Once a validate job is completed, you can view the log files of the job to identify and correct any validation issues.

    During validation, the backup jobs are simulated without the media, you can view the log files of the job to identify and correct any validation issues.

    Use the following steps to enable validation of backup jobs:

    Prior to running a backup, you can check the following:

    • Datafiles for physical and logical block corruption
    • Database files exist and are in the correct location.
    1. From the CommCell Browser, navigate to Client Computers | <RAC Client> | <Instance>.
    2. Right-click the <Subclient>, and then click Properties.
    3. Click the Advanced tab, and then click the Options tab.
    4. Select the Validate check box.
    5. Click OK.

    Specifying the Media Parameters for RMAN Command Line Operations

    RMAN command line backups use storage policy and data path specified in the CommCell Oracle database instance by default.

    You can override the default parameters by specifying media and SBT parameters in the RMAN script and then running the script from the RMAN command line. This feature is supported for backup, restore, and duplicate database operations.

    You must associate the Data Path (MediaAgent, Library, Drive Pool) with the specified storage policy in the parameters file.

    Procedure

    1. Create a media parameters file with the required media parameters.

      You can also include the SBT Parameters in the parameters file. For information on the supported media and SBT parameters, see Media Parameters and SBT Parameters.

      The parameter file format is

      [<Parameter Name-1>]
      <Value-1> <
      [<Parameter Name-2>]
      <Value-2>

      Example

      [sp]
      SP_Ora
      [mediaagent]
      firewall-con_cn
      [library]
      CommVault VirtualLib 276
      [drivepool]
      DrivePool(firewall-con_cn)254

    2. Create an RMAN script and use the CvOraSbtParams environment variable to specify a path to the media parameters file.

      Example

      run {
      allocate channel ch1 type ‘sbt_tape’ PARMS=”BLKSIZE=1048576,
      ENV=(CvOraSbtParams=D:\parameters.txt)”;
      backup database;
      release channel ch1; }

    3. On the RMAN command line, connect to the target database.

      Example

      rman target sys/sys@dbtnsname

    4. On the RMAN command line, run the RMAN script.

      Example

      Run the RMAN script named backup.txt.

      @backup.txt

    Disabling the RMAN Crosscheck

    By default, during a data aging operation, an Oracle CROSSCHECK is performed by the system to synchronize the entries in the CommServe database with the RMAN catalog. Use the following steps to disable the cross check operation:

    1. From the CommCell Browser, navigate to Client Computers | <RAC Client>.
    2. Right-click the <Instance>, and then click Properties.
    3. Click the Details tab.
    4. Select the Disable Backup Aging check box.
    5. Click OK to close the warning message.
    6. Click OK.

    Enabling Multiple Backup Copies

    You can take multiple copies of the data or log backups using RMAN command line. During restores, even if one of the copies is missing or corrupted, the restore operation will automatically failover to the other copy and restore the data.

    1. To utilize the PARALLELISM option, you need to set the initial parameter in pfile or spfile. Example:

    BACKUP_TAPE_IO_SLAVES=TRUE

    2. Configure device type. Example:

    RMAN> CONFIGURE DEVICE TYPE DISK PARALLELISM 2 BACKUP TYPE TO BACKUPSET;

    3. Specify two copies of data. Example:

    RMAN> CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE 'SBT_TAPE' TO 2;

    4. Specify two copies of log backups. Example:

    RMAN> CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE 'SBT_TAPE' TO 2;

    5. Add the environmental variables for the client and instance on which the iDataAgent is installed. Example:

    allocate channel ch1 type 'sbt_tape'

    PARMS="<software_install_path>/Base/libobk.so,

    ENV=(CvClientName=<client_name>,

    CvInstanceName=<instance_name>)"

    6. Once you set the parameters, restart the Oracle database and perform backup operations from the CommCell Console. Example: To restart the database,
    1. Connect to the database.

      SQL> connect admin/admin@orcl as sysdba

    2. Shutdown the database.

      SQL> shutdown

    3. Mount the database.

      SQL> startup mount;

    4. Change to archivelog mode.

      SQL> alter database archivelog;

    5. Open the database.

      SQL> alter database open;

    Configuring the Backup Piece Format

    The backup piece format is as follows for GUI backups  <CVJobID>_%d_%U which ensures to get unique name for backup pieces.

    Hex_CommCell_ID – Hexadecimal CommCell ID

    CvJobID –SnapProtect  job id

    %d - represents the Oracle database name

    %U – unique identifier

    Procedure

     

    Using the Connect String Instead of OS Authentication (/) to Connect to the Oracle RAC Database

    Oracle restores use OS authentication (/) as the connection for control file, SP file or full database restores because the connection to the Oracle instance will not work when a dynamic listener is configured. Set this addition setting to use the connect string instead of OS authentication when you have configured a static listener.

    Procedure

    • To the client computer, add the additional setting as shown in the following table.

      For instructions on how to add additional settings from the CommCell Console, see Add or Modify an Additional Setting.

      Property Value
      Name sUSECONNECTSTRING
      Category OracleAgent
      Type String
      Value Y

    Specifying the Servers that Run Backups in an Oracle Data Guard Configuration

    When you have an Oracle Data Guard configuration, you can use this additional setting to specify which server, primary or secondary, runs the data and log backups.

    Use the following values to specify the backup location.

    Value Definition
    1 Run the database backup and the archive log backup on the standby server
    4 Run the database backup on the standby server and the archive log backup on the primary server
    10 Run the database backup on the primary server and the archive log backup on the standby server
    12 Run the database backup and the archive log backup on the primary server

    Procedure

    • To all client nodes, add the additional setting as shown in the following table.

      For instructions on how to add additional settings from the CommCell Console, see Add or Modify an Additional Setting.

      Property Value
      Name sORARUNBKPONDBROLE
      Category OracleAgent
      Type Integer
      Value The value that specify the servers that run the backups.

    Modifying an Agent, Instance, or Subclient

    There are several configurable properties available for your agent that can be modified from the agent, instance, or subclient level as per need.

    The following table describes the properties that can configured from the agent, instance, and subclient levels.

    Option Description Related Topics
    Change Storage Policies You can modify the storage policies in any of the following situations:
    • To include a different media for the backup operation.
    • To use a storage policy with a different retention criteria.

    You can change the storage policies from the subclient level.

    1. From the CommCell Browser, right-click the subclient.
    2. Click Properties.
    3. Click Storage Device.
    4. Select the Storage policy from the drop-down menu.
    5. Click OK.
    Refer to Storage Policies.
    Rename a Subclient

    You can rename a subclient:

    1. From the CommCell Browser, right-click the subclient.
    2. Click Properties.
    3. Type the new name in the  Subclient name field.
    4. Click OK.
     
    Data Transfer Options You can configure the available resources for transferring data secured by data protection operations from the subclient level. This includes the following:
    • Enable or disable Data Compression either on the client or on the MediaAgent.
    • Configure the transfer of data in the network using the options for Network Bandwidth Throttling and Network Agents.

    You can configure the data transfer options.

    1. From the CommCell Browser, right-click the subclient.
    2. Click Properties.
    3. Click Storage Device.
    4. Click Data Transfer Option tab.
    5. Choose the appropriate software compression option for this subclient.
    6. Select Throttle Network Bandwidth and set the required bandwidth.
    7. Click OK.
    Refer to Data Compression and Network Bandwidth Throttling.
    View Data Paths You can view the data paths associated with the primary storage policy copy of the selected storage policy or incremental storage policy. You can also modify the data paths including their priority from the subclient level.
    1. From the CommCell browser, right-click the subclient.
    2. Click Properties.
    3. Click Storage Device.
    4. Select Storage Policy from the drop-down menu.
    5. Click Data Paths.
     
    Configure a Subclient for Pre and Post Processing of Data Protection You can add, modify or view Pre/Post processes for the subclient. These are batch files or shell scripts that you can run before or after certain job phases. If needed, the database instance can be sent to the script. See Passing the Instance Name to Pre and Post Scripts for Databases.
    1. From the CommCell browser, right-click the subclient.
    2. Click Properties.
    3. Click Pre/Post Process.
    4. Click one of the following phases and type the full path of the process that you want to execute during that phase. Alternatively, click Browse to locate the process (applicable only for paths that do not contain any spaces).
      • PreBackup Process
      • PostBackup Process
      • PreSnap Process
      • PostSnap Process
    5. Click OK.
    6. Select Run Post Backup Process for all attempts to run a post backup process for all attempts.
    7. For subclients on Windows platforms, Run As displays Not Selected.

      If you want to change the account that has permission to run these commands, click Change.

      1. In the User Account dialog box, select Use Local System Account, or select Impersonate User and enter the user name and password. click OK.
      2. If you selected Local System Account, click OK to the message advising you that commands using this account have rights to access all data on the client computer.
    Refer to Pre/Post Processes.
    Configure Activity Control You can enable backup and restore operations from the agent and subclient level. However, you can enable restore operations only from the agent level.
    1. From the CommCell browser, right-click the subclient.
    2. Click Properties.
    3. Click Activity Control, select or clear option(s) as desired.
    4. Click OK.
    Refer to Activity Control.
    Configure User Security You can configure user security from the agent or subclient level. You can perform the following functions:
    • Identify the user groups and roles associated with the CommCell object.
    • Associate this object with a user group and role.
    • Disassociate this object from a user group and role.
    1. From the CommCell browser, right-click the subclient and then click Properties.

      The Subclient Properties dialog box appears.

    2. Click the Security tab and then click Add.

      The Add Users and Groups dialog box appears.

    3. In the Users and Groups section, select the user group to associate with the CommCell object, and then click Add.
    4. In the Role section, select the role to associate with the CommCell object.
    5. Click OK.

      For this subclient, the users in the user group are restricted by the permissions in the role.

    Refer to User Administration and Security.
    Enable and Disable Data Encryption When you configure encryption at the client level, it is configured automatically for all the subclients associated with all the agents installed on that client. If you want to disable or change the encryption at the subclient level, follow the steps given below:
    1. From the CommCell browser, right-click the subclient.
    2. Click Properties.
    3. Click Encryption.
    4. Select the desired encryption.
    5. Click OK.
    Refer to Data Encryption.
    View Software Version and Installed Updates At the client level, the Version tab of the Properties dialog box displays the software version of the component.
    1. From the CommCell Browser, expand Client Computers.
    2. Right-click the appropriate client, and then click Properties.
    3. Select the Version tab.
    4. Click OK.
     
    CommCell Configuration Report The CommCell Configuration Report provides the properties of the CommServe, MediaAgents, clients, agents, subclients, and storage policies within the CommCell based on the selected filter criteria.
    1. From the CommCell browser, click Reports icon.
    2. Select CommCell Configuration.
    3. Click Run.
    Refer to CommCell Configuration.

    Deleting an Agent, Instance, or Subclient

    The following sections describe the steps involved in deleting an agent, instance, or subclient.

    When you delete an instance or backupset, the associated data is logically deleted and you can no longer access the corresponding data from CommCell Console for recovery purposes.

    Refer to the troubleshooting article on Recovering Data Associated with Deleted Clients and Storage Policies for information on how to recover data if you accidentally delete an entity.

    Deleting an Agent

    You need to uninstall or DeConfigure the agent software from the client computer before deleting from CommCell Browser. After you delete the client software, you can either leave the corresponding data intact for appropriate action or you can remove the data immediately. If you choose to remove the data immediately, you must delete the agent from the CommCell Browser. If you delete the agent, all of the agent's data is irretrievably lost.

    • You cannot delete an agent while operations for that agent are running.
    1. From the CommCell Browser, navigate to Client Computers | <Client>.
    2. Right-click the <Agent>, and then click Delete.
    3. A confirmation message is displayed with the following message:

      This operation will permanently delete the data backed up from this level and it cannot be restored.

    4. Click OK to continue with the deletion operation or click No to abort the deletion.

    Deleting an Instance

     Data that is backed up for any Oracle instance configured on the Oracle RAC node is lost if the configured Oracle instance is hard-deleted.

    Consider the following before deleting an instance:

    • When you delete a specific instance all job schedules and job histories that pertain to any of the levels within the deleted instance are deleted.
    • You cannot delete an instance if it is being backed up. Attempts to delete an instance under such conditions cause the deletion to fail. If a backup is in progress, either wait for the backup to complete or kill the backup job using the Job Manager. Once the backup is no longer in progress, you can delete the instance level.
    • You cannot delete an instance if there is only one instance present for an agent. To delete the final instance, you must remove the agent software from the client computer.
    1. From the CommCell Browser, right-click the instance that you want to delete, click All Tasks and then click Delete.
    2. click Yes to confirm the deletion. (clicking No cancels the deletion and retains the node.)
    3. Type the requested phrase in the Enter Confirmation Text dialog box and click OK. This should delete the instance.

    Deleting a Subclient

    Consider the following before deleting a subclient:

    • You cannot delete a default subclient.
    • Schedules associated with the subclient are also automatically deleted.
    1. From the CommCell Browser, navigate to Client Computers | <RAC Client> | <Instance>.
    2. Right-click the <Subclient> that you want to delete, and then click Delete.
    3. A confirmation message is displayed, asking if you want to delete the subclient.

      Click No to cancel the deletion and retain the subclient, or click Yes to continue the deletion.