SnapProtect - Advanced Configuration - 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

In the CommCell Console each instance references an Oracle database. Hence it is necessary to discover the instances which can then be used to backup data. You can discover or add an instance as described in the following sections:

Enabling Automatic Instance Discovery

When automatic instance discovery is enabled, the existing Oracle database instances are discovered every 168 hours.

This capability ensures that all instances are accounted for on a regular basis for backups.

Automatic instance discovery will not detect the manually created databases in an instance. Make sure there is an entry in /etc/oratab for manually created oracle instance which contains manually created databases. Then, this instance is automatically discovered when you enable instance discovery.

Use the following steps to enable automatic instance discovery:

  1. From the CommCell Browser, navigate to Client Computers |<Client>.
  2. Right-click Oracle, and then click Properties.
  3. Select the Enable Instance Discovery check box.
  4. Click OK.

Setting the Automatic Discovery Frequency

When instance discovery is enabled, Oracle instances are automatically discovered every 168 hours or whenever the Communications Service (GxCVD) is restarted. Use the following steps to modify the default discovery time interval.

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

    The Additional Settings dialog box will automatically display the Category and Type for this setting.

  6. In the Value box, type the time interval to discover instances.

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

  7. Click OK.

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, navigate to Client Computers |< Client >.
  2. Right-click Oracle, point to All Tasks, and then click New Instance (ORACLE SID).
  3. In the Instance (ORACLE SID) box, type the Instance name.
  4. In the User Account box, type the login credentials to access the Oracle client.
  5. In the ORACLE HOME box, type the Oracle application install path.
  6. In the Storage Policy used for the data of default subclient box, select a storage policy name.

  1. Click the Details tab.
  2. In the Connect String box, type the credentials to access the Oracle database. For example, sys/pwd12@orcl4.
  3. Click the Storage Device tab.
  4. In the Storage Policy used for user command backup of data box, select a storage policy.
  5. In the Storage Policy used for all Archive Log backups box, select a storage policy name.
  6. Click OK.

Configuring the Oracle Home Directory

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

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

Configuring the TNS ADMIN Directory

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

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

Configuring User Accounts for Backups

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

  1. An operating system account with administrator privileges to access the Oracle application.

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

    Operating System The User Account Should Be
    Windows
    • Local Administrator of the computer on which the Oracle database resides.
    • User should be part of the ora_dba group with read/write permissions on the SnapProtect folder.
    UNIX Member of the user group assigned during the iDataAgent installation. The operating system user account can also be used.
  2. An oracle user  account with sysdba privilege to access the Oracle database (Standard and Recovery Catalog databases). The account information is provided as a connect string with the following information:
    • Database User ID
    • Password for User ID
    • Oracle Service Name (As defined in tnsnames.ora file)

    You can 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.

    By default, the user account for the target database has administration privileges.

    Additional accounts (except Impersonate User) should be established by the Oracle database administrator.

    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 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. Navigate to the Details tab on the Properties dialog
  4. Enter the Connect String to connect to the Oracle database as follows:
    • Enter the Database user ID in the first box.
    • Enter the Password in the second box.
    • In the Confirm Password dialog, re-enter the password, and click OK.
    • Enter the Oracle Service name in the third box.
    For example, in the following:
    sysdba/<password>@orcl
    sysdba is the Database User ID, <password> is the Database User ID password, and orcl is the Oracle service name.
  5. Click OK.

Managing Subclients

When you create an instance, a default subclient is automatically created. The default subclient includes the entire database associated with that instance, which includes all components, such as the log files and control files. However, you can create user-defined subclients to backup the specific components or conditions, such as the following:

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

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

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.

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

  1. From the CommCell Browser, navigate to Client Computers | <Client>| Oracle.
  2. Right-click the <Instance>, point to All Tasks, and then click New Subclient.
  3. In the Subclient name box, type the subclient name.
  4. Click the Content tab.
  1. Click Offline Database.
  2. Click the Storage Device tab.
  3. In the Data Storage Policy box, select the storage policy name.
  1. Click the SnapProtect Operations tab.
  2. Select the SnapProtect checkbox.
  3. In the Available Snap Engines box, select the snap engine name.
  4. From the Use Proxy list, select the MediaAgent where backup copy operations will be performed.

    When performing SnapProtect backup using proxy, ensure that the operating system of the proxy server is either same or higher version than the client computer.

  5. Click OK.

Creating a Subclient for Online Backups

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

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

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

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

  1. From the CommCell Browser, navigate to Client Computers | <Client>| Oracle.
  2. Right-click the <Instance>, point to All Tasks, and then click New Subclient.
  3. In the Subclient name box, type the subclient name.
  4. Click the Content tab.
  1. Click Online Database.
  2. Click the Storage Device tab.
  3. In the Data Storage Policy box, select the storage policy name.
  1. Click the SnapProtect Operations tab.
  2. Select the SnapProtect checkbox.
  3. In the Available Snap Engines box, select the snap engine name.
  4. From the Use Proxy list, select the MediaAgent where backup copy operations will be performed.

    When performing SnapProtect backup using proxy, ensure that the operating system of the proxy server is either same or higher version than the client computer.

  5. Click OK.

Creating a Subclient to Back Up Individual Datafiles and Tablespaces

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

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

  1. From the CommCell Browser, navigate to Client Computers | <Client>| Oracle.
  2. Right-click the <Instance>, point to All Tasks, and then click New Subclient.
  3. In the Subclient name box, type the subclient name.
  4. Click the Content tab.
  1. Click Online Subset and select the database objects to be included in the backup.
  2. Click the Storage Device tab.
  3. In the Data Storage Policy box, select the storage policy name.
  1. Click the SnapProtect Operations tab.
  2. Select the SnapProtect checkbox.
  3. In the Available Snap Engines box, select the snap engine name.
  4. From the Use Proxy list, select the MediaAgent where backup copy operations will be performed.

    When performing SnapProtect backup using proxy, ensure that the operating system of the proxy server is either same or higher version than the client computer.

  5. Click OK.

Creating a Subclient for Selective Online Full Backups

You can selectively copy full backup to a selective copy during an auxiliary copy. The advantage of this type of backup is that both data and logs use the same storage policy, which means that they reside together on the same media. They are completely self-contained for restore and long term archiving purposes. Also, the data aging rules for selective online full backups are different from regular full backups, as both data and logs are aged together under the same storage policy

When performing the selective online full backup, note the following:

  • A selective online full backup job will wait for other Oracle backup jobs currently running on the same instance to complete before it begins.
  • For this type of backup, both data and archive logs will use the same storage policy as defined for data in the subclient, and will ignore the storage policy setting for archive logs (which is defined at the instance level).
  • During selective online full backups, if the data streams (defined at the subclient level) is less than the archive log streams (defined at the instance level), then both the data phase and the archive log phase will use the same number of streams defined for the data in the subclient, and will ignore the number of streams set for the archive logs.
  • While the data backup phase of a selective online full backup is running, the only other Oracle backup jobs that are allowed to run on the same instance are archive log backups. During the log backup phase of a selective online full backup, no other Oracle backups are allowed to run (neither logs nor data) on the same instance.
  • If other Oracle archive log backup jobs are running at the same time as the selective online full backup, they will be forced to use the same storage policy used by the selective online full backup during the time-frame in which the selective online full backup job is running, and will be included in the same auxiliary copy operation.
  • Selective online full backup jobs can be suspended in the job controller.
  • Selective online full backups restarts from the beginning of the phase. For example, if the selective online full backup jobs goes to pending state during the data phase, when restarted, the job starts from the beginning of the data phase.
  1. From the CommCell Browser, navigate to Client Computers | <Client>| Oracle.
  2. Right-click the <Instance>, point to All Tasks, and then click New Subclient.
  3. In the Subclient name box, type the subclient name.
  4. Click the Content tab.
  1. Select the Selective Online Full check box.
  2. Click the Storage Device tab.
  3. In the Data Storage Policy box, select the storage policy name.
  1. Click the SnapProtect Operations tab.
  2. Select the SnapProtect checkbox.
  3. In the Available Snap Engines box, select the snap engine name.
  4. From the Use Proxy list, select the MediaAgent where backup copy operations will be performed.

    When performing SnapProtect backup using proxy, ensure that the operating system of the proxy server is either same or higher version than the client computer.

  5. Click OK.

Configuring Selective Online Full Backups from Command Line

If you want to create a subclient for selective online full backup 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 selective online full 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 for Oracle Selective Online Full backup.

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

  3. Run the command to execute the qscript.

    D:\>qoperation execscript -sn SetSubClientProperty.sql -si 'c=client' -si 'a=Q_ORACLE' -si 'i=auto' -si 'b=default' -si 's=NEWSUB' -si 'Oracle Online Selective Full' -si '1' -si '2'

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

Selective Online Incremental Backup

When performing selective online incremental backups, note the following:

  • Selective online incremental backup jobs can be suspended in the Job controller and restarted from the point of failure like regular backups.
  • Selective online incremental backups are not copied to Selective copy.
  • Selective online incremental backup will use the storage policies specified for both data and logs.

Creating a Subclient for Log Backups

You can perform an SnapProtect backup separately for Logs. By default, the system will use data storage policy for SnapProtect backups and backup copy. If you create a log specific subclient, the log specific storage policy is used for SnapProtect backups and backup copies.

Use the following steps to configure log specific SnapProtect backups.

  1. From the CommCell Browser, navigate to Client Computers | <Client>| Oracle.
  2. Right-click the <Instance>, point to All Tasks, and then click New Subclient.
  3. In the Subclient name box, type the subclient name.
  4. Click the Content tab.
  1. Clear the Data checkbox.
  2. Click the Logs Backup tab.
  3. Select the Backup Archive Log check box.
  4. Click the Storage Device tab.
  5. In the Data Storage Policy box, select the storage policy name.
  6. Click the SnapProtect Operations tab.
  7. Select the SnapProtect checkbox.
  8. In the Available Snap Engines box, select the snap engine name.
  9. From the Use Proxy list, select the MediaAgent where backup copy operations will be performed.
  10. When performing SnapProtect backup using proxy, ensure that the operating system of the proxy server is either same or higher version than the client computer.

  11. Click OK.

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 SnapProtect Backup of Archive Logs

For subclients containing data and archive logs, you can choose to run an SnapProtect backup of only the data volume by configuring the logs to use RMAN. When using RMAN, the log backup will use the traditional backup method.

It is recommended to use this backup method in the following scenarios:

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

The SnapProtect backup and RMAN log backup will be executed as two separate jobs. Hence, prior to enabling RMAN for log backups, ensure that the catalog connect database is configured for the instance. This is required since the control file from the snapshot does not record the log backup information and you need the catalog database to restore the archived logs.

When a FULL job is submitted for this subclient, the SnapProtect job will be marked as FULL. However, the RMAN log job will be marked as Incremental.
Even though the entire set of logs are backed up, the log backup would be marked as Incremental only to make both the SnapProtect data and RMAN logs as part of the same cycle. During the data aging process, the data will be retained correctly based on the retention rules.

Snapping archive log volume in high transactional databases where check point frequently occurs, can sometimes lead to  incomplete data in the logs, which causes a recovery or RMAN backup copy to fail. We recommend using the “Use Rman for Log backup” option in a subclient used for RMAN streaming backups in these cases.

Use the following steps to configure RMAN log backups:

  1. From the CommCell Browser, navigate to <Client> | Oracle | <Instance>.
  2. Right-click the subclient and click Properties.
  3. Click the Log Backup tab.
  4. Click the Use RMAN for Log Backup option.
  5. Click OK.

Enabling Log Deletion after Backups

By default, the logs are not deleted after performing an SnapProtect backup for Logs. Use the following steps to enable the deletion of logs immediately after an SnapProtect backup.

Alternatively, you can also delete the logs from specific backups. See Deleting Archive Logs for a Specific Backup for more information.

  1. From the CommCell Browser, navigate to <Client> | Oracle.
  2. Right-click the <Instance> and then click Properties.
  3. Click the Log Backup tab.
  4. Click the Archive Delete checkbox.
  5. Click OK.

Configuring Archive Log Destinations

When you perform an SnapProtect backup for archive logs, you can specify the location for which an SnapProtect operation should be performed. This capability enables you to schedule SnapProtect operations from different log destinations on the same subclient. If necessary, you can also delete the logs after an SnapProtect backup.

Configuring the Log Destination for Backup

Use the following steps to configure the log destination for an SnapProtect 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 Log Backup tab.
  4. Click the Select ArchiveLog Destinations for Backup check box.
  5. Click Add.
  6. Type or select the Archive log file destination, and then click OK.
  7. Click OK.

Configuring the Log Destination for Deletion

Make sure to perform an SnapProtect backup on the logs in the specified location. If you have not performed an SnapProtect backup on the archived logs, it may lead to a data loss.

Use the following steps to delete the logs after an SnapProtect 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 Log Backup tab.
  4. Click the Select ArchiveLog Destinations for Delete check box.
  5. Click Yes to close the warning message.
  6. In the Confirmation box, type Confirm.
  7. Click OK.
  8. Click Add.
  9. Type or select the Archive log file destination.
  10. Click OK.

Configuring an ASM Instance

Prior to configuring the ASM instance, note the following:

  • Make sure to separately configure an ASM instance on the CommCell Console in addition to an RDBMS instance.
  • Make sure that the kfed utility resides under <Oracle ASM Home>/bin location. If the kfed utility do 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.

Use the following steps to configure the ASM instance:

  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.

    If your instance is in a different Oracle Home, you may have to manually add the instance as the discovery operation may not find it. When configuring the instance, verify the database status shows as STARTED.

  1. From the CommCell Browser, navigate to Client Computers |< Client >.
  2. Right-click Oracle, point to All Tasks, and then click New Instance (ORACLE SID).
  3. In the Instance (ORACLE SID) box, type the Instance name.
  4. In the User Account box, type the login credentials to access the Oracle client.
  5. In the ORACLE HOME box, type the Oracle application install path.
  6. In the Storage Policy used for the data of default subclient box, select a storage policy name.
  7. Click the Storage Device tab.
  8. In the Storage Policy used for user command backup of data box, select a storage policy.
  9. Click the Log Backup tab.
  10. In the Storage Policy used for all Archive Log backups box, select a storage policy name.
  11. Click OK.

  1. Click the Details tab.
  2. In the Connect String box, type the credentials to access the Oracle database. For example, sys/pwd12@orcl4.
  3. Click the Storage Device tab.
  4. In the Storage Policy used for user command backup of data box, select a storage policy.
  5. In the Storage Policy used for all Archive Log backups box, select a storage policy name.
  6. Click OK.

Once you create the ASM instance, you also need to create a corresponding RDBMS instance for the Oracle client.

You can create subclients for the regular RDBMS instance and perform SnapProtect backup jobs. When creating the subclient for SnapProtect operations, you must manually refresh the database after enabling SnapProtect. This will automatically select and grey out the Use RMAN for backup copy option on the subclient.

If the ASM disks are from persistent snap engine, then you need to disable the snap integrity. Refer Disabling Verification of Datafiles during SnapProtect 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

Configuring Table Restore

When a table backup is performed, all database tables are gathered in order to present the backup data in a table view during a browse operation.

Use the following steps to configure table backups:

  1. From the CommCell Browser, navigate to <Client> | Oracle | <Instance>.
  2. Right-click the subclient and click Properties.
  3. Click the Backup Arguments | Options tab.
  4. Click the Enable Table Browse option.
  5. Click OK.

After running a SnapProtect backup with table browse enabled on the subclient, you can restore database tables.

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 SnapProtect 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 SnapProtect backup using VSS:

  • You need to install the VSS Software Provider along with Oracle iDataAgent to perform SnapProtect backups.
  • To perform VSS SnapProtect 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 SnapProtect backup using VSS. Use the following steps to enable VSS for SnapProtect 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 SnapProtect 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 Backup Arguments tab, and then click the Offline Arguments tab.
  5. Select the Lights Out Script check box.
  6. Select the Warning checkbox to display a warning message on the physical node.
  7. In the Delay Time box, select the delay time interval in minutes.
  8. In the Sleep Time (min) box, select or type the number of minutes to wait between retry attempts.
  9. In the Sleep Time (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. In the Tries Number box, type the number of times the system must retry to attempt to shut down the database.
  11. Select the Use SQL Connect checkbox to connect to the oracle database.
  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 SnapProtect 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 SnapProtect backup without the snap integrity check

  1. The database is placed in a quiesced state.
  2. A snapshot is created for data volumes.
  3. The database is placed in a unquiesced 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 SnapProtect 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 SnapProtect jobs.

Configuring Proxy Clients for Backup Copy Operations

Configure a proxy client to run the backup copy operations, which frees resources on the source client. The proxy client must be logged in and visible on the hardware array containing the snapshots to be copied to media.

File System Copy Proxy Client Requirements

  • The proxy client operating system must be the same or higher than the source client operating system.
  • The File System Agent and MediaAgent must be installed on the client proxy.

RMAN Backup Copy Proxy Client Requirements

  • The proxy instance is started in MOUNT mode using the backup control file from the SnapProtect backup during an RMAN backup copy. Additional Oracle licenses may be required for proxy instances. Contact Oracle support to determine if additional Oracle licenses are required in your environment.
  • The proxy client operating system must be the same or higher than the source client operating system.
  • The Oracle Agent and MediaAgent must be installed on the proxy client.
  • The Oracle user ID and group ID on the proxy client must be the same as on the source client otherwise the RMAN backup copy will fail due to permission issues.
  • The Oracle database versions installed on the proxy and source clients must be compatible and the major version of Oracle must be the same.
  • A recovery catalog database must be used and accessible from RMAN on both the source and proxy client.
  • The proxy client must have the same directory structure for dump, diagnostic and data directories as the source client.
  • When multiple source client database instances are configured to run a RMAN backup copy using the same proxy client may fail due to instance and database name conflicts. Move the conflicting database and instances to a different proxy.
  • Configure an Oracle instance in the CommCell on the proxy client with the same source client instance name. See Managing Instances.
  • For non-ASM locations, all directories referring to Oracle parameters (for example db_create_file_dest) must exist and be accessible to Oracle.

 The following are mandatory requirements for the RMAN Backup Copy Proxy client when ASM is used for storage on the source database.

  • An Oracle ASM instance must be installed and running on the proxy client
  • The Oracle ASM instance must be configured in the CommCell.
  • Register the Oracle ASM with the Oracle Cluster Registry (OCR) so RMAN can successfully mount the ASM disk groups.
  • The Oracle ASM data diskgroup must not have the same name as any diskgroups on any source databases using the proxy. For example, if the source client ASM instance has a diskgroup named “DG1” then the proxy client ASM instance must not have “DG1” as a diskgroup name. Use the following SQL to find diskgroup names in use by ASM:

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

The proxy instance must be able to start up in the NOMOUNT mode using the PFile prior to backup copy. Create a PFile from the SP file on the source database with the following SQL command.

SQLPLUS> create pfile=/path/to/init<SID>.ora from spfile;

Copy the backup PFile to the proxy client’s $ORACLE_HOME/dbs (UNIX) or %ORACLE_HOME%/database (Windows) directory.

If the source database is an Oracle RAC database, create and copy the PFile using the method describe in the above paragraph, from one of the RAC clients to the corresponding location on the proxy client and delete or comment out the following line:

*.cluster_database=true

When the software starts the proxy database, it uses the source database control file.

When the software starts the proxy database, it uses the source database control file. This ensures that the source and proxy databases have the same database ID and that the source database can pick up the same backup pieces in the recovery catalog.

Configuring Backup Copy Operations

Configuring File System Backup Copy

By default the system uses the File System for copying data to the media. The system scans the file, generates and reads the collect file. It then extracts the file list and copies he data to the tape or magnetic library using the MediaAgent data mover.

The advantages include:

  • Simpler configuration
  • Fewer required resources
  • The same proxy computer can b used when running parallel backup copies for different sources

The disadvantages include:

  • Only full backups of non-ASM databases are supported
  • Backups include empty blocks of data files

Before You Begin

Verify all File System Copy Proxy Client Requirements are met.

Procedure

  1. From the CommCell Browser, navigate to Client Computers <Client>| Oracle | <Instance>.
  2. Right-click the <Oracle Subclient>, and then click Properties.
  3. On the SnapProtect Operations tab the Subclient Properties dialog box:
    1. Select the SnapProtect check box.
    2. In the Available Snap Engines box, select the storage array.
  4. Click OK to close the Subclient Properties dialog box.

Configuring RMAN Backup Copy

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. These backup operations are recorded on the RMAN catalog. RMAN is required in the case of Automatic Storage Management (ASM) Oracle Databases, because ASM data is not available on the file system. Run RMAN restores/reports from these backups.

The advantages include:

  • Full and incremental backup copies are supported
  • ASM database backups are supported
  • Most RMAN features for backups and restores are supported

The disadvantages include:

  • The Oracle application must be installed on the proxy client
  • More resource-intensive because Oracle instances need to be configured on the proxy computer
  • Parallel backup copies of the same instance or data directory structure for different sources using the same proxy is not possible.

Before You Begin

Verify all RMAN Backup Copy Proxy Client Requirements are met.

Procedure

  1. From the CommCell Browser, navigate to Client Computers <Client>| Oracle | <Instance>.
  2. Right-click the <Oracle Subclient>, and then click Properties.
  3. On the SnapProtect Operations tab the Subclient Properties dialog box:
    1. In the Use Proxy box, select the proxy.
    2. Select the Use RMAN for backup copy check box.
  4. Click OK to close the Subclient Properties dialog box.

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 SnapProtect Operations.
  10. Select SnapProtect.
  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 registry key 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.
  • Limiting the number of open datafiles that can be read by RMAN during the backup. The default value is 8.
  • Limiting the maximum size of data blocks used during backups. The default value is 262144 Kb.

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 Backup Arguments tab.
  4. In the Data Files per BFS box, type or select the number of datafiles in each RMAN backup set.
  5. In the MAX Backup Set Size (kb) box, type or select the size of backup set allowed for RMAN backup set.
  6. In the Archive Files per BFS box, type or select the number of archive files in each RMAN backup set.
  7. In the Max 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 Backup Arguments tab.
  4. In the Oracle Tag box, enter the tag name.
  5. Click OK.

Excluding Data during Backups

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

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

Use the following steps to exclude data during backup operations:

  1. From the CommCell Browser, navigate to Client Computers | <Client>| Oracle| <Instance>.
  2. Right-click the <Subclient>, and then click Properties.
  3. Click the Backup Arguments tab, and then click the Options tab.
  4. Select the SKIP READ ONLY check box to exclude the read only tablespaces.
  5. Select the SKIP OFFLINE check box to exclude the offline tablespaces.
  6. Select the SKIP INACCESSIBLE check box to exclude inaccessible data and log files.
  7. Click OK.

Disabling the RMAN Crosscheck

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

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

Configuring the Backup Piece Format

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

CvJobID –SnapProtect  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.

It is recommended that that you do not modify the properties of a subclient when a job is in progress for that specific 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 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.
 
Rename an Instance You can rename a subclient.
  1. From the CommCell Browser, navigate to Client Computers | <Client>| Oracle.
  2. Right-click the <Instance>, and then click Properties
  3. In the Instance( Oracle SID) box, type the instance name.
  4. Click OK.
 
Data Transfer Options You can configure the available resources for transferring data secured by data protection operations from the subclient level. This includes the following:
  • Enable or disable Data Compression either on the client or on the MediaAgent.
  • Configure the transfer of data in the network using the options for Network Bandwidth Throttling and Network Agents.

You can configure the data transfer options.

  1. From the CommCell Browser, right-click the subclient.
  2. Click Properties.
  3. Click Storage Device.
  4. Click Data Transfer Option tab.
  5. Choose the appropriate software compression option for this subclient.
  6. Select Throttle Network Bandwidth and set the required bandwidth.
  7. Click OK.
Refer to Data Compression and Network Bandwidth Throttling.
View Data Paths You can view the data paths associated with the primary storage policy copy of the selected storage policy or incremental storage policy. You can also modify the data paths including their priority from the subclient level.
  1. From the CommCell browser, right-click the subclient.
  2. Click Properties.
  3. Click Storage Device.
  4. Select Storage Policy from the drop-down menu.
  5. Click Data Paths.
 
Configure a Subclient for Pre and Post Processing of Data Protection You can add, modify or view Pre/Post processes for the subclient. These are batch files or shell scripts that you can run before or after certain job phases.

To send the database instance name to the script, see Passing the Instance Name to Pre and Post Scripts for Databases.

  1. From the CommCell browser, right-click the subclient.
  2. Click Properties.
  3. Click Pre/Post Process.
  4. Click one of the following phases and type the full path of the process that you want to execute during that phase. Alternatively, click Browse to locate the process (applicable only for paths that do not contain any spaces).
    • PreBackup Process
    • PostBackup Process
    • PreSnap Process
    • PostSnap Process
  5. Click OK.
  6. Select Run Post Backup Process for all attempts to run a post backup process for all attempts.
  1. For subclients on Windows platforms, Run As displays Not Selected.

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

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

You can perform the following functions:

  • Identify the user groups 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 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.

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

Deleting an Agent

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

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

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

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

Deleting an Instance

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.