seems that SUDO and privilege account management are unexplored lands in a Avamar’s landscape. SUDO and privilege account management are forbidden lands in the Avamar landscape. Creation of additional OS-level user accounts on Avamar systems is not supported. Modification of the sudoers configuration on an Avamar system is not supported. You may be denied support if you make these sorts of changes to your system. If your operators specifically need mccli access to the system, I recommend installing the mccli package on a virtual machine as [NAME] mentioned above. The mccli guide for the most recent release is available here: [URL] A better alternative would be the Avamar REST API. The REST API underpins the new AUI interface. It is powerful, flexible, and freely available for customer use. Any tasks that can be performed using the AUI interface can be performed by calling the REST API directly. There is a getting started guide here: [URL]
Hi community, I'm trying to use sudo to avoid granting admin and root password to operators team, they need to do some checks from SO side.Sudo allows us flexibility like this. avoperator[NAME]-04:~/#: sudo mccli client show0,23000,CLI command completed successfully. avoperator[NAME]-04:~/#: sudo mccli client deleteavoperator's password:Sorry, user avoperator is not allowed to execute '/usr/local/avamar/bin/mccli client delete' as root on ave-04. Now operator called "avoperator" has some new commands available after adding there lines in /etc/suders.# Extend permissions to avoperator group%avoperator ALL=(root) NOPASSWD: /usr/local/avamar/bin/mccli * show, /usr/local/avamar/bin/dpnctl status, /usr/local/avamar/bin/status.dpn There are no official avamar doc related to this config. Do you know if it is a config "blessed" by support?
Sudo on avamar