Start-VBRWindowsFileRestore Volume Mappings

[AndyH]

When Start-VBRWindowsFileRestore is run in a script, it obviously maps the different VM drives to folders in C:\VeeamFLR, using Volume0, Volume1 etc. The problem I have is that these mappings are not consistent from restore point to restore point of a single VM. On some restore points Volume1 will contain the files from D: and on others the contents of E:. This is causing me a big headache, as I am having to mount each restore point prior to running a script and check the volume contents.

In your examples, you reference $result.MountSession.MountedDevices as a source for these mappings, but that function is no longer available. Is there an alternative for this, without writing more code to compare the contents of the volumes to known folder names within the volumes?

[veremin]

We will investigate the situation internally and update the topic, once more information is available. Thanks!

[veremin]

The parameter was removed almost three years ago. Try MountPoint or Drives parameters instead. Thanks!