SnapProtect - Advanced Configuration - Oracle RAC

Table of Contents

Understanding the CommCell Console

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

Agent

Facilitates Oracle instance discovery.

Instance

Defines the Oracle database to be backed up.

Subclient

Defines the Oracle database objects to be backed up.

Adding a New Instance to Existing RAC Client

You can add a new instance to the existing RAC client. While adding a new instance, make sure to use SYS login as connect string to connect to the database. Make sure that the Connect String value does not include "/" when used with Use SQL Connect as RAC will have multiple nodes.

If you want to use a SCAN connect string for an instance, use connect string as: sys/sys@nodename:1521/service name of the database where, service name is the database name.

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

Use the following steps to add an instance to the existing RAC client.

  1. From the CommCell Browser, navigate to Client Computers | <RAC Client>.
  2. Right-click the <Instance>, click the Details tab and then click Add.
  3. In the Instance Physical Client list, select the Instance Physical client name.
  4. In the Instance (ORACLE SID) box, type the Instance name.
  5. Click the Change User Account.
  6. In the User Account box, type the user account name.
  7. In the Enter Password box, type the password for the user account.
  8. In the Confirm Password box, type re-type the password for the user account.
  9. Click OK.
  10. In the ORACLE Home box, type the Oracle installed path. Alternatively, you can click Browse to select the location.
  11. In the Connect String box, type the Connect String (SYS login):  <sys>/<syspassword>@<Oracle service>

    Example: sys/password1@neworac1

  12. In the TNS_ADMIN Folder box, type the TNS ADMIN folder name. Alternatively, click Browse to select the location.
  13. Click the Storage Device tab.
  14. In the Storage Policy used for user command backup of data box, select a storage policy.
  15. Click the Log Backup tab.
  16. In the Storage Policy used for all Archive Log backups box, select a storage policy name.
  17. Click OK.

Configuring an ASM Instance

If Oracle home of ASM instance and RAC instance are different, then make sure to separately configure an ASM instance on the physical RAC client. 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.

Create an ASM instance on the node on which you perform an SnapProtect operation. The kfed utility needs to be configured on all the nodes.

Assuming that you are using the first node for SnapProtect and hence using the first instance (+ASM1), use the following steps to configure the ASM instance:

  1. From the CommCell Browser, navigate to Client Computers | <RAC Physical Client>.
  2. Right-click the <Oracle Agent>, point to All Tasks and then click New Instance (Oracle SID).
  3. In the Instance (ORACLE SID) box, type the Instance name (Ex:+ASM1).
  4. In the ORACLE USER box, type the user account name for ASM Instance.
  5. In the ORACLE HOME box, type the Oracle home path for ASM instance. Alternatively, you can click Browse to select the location.
  6. Select the Storage Policy for the data of  a default subclient from the list.

  7. Click the Details Tab.
    • In the Connect String box, type the Connect String. Use / as connect string.
    • In the TNS_ADMIN Folder box, type the TNS ADMIN folder name. Alternatively, click Browse to select the location.

  8. Click the Storage Device tab.
  9. In the Storage Policy used for user command backup of data box, select a storage policy.

  10. Click the Log Backup tab.
  11. In the Storage Policy used for all Archive Log backups box, select a storage policy name.
  12. Click OK.

Configuring Online Backups for SnapProtect Subclients

When you perform an SnapProtect backup for online databases, ensure you also backup the archive logs. The archive log destination should be shared among all RAC instances. If the log destination is not shared among all RAC instances, you need to separately schedule the archive log backups using a user-defined subclient.

When you backup archive logs, you can specify the location (archive log destinations) from where log backups should be performed. Oracle RAC database will be distributed across many physical clients. These physical clients may or may not share archive log destinations for all instances.

Use the following steps to configure backups for online databases if the archive log destination is shared among all RAC instances:

  1. From the CommCell Browser, navigate to RAC Client | Instance.
  2. Right-click the <Subclient> and click Properties.
  3. Click the Content tab.
  4. Select the Backup Archive Log checkbox. If you want the archive log files to be deleted after they are backed up, select the Archive Delete checkbox.
  5. If you have multiple log locations, do the following:
    • Click Select ArchiveLog Destinations for Backup and click Add.
    • Type the path to the log files to be backed up.
    • Click Select ArchiveLog Destinations for Delete and click Add.
    • Type the path to the log files to be deleted.
  6. Click OK.

Configuring Offline Backup

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.

  1. From the CommCell Browser, navigate to <RAC Client>.
  2. Right-click the <Instance> and click All Tasks | New Subclient.
  3. In the Subclient Name box, type a name.
  4. Click the Content tab.
  5. Select the Offline Database checkbox.
  6. Click the Storage Device tab.
  7. In the Data Storage Policy box, select a storage policy name.
  8. Click the SnapProtect Operations tab.
  9. Click SnapProtect to enable SnapProtect backup for the selected subclient.
  10. Select the storage array from the Available Snap Engine drop-down list.
  11. From the Use Proxy list, select the MediaAgent where SnapProtect and 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.

  12. Click OK.

Configuring 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> | Oracle RAC.
  2. Right-click the <Instance> and click All Tasks | New Subclient.
  3. In the Subclient Name box, type a name.
  4. Click the Content tab.
  5. Click to clear the Data checkbox.
  6. Click the Log Backup tab.
  7. Click the Backup Archive Log checkbox.
  8. Click the SnapProtect Operations tab and select the SnapProtect check box.
  9. Select the Snap Engine from the dropdown list in the Available Snap Engines.
  10. Click OK.

Using RMAN to 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.

Use the following steps to configure RMAN log backups:

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

Enabling Log Deletion after an SnapProtect Backup

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:

  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.

Deleting Archive Logs after a Specific SnapProtect Backup

After performing an SnapProtect backup on the archive logs, you can choose to delete them from the destination location. You can do this by configuring the subclient to delete the archive logs soon after the SnapProtect backup. See Enabling Log Deletion After an SnapProtect Backup for step-by-step instructions on enabling the deletion of logs. Always ensure that the archive logs are backed up before they are deleted to prevent the data loss.

You can also choose to delete the archive logs after a specific SnapProtect backup job. You can even specify additional criteria to delete the archive logs.

Use the following steps to delete the archive logs for a specific SnapProtect backup:

  1. From the CommCell Browser, navigate to Client Computers | <Client> | Oracle | <Instance>
  2. Right-click the <Subclient> configured for archive log backup and then click Backup.
  3. Click Advanced .
  4. Click the Delete Archive Logs tab.
  5. Select the Delete Archive Log check box.
  6. Click Yes on the warning dialog box.
  7. Type confirm in the Enter Confirmation text Dialog box, and then click OK.
  8. Specify the desired criteria for archive log deletion.
  9. 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. See Deleting the Logs after an SnapProtect Backup for more information.

Configuring the Log Destination for an SnapProtect 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.

Deleting the Logs after an SnapProtect Backup

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 Selective Online Full Backup

Selective Online Full backup is a full backup taken when Oracle database is online, and the backup data is copied to a selective copy (during an auxiliary copy operation) from which it can be restored.

  1. From the CommCell Browser, navigate to <Client> | Oracle.
  2. Right-click the <Instance> and click All Tasks | New Subclient.
  3. In the Subclient Name box, type a name.
  4. Click the Content tab.
  5. Select the Selective Online Full checkbox.
  6. A message indicating that you need to use a separate Storage Policy for Selective Online Full backups is displayed. Click OK.
  7. Click the Storage Device tab.
  8. In the Data Storage Policy box, select a storage policy name.
  9. Click the SnapProtect Operations tab.
  10. Click SnapProtect to enable SnapProtect backup for the selected subclient.
  11. Select the storage array from the Available Snap Engine drop-down list.
  12. From the Use Proxy list, select the MediaAgent where SnapProtect and 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.

  13. Click OK.

Creating a Clone Environment

You can duplicate the source database by cloning the NetApp snapshots created during backup.

This operation, referred as cloning, utilizes the cloning capability of the storage array hardware, which enables you to duplicate large databases within a short period of time. Clones can be used for multiple purposes, such as:

  • As test environments to troubleshoot issues found in the production database.
  • Quick data retrieval without running resource intensive restores on the production environment and without requiring additional space on destination server.
  • Alleviate load from the production servers for running reports and queries.

A clone can be created from any existing full backup job (data and log volume backup). During the clone creation, a reservation period is specified by the user. At the end of the period, the system automatically shuts down the clone database and frees up all resources, including snapshot clones on the storage array and ASM disk groups. The cloning operation can also be scheduled to run periodically to allow the clones to get refreshed from the latest backups on a regular basis.

When cloning a RAC database, consider the following:

  • The Clone environment for Oracle RAC only supports ASM databases.
  • RAC databases cannot be cloned to another RAC instance. The destination instance should be a regular Oracle database.

Configure Your Setup

Perform the following steps before creating the clone environment:

  • On the client where you plan to create the clone, create a directory to be used as the mount path for the database clone. This directory should be writable by the Oracle user.
  • Optionally, you can also create an additional instance on the destination client with the same name as of the clone database. This instance can be used to store the clone instance properties, such as ORACLE_HOME. These properties will be pre-populated when specifying the clone options in the CommCell Console.
  • You can clone a database to the same or different computer. If you are cloning a database to an instance residing in a proxy computer, ensure the following conditions are met:
    1. The Oracle database version on the proxy computer is the same as the one in the source database.
    2. The proxy computer has access to the storage array containing the source database volumes.
    3. The Oracle user in both the source and destination computers should have the same user ID.
    4. The Oracle iDataAgent and the MediaAgent must be installed on the proxy.
    5. Using the CommCell Console, a dummy Oracle instance is created with the same name as of the source database.

Create the Clone Environment

Follow the steps given below to create a clone environment from existing snapshots:

  1. From the CommCell Browser navigate to the Client Computers | <RAC Client>.
  2. Right-click the <Instance> and then click All Task | Clone.
  3. From the Clone Options dialog box, click OK.
  4. From the browse window, select an ASM database on the left pane and then click Clone.
  5. From the Oracle Clone Options dialog box, select the client where you want to clone the database from the Destination Client list.
  6. Click the Clone Options tab.
  7. Select the destination database from the Instance Name list. Ensure the selected instance is an Oracle database not configured with ASM.

    If you want to specify a database that is not listed, type the instance name and provide the following details:

    • Specify the location of the Oracle HOME directory in the ORACLE HOME box.
    • Specify the database user ID in the ORACLE User box.
  1. Specify the location of the startup Parameter file in the PFile Path box e.g., /oracle/clone/initdup1.ora. You can also click Browse to locate the directory.
    • If the specified PFile does not exist, the system will create the file and will set all parameters needed. Ensure the Oracle user has write permissions for the directory where the PFile resides.
    • If the specified PFile exists, the file should have read permissions for the Oracle user and contain all initialization parameters required by the Oracle database version used. In addition, ensure the dump and control file directories exist and have write permissions for the Oracle user.
  2. Specify the mount path location in the Snap Mount Location box e.g., /oracle/clone. This mount path will contain mounted snapshots from the Oracle database.

    The Oracle user should have write permissions to this directory. Also, if you chose to let the system create the PFile, then all dump directories will be created under this directory. Enough disk space should be available to hold the logs until the reservation period expires.

  3. Specify the Reservation Period for which you would like to retain the test environment.

    By default the clone environment will be retained for one hour. Once the specified reservation period expires, the database will be dismounted and the mount point will be deleted.

  4. By default, the system will set up two Redo log groups with one log file on each group. If you want to override this configuration (location, number of groups, files), click the Online Log Files check box. Then select Group and add the group and files that you want to create.
  5. 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 RAC | <Instance>.
  2. Right-click the <Oracle RAC 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.

 

Configuring RMAN Backup Copy for SnapProtect Operations

You can use RMAN for copying the data to the media in an Oracle RAC setup. When the data is moved to media, the RMAN backup interface is used for block level backup operations. Also, these backup operations are recorded on the RMAN catalog.

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

  • The Oracle (non RAC) instance on the proxy computer should have the same name as that in the source computer.
  • You must configure the Oracle instance and corresponding ASM instances under the proxy client.
  • The Oracle user id/group id on the on the proxy computer should be identical to the user id/group id on the source computer
  • The catalog user and the catalog database must be the accessible by the source and the proxy Oracle instances. Catalog is mandatory for RMAN backups on proxy computer.
  • The Oracle database installed on the proxy and source computers should be compatible.
  • The proxy and source computer should have the same directory structure e.g. dump, diagnostic and data directories.
  • Oracle database requires the ASM to be registered with Oracle Cluster Registry (OCR). It will ensure the RMAN to successfully mount the disk group.
  • If multiple source client database instances are configured to run RMAN backup copy on the same proxy MediaAgent, the backup copy may fail due to instance and database name conflicts. The conflicting database and instances need to be moved to a different proxy MediaAgent in such cases.
  • 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, set the sRMANDATAFILECOPY registry key 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.

If you plan to use RMAN for copying the data to the media on the proxy computer, copy the Oracle parameter file (pfile) from the client to the proxy computer's $ORACLE_HOME/dbs/ directory, and remove any parameter containing Oracle RAC related entries.

For example:

  • cluster_database_instances
  • cluster_database
  • <RAC Instance name>.thread
  • <RAC Instance name>.local_listener
  • <RAC Instance name>.instance_number

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.

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

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

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

You can perform the following functions:

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