Topics | How To | Related Topics
Using UNC Paths for Job Results Directory
Client Configuration Considerations
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 of the agents that installed on that 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.
The software for the NAS NDMP iDataAgents is installed automatically as part of the MediaAgent installation. Additional software components must also be installed and configured as part of NAS NDMP iDataAgent Deployment, but the Client is not automatically created in the CommCell Browser. To add the Client to the CommCell, refer to the following procedure:
Information on whether the client is a physical or virtual client is displayed in the Client Properties.
Agent and/or MediaAgent software can be installed on a computer that is not part of a CommCell. For more information, see De-coupled Install.
A Client or MediaAgent can be pre-configured on the CommServe, using the Register a Client Computer procedure, and 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 is functional in the CommCell.
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.
You can specify the location on the source and destination computers for saving replication log files for Continuous Data Replicator. For step-by-step instructions, see Specify CDR Log File Location on Source and Destination Computers.
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, Archived Mail Browser and/or OWA functionality. The proper setting for this property depends on the type of installation configuration, as discussed below:
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 DataArchiver Outlook Add-In/Archived Mail Browser (if applicable), but must be configured before using Outlook Add-In, Archived Mail Browser and/or OWA in the configurations mentioned above. For step-by-step instructions, see Configure the Proxy for Exchange.
When the client is configured as a Web Search Server to support content index and search capabilities from the Search Console, options are provided which allow you to view or change the URLs used to access the Search Console and User Administration page. When the client is an Exchange Server, an option is provided which allows you to associate a Web Server to the client for searching.
For step-by-step instructions, see Configure the Web Server URLs.
You can enable or disable the encryption of data for transmission over unsecure networks and for storage on media. For more information, see Data Encryption.
You can set the following job configuration options:
TIP Use ping (or other such network connectivity utilities) to verify whether the computer which has a new name, is accessible. Also ensure that the other computers in the network are accessible to the computer with the new name. |
You can perform the following functions:
For more information, see User Administration and Security.
The Version tab displays the software version and post-release service packs and updates installed for the component. See Version for an overview.
UNC paths are supported for job results directory by the Windows and Exchange Database 2007 iDataAgents with Cluster Continuous Replication (CCR). Consider the following when assigning an UNC path for the job results directory:
\\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.
Storing job results on a UNC path is not supported for Windows File
System iDataAgents in the
following cases:
When using these options you must store or change the job results to a local drive. (For step-by-step instructions, see Change the Job Results Path of a Client.) |
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 the paths.
For File System iDataAgent, the user impersonation occurs only once and therefore the user impersonation account specified for the job results directory will take precedence and will be used to backup the contents of the UNC path included in the subclient content.
For Exchange iDataAgent the account must have the following:
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.
For step-by-step instructions, see Change the User Account for Accessing the Job Results Directory.
You can check whether or not a client is accessible in the CommCell using the Check Client Connectivity 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 Service Control Manager to ensure the client's services are running.
For step-by-step instructions, see Check Client Connectivity.
Consider the following when configuring your clients:
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, which 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 1 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.
The following operations are recorded in the Audit Trail, if Audit Trail is enabled:
See Audit Trail for more information.