Veeam Agent for Oracle Solaris 2.0
User Guide
Related documents

Granting Permissions to Users

When you install Veeam Agent for Oracle Solaris, the product program files are placed to the directories on the system volume. For full access to Veeam Agent for Oracle Solaris files, super user (root) privileges are required. Rights to execute product files and run commands are also granted to users that belong to the veeam group.

The veeam group is automatically created by Veeam Agent for Oracle Solaris at the process of the product installation. To let regular users work with Veeam Agent for Oracle Solaris without the need to gain root privileges, you can add the necessary users to this group. Users in the veeam group will be able to execute Veeam Agent for Oracle Solaris commands and perform backup and restore tasks under a regular user account.

To add a user to the veeam group, use the following command:

usermod -G veeam <username>

where <username> is a user name of the account to which you want to grant access to Veeam Agent for Oracle Solaris.

For example:

root@srv01:~# usermod -G veeam user01

 

Granting Permissions to UsersImportant!

Mind the following:

  • To add a user to the veeam group, you must have super user (root) privileges in the Oracle Solaris OS.
  • After a user is added to the veeam group, the user must re-login to the Oracle Solaris OS to complete the procedure of adding the user to the group.
  • Add only trusted users to the veeam group. Veeam Agent for Oracle Solaris daemon runs and executes commands and scripts with the super user privileges. Thus, users who belong to this group can potentially escalate their privileges through the use of pre-job/post-job scripts.

 

To check whether the user who is currently logged in to the Oracle Solaris OS is added to the veeam group, you can use the following command:

groups

For example:

user@srv01:~$ groups
staff veeam

 

This Document Help Center
User GuideVeeam Agent for IBM AIX User Guide
I want to report a typo

There is a misspelling right here:

 

I want to let the Veeam Documentation Team know about that.