Client

Table of Contents

Overview

A client is a logical grouping of the agents installed on a computer. A client level is created in the CommCell Browser the first time an agent is installed on a computer.

You can perform client operations as long as the client is available and has agents installed on that computer. Operations performed on clients are applicable to all the agents that are installed on that client.

DB2 DPF Pseudo-Client

For the DB2 DPF iDataAgent, the DB2 DPF pseudo-client and its corresponding instance serve as a logical grouping of DB2 DPF database partitions that are housed on various clients. See Overview - DB2 DPF iDataAgent for more information. The pseudo-client is not automatically created in the CommCell Browser by the software; you must create and configure it using the Create a DB2 DPF Client procedure.

RAC Pseudo-Client

For the Oracle RAC iDataAgent, the RAC pseudo-client serves as a logical grouping of one or more Oracle iDataAgent instances within a RAC pseudo-client instance. See Overview - Oracle RAC iDataAgent for more information. The pseudo-client is not automatically created in the CommCell Browser by the software; you must create and configure it using the Create a RAC Client procedure.

NAS Clients

The software for the NAS iDataAgent is installed automatically as part of the MediaAgent installation in the NAS iDataAgent deployment. However, the client is not automatically created in the CommCell Browser. To add the NAS client to the CommCell, refer to the following procedure:

Clustered Environments

Information on whether the client is a physical or virtual client is displayed in the Client Properties.

Decoupled Installs

Agent and/or MediaAgent software can be installed on a computer that is not part of a CommCell. For more information, see Decoupled Install.

A client or MediaAgent can be pre-configured on the CommServe, and it can be subsequently connected to a computer with client and/or MediaAgent software already installed. A Product License(s) will be consumed when you perform this procedure.

The two parts involved in a Decoupled Install can be performed in any order, but must both be performed before the client and/or MediaAgent are functional in the CommCell.

Configurable Properties

Once installed, the client computer is configured and is therefore able to manage the data or volumes. You can change the following aspects of the configuration:

Activity Control

You can enable or disable all operations for this CommCell object and all objects below it. For more information, see Activity Control.

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.

Configuring the CDR Log File Location

ContinuousDataReplicator (CDR) performs replication by logging all activities in the source computer and replaying the log in the destination. On the source computer CDR logs all file write activities - new files and changes to existing files - both in the directories and volumes specified in the source paths of all the Replication Pair(s). These replication logs are transferred to the destination computer and replayed, ensuring that the destination remains a nearly real-time replica of the source.

You can specify the location of these log files and how often the logs must be replayed. For more information, see Replication Logs.

Configuring the Proxy for Exchange

When 32-bit Exchange agents are installed in non-standard configurations, such as off-host proxy or 32-bit on 64-bit, this property must be configured on the client hosting the Exchange Server to establish communications between the 32-bit Exchange agents and the Exchange Server in order to support Outlook Add-In and/or OWA functionality. The proper setting for this property depends on the type of installation configuration, as discussed below:

  • When Exchange 2007 agents are installed in a 32-bit on 64-bit configuration, set this value to the client name of the 32-bit instance.
  • When Exchange 2003/2007 agents are installed in an off-host proxy configuration, set this value to the client name of the off-host proxy computer.

This field should be configured after installing the Exchange agents and the OWA Proxy Enabler; it can be configured either before or after the installation of the Outlook Add-In (if applicable), but it must be configured before using Outlook Add-In and/or OWA in the configurations mentioned above. For step-by-step instructions, see Configure the Proxy for Exchange.

Web Server URLs

If you have a Web Console or Compliance Search installed on the client, options are provided to view the URLs used to access the Web Console or Compliance Search and search admin pages.

Similarly, if you have the Web Server installed on the client, you can also view the name and URL of the Web Server. Note that, the Web Server association cannot be changed without re-installing the Web Console or Compliance Search component. Also note that, the Web Server URL specified in the Client Properties (Web Server URLs) tab is not directly accessible by the user from any Web browsers.

When there are more than one Web Servers installed in the CommCell group, you can select the Web Server to be used for search operations on the client. By default, the Web Server configured in the client group level or Browse/Search/Recovery options will be used.

For instructions on viewing the Web Server URLs, see Viewing the Web Server URLs.

Job Configuration

You can set the following job configuration options:

  • The Job Priority of a client.
  • The time period and disk capacity after which job results are pruned.
  • The directory path of the client where the job results files are located. See Using UNC Paths for Job Results Directory for more information.
  • The amount of time the job results for a client should be retained.
  • The low-space threshold of the job results directory, which is used to configure an  alert. See Alerts and Monitoring for more information.

  • Change the name of the computer in the operating system.
  • Make sure that the computer is available in the network with the new name. (DNS lookup or other name resolution facilities are appropriately configured to resolve the new name of the computer.)
  • Ensure that all applications running on the computer, such as SQL server, Exchange, Server, Oracle database, etc., function with the new name.

TIP

Use ping (or other such network connectivity utilities) to verify whether the computer that has a new name is accessible. Also, ensure that the other computers in the network are accessible to the computer with the new name.

Name Management

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.

User Security

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.

For more information, see User Administration and Security.

Associate or Disassociate Clients

You can associate or disassociate clients to or from a client computer group.

Version

The Version tab displays the software version and post-release service packs and updates installed for the component. See Version for an overview.

Data Interface Pairs

You can add, delete, and view data interface pairs between the client and other CommCell computers. The Advanced tab of the client's Properties dialog box contains options to configure new data interface pairs and view and delete any existing data interface pairs. For more information on data interface pairs, see Data Interface Pairs.

Firewall Configuration

You can define the connection details required to operate this client or client group across firewalls. Details of the connection passage for incoming and outgoing connections between this and other clients behind a firewall must be defined. For complete configuration details, see Firewall.

Configuring Deduplication Options

You can configure client-side deduplication options for the client. The Client Side Deduplication tab of the client's Properties dialog box consists of the following configuration options for client-side deduplication.

  • Enable deduplication at the client side.
  • Enable signature cache at the client side.
  • Enable intelligent block alignment for deduplication operations.

See Modifying Client Deduplication Settings for step-by-step instructions.

Content Indexing

You can enable/disable offline content indexing for the client from the Content Indexing tab in the Advanced Client Properties dialog. To navigate to the Content Indexing tab, right-click the client name, select Properties, and click the Advanced button.

Using UNC Paths for Job Results Directory

UNC paths are supported for job results directory by the SharePoint Server Agent. If configured in a Cluster Continuous Replicator environment, the UNC paths are also supported by the Windows File System Agent and the Exchange Database Agent 2007 and later.

When assigning UNC paths, the designated directory must be ONE level below the directory which is shared for this purpose.

Examples:

\\machine1\<share_name>\job_results\ is shared. Then specify \\machine1\<share_name>\job_results\job_results_1 as the job results directory.

\\machine1\<share_name>\job_results\ is shared. Then specifying \\machine1\<share_name>\job_results as the job results directory is not supported.

User Impersonation for Accessing the Job Results Directory

On a Windows client, you need to specify a Windows User Account with the appropriate privileges to access the job results directory.

User impersonation requires that the specified user have write permissions to the product installation folders; otherwise, the user impersonation account may not take effect. This is especially true if the associated computer is not part of a domain and if the user is not a domain user. Additionally, users will need full permissions (registry rights) to the following registry key: \\HKEY_LOCAL_MACINE\SOFTWARE\CommVault Systems.

In addition, if UNC paths are used for job results and subclient contents are specified as UNC paths, the user impersonation account used for the job results directory must have access to both paths.

For the File System iDataAgent, the user impersonation occurs only once; therefore, the user impersonation account specified for the job results directory will take precedence and will be used to back up the contents of the UNC path included in the subclient content.

For the Virtual Server iDataAgent, the user impersonation account specified for the job results directory will take precedence and will be used to backup and restore data from a virtual machine. This may result into file access related issues during the backup. Therefore, it is recommended to use a local folder on the client computer as the job results directory.

For the Exchange iDataAgent, the account must have the following:

  • The account must have the Remote Access rights to the UNC path.

    Remote Access can be granted by right-clicking My Computer | Properties | Remote | Select Remote Users | Add and then specifying the domain\user in the Select User dialog box in the computer hosting the UNC path.

  • In addition, the Exchange Administrator account specified in the Agent Properties dialog box must have write access permissions to the share used for job results.

For step-by-step instructions, see Change the User Account for Accessing the Job Results Directory.

Client Connectivity

You can check whether or not a client is accessible in the CommCell by using the Check Readiness option in the CommCell Console.

When selected, this option will display a message indicating whether or not the client is accessible. If the client is not accessible, you can check the Process Manager to ensure the client's services are running.

Client Configuration Considerations

Consider the following when configuring your clients:

  • The volume containing the job results directory must have sufficient free space for the collect file. Bear this in mind when backing up large file systems, such as those residing on a SAN. Each subclient in each backup set will consume disk space for the collect file. Change the Job Results Path of the Client if there is insufficient room for collect file growth during large backups.

    The Collect File records the path and name of each scanned file that is to be backed up; therefore, the collect file size is determined by the number of files to be backed up and the length of the file path and file name. If you are working with very deep directory structures, the file paths will be longer, and this impacts the collect file size. When performing full backups of large file systems with a mix of short and long file paths, plan on collect file growth of approximately 50MB for every 1 Million files. Plan on 100MB-200MB per one million files if most of the files in your backup operation have very long file paths (200 + characters in length). Incremental and Differential backups tend to back up fewer files than full backups, and so create smaller collect files.

  • If you change the path of the URLs in the Client Properties (Search Server URLs) tab, which are used for accessing the end-user or compliance user Search Console and/or the User Administration page, then you must manually update the corresponding virtual directory path in the IIS Server. Likewise, if you change the path of the URLs in the IIS Server that are used for accessing the end-user or compliance user Search Console and/or the User Administration page, then you must manually update the corresponding paths in the Client Properties (Search Server URLs) tab.
  • When you configure a new client in the CommCell, note the following:
    • The client name must not match the hostname of another client.
    • The client hostname must not match the name of another client.

    If you do not take the above items into consideration, backup and restore operations may fail.

Operation Window

You can configure operation rules at this level using the Operation Window. See Operation Window for an overview.

Audit Trail

Operations performed with this feature are recorded in the Audit Trail. See Audit Trail for more information.