Hi,

Thanks to all for the information you shared.
We are currently testing a fix for the VDI_NOT_IN_MAP error.

The fix should be released for the next update.
So feel free to test and tell us if it fixed the problem.

Device: \\1.2.3.4.:Port:/backupVM
Options: vers=4,nconnect=16,noauto,x-systemd.automount,x-systemd.device-timeout=10,x-systemd.idle-timeout=1min

I tried mounting and backing up with the same settings and didn't notice anything special. The changes in the update only concerned the case where a port number was entered.

The NFS mount is done correctly and the error only occurs at the time of backup, is that it?

@Tristis-Oris said in The "paths[1]" argument must be of type string. Received undefined:

@xen-orchestra/fs/dist/abstract.js:412

Hi @Tristis-Oris

Can you show the settings you used for your NFS mount?

Is it PV, HVM or a PVHVM VM?
Health Check can't work on HVM because there are no tools.

@djingo As said before, we will work on improving error handling to better identify specific issues with some users' NFS servers.

Unfortunately, we cannot reproduce the exact configuration of each user.

@olivierlambert No, in the code we only check for non-hidden files, and @djingo checked that the directory was totally empty.

@djingo said in NFS Remote encryption problem:

"/mnt/disk3" -fsid=87,async,no_subtree_check 192.168.100.0/24(sec=sys,rw,no_root_squash,insecure) *(sec=sys,ro,insecure,anongid=100,anonuid=99,all_squash)

Thank you.
By reusing the same NFS config that fails on your server, I unfortunately could not reproduce the problem.
The only case where I saw the same error was when the shared directory already contained files, but you told me that was not your case.

We will work on improving error handling to better identify NFS server-specific problems.

@djingo Can you share your NFS config file (/etc/exports) ?

@djingo Do you have any error logs on the unraid server side?

@djingo

It seems the problem happens when the directory shared contains non-hidden files.
Can you try to add a NFS remote with encryption on an new empty directory, and let us know if it works?

This is not specified, but the encrypted remote must not contain encrypted and unencrypted file, as they may conflict.
We should add this information.

@djingo said in NFS Remote encryption problem:

@stephane-m-dev the path exists but it was empty.

The problem doesn't happen on our enterprise NFS server with encryption.

But I tested on a freshly installed personal NFS server, and I get the same error as you if I use encryption.

We are investigating and will keep you informed.

@djingo said in NFS Remote encryption problem:

"message": "ENOENT: no such file or directory, open '/run/xo-server/mounts/e782c43e-2ac7-472c-...etc.../metadata.json'"

Hi,

Can you see if the specified path and file exist?

Hi McHenry,

After the initial full backup, the system stores only the incremental changes (deltas) at the frequency defined.

If you’ve set up multiple schedules within the same job (hourly, daily, weekly, monthly), it doesn't mean each schedule gets its own full backup.