[Enhancement Request] FLR to continue (not die) on finding "corrupt" file / allow filesystem repair before FLR

[AlexHeylin]

Support case 05518045

Currently if FLR finds a "corrupt" file the FLR session dies, and if you're lucky it reports which file is corrupt. A new FLR session has to be run to restore everything up to that file, then another FLR session to restore everything after that file. This needs to be repeated for every "corrupt" file.

While cloud-connect-backup-f43/vbr-vaw-val-to ... 80878.html aims to ensure that the filesystem in the backups is good (or at least known to be bad), FLR should have an option to continue if it finds a "corrupt" file and provide a list of failed files at the end of the FLR job. I suggest that option should be enabled by default.

It might be that having FLR able to run filesystem repair on a virtual RW copy of the backup point might be a good way forward here as if many files are "corrupt", this might allow the filesystem repair to un"corrupt" them and then they'll become restorable. That would be better than FLR failing to restore those files and providing a list of them.

[HannesK]

Hello,
yes, I read the request in the other forum, makes sense yes

Best regards,
Hannes