Configure a dedicated Proxmox backup user and give it only the necessary permissions. This way the agent can work, and the root account does not need to roam the hallway unattended.
Manufacturer documentation recommends a dedicated user instead of root. The three basic roles are attached to the Datacenter path /Sys.Modify permission is a separate extension required only if you want to limit bandwidth, and its scope should be minimized.
What does each role do?
PVEVMAdmin
Administrative permissions for machines, including creating snapshots and access to VM configuration, required for the backup process.
PVESDNUser
Access to read Software-Defined Network (SDN) configuration, necessary for proper operation.
PVEDatastoreAdmin
Reading Datastore content and allocating space, for backup and restore operations.
Sys.Modify — only as needed.
Required when you want to apply bandwidth restrictions. The permission also allows the creation, modification, or removal of node network parameters and related system settings; therefore, it is not granted automatically or broadly.
Creating a dedicated user
In the Proxmox VE interface, create a dedicated user, for example backupuser@pve or backupuser@pam, according to the realm you are using. Store the login details in a secret vault and provide them only to operators and services that need them.
Granting the three basic roles in the interface
-
Open the Datacenter.
Log in to the Proxmox VE interface and select the object Datacenter in the tree on the side.
-
Go to Permissions.
Open the tab Permissions and click Add → User Permission.
-
Select the user and path.
Set Path to the value. /, and select the dedicated backup user. This scope applies to the Datacenter node; if your environment requires a different scope, review the permissions design before applying.
-
Add roles and save
Add PVEVMAdmin, PVESDNUser andPVEDatastoreAdmin, and then save. Broad built-in roles such as PVEAdmin or Administrator are suitable at most for testing; in production, the principle of least privilege is preferred.
If bandwidth limitation is required
An informational message about lack of authorization for the bandwidth limit is not necessarily a backup failure: according to the manufacturer, the backup can complete successfully even if the limit is not applied. If the limit is required, the permission must be added Sys.Modify via a role. It cannot be assigned directly, andPVEAdmin does not include it.
Creating a dedicated role in the interface
- Open Datacenter → Permissions → Roles and click Add.
- Create a role, for example NodeAdmin, and select the permission Sys.Modify. Add additional permissions only if needed.
- Go to Datacenter → Permissions → Add → User Permission. Select the user or group, a path as narrow as possible — for example /nodes/node1 instead of / if sufficient — and the role NodeAdmin.
- Activate Propagate only if permission inheritance is needed, save and check.
Alternative via CLI
Perform only after you have checked the user and path scope:
pveum role add NodeAdmin --privs "Sys.Modify"
pveum aclmod /nodes/node1 -user user@pve -role NodeAdmin
Replace the node1 And user@pve in your values. If authorization is required at the Datacenter level, the manufacturer also records the path /; this is a broader authorization, so use it only when necessary.
Authentication and control
- Check that the account can connect and that the program sees the host and the designated machines.
- Run a backup and check its result and the authorization messages. In case of code 1981, check if only the bandwidth limit was not applied or if there is an additional failure.
- If you changed permissions, perform a limited backup and restore test, and ensure the access is not broader than required.
- Document the owner, purpose of the authorization, path, and role, and set a date for reevaluation.
Short checklist
- A dedicated user has been created; root details were not entered instead.
- The three basic roles are assigned to the appropriate path.
- Sys.Modify was added only if a bandwidth limitation is required, and to the minimal extent possible.
- Backup and restore were tested, and every information message was distinguished from a real error.
Further reading: Questions and answers about Proxmox backup.


