Automation Suite on Linux installation guide

Last updated Mar 26, 2026

How to reduce permissions for an NFS backup directory

For Velero to function, you must assign read, write, and execute permissions. The backup hook pod runs with the nobody group, so you can set the same group for Velero and the NFS directory.

You need to take the following steps to configure Velero and update the NFS directory permissions:

Assign the nobody group to Velero by running the following command:
```
kubectl patch deploy velero -n velero \
  --type='merge' \
  -p '{"spec":{"template":{"spec":{"securityContext":{"runAsUser":1002,"runAsGroup":65534,"fsGroup":65534}}}}}'
kubectl patch deploy velero -n velero \
  --type='merge' \
  -p '{"spec":{"template":{"spec":{"securityContext":{"runAsUser":1002,"runAsGroup":65534,"fsGroup":65534}}}}}'
```
This command sets the group to nobody for Velero.

Note:
Reapply this command if you rerun the manifest or upgrade Velero.
Change permissions on the NFS directory by running the following commands:
```
chown -R nobody: /data/disk
chmod -R 770 /datadisk/
chown -R nobody: /data/disk
chmod -R 770 /datadisk/
```
These commands set the directory to the nobody group and apply read, write, and execute permissions.

Was this page helpful?

PREVIOUSHow to troubleshoot services during installation

NEXTHow to uninstall the cluster