CommCell Console SAP Oracle Configuration

Table of Contents

Choosing the Backup Interface

You can set this option for each subclient.

Note: The util_vol and util_Vol_online interfaces are for SnapProtect backups.

The following backup interfaces are available for the SAP Oracle iDataAgent:

  • RMAN_UTIL - Use this interface when you want to perform a full, selective online full, or incremental backup of an online database. You must choose this interface to perform an incremental backup, or when the subclient is for a RAC instance. When you select this option, the Oracle RMAN utility controls the backup.
  • util_file - Use this interface when you want to perform a full backup, or a selective online full backup. When you select this option, the database is locked until the full backup completes.
  • util_file_online - Use this interface when you want to perform a full backup, or a selective online full backup. When you select this option, the database locks each tablespace during the backup and releases it when the backup completes.

Creating an Instance

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

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

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

About This Task

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

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

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

Procedure

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

      Note: For a RAC configuration, this is the DDB SID.

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

      Expand All

      UNIX

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

      On the command line, type the following command:

      su - ora<SID>
      echo $ORACLE_SID

      Example

      su - ora<CER>
      echo $ORACLE_SID
      CER

      Windows

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

      On the command line, type the following command:

      echo %ORACLE_SID%

      Example

      echo %ORACLE_SID%
      TRD

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

      Note: For a RAC configuration, use ora<SID> as the account.

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

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

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

      Note: For a RAC configuration, verify this with the customer, or the administrator.

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

      UNIX

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

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

      echo $ORACLE_HOME

      Example

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

      Windows

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

      On the command line, type the following command:

      echo %ORACLE_HOME%

      Example

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

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

      Note: For a RAC configuration, verify this with the customer, or the administrator.

      The SAP server environment variables contain this information.

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

      Expand All

      UNIX

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

      On the command line, type the following command:

      echo $SAPDATA_HOME

      Example

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

      Windows

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

      On the command line, type the following command:

      echo %SAPDATA_HOME%

      Example

      echo %SAPDATA_HOME%
      I:\oracle\TRD

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

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

      Expand All

      UNIX

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

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

      echo $SAPEXE

      Example

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

      Windows

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

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

      echo %SAPEXE%

      Example

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

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

Creating a Subclient for Offline Backups

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

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

Before You Begin

Procedure

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

    The Create New Subclient dialog box appears.

  3. On the General tab, in the Subclient name box, enter a name for the subclient.
  4. On the Content tab:
    • Select the Data check box.
    • Select the Offline Database option.
    • Select the backup interface. If you will use this subclient for incremental backups, or the subclient is for a RAC instance in the Backup Device section, select the Rman_util option.
  5. On the Storage Device tab, select the name of the Data Storage Policy.
  6. Optional: Run scripts before or after the backup.

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

    On the Pre/Post tab:

    1. In the Pre-Backup Command box, type the full path name for the script.
    2. In the PostBackup Command box, type the full path name for the script.
    3. To run the post backup process regardless of the job's outcome, select the Run Post Process for all attempts check box.
  7. Click OK to close the Create New Subclient dialog box.

What to Do Next

Creating a Subclient for Online Backups

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

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

Full backups include all the datafiles, tablespaces, and log files. Incremental backups include only the changed data and log files and take less time to run than full backups.

Before You Begin

Procedure

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

    The Create New Subclient dialog box appears.

  3. On the General tab, in the Subclient name box, enter a name for the subclient.
  4. On the Content tab:
    • Select the Data check box.
    • Select the Online Database option.
    • Select the backup interface. If you will use this subclient for incremental backups, or the subclient is for a RAC instance, in the Backup Device section, select Rman_util.
  5. On the Storage Device tab, select the name of the Data Storage Policy.
  6. Optional: Run scripts before or after the backup.

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

    On the Pre/Post tab:

    1. In the Pre-Backup Command box, type the full path name for the script.
    2. In the PostBackup Command box, type the full path name for the script.
    3. To run the post backup process regardless of the job's outcome, select the Run Post Process for all attempts check box.
  7. Click OK to close the Create New Subclient dialog box.

What to Do Next

Creating a Subclient for Individual Datafiles and Tablespaces Backups

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

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

Before You Begin

Procedure

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

    The Create New Subclient dialog box appears.

  3. On the General tab, in the Subclient name box, enter a name for the subclient.
  4. On the Content tab.
    • Select the Online Subset option.
    • Click Yes on the Warning dialog box.
    • From the Current Database View, select the database objects to include.
    • Select the backup interface. If this subclient will be used for incremental backups, in the Backup Device section, select the Rman_util option.
  5. On the Storage Device tab select the name of the Data Storage Policy.
  6. Click OK to close the Create New Subclient dialog box.

What to Do Next

Creating Subclients for Log Backups

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

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

Create separate subclients to backup log files because they are mandatory for recovering data.

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

Before You Begin

Procedure

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

    The Create New Subclient dialog box appears.

  3. On the General tab, in the Subclient name box, enter a name for the subclient.
  4. On the Content tab, clear the Data check box and then select interface, from the Backup Device. If  the subclient is for a RAC instance, select Rman_util.
  5. On the Log Backups tab:
    • Select the Backup Archive Log check box.
    • Optional: Select the Archive Delete check box to delete the logs after the backup completes.
    • Optional: Select the Disable Switch Current Log check box to disable log switching for the current redo log.
    • Optional: Select the Archive Log Second Copy check box to create a second copy of the archived offline redo log files.
  6. On the Storage Device tab, in the Log Storage Policy list, select the storage policy name for the log backups.
  7. Optional: Run scripts before or after the backup.

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

    On the Pre/Post tab:

    1. In the Pre-Backup Command box, type the full path name for the script.
    2. In the PostBackup Command box, type the full path name for the script.
    3. To run the post backup process regardless of the job's outcome, select the Run Post Process for all attempts check box.
  8. Click OK to close the Creating New Subclient dialog box.

Creating 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.

Before You Begin

  1. Create a Selective Copy.
  2. Create an instance.

Procedure

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

    The Create New Subclient dialog box appears.

  3. On the General tab, in the Subclient name box, enter the subclient name.
  4. On the Content tab, select the Selective Online Full check box and select the Backup Device type. If  the subclient is for a RAC instance, select Rman_util.
  5. On the Storage Device tab, in the Data Storage Policy list, select the storage policy name with the selective copy.
  6. Click OK to close the Creating New Subclient dialog box.

Configuring the Storage Policy for a Log Backup during a Selective Online Full Backup

When a selective online full backup is running, by default log backups use the data storage policy.

To have log only backups which run in parallel with selective online full backups use the log storage policy execute the following command. Note when this is run, the log phase of the selective online full backup still uses the data storage policy.

qoperation execscript -sn SetKeyIntoGlobalParamTbl.sql -si JMDontForceDataSPForLogBkp -si y -si 1

To have log only backups that are part of a selective online full backup use the data storage policy, run the following command.

qoperation execscript -sn SetKeyIntoGlobalParamTbl.sql -si JMDontForceDataSPForLogBkp -si n

Setting the SAP Oracle Job ID Timeout

You can use the BRARCHIVE tool to archive online redo logs, to prevent the SnapProtect software from generating multiple job IDs in a BRARCHIVE session.

By default, the SnapProtect software generates a new job ID every 6 minutes.

Valid values are from 360 seconds to 86400 seconds.

Best Practice: Set this value to a higher value, based on how often online redo logs are generated.

Procedure

  1. To set the job ID timeout, from the CommCell Browser, right-click the client, and then click Properties:
  2. In the Client Properties dialog box, click the Additional Settings tab and then click Add.
  3. In the Add Additional Settings dialog box, enter the details for the additional setting:
    1. In the Name box, type nSINGLEJOBMERGETIMEOUT.
    2. In Category box, select SAP.
    3. In the Type box, select String.
    4. In Value box, type the value in seconds to wait to merge the job, for example 480.
    5. Click OK to close the Add Additional Settings dialog box.
  4. Click OK to close the Client Properties dialog box.

Registering the Client with SAP Software Landscape Directory (SLD)

Once you install the SAP Oracle Agent, you must register the SAP Oracle Agent software with the SAP SLD.

  1. Create an XML File using the backint program.

    On UNIX:

    Run the BACKINT program in the <iDataAgent> directory as a root user.

    On Windows:

    Run the BACKINT program as an administrator.

    This creates an xml file, with the client name, in the same directory.

    backint <-f createsldxml> <short_client_name> <oracle>

    Example:

    backint -f createsldxml client1 oracle

  2. Verify a minimum of JRE version 1.7.0_17 is installed. On the command line, type the following commands:

    # java -version
    java version "1.7.0"
    Java(TM) SE Runtime Environment (build 1.7.0_b147)
    Java HotSpot(TM) 64-Bit Server VM (build 21.0_b147, mixed mode)

  3. On the SAP Oracle Agent client, on the command line run the following command.

    A return code of 200 is a successful registration of the SAP Oracle client in the SLD.

    java -cp sldreg.jar sldreg <SLD_HOST_NAME> <PORT_NUMBER> <USER_NAME> <PASSWORD> <XML_FILE>
    Example:
    # java -cp sldreg.jar sldreg 155.56.49.26 80 3rd_party isvconnect08 client1_oracle.xml
    Retcode:200

Configuring Multiple Data Paths for Load Sharing

In a primary copy, you can now allow multiple streams of a backup job to share the load on multiple DataPaths. This will release the load on a single Data Path and allows you to obtain the streams from Multiple Data Paths. You can configure a storage policy primary copy with multiple data paths to perform parallel backups.

For Example:

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

  • Configure a storage policy primary copy with multiple data paths
  • Reserve resource allocation for these data paths using media management's Resource Manager.

This allows you to allocate multiple streams of a backup job to share the load on multiple Data Paths.

Configuring a Primary Copy with Multiple Data Paths

Use the following steps to configure a primary copy with multiple data paths:

  1. From the CommCell Browser, navigate to Policies  | Storage Policies.
  2. Select the Storage Policy that you are using for your iDataAgent. Select the Primary Copy. If you have not yet created a Primary Copy for your iDataAgent, see Creating a Storage Polocy for a step-by-step procedure to create a primary copy.
  3. Right click the Primary Copy and click Properties.
  4. Click the Data Paths tab.
  5. Click Add to select and add the additional data paths.

  6. Click OK.

    In the following image, you can view 2 different libraries (For example, HP EML E Series 28 and HP MSL G3 Series 29) configured as different DataPaths.

    DataPathId="111" MediaAgent="dbcs" Library="HP EML E Series 28" DrivePool="DrivePool(dbcs)32" SpareGroup="Default Scratch“

    DataPathId="112" MediaAgent="dbserve12" Library="HP EML E Series 28" DrivePool="DrivePool(dbserve12)28" SpareGroup="Default Scratch"

    DataPathId="113" MediaAgent="dbcs" Library="HP MSL G3 Series 29" DrivePool="DrivePool(dbcs)33" SpareGroup="Default Scratch"

    DataPathId="114" MediaAgent="dbserve12" Library="HP MSL G3 Series 29" DrivePool="DrivePool(dbserve12)29" SpareGroup="Default Scratch"

Configuring Resource Manager to Reserve Resource Allocation for Multiple Data Paths

You can create reservations on multiple data paths at the same time if there is not enough Resources from any single data path. Use the following steps to reserve resource allocation using Media Management's Resource Manager for multiple data paths:

  1. From the CommCell Console toolbar, click Control Panel.

  2. Click Media Management.

  3. Click Resource Manager Configuration tab.

  4. Select Allow load-balance on multiple data paths within one backup job. Double click the value box and set the Value as 1.

  5. Click OK.

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 Sharing for more information.

Modifying an Instance or Subclient

Certain properties of Agents, Instances, and Subclients can be modified to accommodate changes to your configuration, data, or desired backup behavior.

You cannot modify the properties of an instance or subclient when a job is in progress for that specific instance or subclient. If a job is in progress, either wait for the job to complete or kill the job from the Job Controller.

The following table describes the properties that can be configured from these levels.

Option Description Related Topics
Change the User Account Details

You must have administrator privileges to access the Oracle application and perform backup and restore operations.

In the case of  backup and restore operations from the CommCell Console, the user credentials to access the Oracle application are provided initially when you create the instance. You can be modify the user credentials from CommCell Console.

Always use the following user name to perform backup and restore operations from the CommCell Console for the associated instance:

  • On Unix clients, use <SID_name>adm
  • On Windows clients, use <client_name>/<SID_name>adm

On Unix clients:

  1. From the CommCell Browser, right-click the SAP for Oracle Instance
  2. Click Properties.
  3. Click General tab and type the user name in the ORACLE USER field.
  4. Click OK to save your settings.
On Windows clients:
  1. From the CommCell Browser, right-click the SAP for Oracle Instance.
  2. Click Properties.
  3. Click General tab and then click Change.
  4. Enter the impersonate user name and password in Impersonate NT User dialog.
  5. Click OK to save your settings.
 
Change the Designated Home Directory You can change the Home Directory from the instance level.
  1. From the CommCell Browser, right-click the SAP for Oracle Instance.
  2. Click Properties.
  3. Click General tab and type the path in ORACLE HOME field or click Browse to locate the path.
  4. Click OK to save your settings.
 
Change the Path to Oracle Files You can change the path to the Oracle data and control files from the instance level.
  1. From the CommCell Browser, right-click the SAP for Oracle Instance.
  2. Click Properties.
  3. Click General tab and enter the path to the Oracle files in the SAP Data Path field or click Browse to locate the path.
  4. Click OK to save your settings.
 
Change Connect Details You can view and modify the connect string details for an instance. You might need to change the connect string details in any of the following situations:
  • To connect to the Oracle database as a different user.
  • To modify the password for the user.
  1. From the CommCell Browser, right-click the SAP for Oracle Instance.
  2. Click Properties.
  3. Click Details tab and enter the target database connect string in the Connect String field.
  4. Click OK to save your settings.
 
Change the Path to the SAPEXE Folder SAPEXE is a SAP kernel directory for the SAP Application. It is the path where the binaries are stored. The Path to the SAPEXE directory can be found from the Environmental parameters of the SAP system.

You can view and change the path to the SAP EXE folder from the instance level.

  1. From the CommCell Browser, right-click the SAP for Oracle Instance.
  2. Click Properties.
  3. Click Details tab and type the path to the SAP EXE folder in the SAP EXE Folder (Required) field or click Browse to locate the path.
  4. Click OK to save your settings.
 
Change Storage Policies You can configure storage policies from the instance level or subclient level.

You might need to 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 for command line backup and log backup from the instance level.

  1. From the CommCell Browser, right-click the SAP for Oracle Instance.
  2. Click Properties.
  3. Click Storage Device tab and do any of the following:
  4. Click Command Line Backup tab and select from the list of existing storage policies for command line backups.
  5. Click Log Backup tab and select from the list of existing storage policies for log backups.
  6. Click OK to save your settings.

You can change the storage policies for data backup from the subclient level.

  1. From the CommCell Browser, right-click the subclient.
  2. Click Properties.
  3. Click Storage Device tab.
  4. Click Data Storage Policy tab and select a data storage policy to associate with this subclient.
  5. Click OK to save your settings.
Refer to Storage Policies.
Rename a Subclient You can rename an existing subclient.
  1. From the CommCell Browser, right-click the subclient.
  2. Click Properties.
  3. Click General tab and type the new name in the Subclient Name field
  4. Click OK to save your settings.
 
Archive Delete This option is available only when you select the Backup Archive Log option. When you select this option, the archived redo log files will be deleted once they are backed up. Any archived redo log files that do not match the format indicated by the LOG_ARCHIVE_FORMAT environment variable are not deleted.
  1. From the CommCell Browser, right-click the subclient.
  2. Click the Content tab and select the Backup Archive Log option.
  3. Select Archive Delete.
 
Archive Log Second Copy When taking log backups, you can also choose to create a second copy of the offline redo logs files which were already archived. If your first copy of the logs are missing, you can use this second copy to recover a database.
  1. From the CommCell Browser, right-click the subclient.
  2. Click the Content tab and select the Archive Log Second Copy.
 
Enable/Disable Log Switch You can enable/disable the log switch for a SAP Oracle backup from the subclient level.

When performing archive log backups, a log switch is initiated wherein 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. The closed redo log file is then archived during the log phase. However,  you can disable the log switch if required.

  1. From the CommCell Browser, right-click the subclient.
  2. Click the Content tab and select the Backup Archive Log option.
  3. Select the Disable Switch Current Log option to specify that log switch is disabled for current redo log files.
  4. Click OK to save your settings.
 
Configure Data Transfer Options You can efficiently 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 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.
 
Set the number of Streams You can set the number of streams for log backup from the instance level.
  1. From the CommCell Browser, right-click the SAP for Oracle Instance.
  2. Click Properties.
  3. Click Storage Device tab.
  4. Click Log Backup tab and select Number of Data Backup Streams.
  5. Click OK.
Similarly, you can set the number of streams for data backup from the subclient level.
  1. From the CommCell Browser, right-click the subclient.
  2. Click Properties.
  3. Click Storage Device.
  4. Click Data Transfer Option tab.
  5. Select Number of Data Backup Streams.
  6. Click OK.
 
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 to which this CommCell object is associated.
  • Associate this object with a user group.
  • Disassociate this object from a user group.
  1. From the CommCell browser, right-click the subclient.
  2. Click Properties.
  3. Click Security.
  4. Select the appropriate user groups to which you want to associate to the CommCell object from the Available Groups pane, and then move the user group to the Associated Groups pane.
  5. Click OK.
Refer to User Administration and Security.
Enable and Disable Data Encryption You can enable data encryption from the subclient level. Encryption must be enabled at the client level prior to configuring any instances residing on that client.
  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 The Version tab, at the Agent level displays the software version and post-release service packs and updates installed for the component.
  1. From the CommCell browser, right-click the agent.
  2. Click Properties.
  3. Click Version.
  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 Instance or Subclient

The following sections describe the steps involved in deleting an 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 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> | <Backup Set>.
  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.