Error when restore guest file VBR 12.3.1.1139 - backup not opened agent failed to process method {mount.queryanmlabelsonmounteddevice}

Hi All,

 

when i tried to restore guess file , i faced an error like this below,

 

could you please help ?

Hi ​@rasyid nurdiansyah 

Backup not opened. Agent failed to process method {Mount.QueryAsmLabelsOnMountedDevice}
2️⃣ Failed to mount backup.

These typically appear in Veeam Backup & Replication when trying to do a Guest File Restore and the mount server fails to attach the backup data as a virtual disk.

what type of file level restore are you performing? From Windows or Linux?

Check the mount server and verify the correct TCP port connectivity between the mount server and the backup repository/proxy.

Ports - User Guide for VMware vSphere

failing of mounting could be permission issue as well

what kind of user do you?

which server do you used as FLR appliance?

Hi ​@rasyid nurdiansyah ,

I would also go on with checking network and firewall configuration.

My Plan would be something liek this: 

1. Ensure the target machine is reachable over the network and that the network path to the backup repository is accessible.

2. Verify that firewalls are not blocking communication between the Veeam server and the target machine, particularly on the dynamic RPC port range (49152-65535). 

3. Use Test-NetConnection to check if the target machine is reachable on the necessary ports (135 for RPC, then the dynamic range if needed). 
4. Ensure that the Remote Procedure Call (RPC) and DCOM Server Process Launcher services are running and configured to start automatically on both the Veeam server and the target machine.

Hello,
Please share with us the error logs located at the following path:

C:\ProgramData\Veeam\Backup\FLR\<SessionName>\
C:\ProgramData\Veeam\Backup\<JobName>\
 

This type of error usually occurs during a Guest File Restore when the mount server fails to attach the backup data as a virtual disk.

I recommend checking if all Veeam services are running — especially the Veeam Mount Service. If necessary, try restarting this service. It might also help to test the restore process using a different mount server.

Sorry to be a wet-blanket, but strongly recommend a Veeam Support case on this one: https://veeam.com/kb1771

> QueryAsmLabelsOnMountedDevice

Looks to me like at least the disk got attached to mount server, but something failed as we tried to understand what type of disk it was, etc. 

Could be _many_ reasons for this, but logs will tell a lot more and a lot faster. 

A good isolation test, agreed. Reboot isn’t bad idea either but I don’t anticipate it will help personally, but who knows maybe.

You can use the vm from which you are trying to restore the files as a Mount server, in this case you will need to add it as Managed server and specify it as a Mount server in repository settings, from which you are restoring. If it works, as the Mount server will have the same file system and the files we are trying to mount, you will need to review your Mount servers, to make sure system requirements are met for different type of workloads, REFS, NTFS, windows deduplication enabled and so forth