No disks have been mounted…Windows FLR

When attempting to perform a Windows FLR (Guest Files ‘Windows’) the restore fails with:



No disks have been mounted. Either disks of this type aren’t supported or some errors occurred. See log file for details.

Confirm that the VM that the files are being restored from was using one the following filesystems.        

• FAT
• FAT32
• NTFS
• ReFS*

 ──────────────────────────────────────────────────────────
Troubleshooting Steps
──────────────────────────────────────────────────────────
 
1.  Clear all temporary files from “C:\Users\<serviceaccount>\AppData\Local\Temp\”

Note: When the Veeam Backup Service account is ‘local system’, the temporary directory used is C:\Windows\Temp.

2.  Open an Administrator Command Prompt and run the following commands: 3.  Confirm that the account being used for the Veeam Backup Service has the "Perform volume maintenance tasks" right assigned to it. This can be located within the group policy (gpedit.msc) under: 4.  Reboot the Veeam server

 

To restore files from a VM running Microsoft Windows ReFS 3.x, the console and mount server must be installed on machines running Microsoft Windows Server 2016.

To support restore of files from a VM running Microsoft Windows ReFS 2.0 or earlier the console and mount server must be installed on machines running Server 2012/Server 2012 R2.

If the server you are attempting to restore from has volumes with native 2012 data deduplication, the Veeam console and mount server must be installed on the same operating system and also have the “Data Deduplication” role enabled. The “Data Deduplication” role appears under "File and ISCSi Services" in server manager.

If the Windows FLR continues to fail after attempting the steps outlined in this KB, please attempt and Other-OS FLR. For more information regarding how to do that please review the following:

http://helpcenter.veeam.com/backup/70/vsphere/multios_restore_intro.html