Veeam on 2016 can't mount REFS volumes at FLR

[mrholm]

Hi
All our Veeam servers are on windows 2016 and the backuped VM (that we try to do FLR from) are also on windows 2016. The D: drive on the VM is formatted with Refs and according to Veeam Mount log at restore the volume is a Refs 3.4 version.

5/27/2020 2:20:53 PM Warning Failed to mount volume C:\VeeamFLR\servernam_44326e93\Volume2 Error: Failed to call RPC function 'FcCheckFilesystemIsAccessible': The volume does not contain a recognized file system. Please make sure that all required file system drivers are loaded and that the volume is not corrupted.

Refs.sys at mount server is 10.0.14393.3471 and on the backuped VM are on 10.0.17763.1192

According to: veeam-agent-for-windows-f33/bsod-pnp-de ... 64833.html the only workaround now is to have a Veeam server on windows 2019 (1809).
Is it possible to upgrade the Refs drivers on Windows 2016 servers instead?

//Mats

[Andreas Neufert]

The build number of the backed up VM is from April 21st windows update. So I think updating backup & replication server windows will help you.

You can try by installing a new windows server and update it. Then use it temporary as mount server for the Repository and potentially run the Veeam console from there as well (needed for older Veeam versions).

If it works you can apply the same update in your environment.

[mrholm]

Hi Andreas and other
We installed windows 2019 (1809) on a new server and it got the refs.sys with version 10.0.17763.1131.
We installed VBR console and the FLR works fine.

[stace]

I am have this same error message. In the comments, a new 2019 server was built. Does the VBR server need to be configured that way to work or can I use a proxy as the mount server built on 2019 and drive with ReFS? Thank you.

[HannesK]

Hello,
and welcome to the forums.

Yes, you can configure a proxy as mount server. Just select it in the dropdown menu: https://helpcenter.veeam.com/docs/backu ... ml?ver=110

Best regards,
Hannes

[stace]

Thank you Hannes, I have tried to restore a file from Exchange and have been getting the same error above. Exch Servers are built on 2016 w/ ReFS drive. I have a new proxy 2019 with a ReFS drive but still getting this same error. Will VBR server built on 2012 R2 also need to be built on 2016 or higher OS with ReFS? Thank you!

[HannesK]

Hello,
it's always a good idea to have the VBR server at the latest Windows version to avoid issues like you describe them.

Which VBR version do you use? At least V10 is required for my suggestion above.

Other option: install the console on the Server 2019 proxy and restore from there

Best regards,
Hannes