Remote Install - Prerequisites
Prior to installing SnapProtect® components from the CommCell Console, make sure to review the following prerequisites:
- Download Software Packages
- Space Requirements
- Firewall and Network Port Requirements
- User Permissions
Prior to installing the software on Windows computers, make sure that the Remote Registry service is enabled. For more information, see Remote Install - Troubleshooting.
To perform a remote install from the CommCell Console, the required SnapProtect packages (agents/components) must be available in the CommServe cache directory. By default, the CommServe cache directory is configured during the installation of the CommServe software.
Use one of the following methods to download software packages to the CommServe cache directory:
- Preferred Method: Download Packages from the CommCell Console
- Alternate Method: Create Package from the Download Manager
You can use the CommCell Console to download the latest software packages to the CommServe cache directory. The CommCell Console downloads all software packages (agents and components) for every operating system supported by the SnapProtect software. The packages are downloaded from an internal FTP site.
Use the following steps to download the software packages and check the state of the CommServe cache directory after the download.
- Verify that the CommServe cache directory has enough space to host the software packages. Several gigabytes might be needed based on the diversity of operating systems in your CommCell.
- From the CommCell Console ribbon, click the Tools tab and then click Add/Remove Software | Download Software.
- On the Download and Sync Cache Options dialog box, complete the following steps:
- Select the Download Packages check box. By default, Windows and Linux operating systems are selected.
- Select the operating systems for which you want to download the packages.
- Click OK.
Software packages from the latest service pack (available in the FTP site since at least 15 days ago) are downloaded.
- After the download completes, from the Tools tab of the CommCell Console ribbon, click Add/Remove Software | Add/Remove Software Configuration.
- On the Add/Remove Software Configuration dialog box, click the CommServe Software Cache tab.
The CommServe Cache Status for Packages should display Valid, as seen in the image below.
If you are unable to download software packages from the CommCell Console, you can create a package from the Download Manager application.
The Download Manager bundles all the required software packages that you need in a single installation package. After the installation package is created, the package can be copied to the CommServe cache to enable remote installations from the CommCell Console.
To create an installation package and copy the package to the CommServe cache, use one of the following procedures (based on your clients' operating system):
- Download Manager - Creating a Windows Installation Package
- Download Manager - Creating a UNIX/Linux/Macintosh Installation Package
On client computers where the software will be installed, the disk space might vary depending on the SnapProtect components that you plan to install.
Important: The following sections display the approximate disk space required to install or upgrade the SnapProtect software on a client. The space values do not include the disk space used by the installation files that are copied to the client. Therefore, make sure to always have additional disk space available on the client.
Space Requirement for the File System Agent
The following section describes the space requirement to install/upgrade the File System iDataAgent and Service Pack in the specified platform:
|Operating System/Platform||Space Requirement for Package (MB)||Space Requirement for Service Pack (MB)|
Space Requirement for the File System Agent and the MediaAgent
The following section describes the space requirement to install/upgrade the File System agent, MediaAgent and service pack in the specified platform:
|Operating System||Space Requirement for Package (MB)||Space Requirement for Service Pack (MB)|
|Macintosh||N/A - MediaAgent not supported on Macintosh|
Space Requirement for Multiple Components
The following section describes the maximum space requirement to install/upgrade multiple components and the service packs in the specified platform.
|Operating System||Space Requirement for Package (MB)*||Space Requirement for Service Pack (MB)*|
Space Requirement for Installing Additional Components on a Computer That has File System or MediaAgent Installed
The following section describes the maximum space requirement to install additional components and the service packs in the specified platform:
|Operating System||Space Requirement for Package (MB)*|
*The above space requirement will vary depending upon the components and previous version of the service packs installed on your client computer.
Refer to the appropriate section based on the client where you want to install the software:
For Existing Clients
You do not need to open additional network ports. However, if you need to set up firewall settings between the client and the CommServe, see one of the following topics based on the type of firewall configuration:
- Firewall: Direct Connections (for one-way and two-way firewall)
- Firewall: Remote Installation Configuration (for one-way firewall, where the CommServe opens connections to the client)
- Firewall: Perimeter Network Using SnapProtect Proxy
For New Clients
You must open some network ports to install the software remotely from the CommCell Console. Review the following port requirements:
Note: If you prefer not to open the required ports, you can set up a remote cache in the network where the computer resides (see Remote Cache).
- For UNIX, Linux, and Macintosh computers, you must enable SSH (Secure Shell) and open port 22.
If you have a Solaris 11 computer, you must also set the cipher as follows:
- Run the following command to stop SSH:
svcadm disable ssh
- Open the /etc/ssh/sshd_config file and add the following line at the end of the file.
- Run the following command to start SSH.
svcadm enable ssh
- Run the following command to stop SSH:
launchctl stop com.openssh.sshd
- Open the /etc/ssh/sshd_config file and add the following line at the end of the file:
- Run the following command to start SSH:
launchctl start com.openssh.sshd
- Run the following command to stop SSH:
- For Windows computers, these ports need to be open temporarily, toward the client, during remote software installation:
- Port 135 for DCOM (Distributed Component Object Model).
- Port 139 for NetBIOS Session Service (if you are using legacy Windows computers (Windows NT and prior)).
- Port 445 for SMB (Server Message Block) file sharing.
- Your Windows Management Instrumentation (WMI) port. For instructions on setting up a fixed port for WMI, see Setting Up a Fixed Port for WMI on the Microsoft website.
Important: If Windows Firewall is enabled on the computer, also open these ports in Windows Firewall:
- Port 135 for DCOM (COM Network Access).
- Port 445 for SMB (File and Printer Sharing).
- The WMI (Windows Management Instrumentation) port, if one is set up.
- If you choose not to open ports 22, 445, 135, 139 and WMI port on your network, you can set up a remote cache in the network where the computer resides.
- Before beginning the installation, open port 8400 toward the CommServe host so that the client can communicate with the CommServe host and send install status to it. Close port 8400 when the installation procedure has finished.
- Important: Once the software has been installed, and the firewall configured and pushed, the only port remaining open should be the firewall tunnel port (8403 by default).
- For UNIX client computers, SSH (secure shell) must be enabled, and the PermitRootLogins entry in the sshd_config file must be set to yes.
- To install software on the CommServe computer, the user must belong to a user group with Administrative Management capabilities.
- If the Authentication for Agent Installs feature is enabled, users that need to perform the remote installation must belong to a user group with the Installation capability set at the CommCell level. The users can also belong to a user group with Administrative Management capabilities for the CommCell or an existing client computer. However, we do not recommend adding non-administrators to an administrative user group.