Loading...

Installation of UNIX Agents By a Non-Root User Without Sudo Privileges

A non-root user without sudo privileges can install UNIX agents.

Prerequisites

The non-root user must have read and write permissions to the /tmp/locks directory.

Supported Installation Methods

The following installation methods are supported:

  • Local installations (including installations in decoupled mode)
  • Custom package creation and installation
  • Unattended installations (silent installations that use prerecorded XML files)

Note: Installation of UNIX agents by a non-root user without sudo privileges cannot be performed from the Commcell Console GUI.

Supported Agents

The following table lists the agents that are available when you install as a non-root user, along with some important considerations.

Note: If you are installing a custom package, the package displays all of its available agents. However, only the agents listed in the following table are supported for installation.

Agents

Considerations

File System Agent

The following features are not supported:

  • Optimized scans
  • OnePass
  • ContinuousDataReplicator
  • IntelliSnap backups

Oracle Agent

  • The agent supports traditional data backups, log backups, and restores, including restores to disk that were performed by the same user who installed Commvault.
  • Table-level restores and IntelliSnap backups are not supported.
  • For third-party command-line and on-demand backup or restore jobs, the user must pass the CVREG=RegistryPath in the RMAN script. For example:

    run {
    allocate channel ch1 type 'sbt_tape'
    PARMS="SBT_LIBRARY=/home/oracle/opt/commvault/Base/libobk.so,ENV=(CVREG=/home/oracle/CommVaultRegistry/)";
    backup database;
    }
    exit;

DB2 Agent

  • The agent supports traditional data backups, log backups, and restores, including restores to disk that were performed by the same user that installed Commvault.
  • IntelliSnap backups are not supported.
  • Before running Db2_config.sh and db2util.sh, you must set the CVREG environment variable to the registry path. If the environment variable is not set, run the galaxy_vm command to set the registry path, as follows:

     . ~/opt/commvault/galaxy_vm

    The command must be run by the same user who installed Commvault.

  • Use the following commands each time you need to start the DB2 application:

    db2set DB2ENVLIST='CVREG'
    db2stop
    export CVREG="/home/db2inst1/CommVaultRegistry"
    db2start

Files and Folders Created

The installation program uses the home directory of the non-root user for the following items (note that the UNIX symbol ~ is an alias for the user's home directory):

  • Installation binaries are stored in the ~/opt directory.

    In a traditional installation performed by the root user, the program stores the binaries in the /opt directory.

  • Log files are stored in the ~/log directory. Users must have write permissions to access the directory.

    In a traditional installation performed by the root user, the program stores the log files in the /var/log directory.

  • The registry is created in the ~/CommVaultRegistry directory.

    In a traditional installation performed by the root user, the program uses the /etc/CommVaultRegistry directory.

Managing Commvault Services

Commvault services do not start automatically during boot-up. You must start the services manually by running the following commands:

$ cd ~/opt/commvault/Base

$ ./commvault start

Note that if you update the PATH environment variable to include ~/opt/commvault/Base, you will be able to run commvault commands from any directory.

Updating Commvault

Updates must be installed by the same user who installed the Commvault software.

When a non-root user installs updates, the installation program checks whether the CVREG environment variable is already set in the registry path. If it is not set, run the commvault shell command to initialize your environment, as follows:

$ cd ~/opt/commvault/Base

$ ./commvault shell

Last modified: 5/31/2019 8:10:02 PM