Silent Installs - Unix Agents

Click on a link below to go to a specific section of the software installation:


The silent install feature allows you to enter installation parameters into a file that is read in by the installation program instead of typing them in response to each installation prompt. The following procedures provide step-by-step instructions for installing the Base software and agent with one command line execution, using the silent install feature. Silent installs can be used to install the following:
  • Unix File System iDataAgents
  • Macintosh File System iDataAgent
  • Oracle iDataAgent on Unix
  • SAP for Oracle iDataAgent on Unix
  • Sybase iDataAgent on Unix
  • Unix MediaAgents

Additionally, you can use the Red Hat Package Manager (RPM) package management system to install all versions of the Linux File System iDataAgent and the Linux MediaAgent. Also, you can use the Advanced Packaging Tool (APT) package management system to install all Debian Linux versions of these software components.

Install Requirements

The iDataAgent is installed on the computer from which the iDataAgent secures data. (This computer is referred to as the Client computer in this install procedure.)

Verify that the computer in which you wish to install the software satisfies the minimum requirements specified in any of the following as appropriate:

Review the following Install Requirements before installing the software:


  • Agents should be installed only after the CommServe and at least one MediaAgent have been installed in the CommCell. Also, keep in mind that the CommServe and MediaAgent must be installed and running (but not necessarily on the same computer), before you can install the Agent.
  • This software should be installed in a CommCell with current versions of the CommServe and MediaAgent software.
  • Ensure there is an available license on the CommServe for the Agent.
  • Verify that you have the software installation disc that is appropriate to the destination computer’s operating system.

    Make sure that you have the latest software installation disc before you start to install the software. If you are not sure, contact your software provider.


  • If the CommServe® Server, MediaAgent and/or Clients communicate across two-way firewall(s):
    • Ensure port 8400 is allowed connections through the firewall.
    • In addition a range of bi-directional ports (consecutive or discrete) must also be allowed connections through the firewall.

     For information on configuring the range of ports, see Port Requirements for Two-way Firewall.

  • If the CommServe Server, MediaAgent and/or Clients communicate across one-way firewall(s):
    • Identify a range of outbound ports (consecutive or discrete) for use by the software.

     For information on configuring the range of ports, see Port Requirements for One-way Firewall.

  • If the MediaAgent/Client communicates with the CommServe Server across a one-way firewall, you must add the MediaAgent/Client host name (or the IP address) in the CommServe computer before installing the necessary software on the MediaAgent/Client computer.

Multi Instancing

  • By utilizing the Multi Instancing feature, the same Agent and MediaAgent software can be installed on a computer multiple times, but not all components support Multi Instancing. This limitation can apply to the component you are installing, or to one already installed on the computer. Prior to installing multiple instances of a software component on the same computer, carefully review the information contained in Multi Instancing, and follow the instructions in the How to Use Multi Instancing section for the additional screens that will appear during the installation process.


  • If you are installing on an AIX computer, and if you have a dual-layer DVD, be sure to issue the following command from the command line to mount the DVD:

    /usr/sbin/mount -v 'cdrfs' -f'' -p'' -r'' /dev/cd0 /mnt



  • For Macintosh, before installing/upgrading the product, log on to the client as a valid user. In the terminal window, issue the su - root command to substitute your user identity with that for the root user. Then enter the valid root user password.
  • For Macintosh, create user groups with permissions to help with the install/upgrade as follows:
    1. From the Finder, go to the NetInfo Manager utility by selecting Applications > Utilities > NetInfo Manager .
    2. Select Security > Authenticate.
    3. In the pop-up screen, enter a user name and password with administration privileges.
    4. Highlight Groups.
    5. Select Directory > New Subdirectory > Get “New_Directory”.
    6. Change “New_Directory” to a user-defined directory name.
    7. Select Directory > New Properties.
    8. Assign the property name GID and property value 777.
    9. Save the changes and update the copy.
  • For Macintosh File System, ensure that the hashed form of the login password (for example, AK4yMgoTZCWYQ) will be used.  To this purpose, follow these steps:
  1. From the client computer, enter a command that allows you to check if the root password is in hashed form (alternatively, you can use the Mac NetInfo GUI utility). For example:

root# nireport / /users name passwd | grep root

If the password is not in hashed form, go to the next step.

  1. Get the hashed password.  For example:

root# openssl passwd -crypt -salt value cv_slam

where value can be any alphanumeric value (e.g. yz)

  1. Replace the root password with the hashed form of this password (e.g., yzijgGETFnb/E) in the NetInfo database (alternatively, you can use the Mac NetInfo GUI utility). For example:

root# niutil -createprop / /users/root passwd yzijgGETFnb/E


A FreeBSD install requires that the libiconv library be present. To this end, complete the following steps:

  1. Ensure FreeBSD ports are installed. See for more information.
  2. Navigate to /usr/ports/converters/libiconv.
  3. Ensure that all the following files are present: Makefile, distinfo, files, pkg-descr, pkg-plist, work.
  4. Run the make install command.

Red Hat Linux

  • Red Hat Linux will create an entry in the /etc/hosts file when it is first installed, in the following format:

    <ip_address> <host name> localhost

    For example, if the host name of your computer is bluesky, the entry will look something like this: bluesky localhost

    If you have not already done so, edit the /etc/hosts file. The edited entry should look like this: localhost

    Depending upon your environment, and using the above example again, you may also need an entry similar to this: bluesky


  • If you are installing the Solaris 10 version of the Solaris File System iDataAgent, be sure to install the iDataAgent on the global zone. This will allow you to back up file systems in both the global zone and the local zone when you run backups for this iDataAgent.

Ubuntu Linux

  • Before installing the software on Ubuntu Linux systems, be sure to install the binutils package by running the apt -get install binutils command as root.

Install Checklist

Collect the following information before installing the software. Note that several items are optional as indicated. (Use the space provided at the right to record the information. Retain this information in your Disaster Recovery binder.)
1. TCP port number for the Communications Service (CVD): _______________________________________

TCP port number for the Client Event Manager Service (EvMgrC): ________________________________

Install directory location:__________________________________________________________________

Log files directory location:________________________________________________________________

Job result directory location:_______________________________________________________________

Index Cache directory location:_____________________________________________________________

Client name (optional):____________________________________________________________________

Client's network host name (optional):________________________________________________________

Client group to which this client will be associated (optional): _____________________________________

CommServe Host Name:__________________________________________________________________

Firewall Ports (optional):___________________________________________________________________

Hostnames and/or IP addresses and corresponding GxCVD port numbers of computers on the other side

of the firewall:___________________________________________________________________________

Keep Alive Interval minutes:_______________________________________________________________

Hostname for outgoing tunnel connections:___________________________________________________

Tunnel initialization interval seconds:________________________________________________________

Storage Policy used by the default subclient:__________________________________________________

Number of streams you want allocated:______________________________________________________


See Step 3 for more information.

SAP for Oracle-Specific Information
2. SAPEXE directory:_____________________________________________________________________

See Step 3 for more information.

Sybase-Specific Information
3. Sybase User ID: __________________________________________________________________________

Sybase User Group: _______________________________________________________________________

Sybase Server: ___________________________________________________________________________

Sybase home directory:_____________________________________________________________________

Sybase ASE home directory:_________________________________________________________________

Sybase OCS home variable___________________________________________________________________

See Step 3 for more information.

Before You Begin

  • Log on to the client as root.
  • The install package requires super-user permissions to execute.
  • If the installation will have /tmp mounted with the NOEXEC option, the GX_TMP_DIR environment variable must be set to a directory with execute privileges and then exported (for example: export GX_TMP_DIR=/space/tmp).

Install Procedure

1. Place the software installation disc for Unix clients into the client computer's disc drive and mount the installation disc.
2. Unless you want to install a Linux iDataAgent or Linux MediaAgent using an available package management system, search the installation disc for silent_install.example file. This file contains the parameters whose values you can modify for use at your site’s installation. You must use either the default version or a user-named version of this file.

To use the default version of the file, copy and rename the silent_install.example file to /tmp/pkgenvinfo.

To use a user-defined version of the file, copy the silent_install.example file to a user-named directory and file of your choice (e.g., /start/user_choice).

If you are installing a Linux iDataAgent or Linux MediaAgent using a package management system, search the system for the cvsi.conf file (e.g., /etc/cvsi.conf) and the RPM or APT package management system file.

3. Edit the pkgenvinfo file, user-defined file, or cvsi.conf file as appropriate to modify the values of the following parameters for use in your site’s installation. Note that several parameters are optional as indicated.
  • SUBSYSTEMS= {these are the names of the subsystems (agents) to be installed, and these parameters are required if they are not specified in the command line. Valid values include CVGxIDA, CVGxMA, CVGxOrIDA, CVGxIfIDA, CVGxSybIDA, CVGxOrSAP and CVGxSRM. One or more parameters can be specified (e.g., CVGxIDA, CVGxMA)}
  • INSTANCE= {this is the name of the instance to which the software will be installed in a multi-instance environment (e.g., Instance001)}
  • COMMCELL_USERNAME/COMMCELL_PASSWORD= {this is the user name and password used to log in to the CommCell, and this information is required if the CommCell is enabled for client authentication. Valid values are registered in the CommServe (e.g., admin, admin)}
  • CVD_PORT= {this is the TCP port number for the Communications Service (CVD) (e.g., 8401)}
  • EVMGRC_PORT= {this is the TCP port number for the Client Event Manager Service (EvMgrC) (e.g., 8402)}
  • INSDIR= {this is the directory where you want the Base software and/or iDataAgent installed (e.g., /opt)}
  • LOGDIR= {this is the directory where you want the log files to reside (e.g., /var/log)}
  • JOBDIR= {this is the directory where you want the job results to reside (e.g.,/opt)}
  • CACHEDIR= {this is provided as a placeholder for when MediaAgent silent installs are supported}
  • CLIENT_NAME= {(optional) this is the client’s long name or short name (e.g., or sirius)}
  • CLIENT_HOSTNAME= {(optional) this is the client’s long name (e.g.,}
  • CLIENT_GROUP= {(optional) this is the name of the client group to which this client will be associated (e.g., unix group)}
  • PHYS_NODENAME= {this is the node name for the physical machine (e.g., sirius)}
  • PHYS_HOSTNAME= {this is the name of the physical interface (e.g.,}
  • SERVER_HOSTNAME= {this is the server’s host name, which can be either a long name or a short name (e.g., or vega)}

    Do not use this parameter if you are running a Decoupled Install of the software. Otherwise, the installation will fail.

  • FW_CONFIG= {(optional) this is used to specify whether you want to configure firewall settings. Use value 1 to configure firewall settings, value 0 (default) to forego configuring the settings}
  • FW_PORTS= {(optional) this is used to identify the number range of the unused ports or the number range of the open incoming ports for a one-way firewall that allows only outgoing connections (e.g., 8600-8620)}
  • FW_ONDEMAND= {(optional) this is used to list the two-way (symmetrical) firewalled host computers (e.g.,}
  • FW_PERSISTENT= {(optional) this is used to list the one-way firewalled host computers that can be accessed from this computer (e.g.,}
  • FW_PASSIVE= {(optional) this is used to list the one-way firewalled host computers that can access this computer (e.g., 172.10.10)}
  • FW_KEEP_ALIVE= {(optional) this is used indicate the number of seconds between tunnel refresh packets (e.g., 300)}
  • SP= {this is the name of the storage policy you want assigned to the default subclient in the default backup set (e.g., SP_Maglibrary_2)}

    Storage policy names are listed on the CommCell Console.

  • NUMSTREAMS= {this is the number of streams you want allocated (e.g., 10)}

    This field is only for Solaris clients.

    If you enter 0 for this field, the /etc/system configuration file is not updated.

    If you enter a value greater than 0, the /etc/system configuration file is updated, and the original version of the file is copied to an /etc/ file (where PID is the installer process ID on the server).

  • GALAXY_GROUP= {this is the name of the group that will be assigned to all files and on behalf of which all processes will run}
  • FORCE_IPV4= {this is used to enforce a probe of the IPV4 network for systems either not running IPV6 or with IPV6 installed but for which IPV6 should not be used. Use value 1 to enforce an IPV4 probe, 0 to disable it.}
  • DECOUPLED_INSTALL= {this is used to run a Decoupled Install of the software. Use value 1 to run this install.}
  • SINGLE_INTERFACE_BINDING = {(optional) this is used if you want to bind all services to the specified interface name or IP address. Use value 1 to enforce this capability, 0 to disable it.}
  • COMMCELL_GLOBAL_FILTER = {(optional) this is used to filter out specific directories or files from the backups within the CommCell. The filters are set using the Control Panel in the CommCell Console and, if enabled, they will be effective for the default subclient. Valid values include 0, the default (use the CommCell-level policy), 1 (on), and 2 (off) (e.g., 0)}
  • INSTALL_LATEST_SP= {(optional) this is used to download and install the latest service pack. Use value 1 to download and install the service pack, value 0 (default) to disable the download and install.}

The following parameter pertains only to SAP for Oracle:

  • SAPEXEHOME= {this is the path of the SAPEXE directory (e.g., /usr/sap/SYS/exe)}

The following parameters pertain only to Sybase:

  • SYBASE_NUM= {this is the instance number for the Sybase instance being configured (e.g., 1)}
  • SYBASE_USER= {this is the Sybase user ID (e.g., sybase)}
  • SYBASE_GROUP= {this is the name of the Sybase user group (e.g., sybase)}
  • SYBASE_SERVER= {this is the name of the Sybase server (e.g., tigger)}
  • SYBASE_HOME= {this is the name of the Sybase home directory (e.g., /sybase/sybase12.5.3)}
  • SYBASE_ASE= {this is the name of the Sybase ASE directory (e.g., ASE-12_5)}
  • SYBASE_OCS= {this is the name of the Sybase OCS variable (e.g., OCS-12_5)}

Save your changes.

4. Run one of the following commands as appropriate:
  • Using the traditional parameters file:

    silent_install [-params <params_file>] [-log <log_file>]\ <module _1>...<module_n>


    • <params_file> specifies the name of the file with installation parameters. If you are using a user-defined file name, be sure to enter the entire path (e.g., /start/user_choice). If you are using the default file name, omit this parameter.
    • <log_file> specifies the custom log file name that you should create as a temporary log file. This file is displayed only if the installation fails.
    • <module_1..._n> specifies the name of the subsystem(s) to be installed. Values include CVGxBase (for the Base software) and CVGxIDA (for the iDataAgent). CVGxIDA is the only <module> parameter that you need to include in the command line to install both the iDataAgent and the Base software.

    For example:

    silent_install -params /start/user-choice -log log_file CVGxBase CVGxIDA

    If you are using the default version of the silent_install.example file (i.e., if you have copied and renamed this file to /tmp/pkgenvinfo), you need only issue one of the following commands:

    silent_install CVGxBase CVGxIDA


    silent_install CVGxIDA.

  • Using the RPM package management system:

    Copy, modify and rename silent_install.example script file from installation discs base location to /etc/cvsi.conf.

    rpm -i <pkgfile>


    <pkgfile> is the name of the RPM package management system file

    For example:

    rpm -i rely_version1.rpm

  • Using the APT package management system:

    dpkg -i <pkgfile>


    <pkgfile> is the name of the APT package management system file

    For example:

    dpkg -i rely_version2.deb

5. The Base software is installed first followed by the iDataAgent. This installation will use the parameters that you entered into the your parameters file or package management system file.
6. The installation has completed when a message appears, similar to the example. Installation of CVGxBase0 CVGxBase CVGxIDA completed successfully

Post-Install Considerations

All Agents

  • Review the Post-Install Considerations specific to the components that were installed using this procedure. (See Installation for a list of all Install procedures.)