Installation of UNIX Agents by a Non-Root User
Many newer UNIX systems and their derivatives do not explicitly have a root user defined at the time of installation. The SUDO command is used for root access on such systems, but the root access obtained this way is limited to the command that is run. To overcome these limitations, create a non-root user with special privileges to install the SnapProtect software.
If there is more than one non-root user running installations on the same computer, then the software is installed on different SnapProtect instances. For example, if an Oracle and DB2 user performed installations, two separate instances exist with different registry locations running independently of each other.
The non-root user must have read and write permissions to the /tmp/locks directory.
Supported Installation Methods
You can install as a non-root user by using the installation package that was created from the Download Manager. Installations that use the CommCell Console are not supported.
The following installation tasks are supported:
- Local installations (including installations in decoupled mode)
- Custom package creation and installation
- Unattended installations (silent installations that use prerecorded XML files)
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.
|File System Agent|| The following features are not supported:
Review the following information after the installation, and ensure that you follow any necessary postinstallation task.
Review Files and Folders Created During Installation
The installation program uses the home directory of the non-root user for the following items:
- 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.
Restart SnapProtect Services
SnapProtect services do not start automatically during a reboot. You must start the services manually by running the following command from the Software_Installation_Path/Base directory:
If the PATH environment variable in the $HOME/.bash_profile or the $HOME/.profile files is exported to the Software_Installation_Path/Base directory, you can run the following command from any directory.
Updates must be installed by the same user who installed the SnapProtect 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 galaxy_vm command to get the registry path, as shown below: