Advanced Configuration - Informix iDataAgent

Table of Contents

Understanding the CommCell Console

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

Agent

Facilitates the Informix instance discovery.

Instance

The Informix Server to be used for the backup and restore operations. Each instance can contain one or more of the databases that you want to back up.

Subclient

Defines the Informix database objects to be backed up.

Informix Configuration

Before you perform backup and restore operations, you must modify parameters in the $INFORMIXDIR/etc/onconfig.<servername> file. For more information, see Informix Configuration

Relinking Instances

For UNIX configurations, you must relink the instance before you perform backups. If you did not relink the instance when you installed the ##_Informix_Agent_##, you must run the Ifx_install script and then relink the instance. The Ifx_install script create a symbolic link in the $INFORMIXDIR/lib directory that points to the SnapProtect XBSA shared library. ON-Bar loads the shared library from the SnapProtect Base path for backup and restore operations.

Procedure

  1. On the command line, go to the SnapProtect/iDataAgent directory and run the Ifx_install script .
  2. You must provide the following Informix instance credentials:
    • The user name
    • The group name
    • The INFORMIXDIR
    • The ONCONFIG
    • The INFORMIXSERVER
    • The BAR_BASLIB_PATH

Managing Instances

In the CommCell Console each instance references an Informix database.

You need the following information before creating an instance.

  • The name of the instance.
  • The OS User account used for performing all system operations.
  • The path to the Informix home directory.
  • The name of the ONCONFIG file, which helps to administer the number of streams, among other capabilities.
  • The storage Policy used by the default subclient in the instance.

Each Informix iDataAgent consumes one license during installation. Note that each license can accommodate multiple instances and databases.

Adding an Instance

During automatic instance discovery, options including the Informix home path, connect string and user account are preset. These options can be customized by manually adding the instance.

  1. From the CommCell Browser, navigate to Client Computers |< Client >.
  2. Right-click Informix, point to All Tasks, and then click New Instance (INFORMIX SID).
  3. On the Creating New Instance dialog box:
    • In the INFORMIX SERVER box, enter the Instance name.
    • In the INFORMIX USER box, enter the user who performs the backups and restores.
    • In the INFORMIX DIR box, enter the Informix home directory path.  Click Browse to change  the path.
    • In the  ONCONFIG File box, enter the name of the ONCONFIG file, which is used to help administer the number of streams and other capabilities.  Click Browse to change  the path.
    • In the Storage Policy used for the data of default subclient box, select a storage policy name.
    • Click the Storage Device tab.
    • In the Storage Policy used for user command backup of data box, select a storage policy.
    • In the Storage Policy used for all Archive Log backups box, select a storage policy name.
    • Click OK.

Changing the Home Directory

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

  1. From the CommCell Browser, navigate to Client Computers | <Client>| Informix|.
  2. Right-click the <Instance>, and then click Properties.
  3. On the General tab of the Properties dialog box:
    • In the INFORMIX DIR box, enter the path to the Informix Home directory. Alternatively, Browse to locate the path.
    • Click OK.

Changing the ONCONFIG File

  1. From the CommCell Browser, navigate to Client Computers | <Client>| Informix|.
  2. Right-click the <Instance>, and then click Properties.
  3. On the General tab of the Properties dialog box:
    • In the ONCONFIG File box, enter the path to the Informix ONCONFIG file. Alternatively, Browse to locate the path.
    • Click OK.

Configuring User Accounts for Backups

Use the following steps to configure the user account to access the Informix database:

  1. From the CommCell Browser, navigate to Client Computers | <Client> | Informix.
  2. Right-click the <Instance>, and then click Properties.
    • On the Properties dialog, navigate to the General tab, enter the INFORMIX USER and click OK.

Refer to User Account and Password Management for the Informix iDataAgent for additional information.

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

If a new dbspace 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.

If you are using the native Informix ON-Bar commands to back up and restore data, subclients are not required.

Creating a Subclient

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 Informix database when it is online. Since full backups includes all the datafiles, dbspaces 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>| Informix.
  2. Right-click the <Instance>, point to All Tasks, and then click New Subclient.
  3. On the Creating New Subclient dialog box:
    • Navigate to the General tab and enter the Subclient Name.
    • Navigate to the Content tab and select Entire Instance Backup.
    • Navigate to the Storage Device tab and select the Data Storage Policy.
    • Click OK.

Creating a Subclient to Backup Individual Datafiles and Dbspaces

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

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

  1. From the CommCell Browser, navigate to Client Computers | <Client>| Informix.
  2. Right-click the <Instance>, point to All Tasks, and then click New Subclient.
  3. On the Creating New Subclient dialog box:
    • Navigate to the General tab and enter the Subclient Name.
    • Navigate to the Content tab and select Selective Backup and then select the dbspace to backup.
    • Navigate to the Storage Device tab and select the Data Storage Policy.
    • Click OK.

Creating a Subclient for Log Backups

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

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

  1. From the CommCell Browser, navigate to Client Computers | <Client>| Informix.
  2. Right-click the <Instance>, point to All Tasks, and then click New Subclient.
  3. On the Creating New Subclient dialog box:
    • Navigate to the General tab and enter the Subclient Name.
    • Navigate to the Content tab and select Full and Current Logical Logs (this option includes completed logs that have not been backed up in addition to the one that is currently being written to).
    • Navigate to the Storage Device tab and select the Data Storage Policy.
    • Click OK.

Creating a Subclient for the Emergency Boot File and the ONCONFIG File

  1. From the CommCell Browser, navigate to Client Computers | <Client>| Informix.
  2. Right-click the <Instance>, point to All Tasks, and then click New Subclient.
  3. On the Creating New Subclient dialog box:
    • Navigate to the General tab and enter the Subclient Name.
    • Navigate to the Content tab and check the Back up Emergency Boot File (ixbar) and Back up ONCONFIG File checkboxes.
    • Navigate to the Storage Device tab and select the Data Storage Policy.
    • Click OK.

Configuring Log Backups

You must configure both TAPEDEV and LTAPEDEV to a value other than the default, /dev/null, for Informix backups and restores to work.

Use the following steps to specify the location to store the logs and perform backups:

  1. Edit the following file :

    #vi $INFORMIXDIR/etc/onconfig

  2. Change the location in TAPEDEV and LTAPEDEV parameters from /dev/null on Unix computers and NUL on Windows computers to any  non-existing directory to which you as an Informix user have full access rights to perform log backups.

    Example:

    For Unix:

    TAPEDEV /dev/null

    LTAPEDEV /dev/null

    Change to:

    TAPEDEV /dev/tmp0

    LTAPEDEV /dev/tmp1

     

    For Windows:

    LTAPEDEV NUL

    Change to:
    LTAPEDEV C:\Program Files\IBM\Informix\tape1

  3. Start a full backup.

Optimizing Log Backups

Use the following additional settings to optimize your log backups:

Reducing the Required Time for Each Log Backup

By default, each on-demand log backup will run a separate job per request. Each log backup job may take 10-15 seconds (for a log size that is less than or equal to 50 MB) to complete with at least one log file. If you run frequent (every couple of minutes) on-demand log backup, use ALARMPROGRAM for better performance.

Use the sPerformanceModeOn additional setting to perform faster log backups. When you set sPerformanceModeOn to Y, the first on-demand log backup will complete within a regular time period (10-15 seconds).  Subsequent log backups will take less time to run. This first job will remain available to backup the subsequent log backup requests. For example, if the regular backup job takes 12 seconds to complete in the performance mode, the subsequent backups of similar logs would complete in 3-4 seconds. It will use the same first job Id for the subsequent log backup requests. This will significantly reduce the time taken to complete your log backups.

Enable Alarmprogram.sh on the client and configure it to backup each completed log file. The time taken for each log backup without using the additional settings ranges between 10-15 seconds (assuming the size of the log file as 50 MB).

The time taken to backup the log files will significantly reduce after using sPerformanceModeOn along with the nPERFMODEIFXJOBCLOSEMINS additional setting. The first log backup will initiate a pipeline. Hence, it may take 10 to15 seconds to complete the backup. The subsequent log backups will take only 3 to 4 seconds for each log backup.

Performance may vary depending on the configurations based on different parameters.

See nPERFMODEIFXJOBCLOSEMINS to learn how to complete your log backup job launched under the performance mode.

Configuring the Timeout Interval to Complete a Job Running under the Performance Mode

By default, the on-demand log backup job running under the performance mode will complete after 6 hours. This duration can be customized using the nPERFMODEIFXJOBCLOSEMINS additional setting.

Set the value of nPERFMODEIFXJOBCLOSEMINS additional setting to a positive number indicating the timeout interval in minutes for completing the on-demand log backup job running in performance mode. The current log backup job will be marked completed after the timeout period set with this additional setting and a new job is submitted for the next log backup request. The jobs completed periodically will be eligible for auxiliary copy and other reporting operations.

Single Job ID

A new behavior has been introduced. SnapProtect now starts one job for third party command line backup and restore jobs. The old method started the number of streams based on the BAR_MAX_BACKUP value set in the ONCONFIG file, when the value was greater than 1.

  • On the client computer, add the sSKIPSINGLEJOBID additional setting and configure the following values:
    Property Value
    Name sSKIPSINGLEJOBID
    Category InformixAgent
    Type String
    Value Y

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

On the Informix side, use the following steps to configure the data streams for backups:

  1. Edit the following file :

    # vi $INFORMIXDIR/etc/onconfig

  2. Set the streams in the BAR_MAX_BACKUP parameter.

    For Example, If you want to set the number of streams to 4 , the parameter would be: BAR_MAX_BACKUP 4

    Example:

    BAR_MAX_BACKUP 4

  3. Start a backup (Full or Incremental). The backup is performed using the number of streams specified.

Configuring Environment Variables for Third Party Command Line (ON-Bar) Utility

You must configure and export the following environment variables to perform ON-Bar third-party command line backups for a specific instance on a client where multiple instances are installed:

  • CvInstanceName
  • CvClientName

For example:

export CvClientName=Client1

export CvInstanceName=Instance001

where Client1 is the name of the Informix client and Instance001 is the name of the instance.

Configuring Backups and Restores for Informix Extended Parallel Server (XPS) Databases

Informix XPS databases are backed up and restored from third party command line (ON-Bar) utility. In a multi-coserver environment, you can configure the XPS database backups in one of the following modes:

  • Install the iDataAgent on one of the coservers (Primary node) , and configure the instance for this coserver (Primary) from the CommCell. You can use this instance to perform backup and restore operations on all the coservers.
  • Install the iDataAgent on all the coservers which have storage managers, and configure the instance in CommCell Console for one of the coservers. The coserver for which you have configured the instance in CommCell console should be specified in the onbar-worker.

Configuring the Primary Coserver (Primary node):

If the Informix iDataAgent is installed on one coserver (primary node), you must configure the storage manager on this primary node. Once you configure the  storage manager, the system will automatically start a single onbar-worker process and perform backups and restores for all coservers from this primary node.  While configuring the storage manager, if you exclude BAR_WORKER_MAX parameter, you must manually start the start_worker.sh file.

Use the following steps to set the ONCONFIG, onbar_worker and storage manager on a primary coserver:

  1. From the command line, navigate to $INFORMIXDIR/etc folder.
  2. Open the ONCONFIG file set the global parameters for Log Backup.The new opera

    For example:

    To set the LOG_BACKUP_MODE to MANUAL, use the LOG_BACKUP_MODE MANUAL parameter.

    Provide one of the following values for this parameter:

    # CONT - backup as soon as the file fills

    # MANUAL - user must perform log backups

    # NONE - don't backup logs and re-use them as soon as they fill.

    Use of NONE is not recommended as data R_PROGRESS_FREQ will be lost if the IBM Informix-XPS server must be restored

  3. Open the start_worker.sh file, and add these parameters before $INFORMIXDIR/bin/onbar_w and save the file to configure onbar_worker.

    CvInstanceName=Instance001  SnapProtect Instance Name Like Instance00x

    CvClientName=dbserver01   #Informix Client Name, this name must be same with commcell gui client name

    CvPrimaryClientName=dbserve01

    In SnapProtect, the entire database server (with all its coservers) is represented as a single Informix database instance running on one of the coservers. You can pick any one of the coservers when creating an Informix instance on the CommCell console. Environment information like INFORMIXDIR etc., for that coserver will be entered into the console. This coserver is identified as CvPrimaryClient and all the jobs in SnapProtect will be associated with this client.

    export CvInstanceName CvClientName CvPrimaryClientName

  4. Set the following parameters on primary coserver to configure a Single Storage manager in a multi coserver environment:

    # Storage Manager for Coserver1 (ex:dbserver01)

    BAR_SM <id>
    BAR_SM_NAME <name>
    BAR_WORKER_COSVR
    BAR_DBS_COSVR
    BAR_LOG_COSVR
    BAR_WORKER_MAX
    BAR_BSALIB_PATH /Informix_HOME/lib/ibsad001.so
    END

    Example:

    In a four coservers Environment:

    # Storage Manager for dbserver01

    BAR_SM 1 # Storage manager ID

    BAR_SM_NAME CV1 # Storage manager name

    BAR_WORKER_COSVR 1 # CV Storage mgr is installed on coserver 1 (dbserver01)

    BAR_DBS_COSVR 1-4 # Route dbspaces for Backup from coserver1 to coserver4 to CV storage mgr

    BAR_LOG_COSVR 1-4 # Route logs for Backup from coserver1 to coserver4 to CV storage mgr

    BAR_WORKER_MAX 2 # Number of streams for Backup to be used which depends on available Tape Drive configuration on command line storage policy

    BAR_BSALIB_PATH /Informix_HOME/lib/ibsad001.so # full pathname of storage manager XBSA shared library ibsad001.so name can be different base upon the OS.

    END # End coserver 1(dbserver01) Storage Manager

Configuring All Coservers

When the Informix iDataAgent is installed on all the coservers which have storage managers, note the following.

  • If storage manager dbserver01 uses BAR_SM1 and storage manager dbserver02 uses BAR_SM2, do not reassign the BAR_SM for the dbservers.

Ensure that the SnapProtect library exists on each coserver node where you are performing onbar_worker processes.

Use the following steps to set the ONCONFIG, onbar_worker and storage manager on all coservers:

  1. From the command line, navigate to $INFORMIXDIR/etc folder on each coserver.
  2. Open the ONCONFIG file and set the global parameters for Log Backup.

    For example:

    To set the LOG_BACKUP_MODE to MANUAL, use LOG_BACKUP_MODE MANUAL parameter.

    You can provide one of the following values for this parameter:

    # CONT - backup as soon as the file fills

    # MANUAL - user must perform log backups

    # NONE - don't backup logs and re-use them as soon as they fill.

    Use of NONE is not recommended as data R_PROGRESS_FREQ will be lost if the IBM Informix-XPS server must be restored.

  3. Open the start_worker.sh file, and add these parameters before $INFORMIXDIR/bin/onbar_w and save the file to configure onbar_worker on each coserver.

    CvInstanceName=Instance001  SnapProtect Instance Name Like Instance00x

    CvClientName=dbserver01  #Informix Client Name, this name must be same with CommCell console client name CvPrimaryClientName=dbserve01  

    In SnapProtect, the entire database server (with all its coservers) is represented as a single Informix database instance running on one of the coservers. You can pick any one of the coservers when creating the Informix instance on the CommCell console. Environment information like INFORMIXDIR etc., for that coserver will be entered into the console. This coserver is identified as CvPrimaryClient and all the jobs in SnapProtect will be associated with this client.

    export CvInstanceName CvClientName CvPrimaryClientName

  4. Set the following parameters to configure storage managers on all coservers:

    # Storage Manager for Coserver1 (ex:dbserver01)

    BAR_SM <id>
    BAR_SM_NAME <name>
    BAR_WORKER_COSVR
    BAR_DBS_COSVR
    BAR_LOG_COSVR
    BAR_WORKER_MAX
    BAR_BSALIB_PATH /Informix_HOME/lib/ibsad001.so
    END

    # Storage Manager for Coserver2 (ex:dbserver02)

    BAR_SM <id>
    BAR_SM_NAME <name>
    BAR_WORKER_COSVR
    BAR_DBS_COSVR
    BAR_LOG_COSVR
    BAR_WORKER_MAX
    BAR_BSALIB_PATH /Informix_HOME/lib/ibsad001.so
    END

    Example:

    In a two coservers environment (dbserver01 and dbserver02):

    # Storage Manager for dbserver01

    BAR_SM 1 # Storage manager ID

    BAR_SM_NAME CV1 # Storage manager name

    BAR_WORKER_COSVR 1 # CV Storage mgr is installed on coserver 1 (dbserver01)

    BAR_DBS_COSVR 1 # Backup dbspaces for coserver 1 (dbserver01) only using CV1 storage mgr

    BAR_LOG_COSVR 1 # Backup logs for coserver 1(dbserver01) only using CV1 storage mgr

    BAR_WORKER_MAX 2 # Number of streams for Backup to be used which depends on available Tape

    #Drive configuration on command line storage policy

    BAR_BSALIB_PATH /Informix_HOME/lib/ibsad001.so # full pathname of storage manager. XBSA shared library ibsad001.so name can be different base upon the OS.

    END # End coserver 1(dbserver01) Storage Manager

     

    # Storage Manager for dbserveont>

    BAR_SM 2 # Storage manager ID

    BAR_SM_NAME CV2 # Storage manager name

    BAR_WORKER_COSVR 2 # CV Storage mgr is installed on coserver 2 (dbserver02)

    BAR_DBS_COSVR 2 # Backup dbspaces for coserver 2 (dbserver02) only using CV2 storage mgr

    BAR_LOG_COSVR 2 # Backup logs for coserver 2(dbserver02) only using CV2 storage mgr

    BAR_WORKER_MAX 2 # Number of streams for Backup to be used which depends on available Tape Drive configuration on command line storage policy

    BAR_BSALIB_PATH /Informix_HOME/lib/ibsad001.so # full pathname of storage manager. XBSA shared library ibsad001.so name can be different base upon the OS.

    END # End coserver 2(dbserver02) Storage Manager

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>| Informix.
  2. Right-click the <Instance>, and then click Properties
  3. In the Instance( Informix SID) box, type the instance name.
  4. Click OK.
 
Data Transfer Options You can efficiently configure the available resources for transferring data secured by data protection operations from the subclient level. This includes the following:
  • Enable or disable Data Compression either on the client or the MediaAgent.
  • Configure the transfer of data in the network using the options for Network Bandwidth Throttling and Network Agents.

You can configure the data transfer options.

  1. From the CommCell Browser, right-click the subclient.
  2. Click Properties.
  3. Click Storage Device.
  4. Click Data Transfer Option tab.
  5. Choose the appropriate software compression option for this subclient.
  6. Select Throttle Network Bandwidth and set the required bandwidth.
  7.  Click OK.
Refer to Data Compression and Network Bandwidth Throttling.
View Data Paths You can view the data paths associated with the primary storage policy copy of the selected storage policy or incremental storage policy. You can also modify the data paths including their priority from the subclient level.
  1. From the CommCell browser, right-click the subclient.
  2. Click Properties.
  3. Click Storage Device.
  4. Select Storage Policy from the drop-down menu.
  5. Click Data Paths.
 
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.
  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 options 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>| Informix.
  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, navigate to Client Computers.
  2. Right-click the <Client> whose version you want to view, 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 backup set, 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 unconfigure 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 permanently deletes 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> | <Backup Set>.
  2. Right-click the <subclient> that you want to delete, and then click Delete.
  3. A confirmation message is displayed, asking if you want to delete the subclient.

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