nfs backup storage fails silently.

[Daxcor]

I am trying to setup a backup location on a remote nfs server. When I go to setup the nfs storage via the datacenter, it goes through and sets up the storage.

storage.cfg snippet

nfs: nfs-backup
        export /home
        path /mnt/pve/nfs-backup
        server 10.20.10.22
        content backup,images
        prune-backups keep-all=1

when I run the backup it proceeds with no errors, however it silently fails to connect to the nfs server and saved the file on the local system at /mnt/pve/nfs-backup. I am not sure what I am doing wrong, is this not the intention of this type of storage configuration? when I am in the gui and I input the ip address of the nfs server it responds with the list of exports from the nfs server. so I know it is communicating with the nfs server.

I am running proxmox 9.2.9 non subscription. The nfs server is ubuntu 26.04 with nfs 4.2

I appreciate any thoughts or solutions.
Brad

 

[Onslow]

saved the file on the local system at /mnt/pve/nfs-backup

Hi, @Daxcor.
This fact suggests that the NFS share isn't mounted in this location in the PVE server.
What does df -hT show?

 

[Daxcor]

Hi, here is the output. Yes you will notice the export name has changed, from /home to /proxmox. This was intentional. the expected dir on the local pve host are there, but they are not translated or saved on the remote nfs hosts.

root@pve0:~# df -hT
Filesystem           Type      Size  Used Avail Use% Mounted on
udev                 devtmpfs  176G     0  176G   0% /dev
tmpfs                tmpfs      38G  7.4M   38G   1% /run
rpool/ROOT/pve-1     zfs       425G  3.2G  421G   1% /
tmpfs                tmpfs     189G   54M  189G   1% /dev/shm
efivarfs             efivarfs  304K   82K  218K  28% /sys/firmware/efi/efivars
tmpfs                tmpfs     189G     0  189G   0% /tmp
tmpfs                tmpfs     5.0M     0  5.0M   0% /run/lock
tmpfs                tmpfs     1.0M     0  1.0M   0% /run/credentials/systemd-journald.servic                                                                                                  e
rpool                zfs       421G  128K  421G   1% /rpool
rpool/var-lib-vz     zfs       428G  6.3G  421G   2% /var/lib/vz
rpool/ROOT           zfs       421G  128K  421G   1% /rpool/ROOT
rpool/data           zfs       421G  128K  421G   1% /rpool/data
zfs-mirror           zfs       3.0T  128K  3.0T   1% /zfs-mirror
/dev/fuse            fuse      128M   68K  128M   1% /etc/pve
tmpfs                tmpfs     1.0M     0  1.0M   0% /run/credentials/getty@tty1.service
tmpfs                tmpfs      38G  4.0K   38G   1% /run/user/0
10.20.10.22:/proxmox nfs4      915G   12G  858G   2% /mnt/pve/nfs-backup

 

[Daxcor]

If I go and create a manual nfs mount

mount -t nfs 10.20.10.22:/home /mnt/testnfs/

it completes the task. when I cd into /mnt/testnfs I can touch a file here. When I go look on the nfs server I do NOT see the file there. I have no clue as to where the files are actually being stored.

root@pve0:/mnt/pve/nfs-backup# df -hT
Filesystem           Type      Size  Used Avail Use% Mounted on
udev                 devtmpfs  176G     0  176G   0% /dev
tmpfs                tmpfs      38G  7.4M   38G   1% /run
rpool/ROOT/pve-1     zfs       425G  3.2G  421G   1% /
tmpfs                tmpfs     189G   60M  189G   1% /dev/shm
efivarfs             efivarfs  304K   82K  218K  28% /sys/firmware/efi/efivars
tmpfs                tmpfs     189G     0  189G   0% /tmp
tmpfs                tmpfs     5.0M     0  5.0M   0% /run/lock
tmpfs                tmpfs     1.0M     0  1.0M   0% /run/credentials/systemd-journald.service
rpool                zfs       421G  128K  421G   1% /rpool
rpool/var-lib-vz     zfs       428G  6.3G  421G   2% /var/lib/vz
rpool/ROOT           zfs       421G  128K  421G   1% /rpool/ROOT
rpool/data           zfs       421G  128K  421G   1% /rpool/data
zfs-mirror           zfs       3.0T  128K  3.0T   1% /zfs-mirror
/dev/fuse            fuse      128M   68K  128M   1% /etc/pve
tmpfs                tmpfs     1.0M     0  1.0M   0% /run/credentials/getty@tty1.service
tmpfs                tmpfs      38G  4.0K   38G   1% /run/user/0
10.20.10.22:/proxmox nfs4      915G   12G  858G   2% /mnt/pve/nfs-backup
10.20.10.22:/home    nfs4      915G   12G  858G   2% /mnt/testnfs

 

[Daxcor]

nfsstat -m
10.20.10.22:/proxmox on /mnt/pve/nfs-backup type nfs4 (rw,relatime,vers=4.2,rsize=1048576,wsize=1048576,namlen=255,hard,fatal_neterrors=none,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=10.20.10.40,local_lock=none,addr=10.20.10.22)

10.20.10.22:/home on /mnt/testnfs type nfs4 (rw,relatime,vers=4.2,rsize=1048576,wsize=1048576,namlen=255,hard,fatal_neterrors=none,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=10.20.10.40,local_lock=none,addr=10.20.10.22)

/mnt/pve/nfs-backup from 10.20.10.22:/proxmox
 Flags: rw,relatime,vers=4.2,rsize=1048576,wsize=1048576,namlen=255,hard,fatal_neterrors=none,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=10.20.10.40,local_lock=none,addr=10.20.10.22

/mnt/testnfs from 10.20.10.22:/home
 Flags: rw,relatime,vers=4.2,rsize=1048576,wsize=1048576,namlen=255,hard,fatal_neterrors=none,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=10.20.10.40,local_lock=none,addr=10.20.10.22

 

[Daxcor]

Ok, this was a zfs dataset issue on the nfs server. The data is actually there on the nfs server. mounting the zfs dataset was what I had to do to see the actual data.