Hi ​@davidbe2,

No need to apologize, technology can sometimes be very complex and it might be difficult to find the actual focus you are looking for. 

You should be good with these two articles:

Restore from Linux, Unix and Other File Systems - User Guide for VMware vSphere

(this one is more explaning in general)

Restoring from Linux, Unix and Other File Systems - Quick Start Guide for VMware vSphere

(this one guides you through the process)

Basically for Linux and Unix it is all about the helper host. This is a component that the backup files are mounted to prior restoring it to the destination VM. The first article describes it with more details.

In case the process gets hung maybe you should try rebooting your VBR server (and other Veeam component systems that might be involved) and maybe also your target (production) VM in case that is possible.

Otherwise I suggest that you open a Veeam support call.

Good luck and take care!

Lukas

Looked through both previously.  Still unsure exactly what talks to what.  One thing I did see is about “/tmp” being mounted with “exec”.  This is not allowed in our environment for security reasons, so I may need to find a workaround.  Such as if there is somewhere in Veeam to tell it to use a different temporary location.

Got further with “https://www.veeam.com/kb2099”.  While it still fails, it fails on the actual restore now.  It still to uses /tmp for some things, but uses the folder in the key to run the restore.  Looks like I may still need a firewall hole for the restore.  It does mount the backup, but appears to fail for port 2501

That last port change was it.  Except for now it still wants to fill up /tmp beyond it’s capacity when restoring a large file.  And with really small ones, it says it restores, but it doesn’t. Enough for today. revisit tomorrow.

​@davidbe2 you can check the HOL to try to figure out some configuration, comparing  with your environment.

During the HOL session, you can press F1, the help page is context base, I’m saying that because you mention the is difficult to find information, that is the easiest way in my opinion.

https://propartner.veeam.com/hands-on-labs/

https://go.veeam.com/hands-on-lab-experience

I’ll give HOL a shot.  But for now, would just like to know how to keep Veeam from filling up /tmp when doing a large file restore. (file being restored is larger than the amount of free space in /tmp)  Those two registry keeps don’t see to have anything to do with where Veeam puts those before actually restoring to the proper location.

I’ve Google’d endlessly

Have you opened a Veeam Support case already? Maybe this is another approach to get some detailled information.

No, but is likely my next step

Maybe you can share the result with this post to let us know! 

Are you using helper appliance or helper host during the IFLR restore?

you can try to instant disk recovery and from there, get the files thart you need

You can also try publish disk or restore virtual disk as workarround

Restoring directly to the system.  I can get to the files, as they are mounted on the system being restored to, and can use standard Linux tools to copy them to where they need to be, so I have a kludgy workaround. I’ll just wait and see what support has to say. Looked through the logs, and don’t see any errors.

It actually looks like it is restoring it to the mounted backup image, instead of the server it should be restoring it to.