I am backing up to a REMOTE NFS share I had previously configured. It was working fine. It stopped working for some reason. The remote is on a TrueNAS Scale box. The only thing I did was add a sub folder within the original vmbackup folder for acronis to store backups in. I tried removing the NFS share and recreating it as it's own folder with no sub folders. Still rejecting connection. This is the log file after the recreation of the new NFS share. Any insight would be great. Thanks.
remote.test
{
"id": "80bb9ed6-e221-44b3-8cee-e54a1d48a1d4"
}
{
"shortMessage": "Command failed with exit code 32: mount -o -t nfs 10.0.0.102:/mnt/strong-house/xobackups /run/xo-server/mounts/80bb9ed6-e221-44b3-8cee-e54a1d48a1d4",
"command": "mount -o -t nfs 10.0.0.102:/mnt/strong-house/xobackups /run/xo-server/mounts/80bb9ed6-e221-44b3-8cee-e54a1d48a1d4",
"escapedCommand": "mount -o \"\" -t nfs \"10.0.0.102:/mnt/strong-house/xobackups\" \"/run/xo-server/mounts/80bb9ed6-e221-44b3-8cee-e54a1d48a1d4\"",
"exitCode": 32,
"stdout": "",
"stderr": "mount.nfs: Protocol not supported",
"failed": true,
"timedOut": false,
"isCanceled": false,
"killed": false,
"message": "Command failed with exit code 32: mount -o -t nfs 10.0.0.102:/mnt/strong-house/xobackups /run/xo-server/mounts/80bb9ed6-e221-44b3-8cee-e54a1d48a1d4
mount.nfs: Protocol not supported",
"name": "Error",
"stack": "Error: Command failed with exit code 32: mount -o -t nfs 10.0.0.102:/mnt/strong-house/xobackups /run/xo-server/mounts/80bb9ed6-e221-44b3-8cee-e54a1d48a1d4
mount.nfs: Protocol not supported
at makeError (/opt/xen-orchestra/node_modules/execa/lib/error.js:60:11)
at handlePromise (/opt/xen-orchestra/node_modules/execa/index.js:118:26)
at NfsHandler._sync (/opt/xen-orchestra/@xen-orchestra/fs/src/_mount.js:68:7)"
}
Not sure why it would say Protocol not supported.
I have another NFS share that holds my ISO's that is setup the same and works fine.
XCP-ng 8.3 running on a SuperMicro Server