Hi Juliano Gustavo Becker, and thx for using Q&A,
when you initiate the recovery, try selecting a different drive letter for the recovery volume. instead of letting it auto assign to F:\, manually choose a letter that is far down the alphabet and not in use, like Z:\. sometimes there is a conflict with existing drive mappings or security software that locks specific letters.
pls, check the permissions on the machine where you are running the mars agent. the account you are using to perform the recovery needs full administrative privileges. right click on the mars agent console and select 'run as administrator' to ensure it has the highest level of access.
another common culprit is antivirus or endpoint security software. these programs can sometimes intercept and block the mounting of new volumes from backup services. try temporarily disabling your antivirus real time protection before starting the recovery process and see if the mount succeeds.
if the problem persists, you can try an alternative recovery method. instead of using the 'file recovery' option that mounts a volume, use the 'instant recovery' option if your backup is of an azure vm, or restore the files directly to an alternative location like a network share or a different local drive.
this kind of mounting issue is often environment specific and tied to the local windows machine's configuration rather than a problem with azure backup itself.
so, try using a different, unused drive letter, run the mars agent as an administrator, and temporarily disable antivirus software to see if the volume mounts correctly.
rgds,
Alex