Loading...
Loading...
This article provides examples of granular ‘sudo’ configuration for the Linux account that will be used by Veeam Backup & Replication when managing Veeam Agent for Linux deployments with a Protection Group.
Per the Agent Management User Guide, a user account for Agent Management should have administrative permissions on the computer you want to add to a protection group or a job. If you would like to avoid using the ‘root’ account in favor of a sudoer account, you may also want to set permissions granularly for one. This document helps you to achieve this goal.
Linux user account used by Veeam Backup & Replication for any Veeam Agent for Linux deployment and management operations must have /bin/bash shell set by default. The account must have either ‘root’ or permissions to execute a specific list of commands as a sudoer on the target Linux machine. (See examples below.)
Related Articles Granular sudo Permissions for Management of Hardened Repository Granular sudo Permissions for Management of Linux-base Tape Server Granular sudo Permissions for Management of Veeam Agent for IBM AIX Granular sudo Permissions for Management of Veeam Agent for Linux Deployments Granular sudo Permissions for Management of Veeam Agent for Oracle Solaris Granular sudo Permissions for Installing Veeam Plug-ins for Enterprise Applications using Protection Groups
Veeam Integration
Learn more about where this data comes from
BugZero Plan
Streamline upgrades with automated vendor bug scrubs
BugZero Prevent
Wish you caught this bug sooner? Get proactive today.