I saw the same problem once, in a system where there were some external nfs filesystems mounted and a lot of empty directories. The list of files to restore is built by your web browser, did you try different browsers?
If you can share (send me) the full list of files on your server we can help, but I understand that it will be hard.
But then the problem is only for NFS?
With CIFS sharing there is this problem?
We’re still talking about the corporate file server … thousands of files, a lot of nested directories.
I’ve found a new issue…trying to restore a complete folder. Restore complete without error on gui but if i check:
/var/log/restore-data.log:
2018-05-08 13:39:18 - ERROR - Restore failed, see /var/log/restore.log for details - 4864
2018-05-08 13:42:11 - ERROR - Restore failed, see /var/log/restore.log for details - 4864
/var/log/restore.log:
Local and Remote metadata are synchronized, no sync needed.
Last full backup date: Tue May 8 01:00:12 2018
–file-to-restore not found in archive - no files restored.
Local and Remote metadata are synchronized, no sync needed.
Last full backup date: Tue May 8 01:00:12 2018
The weird issue is that restored folder (and its content) are in place (i’ve also verified md5sum against original files to be sure) correctly.
It happens with booth “Restore files in the original path” or “Restore files in new directory” options.
I’ve also tried to restore folders with and without space in their name. Same bevahviour.