Feature Request: Registry Entry for the Mounter-Service

[TheOnlyWizard17]

Create a Registry Entry for the Mounter-Service that allows you to change the folder where it will try to mount a File Level Restore. Now it seems to be hard coded to do that in C:\Windows\Temp.
If, for some reason, like we do, change C:\Windows\Temp into a reparsepoint to redirect it to somwhere else, Veeam mounting will fail with the error: Mount Failed. Mounter is in "Failed" state...
Having a Registry Entry to be able to simply change this hardcoded default to something else would allow it to continue working, even in the above case...
Im actually surprised about this hard coded one, since most folders used by Veeam can be customised, just this one not, so it seems...

[foggy]

Hi Bart, we've looked a bit into this and the path is actually not hard-coded (at least not in the mount service code). We'll continue investigating but it will help if you could open a case and provide logs for review. Thanks!

[TheOnlyWizard17]

I did. Please reference case 01974731. It also includes logs.

[dcampregher]

Hi!

I'm having the error "Failed to mount files: Mounter is in 'failed' state (see agent log for more details)". Do you resolve the issue in your environment ?

[Mike Resseler]

Hi Diogo,

Are you doing this from Enterprise Manager or straight from VBR?

Mostly this could mean two things... Not sufficient disk space or permission issues.

[dcampregher]

Hello Mike.

From VBR, in the backup server and on other server with the console instalei.

There is a lot of free space and the user is local admin of the server, but not the Domain.

[Mike Resseler]

Diogo,

Then I am afraid logs will need to get investigated to see what is going on. Please create a support case and post the support case ID here (and the outcome after investigation of our engineers)

Thanks
Mike

[dcampregher]

The case is 03252448.

[22.10.2018 15:38:28] < 6988> drv| ERR |Failed to attach volume [C:\] to filter. HRESULT=0x801f000f

This message os present in the logs.

[dcampregher]

Mike,

Even after include the user in the Domain Admins, the error happen.

Checking the User Rights Assignments in the local policy of the veeam server, i see that the "Logon as a Server" is managed by the Default Domain Policy and can't changed by the logged user.

I try to install other Veeam Backup Server in a VM out of domain and the installation created many entries in the "Logon as a service" policy, and all works fine.

I think that the installation was unable to change the "Logon as a service" on the server joined in the domain and because this the FLR is failling. What you think about this ?

[Mike Resseler]

Not sure to be honest. I wonder why the logon as a service policy is blocked in the first place. Hopefully support can get you a bit further, but as I said. Logon as a service is something that is used with a lot of solutions and I wonder how the company has arranged it for other solutions

[dcampregher]

Hello Mike!

After a lot of tests. The only way to do the FLR to work was:

Install and configure the entire VBR in the server "without the SCSI Controller and disks to the repository". If i install the VBR in the server with the SCSI controller and disks present, the FLR fails with "Mounter is in 'failed' state".

I never see this behavior and all my installations. This make sense for you ?

[Mike Resseler]

Not even close. Are you sure you don't want to let support look at it?