V11 SP8
Loading...

Advanced Configuration - FlexFrame for IntelliSnap Oracle

Table of Contents

Understanding the CommCell Console

The Oracle 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.

Managing Instances

Enabling Automatic Instance Discovery

Use the Enable Instance Discovery option to automatically discover databases.

CommCell instances are created for Oracle databases under the following conditions:

  • Discovery is initiated every 168 hours..
  • When the Communications Service (GxCVD) is restarted (for example after a computer reboot).

Enabling Automatic instance discovery ensures that newly added Oracle databases are regularly accounted for backups.

The Commvault software only discovers instances defined in the Oracle oratab file, which is created by Oracle at installation and acts as a database registry file. On Solaris systems, this file is normally located in the /var/opt/oracle directory and on Linux/UNIX systems, it is located in the /etc directory.

  1. From the CommCell Browser, expand Client Computers.
  2. Right-click client, and click Properties.
  3. On the Client Properties dialog box, check the Enable Instance Discovery check box and click OK.

Setting the Automatic Discovery Frequency

  1. From the CommCell Browser, expand Client Computers.
  2. Right-click the Client, and click Properties.
  3. On the Client Properties dialog box, click Advanced.
  4. On the Additional Settings tab of the Client Properties dialog box and click Add.
    1. In the Additional Settings dialog box, in the Name box, type nDBDISCOVERYINTERVAL.
    2. In the Category box, select the database agent (for example, OracleAgent).
    3. In the Type box, select String.
    4. In the Value box, type the time interval in hours in which databases are detected.

      For example, to discover databases every two hours, type 2.

    5. Click OK to close the Add Additional Setting dialog box.
  5. Click OK to close the Client Properties dialog box.

Skipping Windows User Impersonation

When you are running RMAN commands, you must enter the domain name and password  If you are running Oracle on a local system, you do not need to do this and can override the option by setting the Additional Setting.

  1. From the CommCell Browser, navigate to the CommCell.
  2. Right-click the <CommCell>, and click Properties.
  3. On the Properties dialog box, navigate to the Additional Settings tab and click Add.
  4. On the Add Additional Settings for CommServe dialog box:
    • In the Name box, enter IGNORE_IMPERSONATION.
    • Select CommServe for the Category.
    • In the Value box, enter Y.
    • Click OK.

Manually Discovering Instances

If you have manually created an Oracle database, then you must manually discover the corresponding instance. Automatic instance discovery will not detect the manually created databases.

In addition, you can also use the manual discovery process to discover the Oracle databases at any point in time. Use the following steps to manually discover instances:

  1. From the CommCell Browser, navigate to Client Computers | <Client>.
  2. Right-click Oracle, point to All Tasks, and then click Discover Instance.
  3. Click Yes to confirm discovery of instances.

Manually Adding an Instance

During automatic instance discovery, options such as oracle home path and user account, connect string are preset. When instances are manually added, these options can be customized. Use the following steps to manually add an instance:

  1. From the CommCell Browser, expand Client Computers > client.
  2. Right-click Oracle, point to All Tasks and then click New Instance (ORACLE SID).

    The Creating New Instance dialog box appears.

  3. On the General tab:
    1. In the Instance (ORACLE SID) box, enter the instance name.
    2. In the User Account box, enter the login credentials to access the Oracle client.
    3. In the ORACLE HOME box, enter the Oracle application install path.
    4. In the Storage Policy used for the data of default subclient list, select a storage policy name.
  4. 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 Connect String Enter the 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

    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

  5. In the Automatic Backup of Control Files list, select Configure On to include the control file in all backups for this instance.

    Note: You can override this option to have the feature on the subclient level. For more information, see Enabling Automatic Backups of the Oracle Control File at the Subclient Level.

  6. Select the Disable Backup Aging check box to disable the Oracle CROSSCHECK and, then click OK to close the warning message.
  7. On the Storage Device tab, enter storage policy information:
    • In the Storage Policy used for user command backup of data list, select a storage policy.
    • 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.
  9. On the Oracle database host, edit the oratab file and add an entry for the added instance.

Configuring User Accounts for Backups

The Oracle 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 Commvault folder.

    Note: when using Oracle 12c, grant full control permission for the Oracle home user for the Commvault 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 | <Client> | Oracle.
  2. Right-click the <Instance>, and then click Properties.
    • On the Properties dialog, navigate to the General tab.

      For Windows clients:

      • Click Change, which displays the Impersonate NT User dialog.
      • In the User Account box, enter the user account name.
      • In the Enter Password box, enter the password for the user account.
      • In the Confirm Password box, re-enter the password, and then click OK.

      For Unix clients:

      In the User Account box, enter the user account that you use to access the Oracle application.
    • 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 | <Client> | Oracle.
  2. Right-click the <Instance>, and then click Properties.
  3. On the Details tab, enter the Oracle connection information:
    • To use the Oracle Wallet feature, select the Oracle Wallet Auto Login check box.
    • To use the Oracle 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 that is other than 'sys', you must grant the SYSDBA or SYSBACKUP (in Oracle version 12 or higher) privilege to the user account.

      Enter the Connect String to connect to the Oracle database as follows:

      1. In the first box enter the Database user ID.
      2. In the second box enter the Password.
      3. In the Confirm Password dialog box, re-enter the password, and click OK.
      4. In the third box enter the Oracle Service name.

      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. Click OK.

Managing Subclients

Subclients contain the information about what Oracle data is backed up.

When you create an Oracle database instance, a default subclient that includes the entire database and log and control files is automatically created.

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

You can use the CommCell Console or the Commvault Command Line Interface to create separate subclients for each unique data set and log files. Use the following criteria when determining the unique data sets:

  • The data content you want to back up and how you need to restore the data (for example, all tables or a subset of tables)
  • The database state when you perform backups
  • The required schedule for the data

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 perform an IntelliSnap backup, the software creates a backup copy.

Use a proxy server when you want to reduce the load on the production server. The proxy server also moves the snap to the backup media.

Note:  If you want to use the Oracle RMAN backup copy option by using a proxy server, you must contact Oracle for their required licensing.

If you want to create a subclient for the Oracle Instant Application Recovery feature, you must set the Volume Copy option for the subclient (Subclient Properties dialog box, IntelliSnap Operations tab, Volume Copy (Block-Level Backup - Support Instant Database Recover).

Best Practice: To ensure that the snapshot reflects the backup details in the schema, after you connect to the catalog, run a traditional full backup on the IntelliSnap subclient. For information on how to perform the backup, see Performing an Oracle Full Backup.

Creating a Subclient for Offline Backups

During an offline backup, the database is shutdown and is not available for use. Since incremental backups require access to various tablespaces and datafiles, it is always recommended that you perform a full backup of the database when it is offline. 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.

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

    The Create New Subclient dialog box appears.

  3. On the General tab, in the Subclient Name box, enter a name for the subclient.
  4. Click Content.
  5. Select the Data check box.
  6. Select Offline Database.
  7. Click Storage Device.
  8. From the Storage Policy list, select the storage policy name for the log backups.

    Note: You must provide a storage policy even though the log backups do not use the subclient storage policy. Log backups always use the storage policy that you define for the Oracle instance (Instance Properties dialog box, Storage Device tab, Log Backup tab, Storage Policy used for all Archive Log backups).

  9. Click Storage Device.
  10. From the Storage Policy list, select the storage policy name for the data backups.
  11. Click IntelliSnap Operations.
  12. Select the IntelliSnap check box.
  13. In the Available Snap Engines box, select the snap engine name.

    Note: If your Oracle database is hosted by an Amazon EC2 account, you must select Amazon as the Available Snap Engine value.

  14. From the Use Proxy list, select the MediaAgent that performs the backup copy operations.

    Note: The proxy server operating system must be the same or later than the client computer.

  15. 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 PreSnap Command box, type the full path name for the script.
    2. In the PostSnap 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.
  16. Click OK to close the Creating New Subclient dialog box.

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

Use the following steps to create a subclient for online backups:

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

    The Create New Subclient dialog box appears.

  3. On the General tab, in the Subclient Name box, enter a name for the subclient.
  4. Click Content.
  5. Select the Data check box.
  6. Select Offline Database.
  7. Click Storage Device.
  8. From the Storage Policy list, select the storage policy name for the data backups.
  9. Click IntelliSnap Operations.
  10. Select the IntelliSnap check box.
  11. In the Available Snap Engines box, select the snap engine name.

    Note: If your Oracle database is hosted by an Amazon EC2 account, you must select Amazon as the Available Snap Engine value. For information on how to manage the Amazon array, see Getting Started for Amazon.

  12. From the Use Proxy list, select the MediaAgent that performs the backup copy operations.

    Note: The proxy server operating system must be the same or later than the client computer.

  13. 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 PreSnap Command box, type the full path name for the script.
    2. In the PostSnap 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.
  14. Click OK to close the Creating New Subclient dialog box.

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.

Note: The operating system of the proxy server must be the same version or later than the client computer

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

    The Create New Subclient dialog box appears.

  3. On the General tab, in the Subclient Name box, enter a name for the subclient.
  4. Click Content.
  5. Click Online Subset and then select the database objects to be included in the backup.
  6. Click the Storage Device tab.
  7. In the Data Storage Policy box, select the storage policy name.
  8. Click the IntelliSnap Operations tab.
  9. Select the IntelliSnap check box.
  10. In the Available Snap Engines box, select the snap engine name.
  11. From the Use Proxy list, select the MediaAgent where backup copy operations will be performed.
  12. Determine the copy option.

    For more information on the backup copy options, see Oracle IntelliSnap - Backup Copy

    • To use the File system copy, select File System.
    • To use the RMAN backup copy, select RMAN.
    • To use Volume Copy, select Volume Copy (Block-Level Backup - Support Instant Database Recover).

      Note: You must select this option when you want to use the Instant Application Recovery feature.

  13. Optional: To perform an integrity check of the hardware, select the Enable Snap Integrity Check check box.
  14. 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 PreSnap Command box, type the full path name for the script.
    2. In the PostSnap 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.
  15. Click OK.

Creating a Subclient for Selective Online Full Backups

You perform a selective online full backup when the database is online. A selective copy subclient includes the data, logs and control file. The advantage of a selective online full backup is that the data and logs use the same storage policy, which means that they reside on the same media and are self-contained for long-term archiving. You can use this in a disaster recovery, because you do not need to locate different media from multiple jobs to recover the database.

For more information on selective online full backups, see Selective Online Full Backups.

Note: The operating system of the proxy server must be the same version or later than the client computer

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

    The Create New Subclient dialog box appears.

  3. On the General tab, in the Subclient Name box, enter a name for the subclient.
  4. Click Content.
  5. Click the IntelliSnap Operations tab.
  6. Select the IntelliSnap checkbox.
  7. In the Available Snap Engines box, select the snap engine name.
  8. From the Use Proxy list, select the MediaAgent where backup copy operations will be performed.
  9. Determine the copy option.

    For more information on the backup copy options, see Oracle IntelliSnap - Backup Copy

    • To use the File system copy, select File System.
    • To use the RMAN backup copy, select RMAN.
    • To use Volume Copy, select Volume Copy (Block-Level Backup - Support Instant Database Recover).

      Note: You must select this option when you want to use the Instant Application Recovery feature.

  10. Optional: To perform an integrity check of the hardware, select the Enable Snap Integrity Check check box.
  11. 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 PreSnap Command box, type the full path name for the script.
    2. In the PostSnap 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.
  12. Click OK.

Creating a Subclient for Log Backups

You can perform an IntelliSnap backup for a subclient that only contains the logs. By default, the system will use data storage policy for IntelliSnap backups and backup copy. If you create a log specific subclient, the log specific storage policy is used for IntelliSnap backups and backup copies.

You can use the image copy option when you have a set of Oracle data files that are located on volumes that cannot be snapped.

When you select the option, the Commvault software uses RMAN to back up the incremental database changes to a volume that can be snapped.

During the backup copy operation, the Commvault software uses the block-level interface so that you can use the data for other Oracle block-level operations, such as Instant Application Recovery.

Before You Begin

  • If you want to use the Oracle RMAN backup copy option by using a proxy server, you must contact Oracle for their required licensing.

Procedure

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

    The Create New Subclient dialog box appears.

  3. On the General tab, in the Subclient Name box, enter a name for the subclient.
  4. When you have not enabled control files as part of all subclient backups, on the Content tab, clear the Data check box and then select the Backup Control File check box.

    If the automatic control file backup is configured for subclients, the Commvault software adds AUTO BACKUP CONTROLFILE ON to the backup script. For more information, see Enabling Automatic Backups of the Oracle Control File at the Subclient Level.

  5. On the Log Backups tab, select the Backup Archive Log check box.
  6. On the Storage Device tab, in the Storage Policy list, select the storage policy name for the log backups.

    Note: You must provide a storage policy even though the log backups do not use the subclient storage policy. Log backups always use the storage policy that you define for the Oracle instance (Instance Properties dialog box, Storage Device tab, Log Backup tab, Storage Policy used for all Archive Log backups).

  7. Configure the IntelliSnap options.
    1. On the IntelliSnap Operations tab, select the IntelliSnap check box.

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

    2. Click OK.
    3. From the Available Snap Engines list, select the appropriate engine.

      Note: If your Oracle database is hosted by an Amazon EC2 account, you must select Amazon as the Available Snap Engine value. For information on how to manage the Amazon array, see Getting Started for Amazon.

    4. From the Use Proxy list, select the appropriate MediaAgent.

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

      Note: When you perform an IntelliSnap backup using a proxy, make sure that the operating system on the proxy server is either same version or later than the operating system on the client computer.

    5. To perform the backup copy operations on a different MediaAgent, select the Use Separate Proxy for Backup Copy check box, and then, from the Proxy list, select the appropriate MediaAgent.
    6. To have the software create an image copy, select the Use RMAN Image Copy check box, and then in the Path box, type the full path to the image copy.

      Note: The path must have the following properties:

      • It must be a mount path that can be snapped
      • It must have enough space to store the maximum size of all the datafiles and one incremental backup.
      • It must have UNIX 750 permissions
    7. Determine the copy option.

      For more information on the backup copy options, see Oracle IntelliSnap - Backup Copy.

      • To use the File system copy, select File System.
      • To use the RMAN backup copy, select RMAN.
      • To use Volume Copy, select Volume Copy (Block-Level Backup - Support Instant Database Recover).

        Note: You must select this option when you want to use the Instant Application Recovery feature.

        The option is automatically selected when you select the Snap Image Copy check box.

    8. Optional: To perform an integrity check of the hardware, select the Enable Snap Integrity Check check box.
  8. Optional: Manage log file backup options, see Managing Oracle Log Files on a Subclient.
  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 PreSnap Command box, type the full path name for the script.
    2. In the PostSnap 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 Log Backups from Command Line

If you want to create a subclient for Log backups on multiple instances or clients instead of navigating to each client and creating the subclients, then, use this qscript.

Use the following steps to create a subclient for Log backups from the command line using qscript:

  1. From the command prompt, logon to the CommServe using the qlogin command.

    Example: To log on to CommServe commserve.commcell.com with user name user1:

    qlogin -cs commserve.commcell.com -u user1

    Password:

  2. Run the command to create a subclient.

    D:\>qcreate sub client -cs commserve.commcell.com -c client_name -a Q_ORACLE -i auto -n "NEWlog" -sp "data_storage_policy" -f "auto"

  3. Run the command to disable Data option.

    D:\>qoperation execscript -sn SetSubClientProperty.sql -si 'c=client' -si 'a=Q_ORACLE' -si 'i=auto' -si 'b=default' -si 's=NEWlog' -si 'Oracle Backup Mode' -si '1' -si '2'

  4. Run the command to disable Backup Control File option.

    D:\>qoperation execscript -sn SetSubClientProperty.sql -si 'c=client' -si 'a=Q_ORACLE' -si 'i=auto' -si 'b=default' -si 's=NEWlog' -si 'Backup Control Files' -si '0' -si '2'

  5. Run the command to disable Delete Archive log option.

    D:\>qoperation execscript -sn SetSubClientProperty.sql -si 'c=client' -si 'a=Q_ORACLE' -si 'i=auto' -si 'b=default' -si 's=NEWlog' -si 'Archive Log Deleting' -si '0' -si '2'

For more information about the parameters and arguments, see qscript.

Skip IntelliSnap Backup of Archive Logs

For subclients that contain data and archive logs, you can choose to run an IntelliSnap backup of only the data volume by configuring the logs to use RMAN. When the backup uses RMAN, the log backup uses the traditional backup method.

Best Practice: Use this backup method when:

  • The log volume is located on a non snap-able device.
  • The instance that contains the archive logs in the Oracle RAC database is not shared.

The software runs the IntelliSnap backup and RMAN log backup as 2 separate jobs. You must configure the catalog connect database for the instance because the control file from the snapshot does not record the log backup information.

When a FULL job is submitted for this subclient, the IntelliSnap job will be marked as FULL and the RMAN log job will be marked as Incremental. The entire set of logs are backed up and the software marks them as Incremental so that the IntelliSnap data and RMAN logs are part of the same cycle.. During the data aging process, the data will be retained correctly based on the retention rules.

Best Practice: Use this option when you snap archive log volume in high transactional databases where check points frequently occur.

Procedure

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

    The Subclient Properties dialog box is displayed.

  3. Click Log Backup.
  4. Select the Use RMAN for Log Backup check box.
  5. Click OK.

Configuring an ASM Instance

Before You Begin

  • Configure an ASM instance on the CommCell Console in addition to an RDBMS instance.
  • Make sure that the kfed utility is located in the <Oracle ASM Home>/bin directory. If the kfed utility does not exist, then build the kfed utility as shown in the following example:

    cd <Oracle ASM Home>/rdbms/lib

    make –f ins_rdbms.mk ikfed
  • Ensure that the ASM disk string is not empty.
  • Discover the Oracle instance

Procedure

  1. From the CommCell Browser, expand Client Computers > client.
  2. Right-click Oracle, point to All Tasks and then click New Instance (ORACLE SID).

    The Creating New Instance dialog box appears.

  3. On the General tab:
    1. In the Instance (ORACLE SID) box, enter the instance name.
    2. In the User Account box, enter the login credentials to access the Oracle client.
    3. In the ORACLE HOME box, enter the Oracle application install path.
    4. In the Storage Policy used for the data of default subclient list, select a storage policy name.
  4. 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 Connect String Enter the 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

    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

  5. In the Automatic Backup of Control Files list, select Configure On to include the control file in all backups for this instance.

    Note: You can override this option to have the feature on the subclient level. For more information, see Enabling Automatic Backups of the Oracle Control File at the Subclient Level.

  6. Select the Disable Backup Aging check box to disable the Oracle CROSSCHECK and, then click OK to close the warning message.
  7. On the Storage Device tab, enter storage policy information:
    • In the Storage Policy used for user command backup of data list, select a storage policy.
    • 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.
  9. On the Oracle database host, edit the oratab file and add an entry for the added instance.

What to Do Next

  1. Create a corresponding RDBMS instance for the Oracle client.

    You can create subclients for the regular RDBMS instance and perform IntelliSnap backup jobs. When you create the subclient for IntelliSnap operations, you must manually refresh the database. The software automatically selects and makes the Use RMAN for backup copy option on the subclient unvailable.

  2. If the ASM disks are from persistent snap engine, then you need to disable the snap integrity. Refer Disabling Verification of Datafiles during IntelliSnap Backup for more information.

Allowing the Software to use the ASM Disk Advanced Format

Set this additional setting to Y so that the software can use advanced format ASM disks. The software accesses the ASM disks by using the ASMLib kernel (ORCL: devices).

Note: You must set this for Oracle Linux configurations that use ASM disk groups with a 4K sector size.

Procedure

 

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.

Configuring VSS for IntelliSnap Backup on Windows

 Volume Shadow Copy Service (VSS) is an infrastructure on Windows server platforms that enables applications to create shadow copies. A shadow copy is a consistent snapshot of the data held on a volume or component at a well-defined point in time. It provides a Windows-specific interface that enables coordination between requestors that back up data, writers that update data on disk, and providers that manage storage. In our case, Oracle iDataAgent works as a requestor, Oracle VSS Writer works as a writer and VSS Provider works as a provider. Oracle iDataAgent supports hardware providers.

Prerequisites

Consider the following before performing IntelliSnap backup using VSS:

  • You need to install the VSS Software Provider along with Oracle iDataAgent to perform IntelliSnap backups.
  • To perform VSS IntelliSnap backup for Oracle 10g, you have to install the Oracle VSS Writer. (metalink id 580558.1)
  • The snapshot Control and SP file locations should be snap-able.
  • Volume level Snaps are supported.
  • Database volumes should be on one of the supported storage arrays.

You need to enable Snap Protect from subclient properties to perform a IntelliSnap backup using VSS. Use the following steps to enable VSS for IntelliSnap backup:

  1. From the CommCell Browser, navigate to Client Computers | <Client>| Oracle | <Instance>.
  2. Right-click the <Subclient>,and then click Properties.
  3. Click the IntelliSnap Operations tab.
  4. Select the Snap Engine from Available Snap Engines list.

  5. Select Use Oracle VSS Writer check box.
  6. Click OK.

Configuring Lights Out Script 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 | <Client> | Oracle | < Instance>.
  2. Right-click the <Subclient>, and click Properties.
  3. Click the Content tab, and then click Offline Database.
  4. Click the Advanced tab, and then click the Offline Databases 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. In the No. of Retries box, type the number of times the system must retry to attempt to shut down the database.
  9. In the Sleep Time Between Retries (Sec) box, select or type the number of seconds that you want the script to wait between retry attempts to shut down the database and check the status.
  10. Select the Use SQL Connect checkbox to connect to the oracle database.
  11. In the Startup Parameter File (PFILE) Location box enter the PFILE location.
  12. 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 | <Client>| Oracle.
  3. Right-click the <Instance>, and then click Properties.
  4. Click the Details tab.
  5. Select the Use Catalog Connect check box.
  6. In the Catalog Connect String box
    • In the User ID box, type the Database user ID.
    • Click the Password box, in the Enter Password box, type the password for the user ID.
    • In the Confirm Password box, retype the password, and then click OK.
    • Type the Oracle service name.

    For example:

    sysdba/<password>@<orcl

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

  7. Click OK.

Enabling Verification of Datafiles during Backup (Snap Integrity Check)

The Snap Integrity Checks are off by default.

To change the Snap Integrity Check value:

  1. From the CommCell Browser, navigate to Client Computers <Client>| Oracle | <Instance>.
  2. Right-click the <Oracle Subclient>, and then click Properties.
  3. Navigate to the IntelliSnap Operations tab the Subclient Properties dialog.
  4.         Check the Enable Snap Integrity Check check box to enable the feature.

            Clear the Enable Snap Integrity Check check box to disable the feature.

  5. Click OK.

The following steps are performed during an IntelliSnap backup without the snap integrity check

  1. The database is placed in a quiesce state.
  2. A snapshot is created for data volumes.
  3. The database is placed in a unquiesce state.
  4. The snapshot is created for log volumes.

When the Snap Integrity Check is enabled, the following two additional steps are performed after taking snaps.

  1. The snapshot is mounted on the source and cataloging of datafiles/archived logs is performed from the mounted snapshot. This verifies whether all the datafiles/archived logs are properly captured during an IntelliSnap backup. RMAN catalog datafilecopy checks the datafile header and verify its authenticity before cataloging it.
  2. Once the catalog is completed, an uncatalog happens and the snapshot is unmounted from the source.

When using ASM databases, during snap integrity check, the snap mount path is appended to the ASM disk string to enable discovery of ASM disks. This does not have any impact on the Oracle database or clients. Also, the check ensures that the modified ASM disk string does not impact the discovery of ASM disks belonging to already existing disk group.

Once the snap integrity check is completed, the appended snap mount path in the ASM disk string is retained and can be reused for other IntelliSnap jobs.

Configuring Backup Copy Operations

The following sections describe the additional modes of Backup Copy Operations:

File System Backup Copy

By default, the system will use the File System for copying the data to the media. The system will scan the file, generate and read the collect file, extract the file list and copies the data on to the tape using MediaAgent's data mover.

In order to perform the file system snap to tape copy on a proxy computer, ensure that the MediaAgent and File System iDataAgent are installed on the proxy computer.

Advantage:

  • Requires less resources and the configuration is simple.
  • Parallel backup copies can be run for different sources using the same proxy computer.

Disadvantage:

  • File system backup copy is supported for full backups of non-ASM databases.
  • Empty blocks of data files are also included in the backup.

Use the following steps to configure file system backup copy operation:

  1. From the CommCell Browser, navigate to Client Computers | <Client> | Oracle | <Instance>.
  2. Right-click the subclient and click Properties.
  3. Click IntelliSnap Operations.
  4. Select IntelliSnap.
  5. Click Available Snap Engines drop-down box and select the storage array.
  6. Click OK.

RMAN Backup Copy

You can also use RMAN for copying the data to the media.

When data is moved from snap to media, the RMAN backup interface is used for block level backup operations. Also, these backup operations are recorded on the RMAN catalog. RMAN is required in the case of Automatic Storage Management (ASM) Oracle Databases, since ASM data is not available on the file system. You can also run RMAN restores/reports from these backups.

Advantage:

  • Supports full and incremental backup copy
  • Supports backup of ASM database
  • Most of the RMAN features can be utilized for backups and restores.

Disadvantage

  • The Oracle application should be installed on the proxy computer.
  • Resource intensive since Oracle instances need to be configured on the proxy computer
  • Parallel backup copies of same instance or data directory structure for different sources using the same proxy is not possible.

Prior to using RMAN for copying the data to the media, ensure the following:

  • The Oracle iDataAgent and MediaAgent must be installed on the proxy computer.
  • The Oracle instance on the proxy computer should have the same name as that in the source computer.
  • The Oracle version installed on the proxy and source computers should be compatible. However, the major version of Oracle should be the same.
  • For backups involving ASM instances, both ASM and the RDBMS instances have to be configured on the proxy computer.
  • The catalog user and the catalog database must be the accessible by the source and the proxy Oracle instances.
  • The proxy and source computer should have the same directory structure e.g. dump, diagnostic and data directories.
  • Oracle database requires the ASM to be registered with Oracle Cluster Registry (OCR). It will ensure the RMAN to successfully mount the disk group.
  • If multiple source client database instances are configured to run RMAN backup copy on the same proxy MediaAgent, the backup copy may fail due to instance and database name conflicts. The conflicting database and instances need to be moved to a different proxy MediaAgent in such cases.

During an RMAN backup copy, the proxy database is started in mount mode using the backup control file from the IntelliSnap backup. Additional Oracle licenses may be required for the proxy database. Please inquire with Oracle support to determine if additional Oracle licenses are required in your environment.

Use the following steps to configure RMAN backup copy:

  1. From the CommCell Browser, navigate to Client Computers | <Client> | Oracle | <Instance>.
  2. Right-click the subclient and click Properties.
  3. Click IntelliSnap Operations.
  4. Select IntelliSnap.
  5. Click Available Snap Engines drop-down box and select the storage array.
  6. Select Use RMAN for Backup Copy.

    The Use RMAN for Backup Copy option is not supported for software snapshots.

  7. Click OK.

RMAN Incremental Backup Copy

Oracle RMAN incremental backup copy can be performed on a proxy server.

Prior to performing the RMAN incremental backup copy, ensure the following:

  • The database physical schema is the same in both the snap and the current backup (i.e. no addition or deletion of tablespaces between time of snap and current backup).
  • The Oracle user ID/group ID on source and proxy should be the same otherwise the RMAN backup copy will fail due to permission issues.
  1. Copy the Oracle parameter file (pfile) and password file from the source to the proxy computer's $ORACLE_HOME/dbs/ directory.
  2. Create the bdump, udump, adump, cdump and diagnostic_dest directories. Ensure that the directories are in the same location as the source.
  3. Create the DB_CREATE_FILE_DEST and LOG_ARCHIVE_DEST directories. If there are multiple archive destinations, then create the directories for each of the archivelog destinations.
  4. Copy the catalog connection information from the source to the proxy in the tnsnames.ora.
  5. Startup the proxy instance in NOMOUNT mode.
  6. Configure the proxy Oracle Instance on the CommCell Console.
  7. From the CommCell Browser, navigate to Client Computers | <Client> | Oracle | <Instance>.
  8. Right-click the subclient and click Properties.
  9. Click IntelliSnap Operations.
  10. Select IntelliSnap.
  11. Click Available Snap Engines drop-down box and select the storage array.
  12. Click Use Proxy drop-down box and select the configured proxy from the dropdown list.
  13. Select Use RMAN for Backup Copy and click OK.

    The Incremental option is now available for backup.

Preventing RMAN Backup Copy Failures due to Mount Point and ASM Disk Group Name Conflicts on a Proxy MediaAgent

By default, during RMAN backup copy the data snaps are mounted in the same location as source on proxy MediaAgents. In case of ASM databases, the ASM Disk Groups are not renamed during RMAN backup copy. This is to facilitate incremental RMAN backup copy where the datafile paths need to be in the same path as source.

However, if you use the same proxy MediaAgent for multiple databases RMAN backup copy may fail if the file system mount points or ASM Disk Group names of different Oracle instances conflict with each other.

In such cases, use the following steps to make the data snaps to be mounted on a different path or in case of ASM databases, to rename the ASM Disk Groups uniquely:

  1. From the CommCell Browser, navigate to Storage Resources | MediaAgents.
  2. Right-click the <Proxy MediaAgent>, and then click Properties.
  3. Click the Additional Settings tab.
  4. Click Add.
  5. In the Name box, type sRMANDATAFILECOPY.
  6. In the Category box, type or select OracleAgent from the list.
  7. In the Type box, select String.
  8. In the Value box, type Y and then click OK.

    RMAN incremental backups will not be possible if we set this additional setting as we use BACKUP DATAFILECOPY syntax in this case.

Configuring Streams for Backup Copy

By default, backup data is sent to media in two streams. This means that a database is sent to media during a backup in two parallel waves. This results in backup taking about half the time to complete as it otherwise would if only one stream is used.

You can increase the number of streams used for backups for a particular subclient provided the number of streams does not exceed the maximum number configured in the subclient's storage policy. Increasing the number of streams for a subclient further reduces the amount of time a backup takes to complete. For example, increasing the number of streams from 2 to 3 enhances backup time from one-half that of a single stream to one-third.

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 | <Client>| Oracle | <Instance>.
  2. Right-click the <Subclient>, and then click Properties.
  3. Click the Storage Device tab.
  4. In the Number of Data Backup Streams box, type or select the number of data backup streams.
  5. Click OK.

Log Backups

  1. From the CommCell Browser, navigate to Client Computers | <Client>| Oracle.
  2. Right-click the <Instance>, and then click Properties.
  3. Click the Storage Device tab, and then click the Log Backup tab.
  4. In the Number of Archive Log Backup Streams box, type or select the number of log backup streams.
  5. Click OK.

Performance Tuning

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 1048576 Kb.

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 | <Client> | Oracle | <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 in each RMAN backup set.
  5. In the Maximum Size box, type or select the size of backup set allowed for RMAN backup set.
  6. In the Archive Files (BFS) box, type or select the number of archive files in each RMAN backup set.
  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.

  1. From the CommCell Browser, navigate to Client Computers | <Client>| Oracle.
  2. Right-click the <Instance>, and then click Properties.
  3. Click the Details tab.
  4. In the Block Size box, type or select the size of the block for backup and restore operations.
  5. Click OK.

Assigning Unique Identification Tags for Backup Copy

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 Subclient Properties dialog box , navigate to the Backup Arguments tab under the Advanced tab.
  4. In the Backup 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 | <Client>| Oracle| <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 Inacessible Data and Archive Redo Log Files check box to exclude inaccessible data and log files.
  7. Click OK.

Configuring RMAN Backup Copy Using Proxy for ASM Databases

When data is moved from snap to media, the RMAN backup interface is used for block level backup operations. Also, these backup operations are recorded on the RMAN catalog. RMAN is required in the case of Automatic Storage Management (ASM) Oracle Databases, since ASM data is not available on the file system. You can also run RMAN restores/reports from these backups.

Prerequisites

Prior to using RMAN for copying the data to the media, ensure the following:

  • Both source and proxy machine should have the same O/S resources like directory structure, memory, and kernel.
  • The Oracle iDataAgent must be installed on the proxy computer.
  • The Oracle instance (RDBMS) on the proxy computer should have the same name as that in the source computer.
  • The Oracle version installed on the proxy and source computers should be compatible. However, the major version of Oracle should be the same.
  • For backups involving ASM instances, both ASM and the RDBMS instances have to be configured on the proxy computer.
  • The ASM instance and RDBMS instance should be started.
  • Also RDBMS and ASM instances should be configure on commcell GUI for PROXY client.
  • Using ASM storage, ASM data group should not be same as source database. For example, if source ASM instance has a disk group “DG1”, proxy machine should not use “DG1” as disk group name.

    Use the following SQL Script to find data group names on both source and proxy computers:

    SQlPLUS# select name,total_mb,free_mb from v$asm_diskgroup;

  • The catalog user and the catalog database must be the accessible by the source and the proxy Oracle instances.
  • Make sure the software has permissions to create a disk group on proxy machine similar to source.
  • The proxy and source computer should have the same directory structure e.g. dump, diagnostic and data directories.
  • Oracle database requires the ASM to be registered with Oracle Cluster Registry (OCR), since the ASM instance is a resource in CRS repository. It will ensure that the RMAN has successfully mounted the disk group.

Use the following steps to configure RMAN backup copy for ASM database:

  1. Confirm Oracle Version is same on both Proxy and Source.

    Grid@dbproxy>sqlplus -v
    SQL*Plus: Release 11.2.0.1.0 Production.

  2. Copy spfile<SID>.ora from source to target for both ASM instance and RDBMS instance.
  3. Create a user for proxy ASM instance with SYSASM, SYSOPER previleges.

    Grid@powerstar>sqlplus "/ as sysasm" SQL> create user ASMDBA identified by test01;
    User created.
    SQL> grant SYSASM, SYSOPER to ASMDBA;
    Grant succeeded.
    SQL> select * from v$pwfile_users;
    USERNAME SYSDBA SYSOPE SYSASM
    —————————— —— —— ——
    SYS TRUE TRUE TRUE
    ASMDBA FALSE TRUE TRUE

  4. Startup the ASM instance and RDBMS instance.
  5. Configure the ASM instance and RDBMS instance from the CommCell Console for proxy.

    Once configured, you can run inline or offline backup copy jobs on the CommCell Console.

Preventing the Software from Setting the RMAN Backup Piece to Unavailable

By default during the data aging operation, the Commvault software sets the backup piece to unavailable, by adding the following line to the RMAN script:

change backuppiece 'id1','id2' 'idN' unavailable

If you want to prevent the software from adding the line to the script, set the Disable RMAN cross check check box.

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

    The Instance Properties dialog box appears.

  3. On the Details tab, select the Disable RMAN cross check check box.
  4. Click OK to close the warning message.
  5. Click OK.

Configuring the Backup Piece Format

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

Hex_CommCell_ID – Hexadecimal CommCell ID

CvJobID –Commvault  job id

%d - represents the Oracle database name

%U – unique identifier

To have the default backup piece format ‘%U’ as before, set the following Additional Setting on  the CommCell.

  1. From the CommCell Browser, navigate to Client Computers.
  2. Right-click the <Client>, and then click Properties.
  3. Click Advanced.
  4. Click the Additional Settings tab.
  5. Click Add.
  6. In the Name box, type sDisableBackupPieceFormat.
  7. In the Category box, select or type OracleAgent.
  8. In the Type box, select String.
  9. In the Value box, type Y and click OK.
  10. Click OK.

Customizing the Backup Piece Format

You can customize the backup piece format for non RMAN backups by setting the following Additional Setting.

  1. From the CommCell Browser, navigate to the CommCell.
  2. Right-click the <CommCell>, and click Properties.
  3. On the Properties dialog box, navigate to the Additional Settings tab and click Add.
  4. In the Name box, type sCustombackupPieceFormat.
  5. In the Category box, select or type CommServe
  6. In the Type box, select String.
  7. In the Value box, type the format and click OK.
  8. Click OK.

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 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.
Enable and Disable Encryption for Third-Party Command Line Operations You can enable data encryption for the command line operations from instance properties:
  1. From the CommCell Browser, navigate to Client Computers | <Client>| Oracle.
  2. Right-click the <Instance>, and then click Properties.
  3. Click the Encryption tab.
  4. Select the desired Encryption from the following:
    • None
    • Media Only (MediaAgent Side)
    • Network and Media (Agent Side)
    • Network Only (Agent Encrypts, MediaAgent Decrypt
  5. Click OK.
 
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.

For information on how to recover data if you accidentally delete an entity, see Recovering Data Associated with Deleted Clients and Storage Policies.

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

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 Controller. 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 | <Client> | <Agent> | <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.