MediaAgent - Configuration

Table of Contents

Scanning a MediaAgent for Hardware Changes

You can scan the MediaAgent for any new hardware, and changes to existing hardware configurations, from the CommCell Console. This triggers a device detection at the operating system level for all corresponding CommCell computers, and reports the latest hardware configurations to the MediaAgent.

Use the following steps to scan a MediaAgent for hardware changes:

  1. From the CommCell Browser, expand Storage Resources | MediaAgent.
  2. Right click the appropriate MediaAgent, and then click Scan Hardware.

    A device detection operation is performed on the CommCell computers registered to the MediaAgent, and the MediaAgent is updated with the latest hardware setup.

Viewing Information about a MediaAgent

From the CommCell Browser, you can perform the following operations on MediaAgent.

MediaAgent Name

General information includes the MediaAgent name, host name, the name of the CommServe to which the MediaAgent is attached, and whether the MediaAgent is installed in the Physical or in the Virtual machine in a clustered environment.

You can change the name of the Client/MediaAgent computer if the Host name is changed. See Name Management for more information.

Do not use spaces when specifying a new name for the Client.

Use the following steps to modify the name of the MediaAgent.

  1. From the CommCell Browser, expand Storage Resources | MediaAgent.
  2. Right click the appropriate MediaAgent, and then click Properties.

    The MediaAgent/Host name and the name of the CommServe to which the MediaAgent is attached will be disabled under Names.

  3. Click Edit to modify the MediaAgent name.
  4. Click OK.

Host Information

Host information includes the MediaAgent's operating system, platform and NDMP Remote Server information. If necessary you can use the description field to record additional information about the MediaAgent.

Use the following steps to view the host information.

  1. From the CommCell Browser, expand Storage Resources | MediaAgent.
  2. Right click the appropriate MediaAgent, and then click Properties.

    The operating system and software version is displayed under host information.

  3. Click OK.

Setting the Maximum Number of Parallel Data Transfer Operations

Parallel Data Transfer Operations option allows you to set the maximum number of concurrent read/write operations to the MediaAgent. This value controls the maximum number of data streams that can be managed by the MediaAgent.

  1. From the CommCell Browser, expand Storage Resources | MediaAgent.
  2. Right click the appropriate MediaAgent and then click Properties.

    The MediaAgent Properties dialog box appears.

  3. Under the Maximum number of parallel data transfer operations section, set the number of streams in the Restrict To box.

    The default number of concurrent read/write operations to a MediaAgent is 25. This value can be set between 1 and 75.

    If Optimize for Concurrent LAN Backup option is enabled from the Control tab, then the default is set to 100 and this value can be set to a maximum of 300.

  4. Click OK.

Viewing the Storage Policies Associated with the MediaAgent

The Associated Storage Policies tab provides information about all the storage policy and their copies associated with a MediaAgent. This information is useful when you deconfigure a MediaAgent, as all the storage policy copies associated with the MediaAgent can be re-pointed or deleted prior to deconfiguring the MediaAgent.

Use the following steps to view the storage policies associates with the MediaAgent:

  1. From the CommCell Browser, expand Storage Resources | MediaAgent.
  2. Right click the appropriate MediaAgent, and then click Properties.
  3. Click Associated Storage Policies tab.

    The storage policies and storage policy copies associated to this MediaAgent will be displayed.

Viewing the Deduplication Partitions Associated with the MediaAgent

The Deduplication Partitions tab allows you to view the deduplication database paths, storage policy and storage policy copies accessing this MediaAgent.

Use the following steps to view the deduplication partitions path associates with the MediaAgent:

  1. From the CommCell Browser, expand Storage Resources | MediaAgent.
  2. Right click the appropriate MediaAgent, and then click Properties.
  3. Click Associated Storage Policies tab.

    The storage policies and storage policy copies associated to this MediaAgent will be displayed.

Data Integrity Validation

Data integrity and recoverability is an absolute requirement of any backup system. Making sure backup data remains unchanged and available at all times is crucial for successful restorability. The following section focus Data Invulnerability Architecture on how it helps provide the assurance that backed up data remains invulnerable and available at all times.

Data invulnerability architecture is the set of features designed to maintain integrity and reliability of:

  • Data in motion refers to the transfer of data between these media.

Data Flow

The data flow works as follows:

  • Client computers run client software for supported data agents.

    For example, Windows or Linux File Systems, Exchange, Oracle, SharePoint agents.

  • Backup and Restore operations are centrally managed and scheduled by CommServe which hosts the site wide configuration database.
  • During backup, data flows from the source agent (client) to MediaAgent over a network where the data is processed (optionally compressed, encrypted and deduplicated) and stored on secondary storage.
  • During restore, data flows from MediaAgent controlled storage mediums to clients. Auxiliary Copy operations provide the ability to create multiple copies of backed up data so the flow of data is between MediaAgents.

Data integrity needs to be maintained at all times, that is:

  • data is sourced from the clients
  • data traveled over network to MediaAgents
  • written to secondary storage media

Once written, a policy based mechanism is required to periodically re-evaluate data integrity for tests and audits and to provide the assurance that it can be restored successfully when required. The same validation is also required for all data read operations such as Auxiliary copies and restores. This section explains the following data integrity mechanisms:

  • End to End Data Integrity Validation
  • Periodic Health Checks for Compliance and Recoverability Assurance
  • Flexibility to leverage data integrity features of underlying storage

End-to-End Data Integrity Validation

The integrity of backup operations can be ensured by enabling Data Integrity Validation at the MediaAgent. Data Integrity Validation allows you to verify the integrity of the data secured by the backup operations, and can be used to verify the data stored in the media as well as the data transferred over network.

Consider the following for mixed mode configurations:

  • Data Integrity Validation on Media is supported in mixed mode configuration, where the MediaAgent is used with clients from a previous release.
  • For Data Integrity Validation on Network, the MediaAgent and the clients must be maintained in the current release.

Data Integrity Validation on Media (CRC Checks on Source Data Blocks)

When Data Integrity Validation on Media is enabled, the CRC (Cyclic Redundancy Check) checksums are computed as data blocks are read from the source (client) and stored as part of backup. These checksums are validated during data verification jobs, Auxiliary Copies and restore operations. Note that this option must be enabled during the backup as well as the restore operations.

  1. From the CommCell Browser, expand Storage Resources | MediaAgent.
  2. Right click the appropriate MediaAgent, and then click Properties.
  3. On the MediaAgent Properties dialog box, select Validation on Media to enable Data Integrity Validation of data stored in the media, and then click OK.

Data Integrity Validation on Network (CRC Check on Data Blocks Transferred over the Network)

To verify the integrity of the data transferred over the network, the Data Integrity Validation (CRC checksums) generated at the respective clients before the data transfer will be verified with the Data Integrity Validation generated at the MediaAgent after the data transfer is complete, and vice versa. This verification is done for all backup and restore operation for all data travelling to and from the MediaAgents. Note that this option can be enabled during backup operations, restore operations, or both.

  1. From the CommCell Browser, expand Storage Resources | MediaAgent.
  2. Right click the MediaAgent, and then click Properties.
  3. On the MediaAgent Properties dialog box, select Validation on Network to enable Data Integrity Validation for data transferred over the network, and then click OK.

Data Validity Checks during All Data Read Operations

The backup data is stored in a unique data format that is a small header is followed by variable sized block data. The variability of this format helps in detecting invalid data on reads as compared to a fixed block size that is previous block has to be read before getting to the next block when performing sequential reads.

Periodic Health Checks for Compliance and Recoverability Assurance

Data Verification Jobs

Data verification jobs check the health of data at storage. These can be configured to run immediately after a data transfer operation or scheduled on policy basis. Data verification is supported for all types of copies for offline content verification. If CRC is stored on a backup media, CRC is recalculated for each block read and compared with the stored CRC value. If any mismatch occurs an error message will be displayed. If CRC is not stored on backup media, this operation verifies that all data is readable. Note that this does not verify data integrity. For more information, see Data Verification.

Flexibility to Leverage Data Integrity Features of Underlying Storage

SnapProtect supports a wide range and variety of secondary storage mediums to be used as targets for backup data. To enhance data integrity and availability, data verification mechanisms provided by these storage media can be leveraged.

For example, disk libraries can be configured to take advantage of high availability and fault tolerant architectures such as RAID – example RAID 5, 6, 50, 60. Tape drives also provide data integrity checking features such as Error Correction Code (ECC) and Checksums that are validated automatically on data reads.

Handling Data Integrity Validation Errors

If the Data Integrity Validation job fails, the backup jobs will be moved to a pending state with the corresponding error code and description mentioned in the Reason for Delay field of the job, displayed in the Job Controller.

Review the error code and the description of the pending job to identify the reason for failure.

  • If Data Integrity Validation on Network has failed, verify the network cord connecting the MediaAgent and the corresponding client. Replace the network cord, if necessary.
  • If Data Integrity Validation on Media has failed, check the storage media device and replace the device if necessary.

The pending jobs due to Data Integrity Validation errors can be handled as follows:

  • Restore operations can be configured the operation to skip errors and continue with the restore. See Skip Errors and Continue for more information and step-by-step instructions.
  • Backup operations can be retried and handled as configured in the Job Retry Options.

Related Reports

Jobs in Storage Policy Copies Report

The Jobs in Storage Policy Copies Report provides a list of data protection jobs associated with the storage policy copies based on the selected filter criteria. If the Data Integrity Validation for data is enabled for a job, that information is displayed in the Job ID status.

The Data Integrity Validation status is also displayed in the Jobs for Storage Policy Copy window when you view the Jobs of a Storage Policy Copy.

For comprehensive information on this report, refer to Jobs in Storage Policy Copies Report.

Use the following steps to run a Storage policy copies report.

  1. On the ribbon in the CommCell Console, click the Reports tab, and then click Configuration.
  2. From the Report Selection dialog box, under Reports node, select Jobs for Storage Policy.
  3. Clear Storage Policies and select specific storage policy you want to generate the report.
  4. Click Run to generate the report in HTML page.

    The report will appear in your default Web browser.

Controlling a MediaAgent

The following sections describes various options for controlling the MediaAgent:

Enable or Disable a MediaAgent

You can enable or disable a MediaAgent. When a MediaAgent is disabled, it is not used, even if it is physically available.

MediaAgents and data protection and recovery operations for clients can be enabled or disabled in bulk with the EnableDisableComputers command line utility in the Resource Pack. The tool can be applied to all MediaAgents and clients, or for a select targeted group.

Use the following steps to enable or disable a MediaAgent.

  1. From the CommCell Browser, expand Storage Resources | MediaAgent.
  2. Right click the appropriate MediaAgent, and then click Properties.
  3. Click the Control tab.
  4. Select the Enable MediaAgent option to bring the MediaAgent online.

    Clear this option to take the MediaAgent offline.

  5. Click OK to save the configuration.

Status of a MediaAgent

The status of the MediaAgent is displayed to indicate whether the MediaAgent software is online or offline, and if offline, the reason for the offline status is also displayed.

The system checks for the status of the MediaAgent and updates the information based on the values established in the LAN-Free MediaAgent liveliness check interval in Minutes and LAN MediaAgent liveliness check interval in Minutes options from the Media Management Configuration (Service Configuration) dialog box.

Use the following steps to view the status of a MediaAgent:

  1. From the CommCell Browser, expand Storage Resources | MediaAgent.
  2. Right click the appropriate MediaAgent, and then click Properties.
  3. Click the Control tab.
  4. The MediaAgent's online or offline status can be viewed from the Status.

    Note that if the Media is Offline the offline reason is also displayed.

  5. Click OK.

Mark MediaAgent Offline for Maintenance

You can enable this option when you wish to perform routine or other maintenance tasks on devices. This option is available in the MediaAgent, Library and Drive levels and you can appropriately enable them where needed.

Backup, Restore and Auxiliary Copy operations will not use the associated MediaAgent/Library/Drive, depending on where the option is enabled. However, other administrative tasks on the devices such as Full Scan, Drive Cleaning, Verify Media etc. can be performed, if required.

When this option is enabled, the system will automatically select an alternate resource (MediaAgent/Library/Drive) if Alternate Data Paths (GridStor) is enabled. If alternate resources are not available, backup, restore and auxiliary copy will remain in the Waiting state in the Job Controller and will automatically resume when you re-enable the appropriate MediaAgent/Library/Drive.

Use the following steps to mark MediaAgent/Library/Drive Offline for Maintenance:

  1. From the CommCell Browser, expand Storage Resources | MediaAgent.
  2. Right click the appropriate MediaAgent, and then click Properties.
  3. Click the Control tab.
  4. Select Mark MediaAgent Offline for Maintenance check box to mark a MediaAgent offline for maintenance.
  5. Click OK to save the configuration.

    Subsequent backup, restore and Auxiliary Copy operations will not use the associated MediaAgent/Library/Drive.

Optimize a MediaAgent for Concurrent LAN Backups

This option can be enabled when the MediaAgent is used for concurrent backup operations from a large number of clients. For example, if you have 25 clients concurrently using the MediaAgent for 50 or more data transfer streams in a specific operation window, it is recommended that you enable this option  Enabling this option will help to optimize the Operating System resources on the MediaAgent.

See Setting the Maximum number of parallel data transfer operations for the maximum number of parallel read/write operations with the Optimize for Concurrent LAN Backups option enabled.

See MediaAgents - Supported Features, Agents and Devices for information on the MediaAgents that support this option.

Use the following steps to optimize a MediaAgent for concurrent LAN backups.

  1. From the CommCell Browser, expand Storage Resources | MediaAgent.
  2. Right click the appropriate MediaAgent, and then click Properties.
  3. Click the Control tab.
  4. Select Optimize for concurrent LAN backups to enable the option.

    Clear this option to disable.

  5. Click OK to save the configuration.

    Subsequent data protection operations using the MediaAgent use the selected mechanism.

Automatic Update of SCSI ID during Live Operation

In the SAN environment, the SCSI ID of a device  may get changed due to a HBA failover or if the a hardware component in the SAN is reset. In such a situation, read/write requests to the media in the device may fail, resulting in job failures. However, if this option is enabled, the system will automatically scan the device and update the SCSI ID and the job will be re-tried in the established retry interval.

This option also includes the following sub-options:

  • SCSI/SAN device scan interval n hour(s)

    This option specifies the time interval that must be used for successive retry operations for SCSI ID updates. For example, if a SCSI ID update is performed after a read/write failure and a second read/write failure occurs almost immediately or within the specified time interval, the system will not perform the SCSI ID update. The system will scan for SCSI ID updates only when a error occurs after the specified time interval. It is recommended that the time interval be set to 30 minutes  or more, as running jobs could go into pending, when the SCSI ID is updated.

  • Mark drive inaccessible on error and perform status check according to device scan interval

    When enabled, this option marks the drive controller offline when the SCSI ID for a device is changed. (This can be viewed from the Drive Properties - Drive Controller tab, where the Drive Accessible will be displayed as No.)

    The device detection will be performed once every 24 hours. This property can be modified using the SCSI/SAN device scan interval n hours(s) option in the MediaAgent Properties. Note that if the value established in MediaAgent Properties is less than 24 hours, the system automatically defaults to 24 hours.

    If you want to perform this operation more frequently create the nDisabledDriveDetectIntervalMin additional setting. Once created, this additional setting will override the setting established in the MediaAgent Properties.

     The device detection will be repeated for 7 days. If these drives are not accessible even after 7 days, the drives will be marked as accessible. (If the drive continues to have a problem, the subsequent job accessing the drive will once again cause it to be marked as inaccessible.) If necessary the nDisabledDriveMaxDetectionRetryHours additional settings can be created to change the number of days the device detection will be repeated.

Use the following steps to configure automatic device detection.

  1. From the CommCell Browser, expand Storage Resources | MediaAgent.
  2. Right click the appropriate MediaAgent, and then click Properties.
  3. Click the Control tab.
  4. Select Auto Update SCSI ID during live operation to automatically scan the device and update the SCSI ID.
  5. In the SCSI/SAN device scan interval specify number of hours after which successive SCSI updates can be run on the MediaAgent
  6. Select Mark drive inaccessible on error and perform status check according to device scan interval to mark drive controlled offline when the SCSI ID for a device is changed.
  7. Click OK to save the configuration.

Native Driver Support

To communicate with the tape devices, you can use the pass-through driver provided by the MediaAgent, or the native drivers provided by the operating system. When this option is selected the native driver is used. This option is supported by all UNIX MediaAgents. By default, this option is enabled on all Unix MediaAgents. Disable this option, if you do not want to use the native drivers.

See Also:

Send pass-thru commands to Atape

When using native driver support, use this option to enable MediaAgent to send pass-through commands to Atape device drivers.

Enable or Disable Automatic Detection of WORM Media

When enabled, this option automatically detects WORM media when it is used in a drive. This option must be enabled if you plan to use WORM media in the libraries attached to the MediaAgent. (Check the drive manufacturer's documentation to ensure that both the drive model and firmware must support the usage of WORM media.)

Use the following steps to enable or disable automatic detection of WORM media:

  1. From the CommCell Browser, expand Storage Resources | MediaAgent.
  2. Right click the appropriate MediaAgent, and then click Properties.
  3. Click the Control tab.
  4. Select Automatically detect WORM Tape Media option to enable automatic detection.

    Clear the option to disable it.

  5. Click OK to save the configuration.

Enable Retry on Network Errors

When enabled, this option allows you to set the retry options in case of network errors.

  • Retry Frequency (seconds)

    The interval (in seconds) at which the Job Manager will continuously check for network connectivity.

  • Retry Count

    The number of times the Job Manager will check for network connectivity.

Use the following steps to enable retry on network errors:

  1. From the CommCell Browser, expand Storage Resources | MediaAgent.
  2. Right click the appropriate MediaAgent, and then click Properties.
  3. Click the Control tab.
  4. Select Enable retry on network errors check box.

    Clear the option to disable it.

  5. In the Retry frequency (seconds), specify time in seconds at which job manager will check for network connectivity.
  6. In the Retry Count, specify the number of times the job manage will check for network connectivity.
  7. Click OK to save the configuration.

Additional Operations

Option Description Related topics

Log Files

View Log

You can view the log files generated by a MediaAgent. The files that reside on a given computer may differ depending on the role of the computer in the CommCell (CommServe, MediaAgent, Client). A CommServe computer contains only the CommServe log files. A computer that is both a CommServe and a MediaAgent contains the log files of both entities.

Send log

You can send the log files either from the CommCell Console, or from the Command line to email recipients as mails, or to a remote computer. You can also upload the log files to any existing FTP server.

Refer to Log Files.

Install Updates

This option allows you to install updates from the CommServe Update Cache or a designated update cache on a remote client if multicache configuration is set up for use.

Refer to Install Updates

MediaAgent Alerts

Alerts allow you to set e-mail notifications to MediaAgent related events.

Refer to MediaAgent - Alerts and Notifications

Catalog

A MediaAgent’s Index cache information be viewed from the Catalog tab of the MediaAgent Properties dialog box. You can view or modify the following information associated with the MediaAgent’s index cache configuration:

  • Catalog Profile
  • Index Cache Directory
  • Index Retention Criteria

Refer to Index Cache.

Version

The Version tab of the MediaAgent Properties dialog box displays the version number of the MediaAgent software that is installed on the MediaAgent computer. It also displays all post-release Service Packs and Automatic Updates that may have been installed on the MediaAgent. It also displays the location of the update information.

Refer to Version.

Security

Security allows you to associate the MediaAgent with one or more CommCell user groups.

Refer to User Administration and Security.

Additional Settings

The Additional Settings tab enables you to add, edit, or delete additional settings for Windows and UNIX MediaAgents.

Refer to Additional Settings.

Firewall Configuration

If a firewall separates MediaAgent and other CommCell components it communicates, then you can specify the incoming and outgoing connectivity details between MediaAgent and the components in the Firewall Configuration tab.

Refer to Firewall.

Network Throttling

The network traffic for MediaAgents can be throttled based on the network bandwidth in your environment. This is useful to regulate network traffic and minimize bandwidth congestion.

By default, network throttling is disabled. You can enable the throttling options for a MediaAgent. Once configured, the throttling options are applied to all data transfer and control message operations, such as Backup operations, Copy operations including DASH copy, Restore operations, etc.

Refer to Network Bandwidth Throttling.

Audit Trail

The Audit Trail feature allows you to track the operations of users who have access to the CommCell. This capability is useful when you want to determine the source of a detrimental operation that was performed in the CommCell.

Refer to Audit Trail.

Command Line Operations

You can perform the following job configurations through the command line:

Deleting a MediaAgent (qdelete mediagent)

Description

This command deconfigures and deletes a MediaAgent. By default, the qdelete mediaagent command asks for confirmation before deletion, but this prompt can be suppressed by using the "-y" option.

Upon successful completion, qdelete mediaagent displays the message "Deleted the MediaAgent  successfully" on the command prompt. In case of an error, an error code and description are displayed as: "mediaagent: Error errorcode: errordescription"

Usage

qdelete mediaagent -m <mediaagent> [-y] [-tf <tokenfile>] [-tk <token>] [-h]

Options

-m MediaAgent name
-y Delete without confirmation
-tf Reads token from a file
-tk Token string
-h  Displays help

Diagnostics

Possible exit status values are:

0 - Successful completion.

1 - CLI usage failures, due to the use of an unsupported option or missing argument.

2 - Any other failure.

Example

Delete a MediaAgent with name M_Agent.

E:\commandline>qdelete mediaagent -m M_Agent

You can mass-delete clients with or without their associated MediaAgents using the qdelete mediaagent command. You can include this command (along with the qdelete client command, if appropriate) in a script. Mass deletion of these items is useful if you want to remove them after a split of a CommCell. To mass-delete items where the CommCell is not split, be sure to run the script from the install location of the CommServe host.

Viewing MediaAgents (qlist mediaagent)

Description

This command lists the names of all the MediaAgents configured in the CommCell. Whenever more than one MediaAgent is found, each MediaAgent is listed in its own line on the command prompt. No message is displayed whenever MediaAgents are not found.

In case of an error, an error code and description are displayed as: "mediaagent: Error errorcode: errordescription

Usage

qlist mediaagent [-tf <tokenfile>] [-tk <token>] [-h]

Options

-tf Reads token from a file
-tk Token string
-h Displays help

Diagnostics

Possible exit status values are:

0 - Successful completion.

1 - CLI usage failures, due to the use of an unsupported option or missing argument.

2 - Any other failure.

Example

List all the MediaAgents configured in the CommCell.

E:\commandline>qlist mediaagent
client1

Uninstalling a MediaAgent

The MediaAgent uninstall software performs the following tasks:

  • Cleans up all the information about the MediaAgent in the CommServe database.
  • Deconfigure the libraries and drives.
  • Releases the license associated with the following:

    MediaAgent Libraries or stand-alone drives attached to the MediaAgent

  • Remove the files and registry entries from the computer hosting the MediaAgent.

Before You Begin

Consider the following prior to uninstalling the MediaAgent software:

  • Verify that the CommServe computer is accessible and all services on the CommServe and the MediaAgent in which you wish to perform the uninstall are running.
  • If the deduplication database (DDB) is hosted on this MediaAgent and you still want to use this DDB for backup or restore operation, then change the MediaAgent of the DDB to the new MediaAgent which you want to host the DDB. See Deduplication Database Move for more information.
  • If you want to restore the data from the backups stored on the mount path of this MediaAgent, make sure to copy the data to another location and associate this mount path to another MediaAgent.
  • If you are uninstalling a Solaris MediaAgent from a Unix machine, you must first remove the WA SCSI Driver. To do this, remove the CVGxWA package first before you uninstall the MediaAgent.
  • All the libraries associated to this MediaAgent are re-associated to another new MediaAgent.
  • All the storage policies or copies associated with the configured libraries (or drive pools) in the MediaAgent are deleted or re-associated to another MediaAgent.

You can uninstall the MediaAgent using one of the following method:

Uninstall MediaAgent from CommCell Console

  1. Log on to CommCell Console.
  2. From the CommCell Browser, expand Storage Resources | MediaAgents.
  3. Right-click the appropriate MediaAgent, point to All Tasks | Add/Remove Software, and then click Uninstall Software.
  4. On the Uninstall Software Options dialog box, select Uninstall All check box
  5. Click OK to run the job immediately.

    You can track the progress of the job from the Job Controller.

Uninstall MediaAgent from Computer

For Windows

  1. Log on to Windows computer.
  2. Click the Start button on the Windows task bar and then click Control Panel.
  3. Double-click Add/Remove Programs.

    For Windows Vista/Windows 2008, click Uninstall a Program in the Control Panel.

  4. Click Remove to uninstall the components in the following sequence:
    1. MediaAgent
    2. Windows File System
    3. Base Software

For UNIX

  1. Log on to Unix computer.
  2. Navigate to <Software_Installation_Directory>/Base folder
  3. Run ./cvpkgrm command.
  4. Select the MediaAgent (CVGxMA) to uninstall.

    After MediaAgent uninstall, select other agents and Base software to uninstall.

Releasing a MediaAgent License (Deconfiguration)

If the uninstall fails to cleanup the MediaAgent information from the CommServe, use the following steps to release the license for a MediaAgent.

Releasing the MediaAgent license or deconfiguring the MediaAgent will not remove the files and registry entries associated with this MediaAgent.

The De-configure option performs the following tasks:

  • Cleans up all the information about the MediaAgent in the CommServe database.
  • Releases the license associated with the MediaAgent.
  • Releases the licenses associated with the libraries to the MediaAgent. However, licenses associated with a library whose media changer is not controlled by this MediaAgent (e.g. SAN devices, shared libraries) will not be released.

 Before you Begin:

  • Administrative Management capability cannot be used to release the license from the MediaAgent level. See Capabilities and Permitted Actions
  • To release license for MediaAgent, ensure that all the storage policies or copies associated with the configured libraries (or drive pools) in the MediaAgent are deleted or re-associated to another MediaAgent.

Use the following steps to release license for MediaAgent.

  1. Log on to CommCell Console.
  2. From the CommCell Browser, navigate to Storage Resources | MediaAgents.
  3. Right-click the desired MediaAgent, and then click Release license for MediaAgent.
  4. From the Release License for MediaAgent dialog box, select MediaAgent-MediaAgent Management license and click Add> button.
  5. Click OK.
  6. A popup Confirm message appears.
  7. Click Yes to continue with the deconfiguration or No to abort.
  8. If releasing a license is unsuccessful, a number of popup messages appears. In some cases, the message requests that you take some corrective action.

    For example, the message might advise you to ensure that there are no jobs running on the agent.

    In such case, click OK and take the appropriate action. Then repeat the process.

    If releasing a license is successful, the tree element displays icon and available for deletion.