This is really small and niche case, but gave pretty bad UX. Even I have to admit that this problem is 100% caused by invalid user error.
Restores files to instead of their original destination.
Top folders are removed if possible.
The restore-path value and user rights are only confirmed when actual restore starts. In my case, it took about two weeks to get the error, that the restore-path is invalid. That’s quite annoying, because the intermediate work wasn’t saved, and it took extra two weeks to get the restore to run with correct path.
Sure, any smart admin, would make sure that the path is right in that case, as well as write permissions are set correctly. Or even test restore with limited data set. But if we acknowledge the fact that users are sloppy and stupid (as I am), it would be possible to provide better UX by checking the restore path viability earlier in the process.