Linux File Level Restore

[tsightler]

We are evaluating Veeam to replace our existing solution. One of the most enticing features for us is the ability to do file level restores to a Linux system, however, in testing we've run into a couple of problems. The biggest issue seems to be that the only way to restore such files is to restore them to a Window filesystem first. This causes problem because linux and windows have different restrictions on valid characters and path lengths. Out very first restore attempt failed because one of the files included a character that is invalid in a Windows filename and thus those files cannot be restored, any attempt to restore them produced an error.

The other major issue is that restored files loose all attributes as in, creation and modified date, permissions, owner, etc. The file restore windows shows the correct information, but the restored files all have the current date and time and generic permissions. This particular issue is not a show stopper or anything, but I suspect that information is correct within the Linux VM environment. What would be really nice is if the restore environment simply provided shell access to the actual files and perhaps sftp or rsync. That way you could just easily restore the files directly to the linux host.

Is there any other method of directly access the Linux files and restoring them directly to the Linux host which might work around these issues?

Thanks,
Tom

[Gostev]

Tom, to make it a little easier, you can add your Linux VM into Veeam Backup tree and use our built-in file management to copy the restored file backup from Veeam Backup server back to your VM.

As for the issues you have mentioned above, we actually plan to address both of these in the Veeam Backup 4.0 release. We had quite a few customers asking us about this functionality since 3.0 release...

Thank you.

[tsightler]

Right, I know how to add the host to Veeam, but this does not appear to be an available target for a file level restore. You have to restore to the local Windows system, or a share, first. This causes files where the filename contains characters that are invalid in Windows to be unrestorable.

Good to know there will continue to be enhacements to this feature going forward.

Thanks,
Tom