Hi everyone,
I'm having some trouble with a Windows NFS share and PBS. Maybe someone here has run into a similar issue.
I have an NFS Share on a Windows server 2019 DataCenter running on NFSv3 (server 2019 only supports v3).
- mounted it as follows: mount -t nfs -o vers=3,tcp,nolock,hard,timeo=600,retrans=2 10.1.40.81:/shared /mnt/backup-nfs
- created a folder "backup" on the share and took ownership for the user backup
- used this folder to create a Datastore "backup-nfs"
- So far, I'm able to create files and modify them with the Proxmox backup user in the backup folder
- Attaching the new Backup Datastore to the pve environment without any problems
- But then, if I start to backup a VM it comes up with the following error after a few seconds:
After that I created a test NFS Server on a Ubuntu test VM ... runs out of the box (used the same mount settings and so on).
So, I’d get rid of the Windows NFS server, but I can’t—it's a production Veeam Backup Server with a lot of unused storage that I’d like to use.
I'd appreciate any ideas or suggestions!
I'm having some trouble with a Windows NFS share and PBS. Maybe someone here has run into a similar issue.
I have an NFS Share on a Windows server 2019 DataCenter running on NFSv3 (server 2019 only supports v3).
- mounted it as follows: mount -t nfs -o vers=3,tcp,nolock,hard,timeo=600,retrans=2 10.1.40.81:/shared /mnt/backup-nfs
- created a folder "backup" on the share and took ownership for the user backup
- used this folder to create a Datastore "backup-nfs"
- So far, I'm able to create files and modify them with the Proxmox backup user in the backup folder
- Attaching the new Backup Datastore to the pve environment without any problems
- But then, if I start to backup a VM it comes up with the following error after a few seconds:
Code:
()
INFO: starting new backup job: vzdump 204 102 --storage backup-nfs --fleecing 0 --notes-template '{{guestname}}' --mode snapshot --node pve1 --quiet 1
INFO: Starting Backup of VM 102 (qemu)
INFO: Backup started at 2025-07-30 21:00:03
INFO: status = running
INFO: VM Name: k3s2
INFO: include disk 'scsi0' 'lun1:vm-102-disk-0' 100G
INFO: backup mode: snapshot
INFO: ionice priority: 7
INFO: pending configuration changes found (not included into backup)
INFO: creating Proxmox Backup Server archive 'vm/102/2025-07-30T19:00:03Z'
ERROR: VM 102 qmp command 'backup' failed - backup connect failed: command error: Input/output error (os error 5)
INFO: aborting backup job
INFO: resuming VM again
ERROR: Backup of VM 102 failed - VM 102 qmp command 'backup' failed - backup connect failed: command error: Input/output error (os error 5)
INFO: Failed at 2025-07-30 21:00:03
INFO: Starting Backup of VM 204 (qemu)
INFO: Backup started at 2025-07-30 21:00:03
INFO: status = running
INFO: VM Name: test01wps
INFO: include disk 'scsi0' 'local-lvm:vm-204-disk-1' 100G
INFO: include disk 'efidisk0' 'local-lvm:vm-204-disk-0' 4M
INFO: backup mode: snapshot
INFO: ionice priority: 7
INFO: creating Proxmox Backup Server archive 'vm/204/2025-07-30T19:00:03Z'
INFO: issuing guest-agent 'fs-freeze' command
INFO: issuing guest-agent 'fs-thaw' command
ERROR: VM 204 qmp command 'backup' failed - backup connect failed: command error: Input/output error (os error 5)
INFO: aborting backup job
INFO: resuming VM again
ERROR: Backup of VM 204 failed - VM 204 qmp command 'backup' failed - backup connect failed: command error: Input/output error (os error 5)
INFO: Failed at 2025-07-30 21:00:07
INFO: Backup job finished with errors
INFO: notified via target `mail-to-root`
TASK ERROR: job errorsAfter that I created a test NFS Server on a Ubuntu test VM ... runs out of the box (used the same mount settings and so on).
So, I’d get rid of the Windows NFS server, but I can’t—it's a production Veeam Backup Server with a lot of unused storage that I’d like to use.
I'd appreciate any ideas or suggestions!
Last edited: