https://login.veeam.com/en/oauth?client_id=nXojRrypJ8&redirect_uri=https%3A%2F%2Fwww.veeam.com%2Fservices%2Fauthentication%2Fredirect_url&response_type=code&scope=profile&state=eyJmaW5hbFJlZGlyZWN0TG9jYXRpb24iOiJodHRwczovL3d3dy52ZWVhbS5jb20va2IxNzkxIiwiaGFzaCI6ImU2ZGU2M2NmLTQ3M2EtNDU3Mi04NWEyLWVlYzQxODUzYjFjYiJ9
1-800-691-1991 | 9am - 8pm ET
EN

Incorrect Drive Letters – Windows FLR

Challenge

When performing a Windows FLR. the drive letters listed in the Backup Browser do not reflect those of the original server.

Cause

In version 6.5 of Veeam Backup & Replication, the drive letters listed in the Backup Browser are determined by reading the registry hive stored on the system drive. If the system drive is not backed up in the same backup job, other drives will not display with their drive letters as they are within the Guest OS of the VM. This occurs specifically if you backup a single drive of a VM, and that drive is not the system drive.
 
The following can be found in the VeeamShell.log after the FLR has launched the Backup Browser:
Error    Failed to set letters for mount points
Error    Unable to locate the VM's registry (System.Exception)
Error    Failed to detect drive letters for mount points.

Solution

In order for Veeam Backup & Replication to detect the drive letters as set within the Guest OS of the VM during the Windows FLR, the system disk must be backed up in the same restore point.

KB ID:
1791
Product:
Veeam Backup & Replication
Version:
6.5.0.x, 7.x
Published:
2013-07-09
Last Modified:
2020-08-13
Please rate how helpful this article was to you:
5 out of 5 based on 1 ratings
Thank you for helping us improve!
An error occurred during voting. Please try again later.

Couldn't find what you were looking for?

Below you can submit an idea for a new knowledge base article.
Report a typo on this page:

Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!

Spelling error in text

Knowledge base content request
By submitting, you agree that your personal data will be managed by Veeam in accordance with the Privacy Policy.
Your report was sent to the responsible team. Our representative will contact you by email you provided.
We're working on it please try again later