Operational Defect Database
BugZero found this defect 1098 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
Veeam | kb4166
Upgrading/Uninstalling Veeam Backup & Replication fails with "Error 1327. Invalid Drive: [a-z]:\" or "Warning 1327. Invalid Drive [a-z]:\"
Last update date:
11/12/2021
Affected products:
Veeam Backup & Replication
Affected releases:
11
Fixed releases:
No fixed releases provided.
Description:
Challenge
While upgrading or uninstalling Veeam Backup & Replication, the installer stops and displays either of the following messages:
Cause
The settings in the registry for one or both of the following services are targeting a drive location that no longer exists: Veeam Guest Catalog Service (VeeamCatalogSvc) Veeam vPower NFS Service (VeeamNFSSvc) The invalid registry entries often occur because during the initial installation of Veeam Backup & Replication a drive with a larger amount of free space than the C:\ drive was present. This is because the installer will detect which drive has the greatest free space and uses that for the above services. If that driver is later removed, the settings in the registry will still point to that drive. During the future upgrade process, when the upgrade installer attempts to check the existing configuration, it finds that it cannot access that drive location.
Solution
Check the following registry locations and values. Make sure the path in the registry targets a location that is available. Key: HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Veeam\Veeam NFS Value Name: RootFolder Default Path: C:\ProgramData\Veeam\Backup\IRCache\ Key: HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Backup Catalog Value Name: CatalogPath Default Path: C:\VBRCatalog The above "Default" paths shown are what would have been selected if there was no other drive on the Veeam server during the initial install.
More Information
How to move the VBRCatalog: https://www.veeam.com/kb1453 The IRCache location is controlled within Veeam Backup & Replication by the mount server setting within a repository using the Veeam server as the Mount server.
