Loading...
Loading...
When performing a Windows FLR. the drive letters listed in the Backup Browser do not reflect those of the original server.
This occurs when the drive containing the Guest OS registry hives was not included in the backup process. The registry hive is used to map disk IDs to drive letters. The Svc.VeeamMount.log will contain the entry: Error (1) Failed to get windows version of mounted backup. MountId: [guid] Error (1) Hive [System] file was not found. (System.Exception)SYSTEM registry hive was not found on any of mounted disks.
To resolve this issue, the registry of the VM's Guest OS that is backed up must be included in the restore point. The default location of the registry is: C:\Windows\System32\config\
In a previous iteration of this KB article, the guidance was to resolve this issue by including only the SYSTEM registry hive file, C:\Windows\System32\config\SYSTEM. However, starting in Veeam Backup & Replication 13, all registry hives must be included; hence, the current recommendation is to include the entire C:\Windows\System32\config\ folder. Jobs that were configured according to previous guidance will display the following error during Guest Files Restore: Failed to call RPC function 'RegAttachHiveFile': The configuration registry database is corrupt. Failed to call RegLoadKey function. or The configuration registry database is corrupt.
Veeam Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.