Comprehensive data protection for all workloads
Post Reply
Erwin Linker
Service Provider
Posts: 80
Liked: 8 times
Joined: Mar 30, 2016 12:58 pm
Full Name: Erwin Linker
Location: The Netherlands
Contact:

Enterprise Manager File-Restore

Post by Erwin Linker »

Hi All,

Some times when we do al file-level restore from the Veeam Enterprise Manager we get a error message in gui that says "Failed to pack restored files".

When i look in the logging Svc.VeeamBES i see the following messages:

Code: Select all

[01.02.2024 10:08:10.844]    <31>   Error (3)    Cannot delete temp directory. Path: [D:\Temp\vbr_a5422017]
[01.02.2024 10:08:10.844]    <31>   Error (3)    Access is denied (System.UnauthorizedAccessException)
[01.02.2024 10:08:10.844]    <31>   Error (3)       at Veeam.Backup.Common.LongPathFileInfo.Delete(String longPath)
[01.02.2024 10:08:10.844]    <31>   Error (3)       at Veeam.Backup.Common.LongPathDirectoryInfo.Delete(String path, Boolean removeReadOnlyAttribute)
[01.02.2024 10:08:10.844]    <31>   Error (3)       at Veeam.Backup.Common.LongPathDirectoryInfo.Delete(String path, Boolean removeReadOnlyAttribute)
[01.02.2024 10:08:10.844]    <31>   Error (3)       at Veeam.Backup.Enterprise.Core.CTmpFolder.Dispose()
[01.02.2024 10:08:10.844]    <31>   Error (3)    Failed to zip folder 'D:\Temp\vbr_a5422017' to file 'D:\WebRestore\FLR_20240201_083624.zip' (System.Exception)
[01.02.2024 10:08:10.844]    <31>   Error (3)       at Veeam.Backup.Enterprise.Core.CFLRestoreHelper.ZipFolder(String folderPath, String zipFilePath)
[01.02.2024 10:08:10.844]    <31>   Error (3)       at Veeam.Backup.Enterprise.Core.CFileLevelRestorer.CompleteRestore(CFileRestoreDbSession restoreDbSession, CFlrRestoreTaskLogBuilder logBuilderOrNull)
[01.02.2024 10:08:10.844]    <31>   Error (3)    The system cannot find the path specified (System.ComponentModel.Win32Exception)
[01.02.2024 10:08:10.844]    <31>   Error (3)       at Veeam.Backup.Common.WinAPIWrappers.NativeFile.Open(String path, FileMode mode, FileAccessProvider access, FileShare share, NativeFileAttributes attributes)
[01.02.2024 10:08:10.844]    <31>   Error (3)       at Veeam.Backup.Common.LongPathFileSystemInfo.GetLastWriteTime()
[01.02.2024 10:08:10.844]    <31>   Error (3)       at Veeam.Backup.Enterprise.Core.CFLRestoreHelper.ZipFolderRecursive(ZipArchive zipArchive, LongPathDirectoryInfo directory, LongPathDirectoryInfo rootDirectory)
[01.02.2024 10:08:10.844]    <31>   Error (3)       at Veeam.Backup.Enterprise.Core.CFLRestoreHelper.ZipFolderRecursive(ZipArchive zipArchive, LongPathDirectoryInfo directory, LongPathDirectoryInfo rootDirectory)
[01.02.2024 10:08:10.844]    <31>   Error (3)       at Veeam.Backup.Enterprise.Core.CFLRestoreHelper.ZipFolderRecursive(ZipArchive zipArchive, LongPathDirectoryInfo directory, LongPathDirectoryInfo rootDirectory)
[01.02.2024 10:08:10.844]    <31>   Error (3)       at Veeam.Backup.Enterprise.Core.CFLRestoreHelper.ZipFolder(String folderPath, String zipFilePath)
The problem lies in the combination of windowszip and long file paths.

Is there a option to not use the default windowszip tool but a tool like winrar? Because when i do a manual restore and zip the files with winrar it works.

Regards,
Erwin
Mildur
Product Manager
Posts: 8735
Liked: 2294 times
Joined: May 13, 2017 4:51 pm
Full Name: Fabian K.
Location: Switzerland
Contact:

Re: Enterprise Manager File-Restore

Post by Mildur »

Hi Erwin

I don't see a registry key or configuration parameter to change the default packing tool.
Instead of finding workarounds, I strongly suggest to open a support case and find the root cause of the issue.
Please provide me with the case number so I can follow the case form my side.

Best,
Fabian
Product Management Analyst @ Veeam Software
Erwin Linker
Service Provider
Posts: 80
Liked: 8 times
Joined: Mar 30, 2016 12:58 pm
Full Name: Erwin Linker
Location: The Netherlands
Contact:

Re: Enterprise Manager File-Restore

Post by Erwin Linker »

Hi Fabian,

I had a case with caseid Case #07111362. The case is closed because the file limit of windows is 255 characters was the problem.
I don't want a workaround, but a proper solution :-).

Regards,
Erwin
Post Reply

Who is online

Users browsing this forum: Semrush [Bot] and 123 guests