About Operation 「Restore from FAT, NTFS or ReFS」

[east-climb]

[Question 1]
In veeam v9.5 update4, it says in step 3 to create a second mount point for file level restore.
[Reference source](https://helpcenter.veeam.com/archive/ba ... ndows.html)

It say that this reduces the load on the network, but why does it reduce the load on the network?
I don't see any reason to create an additional mount point when it has already been mounted on the mount server by the first process.


[Question 2]
In Veeam v10, the sentence above about creating a second mount point is gone.
[Reference source](https://helpcenter.veeam.com/docs/backu ... ml?ver=100)

Is the specification to create a second mount point gone?

[Andreas Neufert]

v10 just works differently.
In the old days we always mounted the data to the B&R Server which was as well the Console.
Then we introduced the mount server and console. We mounted the data once to the Console to list the data, and then we mounted the data to the mount server to transport from there the data to the VM. The idea was that you could have the console not on the same site and the traffic stays locally (mount server on same site).
This was fruther optimized by always mouting the data to the mount server and the console server remotely interacting with the mount server to get the tree list.

[east-climb]

I see.

In order to making efficient the traffic for the mount、
the component to be mounted (the mount server)　is placed near the repository.

Thanks for answering.