Use this preinstallation checklist to prepare the computer where you will install the File Share Archiver Client, and to gather all of the information you will need during the installation.
Verify System Requirements
Verify that the computer where you will install the File Share Archiver Client satisfies the minimum requirements. For more information, see System Requirements - OnePass for Hitachi NAS (BlueArc) and Isilon.
Verify License Requirements
The File Share Archiver Client does not require a license.
Determine the Installation Location
Based on your environment, install the File Share Archiver Client on the appropriate computer.
|
Environment |
Where to install the software |
|---|---|
|
Non-Clustered |
On the computer from where you want to recall the stubs. You can also install the File Share Archiver Client on the File System Agent client computer. |
|
Clustered |
On all physical nodes of the cluster. |
Gather Installation Data
Refer to the items in this section to gather the information that you will need during the installation. Record the information before you begin installing the software, so you can refer to it during the installation.
You can install the File Share Archiver Client using either the CommCell Console or the installation package created by the Download Manager. Any item that applies to only one of these installation methods is noted.
Commvault Package to Install
Install the File Share Archiver Client package, which is under the Microsoft Windows category.
Note
If you are installing the File Share Archiver Client using the CommCell Console, the File System Core package is installed automatically.
Destination Folder for the Software Installation
By default, the software is installed in C:\Program Files\CommVault\ContentStore. You can change the destination folder, but it cannot be on a mapped network drive.
The installation program uses the C:\%allusersprofile% folder as a temporary location to copy the installation files. This location does not change, even if you choose to install the software on a drive other than C:.
Firewall Services
-
If there is a firewall between the client computer and the CommServe computer, gather the following information based on your firewall setup:
-
Client connects to the CommServe computer (One-Way Firewall)
Select an HTTP or HTTPS port number that can be used to open tunnel connections to the CommServe computer.
If the client is separated from the CommServe computer by an HTTP proxy, collect the host name (or IP address) and the port number of the HTTP proxy through which the CommServe computer can be reached.
-
CommServe computer connects to the client (One-Way Firewall)
Select a local HTTP or HTTPS port number that can be used by the CommServe computer to open tunnel connections towards the client.
-
CommServe computer can be reached only through a Proxy
Collect the following information:
-
Client name of the Commvault proxy (name is case-sensitive).
-
HTTP or HTTPS tunnel port number on which the proxy expects connections.
If the CommServe computer is behind a port-forwarding gateway, collect the port number of the gateway instead.
-
Host name or IP address of the proxy through which the CommServe computer can be reached.
If the CommServe computer is behind a port-forwarding gateway, collect the host name or IP address of the gateway instead.
Note
If the client is separated from the CommServe computer by an HTTP proxy, collect the host name (or IP address) and the port number of the HTTP proxy through which the CommServe computer can be reached.
-
-
Other Firewall Setups
The following firewall setups share the same preparation requirements as those listed under Client Connects to the CommServe Computer:
-
Two-way firewall, where the client and CommServe computer connect to each other.
-
Port-forwarding gateway, where the gateway forwards incoming connections on specific ports.
-