Veeam Support Knowledge Base
Granular sudo Permissions for Veeam Plug-in for Proxmox VE

Granular sudo Permissions for Veeam Plug-in for Proxmox VE

Q: For Veeam Backup & Replication 13

# the account used by Veeam must have PASSWD set; do _not_ use NOPASSWD.veeamdep ALL=(root) PASSWD: /usr/sbin/dmidecode -s system-uuidveeamdep ALL=(root) PASSWD: /usr/bin/kvm -S *,!/usr/bin/kvm -S *-netdev*,!/usr/bin/kvm -S *-fsdev*,!/usr/bin/kvm -S *netdev=*,!/usr/bin/kvm -S *fsdev=*,!/usr/bin/kvm -S *-net*,!/usr/bin/kvm -S *net=*veeamdep ALL=(root) PASSWD: /usr/bin/qemu-img info *veeamdep ALL=(root) PASSWD: /usr/bin/qemu-img create *veeamdep ALL=(root) PASSWD: /usr/sbin/qm create *,!/usr/sbin/qm create * --hookscript*veeamdep ALL=(root) PASSWD: /usr/sbin/qm ^showcmd [0-9]+ --pretty$veeamdep ALL=(root) PASSWD: /usr/sbin/qm ^unlock [0-9]+$veeamdep ALL=(root) PASSWD: /usr/bin/socat ^TCP-LISTEN:[0-9]+,bind=127\.0\.0\.1 UNIX-CONNECT:/[a-zA-Z0-9_./-]+$veeamdep ALL=(root) PASSWD: /usr/bin/mkdir -p /var/lib/vz/snippets/veeamdep ALL=(root) PASSWD: /usr/bin/pvenode cert info --output-format jsonveeamdep ALL=(root) PASSWD: /usr/bin/pvesh ^get storage/([a-zA-Z0-9_-]+) --output json$veeamdep ALL=(root) PASSWD: /usr/bin/pvesh ^set /nodes/([a-zA-Z0-9_-]+)/qemu/([0-9]+)/config --lock ([a-zA-Z]+)$veeamdep ALL=(root) PASSWD: /usr/bin/pkill -9 -e -f -x socat *veeamdep ALL=(root) PASSWD: /usr/sbin/lvchange -ay *veeamdep ALL=(root) PASSWD: /usr/sbin/lvchange -an *veeamdep ALL=(root) PASSWD: /usr/bin/rbd device map *veeamdep ALL=(root) PASSWD: /usr/bin/mv ^-n /tmp/([a-zA-Z0-9_-]+\.config) /var/lib/vz/snippets/([a-zA-Z0-9_-]+\.config)$veeamdep ALL=(root) PASSWD: /usr/bin/rm ^(/[a-zA-Z0-9_/-]/VeeamTmp[a-zA-Z0-9_.-]\s*)+$ veeamdep ALL=(root) PASSWD: /usr/bin/rm ^-f /[a-zA-Z0-9_/-]+/VeeamTmp[a-zA-Z0-9_.-]+$veeamdep ALL=(root) PASSWD: /usr/bin/rm ^-f /var/lib/vz/snippets/[a-zA-Z0-9_-]+\.config$veeamdep ALL=(root) PASSWD: /usr/bin/rm ^-f /var/lib/vz/template/iso/[a-zA-Z0-9_.-]+\.img$ Copy

Q: For Veeam Backup & Replication 12.x

# the account used by Veeam must have PASSWD set; do _not_ use NOPASSWD.veeamdep ALL=(root) PASSWD: /usr/sbin/dmidecode -s system-uuidveeamdep ALL=(root) PASSWD: /usr/bin/kvm -S *veeamdep ALL=(root) PASSWD: /usr/bin/qemu-img info *veeamdep ALL=(root) PASSWD: /usr/bin/qemu-img create *veeamdep ALL=(root) PASSWD: /usr/sbin/qm create *veeamdep ALL=(root) PASSWD: /usr/sbin/qm ^showcmd [0-9]+ --pretty$veeamdep ALL=(root) PASSWD: /usr/sbin/qm ^unlock [0-9]+$veeamdep ALL=(root) PASSWD: /usr/bin/socat ^TCP-LISTEN:[0-9]+,bind=127\.0\.0\.1 UNIX-CONNECT:/[a-zA-Z0-9_./-]+$veeamdep ALL=(root) PASSWD: /usr/bin/mkdir -p /var/lib/vz/snippets/veeamdep ALL=(root) PASSWD: /usr/bin/pvenode cert info --output-format jsonveeamdep ALL=(root) PASSWD: /usr/bin/pvesh ^get storage/([a-zA-Z0-9_-]+) --output json$veeamdep ALL=(root) PASSWD: /usr/bin/pvesh ^set /nodes/([a-zA-Z0-9_-]+)/qemu/([0-9]+)/config --lock ([a-zA-Z]+)$veeamdep ALL=(root) PASSWD: /usr/bin/pkill -9 -e -f -x socat *veeamdep ALL=(root) PASSWD: /usr/sbin/lvchange -ay *veeamdep ALL=(root) PASSWD: /usr/sbin/lvchange -an *veeamdep ALL=(root) PASSWD: /usr/bin/rbd device map *veeamdep ALL=(root) PASSWD: /usr/bin/mv ^-n /tmp/([a-zA-Z0-9_-]+\.config) /var/lib/vz/snippets/([a-zA-Z0-9_-]+\.config)$veeamdep ALL=(root) PASSWD: /usr/bin/rm ^(/[a-zA-Z0-9_/-]/VeeamTmp[a-zA-Z0-9_.-]\s*)+$ veeamdep ALL=(root) PASSWD: /usr/bin/rm ^-f /[a-zA-Z0-9_/-]+/VeeamTmp[a-zA-Z0-9_.-]+$veeamdep ALL=(root) PASSWD: /usr/bin/rm ^-f /var/lib/vz/snippets/[a-zA-Z0-9_-]+\.config$veeamdep ALL=(root) PASSWD: /usr/bin/rm ^-f /var/lib/vz/template/iso/[a-zA-Z0-9_.-]+\.img$ Copy

KB ID:	4701
Product:	Veeam Backup & Replication \| 12.3 \| 12.3.1 \| 12.3.2 \| 13
Published:	2025-02-24
Last Modified:	2025-09-18

Cheers for trusting us with the spot in your mailbox!

Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest

Oops! Something went wrong.

Please, try again later.

Considerations and System Requirements

Proxmox VE does not include the sudo package and associated command by default; it must be installed manually (installation and configuration documented below).
Veeam Plug-in for Proxmox VE supports sudo version 1.9.10 or newer.
The capability to add Proxmox VE to Veeam Backup & Replication using a non-root sudo user was added in Veeam Plug-in for Proxmox VE version 12.1.3.197 for Veeam Backup & Replication 12.3.
Additional Considerations and Limitations can be found in the user guide.

Purpose

This article provides an example granular ‘sudoers’ configuration for the Linux account that will be used by Veeam Backup & Replication when managing a Proxmox VE host.

Solution

Install and Configure sudo

While the installation and configuration of third-party applications is generally considered outside the scope of Veeam Support, Veeam has elected to provide this guidance as a courtesy to help ensure a smooth implementation of granular permissions. Please note that this configuration method is just one of many possible ways to use sudo to achieve the desired result. We recommend consulting with your Proxmox administration or security team to determine whether your organization has a preferred methodology for configuring sudo.

The following steps should be performed on the Proxmox host while logged in as the root user.

Use the following command to check whether sudo is installed and, if so, which version is installed.
Veeam Plug-in for Proxmox VE requires at least sudo version 1.9.10.

sudo --version

If sudo is not already installed, use the following command to install the latest version of sudo:

apt update && apt install sudo -y
                
            

Use the following command to create a dedicated user account that will be used by Veeam Backup & Replication:
For this article, the account name used is veeamdep.

adduser veeamdep

Create the granular sudoers file using the following command:

visudo -f /etc/sudoers.d/veeamdep

The file /etc/sudoers.d/veeamdep should contain the following:

For Veeam Backup & Replication 13

# the account used by Veeam must have PASSWD set; do _not_ use NOPASSWD.
veeamdep ALL=(root) PASSWD: /usr/sbin/dmidecode -s system-uuid
veeamdep ALL=(root) PASSWD: /usr/bin/kvm -S *,!/usr/bin/kvm -S *-netdev*,!/usr/bin/kvm -S *-fsdev*,!/usr/bin/kvm -S *netdev=*,!/usr/bin/kvm -S *fsdev=*,!/usr/bin/kvm -S *-net*,!/usr/bin/kvm -S *net=*
veeamdep ALL=(root) PASSWD: /usr/bin/qemu-img info *
veeamdep ALL=(root) PASSWD: /usr/bin/qemu-img create *
veeamdep ALL=(root) PASSWD: /usr/sbin/qm create *,!/usr/sbin/qm create * --hookscript*
veeamdep ALL=(root) PASSWD: /usr/sbin/qm ^showcmd [0-9]+ --pretty$
veeamdep ALL=(root) PASSWD: /usr/sbin/qm ^unlock [0-9]+$
veeamdep ALL=(root) PASSWD: /usr/bin/socat ^TCP-LISTEN:[0-9]+,bind=127\.0\.0\.1 UNIX-CONNECT:/[a-zA-Z0-9_./-]+$
veeamdep ALL=(root) PASSWD: /usr/bin/mkdir -p /var/lib/vz/snippets/
veeamdep ALL=(root) PASSWD: /usr/bin/pvenode cert info --output-format json
veeamdep ALL=(root) PASSWD: /usr/bin/pvesh ^get storage/([a-zA-Z0-9_-]+) --output json$
veeamdep ALL=(root) PASSWD: /usr/bin/pvesh ^set /nodes/([a-zA-Z0-9_-]+)/qemu/([0-9]+)/config --lock ([a-zA-Z]+)$
veeamdep ALL=(root) PASSWD: /usr/bin/pkill -9 -e -f -x socat *
veeamdep ALL=(root) PASSWD: /usr/sbin/lvchange -ay *
veeamdep ALL=(root) PASSWD: /usr/sbin/lvchange -an *
veeamdep ALL=(root) PASSWD: /usr/bin/rbd device map *
veeamdep ALL=(root) PASSWD: /usr/bin/mv ^-n /tmp/([a-zA-Z0-9_-]+\.config) /var/lib/vz/snippets/([a-zA-Z0-9_-]+\.config)$
veeamdep ALL=(root) PASSWD: /usr/bin/rm ^(/[a-zA-Z0-9_/-]/VeeamTmp[a-zA-Z0-9_.-]\s*)+$ 
veeamdep ALL=(root) PASSWD: /usr/bin/rm ^-f /[a-zA-Z0-9_/-]+/VeeamTmp[a-zA-Z0-9_.-]+$
veeamdep ALL=(root) PASSWD: /usr/bin/rm ^-f /var/lib/vz/snippets/[a-zA-Z0-9_-]+\.config$
veeamdep ALL=(root) PASSWD: /usr/bin/rm ^-f /var/lib/vz/template/iso/[a-zA-Z0-9_.-]+\.img$
                
            

For Veeam Backup & Replication 12.x

# the account used by Veeam must have PASSWD set; do _not_ use NOPASSWD.
veeamdep ALL=(root) PASSWD: /usr/sbin/dmidecode -s system-uuid
veeamdep ALL=(root) PASSWD: /usr/bin/kvm -S *
veeamdep ALL=(root) PASSWD: /usr/bin/qemu-img info *
veeamdep ALL=(root) PASSWD: /usr/bin/qemu-img create *
veeamdep ALL=(root) PASSWD: /usr/sbin/qm create *
veeamdep ALL=(root) PASSWD: /usr/sbin/qm ^showcmd [0-9]+ --pretty$
veeamdep ALL=(root) PASSWD: /usr/sbin/qm ^unlock [0-9]+$
veeamdep ALL=(root) PASSWD: /usr/bin/socat ^TCP-LISTEN:[0-9]+,bind=127\.0\.0\.1 UNIX-CONNECT:/[a-zA-Z0-9_./-]+$
veeamdep ALL=(root) PASSWD: /usr/bin/mkdir -p /var/lib/vz/snippets/
veeamdep ALL=(root) PASSWD: /usr/bin/pvenode cert info --output-format json
veeamdep ALL=(root) PASSWD: /usr/bin/pvesh ^get storage/([a-zA-Z0-9_-]+) --output json$
veeamdep ALL=(root) PASSWD: /usr/bin/pvesh ^set /nodes/([a-zA-Z0-9_-]+)/qemu/([0-9]+)/config --lock ([a-zA-Z]+)$
veeamdep ALL=(root) PASSWD: /usr/bin/pkill -9 -e -f -x socat *
veeamdep ALL=(root) PASSWD: /usr/sbin/lvchange -ay *
veeamdep ALL=(root) PASSWD: /usr/sbin/lvchange -an *
veeamdep ALL=(root) PASSWD: /usr/bin/rbd device map *
veeamdep ALL=(root) PASSWD: /usr/bin/mv ^-n /tmp/([a-zA-Z0-9_-]+\.config) /var/lib/vz/snippets/([a-zA-Z0-9_-]+\.config)$
veeamdep ALL=(root) PASSWD: /usr/bin/rm ^(/[a-zA-Z0-9_/-]/VeeamTmp[a-zA-Z0-9_.-]\s*)+$ 
veeamdep ALL=(root) PASSWD: /usr/bin/rm ^-f /[a-zA-Z0-9_/-]+/VeeamTmp[a-zA-Z0-9_.-]+$
veeamdep ALL=(root) PASSWD: /usr/bin/rm ^-f /var/lib/vz/snippets/[a-zA-Z0-9_-]+\.config$
veeamdep ALL=(root) PASSWD: /usr/bin/rm ^-f /var/lib/vz/template/iso/[a-zA-Z0-9_.-]+\.img$
                
            

Review the primary sudoers configuration file and ensure the following line is uncommented:
```
includedir /etc/sudoers.d
```
Use the following command to edit the /etc/sudoers file:

visudo

Run the following command to ensure that the dmidecode package is installed:

apt update && apt install dmidecode -y
                
            

Create a Dedicated Proxmox User for Veeam

Within the Proxmox configuration, add the same user name from Step 3 to the Datacenter.
Datacenter > Permissions > Users > Add
Add the Administrator role for the root path ( Path: / ) to that user.
Datacenter > Permissions > Add > User Permission

Configure Proxmox Credentials within Veeam Backup & Replication

Note: When using granular sudo permissions, ensure that the following options are not selected:

Add account to the sudoers file — Enabling this option would cause the Veeam software to add the account to the sudoers file with broader permissions than those specified in the granular sudoers example.
Use "su" if "sudo" fails — Enabling this option would cause Veeam Backup & Replication to switch to using the root account if any of the sudo commands fail due to a command not being included in the granular sudoers file. This could potentially mask a needed update to the granular sudoers file.

Screenshot shows the credentials window with the option to add the account to the sudoers file and use su if sudo fails both unchecked.

Common Errors

The following error may appear if dmidecode is not installed (Step 6 above):

Make sure the specified user has sufficient permissions to execute dmidecode on the Proxmox VE server

The following error may appear if the user is not configured in Proxmox (Step 7 above):
```
The provided credentials are invalid
```

Double Check Configuration

Several recent cases where customers configured granular permissions and faced issues with connecting to the Proxmox VE environment were caused by either incorrectly configured sudo permissions (e.g., wrong username specified in the sudoers file) or missing or incorrect sudo configuration on the Proxmox VE host.

Please create a support case if issues persist after double-checking the sudoers file and sudo configuration.

To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

Spelling error in text

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please, try again later.

You have selected too large block!

Please try select less.

Granular sudo Permissions for Veeam Plug-in for Proxmox VE

Cheers for trusting us with the spot in your mailbox!

Oops! Something went wrong.

Purpose

Solution

Install and Configure sudo

Create a Dedicated Proxmox User for Veeam

Configure Proxmox Credentials within Veeam Backup & Replication

Common Errors

Spelling error in text

Thank you!

Oops! Something went wrong.

You have selected too large block!

KB Feedback/Suggestion

Thank you!

Oops! Something went wrong.