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 Getting Started with the DB2 Agent procedure.
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.
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, see Adding a NAS Client.
Information on whether the client is a physical or virtual client is displayed in the Client Properties.
Agent and MediaAgent software can be installed on a computer that is not part of a CommCell environment by creating a decoupled custom package. For more information, see Custom Package.
A client or MediaAgent can be pre-configured on the CommServe, and it can be subsequently connected to a computer with client and MediaAgent software already installed. A Product License is 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 MediaAgent are functional in the CommCell environment.
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:
You can enable or disable all operations for this CommCell object and all objects below it. For more information, see Activity Control.
Associate or Disassociate Clients
You can associate or disassociate clients to or from a client computer group.
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.
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.
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.
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 instructions.
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.
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. For more information, see Job Results Directory Overview.
- 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.
You can change the name of clients and the MediaAgent. For information about changing the names of clients, see Name Management.
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 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 instructions, see Configure the Proxy for Exchange.
Search Server URLs
When the client is configured as a Web Search Client to support content index and search capabilities from the Search Console, options are provided that allow you to view or change the URLs used to access the Search Console and User Administration page.
You can also view the name and URL of the Web Search Server associated with the Web Search Client. Note that, the Web Search Server association cannot be changed without re-installing the Web Search Client. Also note that, the Web Search Server URL specified in the Client Properties (Search Server URLs) tab is not directly accessible by the user from any Web browsers.
When the client is an Exchange Server, an option is provided that allows you to associate a Web Server to the client for searching.
For instructions, see Configure the Search Server URLs.
You can perform the following functions:
- Identify the users, user groups, and roles associated with this entity.
- Associate this entity with users, user groups, and roles.
- Disassociate this entity from users, user groups, and roles.
For more information, see User Administration and Security - Overview.
The Version tab displays the software version and post-release service packs and updates installed for the component. See Version for an overview.
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 clients 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. If there is insufficient room for collect file growth during large backups, change the path of the job results directory.
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.
You can configure operation rules at this level using the Operation Window. See Operation Window for an overview.
Operations performed with this feature are recorded in the Audit Trail. See Audit Trail for more information.
Last modified: 2/15/2018 3:52:06 PM