Identifying and solving file restore sessions that takes a long time to mount

[KaptenP]

Hello

We got some complaints from our technicans that the process of mounting the restore session during Guest file restore, takes a very long time for some particular large VMs with many disks.
For one of the VMs it will take about 1,5 hours and for one particular VM it will take at least 3 hours or more.
This sometimes results in the technicians believing that the mount process hangs and will not finish.

We need to find a way to identify the servers, where the mounting process during the Guest file restore takes a long time to finish and also speed up this process.
We are unsure how many servers that are affected at this moment, but as mentioned there is a correlation with servers being large and/or have many disks being backed up.
For some backup jobs we run forever incremental and we think that the backup chain might becomes fragmented after a long time, and that we might have to run a new full backup for this to be resolved.
However, we are not sure and would like to find out if anyone else have faced the same problem and what the recommended solution for this problem is.

Any advice would be appreciated.
Thanks in advance!

[veremin]

This type of issue cannot be investigated over forum posts. So I recommend you collecting the debug logs and providing them to the support team. The engineers will be able to identify the cause of slow mount process and propose potential solutions.

Thanks!

[foggy]

I'd check to which server the backup is mounted - take a look if the mount server on the same location is configured for the repository. Otherwise, the mount traffic is traversing the remote connection.

[KaptenP]

Thank you for your replies.

We have controlled and confirmed that the mount server is configured and pointing to the repository where the backup data resides.

Just to make myself clear - We are unsure if there are more VMs that could take a long time to mount while doing a file restore.
Do you have any suggestion to finding the VMs where the file restore could take a long time to mount?

For example, using the Powershell CmdLet Start-VBRWindowsFileRestore, would it be possible to create and run a script where we start restore sessions for a couple VMs at a time in batches and gather the time the mounting process takes for each VM? And through this process identify the VMs we need to fix to minimize the time it takes to mount.
Or is there another way to identify the servers where this process takes a long time before technicans encounters the problem?
If there is no other way than creating a case to the Veeam support we will do so, just checking here before doing so.

Thanks in advance.

[foggy]

Logs should tell what operations take long and likely why so opening a case is preferred. Thanks!