Hello,
I'm a noob when it comes to configuring remote backups but I have a ZFS dataset that I have exported as an NFS share but when I try to run a backup job to backup one my VM image's, the back up status log just hangs at 1%
The associated task ID has a uninterruptible sleep state when running ps:
On the NAS side, it looks like some of the data is being written but mainly just the directories:
I added the share via this command and options on the PVE side:
And exported it from my file server via this command and options:
I understand that no_root_squash is not an ideal option in most cases due to security reasons. Once this is solved I plan on setting up a dedicated proxmox user for this
This could very well be a general NFS or network problem but from what I've been able to tell, proxmox backups over NFS are really the only application that seems to struggle with the file share. I'm wondering if theres anything obvious I'm missing or if I should try a samba share if it plays nicer with proxmox maybe.
I'm a noob when it comes to configuring remote backups but I have a ZFS dataset that I have exported as an NFS share but when I try to run a backup job to backup one my VM image's, the back up status log just hangs at 1%
Code:
()
INFO: starting new backup job: vzdump 101 --prune-backups 'keep-last=2,keep-weekly=2' --all 0 --mode stop --fleecing 0 --storage backup-01 --compress gzip --node proxmox --notification-mode notification-system --notes-template '{{guestname}}'
INFO: Starting Backup of VM 101 (qemu)
INFO: Backup started at 2025-09-09 06:14:28
INFO: status = stopped
INFO: backup mode: stop
INFO: ionice priority: 7
INFO: VM Name: app-server-01
INFO: include disk 'sata1' 'local-lvm:vm-101-disk-0' 256G
INFO: creating vzdump archive '/mnt/pve/backup-01/dump/vzdump-qemu-101-2025_09_09-06_14_28.vma.gz'
INFO: starting kvm to execute backup task
INFO: started backup task 'ae229cbe-d693-4cda-8c2c-22b9fa1b6980'
INFO: 0% (145.0 MiB of 256.0 GiB) in 3s, read: 48.3 MiB/s, write: 4.3 MiB/s
INFO: 1% (2.6 GiB of 256.0 GiB) in 4m 3s, read: 10.3 MiB/s, write: 6.1 MiB/s
The associated task ID has a uninterruptible sleep state when running ps:
root 1553371 0.2 1.2 281976 200564 ? Ds 06:14 0:06 task UPID:proxmox:0017B3DB:02C276AF:68BF9B94:vzdump:101:root@pam:On the NAS side, it looks like some of the data is being written but mainly just the directories:
Code:
ls -lah /maliketh/backups/
total 3.0K
drwxr-xr-x 6 root root 6 Nov 19 00:07 .
drwxr-xr-x 6 root root 6 Nov 18 20:48 ..
drwxr-xr-x 3 root root 4 Nov 19 00:11 dump
drwxr-xr-x 2 root root 2 Nov 19 00:06 images
drwxr-xr-x 2 root root 2 Nov 19 00:06 snippets
drwxr-xr-x 3 root root 3 Nov 19 00:07 template
I added the share via this command and options on the PVE side:
pvesm add nfs backup-01 --server 10.9.0.9 --export /maliketh/backups --content images,backup,snippets --options vers=4And exported it from my file server via this command and options:
Code:
~$ zfs get sharenfs maliketh/backups
NAME PROPERTY VALUE SOURCE
maliketh/backups sharenfs rw=@10.3.0.5,no_root_squash local
I understand that no_root_squash is not an ideal option in most cases due to security reasons. Once this is solved I plan on setting up a dedicated proxmox user for this
This could very well be a general NFS or network problem but from what I've been able to tell, proxmox backups over NFS are really the only application that seems to struggle with the file share. I'm wondering if theres anything obvious I'm missing or if I should try a samba share if it plays nicer with proxmox maybe.