Veeam FLR on Hyper-V sometimes fails, sometimes not ...

[Didi7]

Hi guys,

in one of our environments we are using a virtual VBR-server v10 P1 running under Windows Server 2016 v1607 Build 3659 with 4GB of RAM, currently 6GB of RAM. Trying to restore guest files by selecting a Windows VM and choosing its restore points from Backups/Disk opens the FLR dialog, we can choose a restore point and finish the dialog by starting the restore and the Backup Browser opens.

Within the Backup Browser, we can see the drives but in rare cases we see the contents of the drive. Now we mostly get the error 'Failed to load content of the folder' and in the History we get errors like ...

Exception of type 'Veeam.Backup.AgentProvider.AgentClosedException' was thrown.

I tried to deactivate the IPv6 protocol and increased the amount of RAM, but I still have problems.

I accessed the FLR Backup Browser for all VMs before we updated to VBR v10 P1 as well and I got no errors iirc, even with 4GB of RAM and IPv6 enabled.

Maybe the Cumulative Patch KB3127 introduced the problem?

Anyone might have an idea how to further investigate the problem?

Regards,
Didi7

[Egor Yakovlev]

Hi Didi7,
it is hard to say without support logs bundle. Please open the case and share it's number here.

p.s. meanwhile try to add antivirus exclusions, as each update brings new components versions which AV software might not like in the first place.
/Cheers!

[Didi7]

Hi,

imho something has changed regarding the C:\VeeamFLR directory in VBR v10.

In VBR 9.5 U4b opening a restore point of a selected VM in the Backup Browser instantly created a subdirectory in C:\VeeamFLR beginning with the name of the selected VM (at least when selecting a VMware VM).

In VBR 10 P1 (working in a Hyper-V environment) opening a VM in the Restore Backup Browser does not create a subdirectory in C:\VeeamFLR as long as you do not select the new smart button 'Mount to console', which is new in v10 or v10 P1.

Selecting 'Mount to console' makes the contents of all drives of the selected VM available under C:\VeeamFLR\ and the instantly created subdirectory.

In the Backup Browser the drive contents is still unavailable and you get the error 'Failed to load content of the folder'.

Is this a new bug?

Regards,
Didi7

[Egor Yakovlev]

It is a feature by default backup is mounted on Repository's set Mount Server(check Repository settings) and C:\VeeamFLR instantly appears there. When you click "Mount to console" it re-mounts backups locally on a machine with Veeam console. So yes, I guess it might be a communication issue. Worth checking required ports for Console mounts.
/Cheers!

[Didi7]

Hi Egor,

you know, we created a Hyper-V VM with only a C:\ drive and attached a repository, which is located on the Hyper-V host. In the corresponding repository settings the mount server was also the Hyper-V host (by default), as the repository path was set to a path on the Hyper-V host and not locally to the VBR server. In this case there seems to be some communication problem between the virtual Hyper-V VBR server and the Hyper-V host itself, though sometimes it worked.

Nevertheless, I decided to set the mount server in the repository settings to the local VBR server and now problems have gone and the mountpoint is instantly created on the virtual VBR server in C:\VeeamFLR.

Thanks for the hint.

Regards,
Didi7

[Egor Yakovlev]

Great to hear it worked. Thanks for update too!
Glad to help.
/Cheers!