Hi Oscar,
checked the case, but it only has a single screenshot attachment - can you please upload exported product logs (you can attach them to the case via my.veeam.com). It is hard to guess what caused File-level recovery service outage there.
/Thanks!
Thanks for the logs, interesting reading. Cannot say for sure what causes it(I see some file system access errors) - so let's hear from support engineer!
Does that error pop at the start of the FLR Session? Or during file transfer?
Meanwhile, you can try extending default session timeout(30 mins) to something higher - let's say 2 hours - via registry key [HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Backup and Replication\InactiveFLRSessionTimeout] give it a value of "7200" and restart Veeam server or its VeeamBackup service(make sure no jobs are running!).
By the way, what is the source of FLR session? I see some physical cluster protected and it gives errors upon rescan with CNO not found...just wondering.