DanQcCa wrote:My only option will be to restore VM hard disks, add it to a VM and take the file i need. Not tested...
tsightler wrote:In my testing I was able to simply use Windows Explorer instead of the Veeam File Browser to restore the file. I just tested this by created a very long/deep path. I then started the normal "Guest Files (Windows)" restore wizard and browsed to the file which caused the Veeam File Browser to error with the message noted above. At this point I opened Windows Explorer (while leaving the Veeam File Browser up) so that I could browse to C:\VeeamFLR\<servername>\<volume#\<biglongpath> and was able to copy the files out just fine. Have you tried this?
BigMacNix wrote:It is fixed in the new version 7?
Gostev wrote:This specific issue very long name file name issues should be addressed in 7.0...
By the way, the latest product version is 6.5, and I do recommend that you upgrade.
6.5 had some enhancements around file level recovery, in case your issue is different.
Users browsing this forum: Google Feedfetcher, ivansiu and 1 guest